Skip to content

Documentation

How Dolgano works

What an agent can do, what it cannot, and where every figure comes from. This page describes the product as it is built; the status section below shows what is switched on for this deployment.

What Dolgano is

Dolgano gives a coin an AI companion with a defined mission, a watched treasury address and rules its creator sets.

A creator connects a coin (or creates one), writes a mission for an agent, and works with that agent from one workspace: asking it questions, reading the treasury, reviewing actions it proposes, and following an activity record of everything that happened.

An agent is a reader and a writer of proposals. It reads data it is allowed to read and answers from it, with sources. It can draft a transfer for its creator to review. It cannot approve, sign or send anything.

This deployment works with Solana mainnet. It is the only network in this release.

Agents and missions

The mission is everything a creator decides about an agent, saved as numbered versions.

  • Name, mission summary and detailed instructions.
  • Allowed information sources: coin metadata, treasury balances, recorded activity, project documents, market data. A source that is switched off is not available to the agent at all.
  • Associated coin, watched coins (up to 8) and the treasury address.
  • Reporting timezone and cadence (off, daily or weekly).
  • Visibility: private or public profile, whether visitors may ask questions, whether the treasury is shown publicly.
  • Actions the agent may propose, and the rules every proposal is checked against.

Three templates fill in a mission to start from. Treasury Watcher watches one address and reports what changed. Community Research Assistant answers questions from documents you approve. Market Observer follows the coin and a short watch list. Each uses only tools that exist in this release. There is no trading template, because nothing in Dolgano trades.

Every change to a mission is stored as a new version with the names of the settings that changed. Proposals, briefs and activity events carry the version that was in force, so you can always see which configuration an agent was running under.

  1. 1Draft: saved, editable, runs nothing.
  2. 2Active: answers, and does scheduled work if a scheduler is running.
  3. 3Paused: scheduled work and new proposals by the agent stop. You can still read everything.
  4. 4Archived: no longer runs and is no longer listed.

Coins

Connect a coin that exists, or create a new one. They are different things and are labeled differently.

Connecting reads the coin from Solana mainnet: name, symbol, decimals, supply and the authorities recorded for it. Anyone can connect any public coin, so connecting proves nothing about ownership. The relationship is shown as one of three states.

StateWhat it means
WatchingThe agent reads a public coin. No ownership or official relationship is claimed.
ClaimedThe creator states an official relationship. It is shown as a claim that has not been verified.
VerifiedThe creator’s signed-in wallet is an authority the network records for the coin: its mint authority, its metadata update authority, or the creator recorded by pump.fun. Or the coin was created through Dolgano by that wallet.

Nobody can mark themselves verified. The only way to that state is the check against the network, and it can be repeated by anyone because every input is public.

Creating a coin is one transaction that your wallet signs and pays for. It creates the coin’s mint account and its metadata, creates your token account, and mints the whole supply to you. You choose whether to keep the mint authority (the ability to mint more), whether to keep a freeze authority, and whether the metadata can be changed later; the review step states who holds each one. The cost is measured by simulating the transaction against the network before you sign: rent deposits, the metadata program’s creation fee and the network fee, in SOL.

Creating a coin does not create liquidity, a pool, a market, a listing or a price. Dolgano has no bonding curve and lists nothing anywhere. A new coin is simply a coin you hold.

A creation is a stored record. If you reload or close the page, it is where you left it. The coin’s address is derived from your wallet and the record, so the same creation cannot produce two coins.

Treasury monitoring

An agent watches a public address. Watching is not controlling.

  • Watching a public address: what Dolgano does. Anyone can watch any address. It proves nothing about who controls it.
  • Controlling a wallet: only whoever holds its key can sign for it. Dolgano never holds a key and never asks for a seed phrase.
  • Delegating execution to an agent: not part of this release. No agent can spend.

Balances are read live from Solana mainnet: SOL and every token account. Each reading shows its source and time. If part of the read failed, the reading is marked partial instead of being shown as complete.

A holding is valued in dollars only when the market source lists the token and the market behind it has at least $1,000 of liquidity. Otherwise it shows "Price unavailable". An unknown price is never treated as zero and never estimated, and totals say how many holdings they cover.

