Revenue settlement

Checklist for settling what you owe on TIN:

• TCA — tips
• PSA — pay when selling pre-conf (epoch fees by txn Updates)
• MCA — 65% of backrun profit (pre-conf free for backrun-only; fund a PSA too if you also sell)

Download the latest CLIs from the releases. Revenue overview: TIN revenue streams. Tips: Tips.

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

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 and recommended)

Traders and 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 are done.

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: Partner Tip and Mev Revenue Settlement CLI. Registration: custom tip accounts.

2. MCA — MevShare

For backrun / MevShare, settle through the MCA. Pre-conf is free when you share through the MCA (post-pack confirmation and optional TPU). Settlement is self-reported and you hold the MCA record_authority. If you also resell, pay PSA fees based on txn Updates as well — see Post-pack — access and payments.

• Backrun bundles using post-pack confirmation source transactions get an additional 20% virtual priority boost
• Share 65% of backrun / MevShare revenue through TIN
• Expected baseline: 65 SOL / month / 1M stake
• Use your own RSMS / revenue recognition / attribution system so you can provide an audit report on Rakurai / validator request
• The TPU P2C stream is available on the Mev (mev) path; resell uses the Packet stream only

2.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) — record 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: Partner Tip and Mev Revenue Settlement CLI.

3. PSA — P2C Subscription (resell pre-conf)

Selling pre-conf means you pay through a PSA — keep it funded per service name and validator vote. The account model matches backrun RevShare (one PDA per validator). There is no record step — transfer SOL into the validator PDA only. Any wallet may fund the PDA; no whitelisting is required.

Backrun-only (MCA): pre-conf is free — no PSA. If you also sell, fund the PSA for those updates.

• Expected baseline: $50 / 1M txn Updates (dollar equivalent amount in SOL)
• If you are selling P2C to searchers, share 65% of that subscription revenue through TIN
• Use your own RSMS / revenue recognition / attribution system so you can provide an audit report on Rakurai / validator request

3.1. Each epoch

• Use the rakurai-p2c CLI
• Fund before the epoch ends: fund (one validator vote) or fund-all (--dry-run first if needed) — or solana transfer to the PDA
• Settle / top up: Use fund or fund-all to clear shortfalls so the stream stays active

Detailed commands: P2C Subscription CLI.