SPLICE ROUTERclosed claim → route cycles
PRODUCTION RECEIPTS / EMPTY
The receipt record.
route legs settled
sent to 0x…dEaD with receipt
public timelocked route tables
stock-reserve legs executed
Receipt events verified
What this record measures
SPLICE is an integration layer for existing Pons projects, designed to index sweep and execution events from each adopted vault on Robinhood Chain. The signed site ledger is a separate verification layer, not the onchain event itself. Records can show claims, protocol slices, treasury transfers, executed legs and burns; they do not, by themselves, prove demand, price, reserves, or future performance. Today the production record is empty: no vault exists and $SPLICE is not minted.
- Routed fees and burns: any published routed amount or burn should be checked against its Receipt or BuybackExecuted event, transaction hash, asset, amount and timestamp. A missing receipt is not evidence that an event occurred, and no figure here is SPLICE revenue.
- Protocol slice: the slice is hard-capped at 5% in code and frozen per vault at deploy. Its exact value and the vault deploy cost remain deployment decisions, and appear here only after they are live.
- New route profiles: disposable forks certify direct same-stock GOOGL reserve and native-pair permanent full-range V4 liquidity. These proofs establish bounded execution behavior, not a production deployment or market outcome.
- Pons and graduation: creator tax is at most 10% and fixed at launch by Pons; Pons' native buyback locks tokens for five years and does not burn; V4 graduation liquidity is permanently locked. This archive promises no liquidity, market, redemption or other outcome.
Inspect the current machine-readable evidence at /api/proof, read the stock + liquidity certification manifest, or download the independent verifier. Verify each receipt independently; this page describes what is observed and what remains unproven.
Robinhood ChainSETTLEMENT→
BlockscoutTRANSACTION+
SourcifySOURCE MATCHLATEST VERIFIED SWEEP
AWAITING FIRST RECEIPT00
No fork hash, illustrative amount, or synthetic receipt occupies this surface.
Creator fees claimed by a vault belong to that project's route table and are reported as routed fees, never as SPLICE revenue; the protocol slice is reported separately.
Performance reports sweeps closed, fees routed per leg, $SPLICE burned, stock reserve acquired and receipts verified as separate measurements from public events; no single metric is treated as success and no market data is shown before it is live.
01FORK CERTIFICATIONCORE + STOCK + LIQUIDITY PASSED
3 certified profileOF 3 certified profile
02MAINNET CANARYNOT STARTED
0 sweepOF 1 sweep
PUBLIC RECEIPT LEDGER
EVENT-DRIVEN · SITE-CONFIGEVENT / OBJECTDETAILVALUESTATE / PROOF
00
NO VERIFIED RECEIPTS YET
This ledger activates from vault events on Robinhood Chain. Fork rows and invented receipts are never promoted into public history.
The creator calls transferCreatorFeeRecipient(token, vault) on the Pons factory. No relaunch.
sweep() pulls the credited balance from the Pons fee escrow in the pairing asset.
A protocol slice frozen at deploy and capped at 5% in code moves to SpliceBurner.
The remainder splits by the active table: treasury now; burn, buyback and reserve legs accounted.
Market legs run with a minOut and deadline; a failed leg stays accounted, never re-routed.
SpliceBurner buys $SPLICE on its Pons pool and sends it to 0x…dEaD.
Receipt, BuybackExecuted and ReserveExecuted events are the product; the site reads only events.
CUSTODY
A vault is the Pons creator-fee recipient for its token and holds only balances accounted for market legs. The project keeps exit(), lockRoutes() and the Pons buyback toggle; nothing else is controllable. Pons retains a disclosed timelocked recipient override that no vault can prevent.
CONTROLS
Anyone may sweep or apply matured route changes. Vault burn/buyback and same-stock pass-through are public; venue reserve and protocol burns are operator-gated. Selected policy is a four-hour delay and three-day apply window, subject to deployed-value verification. Locking disables route edits and exit, not upstream authority.
HOLDER RIGHTS
Holding $SPLICE grants no equity, debt, redemption right, legal claim on any vault, treasury or reserve, or promise of distributions. Its only protocol roles are deploy-cost burn and protocol-slice buyback-and-burn.
PROOF BOUNDARY
Receipt records sweep allocations; reconcile StrayRouted for unsolicited funds. Separate execution events and balance deltas establish purchases. Recorded native-fork evidence does not prove stock reserve, liquidity or production activity.
A project exits by calling exit(newRecipient), which forwards the Pons creator-fee recipient to its chosen address. Balances already claimed still follow the active route table; there is no clawback or undisclosed destination.
No receipt row exists without a Receipt event, a transaction hash and a vault address.
Queued market funds remain accounted until execution. Timelocked owner edits can change execution destinations; upstream Pons recipient authority remains. Failed execution is not a completed purchase.