Balance history is built only from snapshots Dolgano stored itself, at most one every 30 minutes, starting when the address was added. Nothing earlier is reconstructed, and the page says when collection began. A watched address is not a vault and not a security boundary.

Talking to an agent

Answers come from retrieved data and approved documents, with sources.

An agent answers with tools that read real data: its mission, the coin’s record on the network, treasury balances, recorded activity and a market snapshot. Each tool result carries its source and the time it was retrieved, and the conversation shows which tools were used.

Project documents are text you paste or public pages you link (up to 24 per agent). The agent may quote them, and a quote appears as a numbered citation that opens the passage it came from. A document is data: nothing written in one can change the agent’s rules or give it a permission.

An agent is instructed to keep retrieved facts and its own reading of them apart, and never to say an action was executed unless the activity record contains the confirming entry.

Without an AI provider configured, conversations show a setup state. There are no canned answers. With one, model use is bounded per UTC day: 60 creator messages per agent, 40 public answers per agent, 12 questions per visitor.

Action proposals

A proposal is a request for review. Approval is not execution, and submission is not confirmation.

This release has one action: a transfer of SOL or of a token, from the wallet that signs. Swaps are not available.

  1. 1Draft: written by the creator, still editable.
  2. 2Pending Review: waiting for the creator’s decision. An agent’s proposals start here.
  3. 3Approved: the creator agreed inside Dolgano. Nothing has been signed or sent.
  4. 4Submitted: a transaction signed in the creator’s wallet was sent to the network.
  5. 5Confirmed: the network reports the transaction as confirmed.

Other outcomes: Rejected (declined by the creator), Expired (not acted on in time), Cancelled (withdrawn before signing), Failed (the network rejected the transaction; nothing moved).

Each proposal shows the action, asset, amount, recipient, reason, supporting sources, creation time, expiration, the rule checks and, once prepared, the fee and the simulation result.

Before your wallet opens, Dolgano checks the network and the signed-in wallet again, re-runs the rules, checks the balance and the recipient, builds the transaction and simulates it. A transaction that fails simulation is not offered for signing. A prepared transaction older than 75 seconds is rebuilt.

After signing, Dolgano relays exactly the transaction you reviewed (it refuses anything whose bytes differ), stores the signature, and follows it on the network. A proposal can be submitted once. It becomes Confirmed only when the network says so, never because a wallet returned.

A transaction is "confirmed" once a supermajority of the cluster has voted on its block and "finalized" about 13 seconds later. A signed transaction that is not included before its recent blockhash expires (about a minute) can never land.

Rules and pause

What is checked, and where the check lives.

  • Allowed assets, each with a largest amount per proposal and a daily proposed budget.
  • Allowed action types.
  • Allowed recipients, and whether only listed recipients may be used.
  • Whether the signing wallet must be the watched treasury address.
  • Proposal expiration (1 to 168 hours).
  • Human approval: always required in this release.

These are application rules: checks Dolgano runs on proposals created in Dolgano. Your wallet enforces one thing, that nothing is sent without your signature. Nothing is enforced by an onchain program, and the rules do not limit what the treasury wallet can do outside Dolgano.

Pause stops scheduled work and stops the agent from creating new proposals, from the moment you press it. A paused agent’s approved proposals cannot be signed until you resume. Pause cannot reverse a transaction that was already submitted to the network.

There is no "revoke permissions" button because no delegated authority exists: an agent never has the ability to sign.

Activity and evidence

A timestamped record of what happened, with what supports it.

Events are written by the part of the system that did the thing: agent created, mission updated, data retrieved, brief generated, proposal created, approved or rejected, transaction submitted, confirmed or failed, agent paused or resumed. Each has an actor, a time, source references, and where they apply a proposal, a transaction signature and the mission version.

Events are short statements. They never contain a model’s reasoning.

"Proof of action" means an inspectable record, plus a transaction signature you can look up on the network where one exists. A row in the activity record is not cryptographically verified. The application cannot edit or delete events once written, which guards against mistakes; whoever operates the database still could.

Community briefs

A short written account of a period, with its figures attached.

A brief covers a period and has four parts: treasury observations, market observations, new proposals and confirmed actions. It also lists its sources and its limitations: what could not be read, what has no price, what history does not exist.

The figures are gathered by the application and stored with the brief, so the prose can be checked against them. The limitations are written from the data, not by the model.

