01 —
DIRECTION IS STATE
Most fee systems discard trade direction after execution.
DUAL keeps it as part of the routing state. Every creator fee is attributed to the side that produced it before entering routing.
fee.side = trade.directionDUAL / DIRECTIONAL ROUTING
ONE TOKEN.
TWO ROUTES.
Every launched token defines two independent execution paths.
A BUY can build something.
A SELL can do something else.
The market decides which route executes.
LIVE ROUTING SCHEMATICexample config
NETWORK STATE / LIVE
- DUAL TOKENS
- 0
- BUY FLOW
- 0.0000 SOL
- SELL FLOW
- 0.0000 SOL
- BUY EXEC
- 0
- SELL EXEC
- 0
- RESERVES
- $0
- DISTRIBUTED
- $0
- BURNED
- 0
THE SPLIT
BUY SIDE
WHAT SHOULD ENTERING THE TOKEN BUILD?
- [ ] RESERVE
- [ ] DISTRIBUTE
- [ ] BURN
BUY↓
BTC↓
RESERVE
SELL SIDE
WHAT SHOULD LEAVING THE TOKEN DO?
- [ ] RESERVE
- [ ] DISTRIBUTE
- [ ] BURN
SELL↓
XMR↓
HOLDERS
SYSTEM NOTES
02 —
ROUTES DO NOT MERGE
BUY-side accounting and SELL-side accounting remain independent after attribution.
A buy increments the BUY route. A sell increments the SELL route. Once attributed, the two paths do not recombine.
buy_accumulator != sell_accumulator03 —
EXECUTION FOLLOWS THE MARKET
The creator defines both instructions once, together with the token.
Trading decides which one receives flow. The market does not merely trade a mint — it executes the two instructions attached to it.
route = config[trade.direction]ROUTE PAIRS
examples · any combination is validPAIR 01
BUY
RESERVE
ZEC
public reserve
SELL
DISTRIBUTE
XMR
private payout
PAIR 02
BUY
RESERVE
BTC
hard reserve
SELL
DISTRIBUTE
USDC
liquid payout
PAIR 03
BUY
RESERVE
BTC
reserve growth
SELL
BUYBACK + BURN
$TOKEN
supply contraction
PAIR 04
BUY
RESERVE
PAXG
gold reserve
SELL
DISTRIBUTE
XMR
private payout
01
DEFINE
one instruction for BUY, another for SELL
02
LAUNCH
token created on Solana Mainnet through DUAL
03
TRADE
market activity generates creator-fee flow
04
ROUTE
each event executes the route matching its direction
THE CREATOR DEFINES THE ECONOMY. THE MARKET EXECUTES IT.