Router: Where a coin's inflows go.

Explanation — not permission to act

New router configuration is deferred. Existing allocations, pause/history and supported top-ups remain subject to their own controls.

The mechanics and diagram include historical specification design. Current gates and finalized evidence govern; configuration is not availability or execution proof.

The routing design records inflows, deducts venue fees, then takes the platform inflow fee once on tax-dividend and creator-fee streams; trade-fee and meme-fee streams are exempt. The configured split then names DESK, INDEX, EMBER, VAULT or DIVIDEND. Splits total 100 and selected destinations carry minimums; DIVIDEND is unavailable on StonkFun reward coins. A permitted re-cut affects only later inflows with public history. A paused share redistributes among active destinations, but when all destinations are paused, funds are held. New configuration is deferred; existing controls remain capability-gated.

The inflow waterfall

Record the native inflow asset, deduct venue fees and applicable inflow fee once, then apply the allocation. A routing entry is not a fill or payout.

Configured destinations

DESK, INDEX, EMBER, VAULT and DIVIDEND are destination concepts, not a guarantee that every engine is active. Reward coins cannot select routed DIVIDEND.

Pauses and held funds

Paused shares redistribute only among active destinations. When all are paused, funds are held, not automatically rerouted elsewhere.

Fee waterfall from inflow to destination.
  1. Inflow row

    Tax dividend, creator fee, trade fee, meme fee or top-up.

  2. Venue fees

    Charged by the venue before anything else.

  3. Inflow fee, once

    Tax and creator inflows only; trade and meme fee streams exempt.

  4. Creator split

    DESK, INDEX, EMBER, VAULT, DIVIDEND by current allocation.

Practical next reading

Existing routing controls · Read receipts and allocations

The numbers that bound it.

Live configuration is not embedded in this guide. No values are shown rather than guessed. Local settings are not chain, provider or release evidence. Spec defaults are not provider proof.

  • PLATFORM_INFLOW_FEE
  • ROUTER_MIN_SHARE
  • ROUTER_RECUT_HOURS
  • POST_ARM_COMPUTER_BURN
  • TOPUP_MIN_USD

Platform spec reference

Historical source summaries, not a statement of current enforcement.

Applicability and precedence · §8 Allocation router · §7 Inflows and the reserve · §27 Decision Ledger (v6.6.1)