Holder rewards

Accounts the program creates

Every account has an address derived from fixed seeds (a PDA), so the page and the service find it from the campaign and nobody can swap in a look-alike. (A PDA is a program-derived addressAn account address worked out from fixed words (seeds) and the program’s ID. Nobody holds a private key for it; only the program can sign for it..)

Each holder’s line in a round is a leaf sha256("VEYDUCT_PUSH_LEAF_V2" ‖ program ‖ campaign ‖ network domain ‖ snapshot digest ‖ token program ‖ wallet ‖ cumulative amount). Leaves pair up into the round’s root; a delivery carries the holder’s proof (at most 30 hashes) and the program recomputes the root before it moves anything.

Who can do what

• ActionWho signsRules the program enforces
• Create a campaignAny wallet; it becomes the campaign adminA first deposit above zero from its own token account. The snapshot approverThe one wallet allowed to publish rounds: you in a manual campaign, or the VEYDUCT service attestor in an automatic one. Set when the campaign is created and never changed. is fixed for good: you (manual) or the service attestor (automatic).
• Add rewardsAny wallet, from its own tokensDeposits into the vault. Nothing is assigned until a round is published.
• Publish a roundThe snapshot approver onlyThe next round number; a snapshot newer than the last and at most the campaign’s maximum age old; a total at least the previous total; everything still owed covered by the vault.
• DeliverAnyone (they pay the fees)Only to the holder’s own associated token account, only the cumulative amount minus what was already delivered, and never to the campaign admin.
• Withdraw or reassignNobodyNo instruction returns deposits to the creator, changes the approver, rewrites a round or closes the campaign.

The program checks the arithmetic and the proofs, not the holder list. Who counts as a holder, and that the snapshot is complete, is what the approver vouches for. In an automatic campaign that is the VEYDUCT service attestor, permanently.

Split math, with a worked example

Amounts on chain are whole token units: 1 DEMO with 6 decimals is 1,000,000 units.

Each round splits its budget across eligible balances at one slot. The creator’s wallet, wallets that are program accounts (such as the Pump bonding curve or a pool) and the reward vault itself are left out. The calculator at the top of the tool uses the same method.

1. Round down each shareshare = budget × holder balance ÷ eligible total (whole units, rounded down)The remainder of each division is kept for the next step.
2. Hand out what rounding leftleftover = budget − Σ shares; +1 unit each to the largest remaindersTies go to the lower wallet address. Every unit of the budget is assigned.
3. Add to what each holder already hasentitled = previous rounds + this share; delivery = entitled − deliveredEntitlements only grow, so a delivery always pays exactly what is new.

Example

1. A holds 500,000, B 300,000, C 300,000 DEMO. Round 1 shares 1,000 DEMO.A: 1,000 × 5/11 = 454.545454 (rest 6/11) · B and C: 272.727272 (rest 8/11)Rounding left 2 units: they go to B and C, the larger remainders. A 454.545454, B 272.727273, C 272.727273.
2. B sells 200,000 to D. Round 2 shares 500 DEMO.A 5/11, B 1/11, C 3/11, D 2/11 of 500A +227.272727, B +45.454546, C +136.363636, D +90.909091 (the 2 leftover units go to D, then B).
3. Entitled after two roundsA 681.818181, B 318.181819, C 409.090909, D 90.909091: 1,500 DEMO in all. Delivering to A now pays 681.818181; delivering again pays nothing until another round.

Run the same steps in Try it (create, capture, publish, let B sell to D, capture and publish again, deliver): it uses this arithmetic, so you will see these numbers.

Costs

VEYDUCT fee to create a campaignPaid once, in the same transaction, to VEYDUCT’s fee wallet. Shown in the review.

0.01 SOL

Account rent for a new campaignCampaign (220 bytes) and reward vault, at mainnet rent of 5,080 lamports per byte plus 128 bytes per account.

≈ 0.0033 SOL (Token-2022) · 0.0033 SOL (classic)

Account rent per published roundA 136-byte round record, paid by the snapshot approver: you in a manual campaign, the service in an automatic one.

≈ 0.0013 SOL

Account rent per new holderA delivery receipt, the first time a holder is paid, by whoever sends the delivery.

≈ 0.0011 SOL

Holder token account, if missingA delivery re-creates a holder’s closed token account first, at the deliverer’s cost.

≈ 0.0015 SOL

Network feePer transaction, one signature.

0.000005 SOL

Percentage feesAdding rewards, publishing and deliveries carry no VEYDUCT fee, and the program takes no cut.

None

RentSOL deposited into an account so Solana keeps storing it. It is normally returned when the account is closed. stays in the program’s accounts: there is no instruction that closes a campaign, round or receipt, so it is not refunded.

Rounds and timing

• Snapshots are current balances. One finalized slotSolana’s clock tick, about 0.4 seconds. 216,000 slots is roughly a day, though slot times vary., no hold-time weighting. Someone who sells before the snapshot gets nothing from that round; someone who buys before it counts in full.
• Snapshots expire. This site creates campaigns with a maximum snapshot age of 216,000 slots (about a day; the program allows at most 432,000). Publish soon after capturing, or capture again.
• Rounds are numbered. Round 2 can only follow round 1, and each snapshot must be newer than the last one published.
• Automatic rounds run on the service’s schedule. At least 216,000 slots apart, within the tokens-per-round and total limits you sign, until your consent expires (1 to 30 days). Expiry pauses the service; earlier entitlements stay deliverable.

Edge cases and what can go wrong

FAQ