Around the protocol
Three things stand next to Assetrix without being part of it. This page says what they are for, in plain words, and who can ignore them.
Who this page is for
You sell or buy ASTRX on Uniswap
While the transfer fee on ASTRX stands above zero, a trade needs one more contract outside the protocol: the router. This follows from the way decentralised exchanges work.
You provide liquidity
On Uniswap v3 you need the router as well; on v4, the position manager.
You are closing a large position below the threshold
The protection level may refuse the whole of it at once. To know exactly how much can be closed in one go, you need the reader — another contract outside the protocol.
If you only mint, redeem, close a position, transfer tokens or vote, none of this touches you. All of that goes through the core alone.
Nothing on the right holds any right over the left. The core does not know these exist and never calls them. Anyone may write better ones and use those instead.
Why a router is needed at all
Above the zero rung, every transfer of ASTRX burns a share on the way.
A pool does not look at what was sent to it. It names a figure and requires its own balance to have risen by at least that much. Hand it exactly the figure it named, and part of that burns before it arrives. The pool comes up short and refuses.
Neither side is wrong. The pool counts correctly and the token behaves exactly as described. They simply cannot settle with each other directly.
The way through is to send enough for the named figure to arrive after the burn. The router works out how much that is and sends it. That is the whole of what it adds, and anyone can check the arithmetic: it is a public function.
The seller names what leaves his balance, the burnt share included. That is the figure he approves, and the figure the router will not exceed.
What it checks before it opens
The pool is real
A pool is accepted only if Uniswap’s own factory names that address for that pair. A contract that merely looks like a pool is refused before anything is paid.
The budget is not exceeded
A trade opens with the amount you named and not one unit more. A pool that asks for more is refused; a pool that asks twice finds nothing left.
The floor is respected
A trade that would deliver less than the least you named is refused. So is a trade that reported success and delivered nothing.
No one walks back in
While one trade is open, no other door of the router opens.
Every refusal is named. Nothing fails silently.
What the router does not do
- It holds nothing between calls and never keeps a balance of yours.
- It has no owner, no settings and no way to be upgraded.
- It cannot mint, cannot close a position and cannot touch the collateral.
- The core does not know it exists. That is why its address is published apart from the core’s, and why it may change while the core’s cannot.
The reader
The protection gate refuses a closing that would dilute backing too far. When it refuses, it says nothing but no — no figure, no reason.
The reader does that arithmetic in advance: how many tokens this position may close right now, and which of eight reasons explains the answer.
It reads the core and changes nothing. If the two ever disagree, the gate is the truth and the reader is wrong.
The manager for Uniswap v4
Uniswap v4 keeps positions in a manager of its own. That manager names an exact figure and moves it itself, letting nobody in while it works. With a burn on transfer, less arrives than was named and the deposit fails. This was measured on the live network, not argued.
Assetrix therefore plans a manager of its own, on the same model, with one difference: it covers what is burnt. It is not written yet. Until it exists, liquidity on v4 is added through the ordinary Uniswap interface while the fee stands at zero.
The full account
This page is the short version. The appendix to the White Paper describes every door of the router, every refusal it can give, the eight answers of the reader, and what all of it has been tested by.