Dispatch
A desk of autonomous trading agents that reads the entire Base ledger, finds the small group of traders whose results are real and repeatable, proves they can be followed under live market conditions, and acts on their decisions inside an account that only its owner controls.
This document describes how the agents are organised, how their layers depend on one another, which principles shaped each design decision, and where the product goes next. It is written for partners, integrators and holders who want to understand the agents before they rely on them.
- Drawing no.
- DSP-BP-001
- Revision
- Rev F.2 · 19 Oct 2026
- Network
- Base mainnet · 8453
- Status
- Live
- Sheets
- 00–17
Abstract
Sheet 00 · SummaryDispatch is a non-custodial desk of trading agents for following verified on-chain traders on Base. They continuously read the full ledger, rebuild trading histories for active wallets, and admit a trader to the roster only after their results prove consistent across independent periods, beat chance and hold up under real execution delay and market depth.
When a rostered trader acts, the agents prepare, price, simulate and settle the corresponding action for each client account within seconds, behind a sequence of safety guards that reject untradeable assets, price chasing and excessive concentration. Client funds remain in smart accounts owned by the clients' own wallets. Signed on-chain permissions allow trading and capped fees but never transfers to third parties.
The $DSP token aligns holders with the agents. Holding it lowers performance fees, unlocks larger trader desks and will give priority access to scarce capacity on the most sought-after traders. This document sets out the problem, the architecture, the security model, the token's role and the roadmap.
The thesis
Sheet A · IntentPublic blockchains are the most transparent markets ever built. Every order, every position and every exit is written to a ledger that anyone can read. In principle this means the best decisions in the market are visible to everyone. In practice almost nobody can use them. The record is enormous and noisy, most visible activity is automated or adversarial, and the few wallets with genuine, repeatable judgment are hidden among hundreds of thousands of others.
Even when such a wallet is found, acting on its moves is hard. Markets on Base move in seconds. Fresh tokens can be built to trap buyers. Liquidity is thin and changes block by block. A person who sees a good trade and repeats it by hand is usually too late, too large for the market or exposed to a token that cannot be sold back.
Dispatch was designed to remove each of these obstacles in turn. The agents treat the ledger as raw material and turn it into a short, continuously verified roster of traders worth following. They measure whether each trader's edge survives real execution before a single client unit is committed. When a rostered trader acts, the agents size the move to each account, check it against a sequence of safety guards and settle it within seconds. Throughout, client funds remain in client-owned smart accounts. The agents can trade on a client's behalf, but they cannot take custody of the money.
Signal from the whole chain
The full Base ledger is the source, not curated lists, social feeds or third-party leaderboards. Every new market and every active wallet is in scope from the block it appears.
Proof before trust
A trader is admitted only after their results hold up across separate periods, beat chance, survive realistic execution delay and clear a set of adversarial checks.
Acted on in seconds
Moves are detected, priced, simulated, safety-checked and settled automatically, and each client's share is sized to their account and to the depth of the market.
Market opportunity
Sheet 02 · ContextBase has become one of the busiest networks for on-chain trading. Low fees and fast blocks have drawn a constant flow of new markets: token launches, community projects, AI-agent tokens and a growing set of established assets with deep liquidity. The same conditions that make the network attractive make it hard to navigate. New markets appear every minute, most of them fail, and the ones that succeed often do so within hours.
In this environment the scarce asset is information. Anyone can buy any token. Very few people can tell, at the moment it matters, which buyers know what they are doing. That knowledge already exists in the ledger, written by the traders themselves. Agents that can extract it reliably and act on it safely give ordinary participants something they could not build alone: the judgment of the best traders on the network, applied to their own capital, at their own risk level, without handing that capital to anyone.
Why existing approaches fall short
Sheet 03 · LandscapeToo slow, too exposed
Watching wallets by hand means reacting minutes late, at worse prices, with no protection against tokens that cannot be sold.
Speed at the cost of custody
Trading bots that hold user keys or funds are fast, but every user carries the operator's security risk.
Ranked on the wrong evidence
Public rankings sort by headline profit. They reward single lucky trades and automated strategies that cannot be repeated by anyone else.
Dispatch is a desk of agents that combines what each of these lacks: machine speed without custody, a ranking built on durable, followable results rather than headline numbers, and the same safety discipline on every action, whoever the client is and whatever the size of their account.
Agent architecture
Sheet B · Five layersThe agents are organised in five layers with clear boundaries. Information flows from left to right: raw chain data becomes candidate signals, candidates become a verified roster, roster activity becomes proposed actions, and proposed actions become settled trades inside client accounts. Results flow back from right to left. Every settled trade, every skipped action and every outcome is fed back to the Signal layer, so the roster is judged on how it performs for clients and not only on history.
Each layer can be improved, tested and scaled independently. This separation is deliberate. Discovery research can run at full depth without touching the live trading path. Risk rules can be tightened without rewriting execution. Most importantly, the Account layer sits outside the reach of every other layer: nothing upstream holds the authority to move client funds anywhere except back to the client.
Turns every block on Base into structured events: new markets, swaps, transfers and positions, attributed to the wallets that made them.
Scores wallets on the quality and durability of their results and maintains the roster of traders that clients can follow.
Decides whether a proposed action is safe, sensible and correctly sized for each account before anything is sent to the network.
Finds the best route through available liquidity, settles the action and confirms the result, recovering automatically from interruptions.
The signal layer
Sheet C · Data fabricEverything starts with a complete, faithful picture of what happens on the chain. The Signal layer reads Base block by block and rebuilds the economic meaning of each transaction. A swap is recognised as a swap whatever venue or route carried it. A transfer between two wallets of the same owner is told apart from a sale. A purchase paid in a stablecoin or another token is valued consistently with one paid in ETH.
On top of this event stream the layer reconstructs full trading histories for wallets of interest: every entry and exit, the size of each position over time, and the value of what is still held. Fresh markets often have no reliable external price. For these the layer derives prices directly from on-chain pool state, so a token launched an hour ago can be valued as accurately as an established one.
The layer is built for completeness. Discovery begins from the markets themselves: every newly created pool on the network, rather than lists published by aggregators, which see only a small fraction of real activity. In our measurements, aggregator coverage represented a few hundred tokens over a period in which hundreds of thousands of new markets were opened on Base.
Discovery pipeline
Sheet D · SelectivityFinding a trader worth following is a search for a few true signals in a very large haystack. Each stage below narrows the field on evidence, never on reputation, follower count or self-reported results. The volumes are from recent discovery cycles on Base.
The steepest cut is the last one. Many wallets look excellent on paper and still cannot be followed: their edge depends on being first in the block, on a position size the market cannot absorb twice, or on assets that cannot be sold back. Execution testing exists to find these cases before a client does. An admission rate of a few per hundred thousand is what remains when all of these effects are removed.
Market scan over 90 days; wallet stages over the latest 30-day cycle. Cycles run continuously, and the admitted roster is reviewed against live results.
How a trader earns a seat
Sheet E · Admission criteriaAdmission is a sequence of independent tests. Each one closes a specific way in which past results can mislead, and a candidate must pass all of them. No single score can compensate for a failed test.
The whole curve, not the best trade
Results are judged on the complete account curve, realised and open, day by day. A trader whose profit comes from one lucky position is identified and set aside, however large that position was.
Proven in more than one period
Candidates are chosen on one period and confirmed on another they were not selected on. Their results must also beat random entries into the same markets, which separates skill from a rising tide.
Survives real execution
Every candidate is replayed with realistic delay and realistic position size against the actual depth of each market. Edges that disappear in practice are discarded, however strong they look on paper.
Adversarial screening
Automated strategies, launch-block sniping, self-issued tokens, coordinated wallet farms and untradeable assets are removed before anyone is scored, so they can never crowd out real traders.
Admission is not permanent. Once rostered, a trader is measured on the results they produce for clients. A trader whose live behaviour drifts from the profile that earned the seat loses weight or is removed. Traders may also change wallets or move holdings between their own addresses. The agents recognise this and follow the position to its real exit rather than losing track of it.
From decision to settlement
Sheet F · Execution pathWhen a rostered trader acts, the agents have a few seconds to respond while the opportunity is still close to the price the trader saw. The execution path is organised around this budget. New blocks are processed as they arrive. The trader's action is recognised and classified, and the corresponding action for each following account is prepared in parallel.
Each prepared action is priced against all available liquidity, and the best route is chosen for the exact size of that account. The action is simulated against the current state of the network before it is sent. The transaction carries a strict minimum outcome, so it either settles within a narrow band around the simulated price or does not settle at all. When an action does not settle because the network moved first, the agents re-evaluate it from scratch under the same guards before deciding whether to try again.
Exits follow the trader just as closely as entries. When a trader sells part of a position, each following account sells the same share of its own position. When a position reaches a predefined multiple of its cost, the original stake is returned to the account and the remainder continues to ride, so only the profit stays exposed.
Execution and risk
Sheet G · Guard railsEvery action passes the same sequence of guards before funds move. The guards are ordered from cheapest to most thorough, so most unsafe actions are rejected immediately and only promising ones reach full simulation. A failed guard skips the action and records why. Nothing is forced through, and every decision can be traced afterwards.
| Guard | What it protects against |
|---|---|
| Pre-trade simulation | Failed or mispriced transactions. Each action runs in simulation first and settles only within a tight price band. |
| Exit-path proof | Assets that can be bought but not sold. Before any entry, the agents prove that a full round trip back to ETH is possible and measures what it would cost. |
| Entry price discipline | Chasing. Entries well above the trader's own price are declined, because the opportunity the trader saw is already gone. |
| Origin checks | Insider assets. A purchase of a token issued by the trader themselves is never followed. |
| Sizing limits | Concentration. There are caps per action, per asset and on early-stage assets, plus daily and per-minute limits on new entries. |
| Circuit breaker | Runaway activity. An abnormal burst of actions pauses new entries automatically until the situation is reviewed. |
| Self-healing runtime | Infrastructure hiccups. Stalls are detected and recovered within seconds, and processing resumes from the exact block where it stopped, so no action is lost. |
Custody by design
Sheet H · Account layerDispatch is built so that the operator never holds client funds. Each client receives a dedicated smart account on Base, owned by the client's own wallet. Deposits go into that account and stay there.
To let the agents act, the client signs a small set of narrowly scoped permissions. Each permission is enforced on-chain, not by policy, and allows exactly one kind of action. One permits trading through approved liquidity routes. One permits returning funds to the owner's wallet. One permits a capped performance fee. Each has its own limits and expiry. There is no permission to send funds to an arbitrary address, so even in the worst case funds can only be traded inside the account or returned to its owner.
Your account, your keys
Funds live in a smart account owned by your wallet. Dispatch never holds them and has no key that can.
Narrow, signed permissions
Each permission is limited on-chain in what it can call, how much it can move and how long it lasts.
Withdrawals go only to you
Funds can leave the account only to the wallet that owns it. Fees are capped, charged only on profit and only at withdrawal.
Security: the gate and the procedures
Sheet I · Defence in depthCustody by design decides where the money lives. This sheet describes what protects it while the agents trade, and what happens when something goes wrong. The principle is the same throughout: the controls that matter are enforced on chain, where a client can verify them, and the operational layer around them is built to detect, bound and recover.
The gate contract
Every trade the agents make passes through GuardedSwap, a verified contract that sits between the client account and the liquidity aggregator. The agents' trading permission points at the gate and at nothing else. The gate decodes the route it is handed and enforces its own rules before any funds move, regardless of who signed the transaction:
Proceeds only to the owner
Whatever a swap returns is paid to the account that owns the position. The route cannot name another recipient.
Only the lot
Only tokens the gate saw bought for the account can be sold through it. Anything else in the account is the owner's alone.
A loss budget
Each account has a bounded share of its cost basis that trades may lose per week. Selling at or above cost is never limited; selling into a loss beyond the budget does not execute.
Rate limits
Caps per account and per hour on the number of sales and on the ETH that can enter or leave through the gate.
The gate has no owner, no upgrade path and holds no funds between calls. Its source is published and verified against the deployed bytecode: deployment on Base · verified source (Sourcify). The current deployment is also linked from the app.
What the gate does and does not promise
The gate limits damage; it does not remove risk. If the agents' trading key were ever compromised, the attacker could still trade badly inside the account, and the worst case is bounded by the loss budget and the hourly limits rather than by the size of the account. That bound is the design goal: a known, limited loss instead of an open-ended one. Market risk, token risk and the risk of defects in the surrounding software remain, as described under Risk factors.
Procedures
| Procedure | What happens |
|---|---|
| Continuous reconciliation | Two independent watchers, one next to the agents and one on separate infrastructure, compare every event on the gate with the agents' own journal. A trade the agents did not initiate is treated as a breach. |
| Automatic halt | On a breach, new entries are paused on chain and the agents are stopped before any operator is involved. Sales at or above cost remain possible for clients at all times. |
| Operator response | The operator receives the verdict with the evidence and chooses between two actions. If the cause was the market, the loss budget is reset and trading resumes. If the cause was a compromise, every client position is moved into ETH on the clients' own accounts, with no action required from clients, after which keys are rotated and permissions re-issued. |
| Cold key | Both actions are signed by a key that is never present on any server. It can only reset budgets and sell positions for ETH paid to the owning account; it cannot move funds anywhere else. |
| Drills | The incident path is exercised end to end on a schedule, from the first alert to the evacuation of a live position, so that the procedure is known to work before it is needed. |
| Continuity | The service runs on dedicated infrastructure with a warm standby, minute-level state replication, continuous backups and encrypted off-site key escrow. Failover is a deliberate operator action, so that two instances of the agents can never trade the same account at once. |
Numeric limits, alert channels and key custody details are operational parameters and are intentionally not published here; the contract rules above are the ones a client can verify independently.
Reliability and operations
Sheet J · Always onAgents that trade on behalf of others have to keep working when their surroundings do not. The runtime reads the network through several independent providers. When one of them slows down or refuses a request, the next one takes over without waiting. Processing state is written to disk continuously, so a restart resumes from the exact block where work stopped and never replays or skips an action.
Independent watchdogs check the agents from the outside. They confirm that the agents are current with the chain, that every trader action received a response, and that the accounts they manage hold what the records say they should. Anything unusual raises an alert to the operators within minutes. Every action, skip and recovery is logged with its reason, so any outcome a client sees can be traced to the decision that produced it.
Strategies
Sheet K · Ready-made desksMost clients do not want to assemble a roster themselves. Ready-made strategies package the verified roster into desks with a defined character: which traders are followed, how much of the account each entry uses, when the original stake is returned, and what fee applies. Clients can also add up to five wallets of their own choice next to a strategy.
Balanced
A broad desk of verified traders in fast-moving Base markets. Moderate entries spread across many traders keep any single outcome small.
Aggressive
The highest-return traders on the roster, with larger entries, for accounts that accept bigger swings in exchange for more upside.
Base Blue
Traders of established Base tokens such as AERO, VIRTUAL, NOCK and MORPHO. Deeper markets give steadier exposure and lower execution cost.
Every account shows its own performance: return in percent and in ETH, an annualised rate before and after fees, and a chart of the account's value since its first deposit. The figures are calculated from the account itself and not from a model or a backtest.
The $DSP token
Sheet 13 · Utility$DSP is the access and alignment layer of Dispatch. Its utility is tied directly to the product. Every benefit corresponds to something the agents already do or are building, and none depends on speculation alone.
| Utility | What holders get | Status |
|---|---|---|
| Fee tiers | A lower performance fee on profit, scaled by holding. | Next release |
| Larger desks | More traders followed per account than the standard limit. | Next release |
| Wallet following | Follow any Base wallet of your choice next to a strategy. | Next release |
| Priority capacity | First claim on capacity of the most popular traders when their markets fill up. | Planned |
| Fee payment in $DSP | Pay performance fees in $DSP at a discount. | Planned |
| Real-time signals | Instant notice when a top trader acts; delayed for non-holders. | Planned |
Supply, allocation and distribution details are published separately by the token issuer. This blueprint covers only how the token interacts with the product.
$DSP holder tiers
Sheet L · Fee scheduleHolding $DSP lowers the fee on profit, step by step. The schedule keeps strategies separate because they carry different returns and different costs to run, and it never raises the fee for anyone above today's base rate. The wallet balance is read at sign-in, with nothing to stake, lock or migrate.
| $DSP held (share of supply) | Balanced | Aggressive · Base Blue |
|---|---|---|
| None | 15% | 20% |
| 0.05% or more | 12% | 17% |
| 0.1% or more | 10% | 15% |
| 1% or more | 5% | 10% |
Roadmap
Sheet M · ReleasesThe core agents are live and trading on Base. The next releases build a holder layer on top of it and then add features that matter at larger scale, where demand for the best traders starts to exceed what their markets can absorb.
- 01Live now
Core agents
- Three ready-made strategies
- Follow up to five wallets of your choice
- Performance view with return and APR
- Non-custodial smart accounts on Base
- 02Next release
Holder layer
- $DSP fee tiers
- Larger trader desks for holders
- Wallet-following as a holder feature
- 03Following releases
Scale layer
- Priority capacity on the most popular traders
- Fees payable in $DSP at a discount
- Real-time trade signals for holders
Risk factors
Sheet 15 · DisclosureTrading digital assets carries substantial risk, and following other traders does not remove it. Past results of any trader, however carefully verified, do not guarantee future results. Markets on Base can move sharply within minutes, newly launched tokens may lose most or all of their value, and liquidity can disappear. Execution happens after the trader's own action, so prices can differ from theirs. Smart accounts and the underlying contracts are software and may contain undiscovered faults. Network congestion or provider outages can delay actions. Clients should deposit only what they can afford to lose and should choose a strategy that matches their tolerance for loss.
Conclusion
Sheet 16 · SummaryThe best decisions on Base are already public. What has been missing is a way to find the few that are real, prove they can be followed, and act on them safely without giving up custody. Dispatch is built around that gap: chain-wide discovery, evidence-based admission, guarded execution and client-owned accounts, operating continuously as one desk of agents. The holder layer and the scale features on the roadmap extend the same principles as the network and the user base grow.
This document is for information only. It is not an offer of securities or investment advice, and it does not create any obligation on the part of Dispatch. Features marked as planned may change.
Glossary
Sheet N · Terms| Roster | The current list of verified traders the agents follow. |
| Entry | A purchase made by an account when a rostered trader buys. |
| Stake back | Return of the original amount when a position reaches a set multiple of its cost. |
| Execution delay | The time between a trader's action and the account's matching action; candidates are tested against it. |
| Exit-path proof | A simulated round trip showing that an asset can be sold back before it is bought. |
| Smart account | An on-chain account owned by the client's wallet that holds funds and enforces signed permissions. |