The gap
Ask anyone who trades what they are trying to end up with, and you will get a clear answer. A stack of the two or three things they actually believe in. Ask them what they are holding, and you will get a different answer: whatever the last few weeks left them with. The gap between those two answers is not a gap in knowledge. It is not caused by bad information or by fees. Everyone in it already knows what they should be doing.
The gap exists because trading and accumulating are two separate actions, and only one of them has a trigger. Trading has a hundred triggers: a chart, a headline, a group chat, boredom on a Sunday night. Accumulating has none. Nothing in your day ever arrives and says now is when you buy the thing you said you believed in. So it waits, and the trades do not.
Why schedules fail
The standard answer to this is a schedule. Set a recurring buy, automate it, forget it. It works, when it survives. The problem is that a schedule is a second financial commitment sitting beside the first one, drawing on the same balance, competing with the same impulses — and it is the one you can cancel in two taps on a bad week.
It also fails in the specific way traders fail. A recurring buy assumes an income stream flowing in from outside, being sliced on a calendar. That is a saver's model. A trader's balance does not arrive monthly; it circulates. It goes out and comes back, four or ten or forty times a month, and the entire flow is invisible to a scheduler that only knows what day it is.
If the money moves when you trade, the accumulation has to move when you trade. Anything on a calendar is measuring the wrong clock.
Attach it to the trade
So attach it to the flow that already exists. Every swap you make is already a moment where you have decided to move money, already signed for, already paying gas. It is the one recurring event in a trader's life that never needs to be remembered — and it is where a dose belongs.
This inverts the usual relationship. In a scheduled plan, accumulation is the discipline and trading is the leak. In DOSE, trading is the engine and accumulation is the exhaust. The more you churn, the more you build. A bad month of overtrading, which normally produces nothing but fees and a worse position, produces a larger stack of the asset you actually wanted.
It also means the thing can never be cancelled by a mood. There is no moment where you decide not to dose this week, because there is no moment where dosing is a decision. You decided once, at the beginning, when you were thinking clearly.
Keep it small
Everything above only holds if the dose stays under the threshold where you start doing arithmetic before a trade. The moment a user thinks let me turn this off for this one, the mechanism is dead — not because the money mattered, but because the automatic thing became a decision again.
That is why the dose is capped at five hundred basis points and why the sensible range is a tenth of that. At 0.50%, a two-thousand-dollar swap gives up ten dollars — less than the spread you accepted without looking. Nobody restructures a trade around ten dollars. But a trader doing eight thousand a month at that rate has routed four hundred and eighty dollars into a single asset by the end of the year, in roughly a hundred and fifty automatic purchases at a hundred and fifty different prices, without ever once having chosen a moment to buy.
It is worth being exact about what that cap is. DOSE deploys no contract, so the ceiling lives in the code that builds the transaction — a product decision, not bytecode. Nobody can raise it without shipping a build, and every transaction it writes is legible in your wallet before you sign it. But it is a promise rather than a guarantee, and the two are not the same thing. Making it a guarantee costs about a hundred lines of periphery contract, and the day that matters more than shipping, it gets written.
One settlement layer
The idea only becomes interesting when the thing you are trading and the thing you are building are not the same kind of object. Routing part of an ETH trade into more ETH is rebalancing. Routing part of an ETH trade into Apple is something you previously could not do at all without a broker, a bank transfer and a three-day wait — which is exactly the friction that guaranteed you would never do it.
On Robinhood Chain, a tokenised equity and a tokenised coin are the same kind of object, sitting in the same pools, settling in the same block. That collapses the entire cross-asset accumulation problem into one swap. It is the only reason DOSE is a piece of software and not a company.
The obvious build for this is a Uniswap v4 hook that skims the pool, and it is worth saying plainly why that is wrong. A hook only ever sees the pools that were created with it. A DOSE hook would dose your trades in DOSE's pools, and nobody trades there — the liquidity is in the canonical pools, which have no hook and never will. A design that can only act where it owns the venue cannot make a claim about every swap you make.
So the dose is composed one level up, in the transaction: your trade goes to the deepest liquidity that exists, and a second leg carries the dose. It means DOSE only works on swaps made through it, which is a real limit and is stated as one. In exchange there is nothing deployed, nothing custodial, and no pool you have to be talked into using.
What this is not
It is not a yield product. Nothing is lent, staked, or leveraged, and the protocol never holds a balance between transactions. It is not a savings account, and it does not promise that the asset you chose goes up — if you build a position in something that falls, you will have built a position in something that falls.
What it does is remove the one thing standing between people and the portfolio they say they want, which was never capital or information. It was the absence of a trigger. DOSE makes the trigger the thing you were going to do anyway.
Every trade. A small dose.