Revenue settlement

This is the quick checklist for settling what you owe on TIN — tips (TCA), prepaid post-pack (PSA), and backrun / MevShare (MCA).

For detailed CLI flags and examples, see the CLI docs linked in each section (and in the table below). Download the latest CLI from the releases.

Revenue flow: TIN revenue streams. Tip mechanics: Tips.

Audience: Traders and landing services tipping for inclusion, and TIN partners on post-pack (PSA + MCA).

1. TCA — Tips Collection Account

Tips for scheduling priority settle into a per-service, per-validator TCA. Prefer the Rakurai tip accounts path — settlement is automatic. A partner tip account is interim only and requires manual settlement each epoch.

1.1. Rakurai Tip Account (default & recommended)

Traders and transaction landing services tip any of Rakurai’s eight tip accounts. Nothing to settle from the trader or landing-service side. Tip into a Rakurai tip account and you’re done. (Minimum recommended tip: 0.001 SOL)

1.2. Partner Tip Account (interim — prefer Rakurai tip accounts)

Registering your own tip account is interim support only. The flow is more complex than Rakurai tip accounts (manually transfer each epoch). Use Rakurai tip accounts

If you still use a partner tip account: traders tip into that account; tips stay with you — Rakurai cannot drain them.

• 60% of the total tip is used for virtual priority
• Each leader turn the validator records that 60% in the TCA (no SOL moves yet)
• After the epoch, you transfer the owed SOL into the TCA

1.2.1. Each epoch

• Wait for the epoch to end
• Use the rakurai-revshare CLI
• Inspect: get-all-accounts (--revenue-kind Tip) — view any pending record
• Settle: transfer-all (--dry-run first if needed) — settle the owed revenue

Detailed commands: Tip and MevShare Settlement CLI. Registration: custom tip accounts.

2. PSA — P2C Subscription

The PSA is the prepaid subscription fee that keeps a validator’s post-pack (P2C) stream enabled. One PSA per service, per validator. The fee is priced from that validator’s staked SOL and deducted when the epoch ends.

• If you are selling P2C to searchers, share 60-70% of that subscription revenue through TIN
• Expected baseline: $500 / month / 1M SOL stake (dollar equivalent amount in SOL)
• Use your own RSMS / Revenue Recognition / Attribution System so you can provide audit report on Rakurai / validator request

2.1. Each epoch

• Use the rakurai-p2c CLI
• Fund before the epoch ends: fund-all, or solana transfer to the PDA — keep the prepaid balance funded
• Wait for the epoch to end
• Inspect: get-all-accounts — view balance, total owed, status (Active / InGrace / Suspended), and any deficit
• Settle / top up: fund-all (--dry-run first if needed) — clear shortfalls so the stream stays active

Detailed commands: P2C Subscription CLI.

3. MCA — MevShare

After the PSA is funded, you consume P2C and can backrun. Profit stays with you during the epoch; you share it through the MCA. Settlement is self-reported — you must hold the MCA record_authority.

• Backrun bundles using P2C source transactions get a 20% virtual priority boost
• Share 60-70% of backrun / MEV revenue through TIN
• Expected baseline: 60-70 SOL / month / 1M stake
• Use your own RSMS / Revenue Recognition / Attribution System so you can provide audit report on Rakurai / validator request

3.1. Each epoch

• Wait for the epoch to end
• Use the rakurai-revshare CLI
• Record: record-revenue once per validator (--revenue-kind Mev-share, record_authority keypair) — ledger only, no SOL moves
• Inspect: get-all-accounts (--revenue-kind Mev-share) — view any pending record
• Settle: transfer-all (--dry-run first if needed) — settle the owed revenue

Detailed commands: Tip and MevShare Settlement CLI.