Briefs are generated on demand. Scheduled briefs need a scheduler that calls the deployment on a timer; when one is running they are generated at your chosen local time, once per due moment, with failures recorded and retried. If no scheduler is running, the product says so and nothing runs in the background.

A brief is private until you publish it. Publishing is a choice per brief.

Sign-in, privacy and security

What is private, what is public, and what Dolgano never asks for.

You sign in by signing a one-time message with your wallet. The message names this site, carries a nonce the server issued, expires in five minutes, and can be used once. Signing it sends no transaction and costs nothing.

  • Always private: settings and rules, conversations, proposals, project documents, unpublished briefs.
  • Public only if you publish: the agent’s profile and mission summary, public activity events, published briefs.
  • Public only if you switch it on separately: the treasury address and its balances.

Dolgano never asks for a seed phrase or a private key, and never stores one. If anything asks you for one, it is not Dolgano.

What is not in this release

Stated plainly, so nothing is assumed.

  • Swaps and trading of any kind.
  • Autonomous or delegated execution: no agent can sign or send.
  • Liquidity pools, bonding curves, listings or prices for coins created here.
  • More than one network.
  • Historical charts from before an address was added.
  • Security audits: none has been performed.

What this deployment can do

The real state of each capability right now, read from this deployment’s configuration.

Selected network: Solana mainnet. Explorer links go to Solana Explorer. “Implemented” means it works here now. “Requires configuration” means the code is complete and the deployment is missing something. “Not implemented” means it is not part of this release.

  • Accounts and saved agents

    Implemented

    A PostgreSQL database is connected. Missions, proposals, activity and briefs are stored there.

  • Read the network

    Implemented

    Solana mainnet is read through the shared public RPC endpoint (api.mainnet-beta.solana.com). The public endpoint is rate limited; a dedicated endpoint makes reads faster and more reliable.

  • Wallet sign-in

    Implemented

    Sign in by signing a one-time message with a Solana mainnet wallet. No transaction is sent.

  • Market prices

    Implemented

    Prices come from Jupiter’s token index. A coin the source does not list is shown as "Price unavailable", never as zero.

  • Agent conversations and briefs

    Implemented

    Answers and briefs are generated by claude-opus-5-5 through Vercel AI Gateway, within daily allowances.

  • Transfer proposals

    Implemented

    Transfers of the network coin and of tokens can be proposed, checked against the mission rules and reviewed.

  • Signing approved transfers

    Implemented

    An approved transfer is simulated, signed in your own wallet, relayed and then tracked until the network confirms or rejects it. Dolgano never holds a key.

  • Create a new coin

    Implemented

    A new coin is created on Solana mainnet by a transaction your wallet signs and pays for. Creating a coin does not create liquidity or a market.

  • Scheduled briefs

    Implemented

    A scheduler calls this deployment on a timer (last run Nov 20, 2026, 07:45 UTC). Briefs are generated at each agent’s chosen local time.

  • Swap proposals

    Not implemented

    Swaps are not part of this release. No swap can be proposed.

  • Swap execution

    Not implemented

    Swaps are not part of this release. Nothing in Dolgano trades.

  • Delegated execution

    Not implemented

    No agent can sign or send anything on its own. There is no delegated authority to grant or revoke.

Questions

What can an agent do?
It answers questions from data it is allowed to read (its mission, the coin’s record, treasury balances, recorded activity, a market snapshot and documents you approve), writes briefs, and can draft a transfer for you to review. Every answer shows where its figures came from.
Can an agent access funds?
No. An agent watches a public treasury address; it does not control it. It has no key and no ability to sign. A watched address is not a vault.
Which actions need my wallet approval?
Every financial action. A proposal moves nothing until you approve it in Dolgano and then sign the transaction in your own wallet. Creating a coin is also a transaction you sign and pay for.
How do source citations work?
Live figures come from tools, and each result carries its source and retrieval time. Project facts come from documents you added; a quote appears as a numbered citation that opens the exact passage. If the documents do not cover a question, the agent says so.
How do I pause an agent?
Press Pause on its overview. Scheduled work stops and the agent stops creating proposals at once. Pause cannot recall a transaction that was already submitted to the network.
Which network does Dolgano run on?
Solana mainnet. It is the only network in this release.