WORKSPACE / FEE POLICYProposal only · local checks

FEE ROUTING / BEFORE DEPLOYMENT

Plan fee sharing

Inspect a fee-router proposal. Check its addresses and shares, then see exactly how hypothetical total SOL receipts would be allocated.

DEPLOYMENT IS A SEPARATE STEP

Local checks verify format and arithmetic. Account ownership, source binding, balances, and deployment are not verified here.

Review router deployment

01 / INSPECT

Your routing policy

2–6 RECIPIENTS

Paste a fee-router JSON export from the workspace. Up to 20 KB. Do not paste keys, signatures, or transactions.

Up to 9 decimals. Assumes zero prior funding or payouts. Use the fee router workspace to project an existing router.

Import a policy or load an example to begin.

What these checks establish

Addresses must be canonical Solana public keys, route shares must total 100%, and the proposal must use the unsigned mainnet proposal schema. These checks do not prove account ownership, a deployed router, a connected fee source, or automated collection.

02 / REVIEW

Allocation results

NOT CHECKED

Make the policy readable.

Check the proposal to reveal exact destinations, the 1% router fee, and any rounding reserve.

Public policy JSON. Editing either input clears the review and requires another check.