MCA — share backrun profit
The MevShare Collection Account (MCA) is where you pay the validator their agreed cut of the profit you made from post-pack confirmations. The PSA buys the stream; the MCA shares what the stream earned you.
Settlement is self-reported because backrun and arbitrage profit lands in your own wallet, where no on-chain program can see it. So after each epoch you do two things: report what you owe, then send it. What you report is written on-chain where the validator can read it. If you do not settle within the grace period, you lose post-pack access.
Audience: Searchers and TIN partners who already consume post-pack and share backrun profit.
Reporting is signed by the MCA record_authority keypair. Without that key you cannot record what you owe, and therefore cannot settle — which eventually stops your post-pack access. Confirm which key it is with rakurai-revshare get-account --detail (Record auth) as soon as the account is created.
1. Who this is for
Searchers and TIN partners that:
- Already fund a PSA for that validator
- Capture MEV (backruns or arbitrage) from the post-pack stream
- Share a percentage of that profit with the validator
There is one MCA per service per validator, matching the PSA layout. The vault itself is RevenueShareAccountV1 with share_kind = MevShare, derived from [REVENUE_SHARE_V1, MEV_SHARE, name, vote].
A custom tip account settles into a TCA (--revenue-kind Tip) and a post-pack backrun share settles into an MCA (--revenue-kind Mev-share). They use the same on-chain struct and the same CLI, but they are separate accounts and separate balances. Passing the wrong --revenue-kind targets the wrong vault.
2. Register
Onboard as for the PSA: share your endpoint and a wallet pubkey you control with the Rakurai team — Setup guide.
Rakurai creates the MCA and gives you a revenue name plus the record key. The revenue name is a PDA seed — use the exact value Rakurai assigned, including case.
Confirm the account exists and the record authority matches your key:
rakurai-revshare \ --url <RPC_URL> \ --program-id <REWARD_DISTRIBUTION_PROGRAM_ID> \ get-account --detail \ --revenue-kind Mev-share \ --revenue-name <REVENUE_NAME> \ --vote-pubkey <VALIDATOR_VOTE_PUBKEY>
Start consuming post-pack and settle after each epoch.
Partner vaults are created by Rakurai or ops. Creating one is not a partner CLI path.
3. During the epoch
Nothing is taken automatically. Profit stays in your accounts for the whole epoch and no ledger entry is written on your behalf.
This is the opposite of a custom tip account, where the validator records what is owed on every leader turn and you only transfer afterwards. For MevShare, you do both the recording and the transfer. See TCA and Tips — leader-turn stage for the contrast.
4. After the epoch
4.1. Report what you owe
record-revenue writes the amount into the epoch ledger. It moves no SOL and always targets the current cluster epoch.
rakurai-revshare \ --url <RPC_URL> \ --program-id <REWARD_DISTRIBUTION_PROGRAM_ID> \ --keypair <RECORD_AUTHORITY_KEYPAIR> \ record-revenue \ --revenue-kind Mev-share \ --revenue-name <REVENUE_NAME> \ --vote-pubkey <VALIDATOR_VOTE_PUBKEY> \ --amount <LAMPORTS>
record-revenue adds to the existing epoch entry rather than replacing it. Running it twice for the same epoch and vote books twice the amount owed, and you will then be expected to transfer that inflated figure. Check the current entry with get-pending-record before recording.
4.2. Send the SOL
transfer settles one epoch on one vault; transfer-all settles every pending epoch across matching vaults. Both accept --dry-run.
rakurai-revshare \ --url <RPC_URL> \ --program-id <REWARD_DISTRIBUTION_PROGRAM_ID> \ --keypair <FUNDER_KEYPAIR> \ transfer-all \ --revenue-kind Mev-share \ --revenue-name <REVENUE_NAME> \ --dry-run
What is still outstanding is pending = amount - transferred_amount, visible per epoch with get-pending-record or get-all-pending-records.
4.3. What Rakurai does next
Rakurai's commission is deducted from what you sent, and the remainder is credited to the validator identity. With block_reward_conversion_enabled on (the default), that remainder is then converted into a high-priority block reward — the same treatment TCA and PSA revenue gets. Indexers should not count both — see the indexing note.
If you do not report and send within roughly two epochs, post-pack access and MCA prioritization stop after that grace period.
5. CLI
Full command reference: Tip and MevShare Revenue Settlement CLI (rakurai-revshare). On-chain struct: Reward Distribution — RevenueShareAccountV1.