DiviPump Whitepaper

DiviPump is a Solana dividend protocol that redistributes creator fees from participating pump.fun coins. A creator opts in by assigning 100% of their fee-sharing configuration to the DiviPump distribution wallet and permanently revoking configuration authority. That immutable on-chain commitment is the foundation of the system.

Once connected, each coin is processed on a private, randomized cadence. DiviPump snapshots eligible balances, claims accrued creator fees, reserves transaction costs, and allocates the remaining budget: 95% to holders and 5% to the protocol. Holders do not stake, bridge, sign, or claim.

Creator fees reward trading activity, but they do not inherently reward the wallets carrying long-term price exposure. This creates a misalignment: the community supplies attention and liquidity while the fee stream exits the holder economy.

DiviPump converts that fee stream into a recurring holder dividend. The protocol deliberately uses balance alone—no streaks, loyalty points, or opaque multipliers—so allocation can be understood and independently reproduced from a holder snapshot.

1. 1
   Commit the fee route

   The creator assigns the DiviPump wallet 10,000 basis points of the pump.fun fee-sharing configuration and revokes admin authority.

2. 2
   Verify on-chain

   DiviPump decodes the sharing-config account and requires both the full allocation and the permanent revoke before accepting the mint.

3. 3
   Snapshot eligible holders

   Token accounts are aggregated by owner, non-holder program accounts are removed, and the remaining wallets are ranked by balance.

4. 4
   Claim accrued fees

   When at least 0.01 SOL is distributable, the permissionless pump.fun claim instruction moves that coin’s accrued fees into the distribution wallet.

5. 5
   Allocate and settle

   The holder pot is calculated with integer lamport arithmetic, dust is filtered and reallocated, and transfers are sent in transaction batches.

Holder balances are summed per owner across token accounts, sorted in descending order, and limited to the top 100 after exclusions. Ties are broken deterministically by wallet address.

Excluded before ranking

• Bonding-curve and canonical pump pool addresses
• Pump pool authority and fee-sharing configuration accounts
• The DiviPump distribution wallet itself
• Explicitly excluded wallets and zero-balance accounts

Filtering happens before the top 100 are selected. This prevents a pool account from consuming a recipient slot or absorbing funds it cannot spend.

All calculations use integer lamports. Any rounding remainder is assigned to rank one so the budget is exhausted exactly. The accounting invariant is:

protocol allocation + sum of holder allocations = cycle budget

Dust and reallocation

Provisional transfers below their economic floor are removed. The pot is then recalculated over the surviving wallets so unpayable dust does not silently become protocol revenue. Existing accounts use a 5,000-lamport floor; new system accounts must clear the rent-exempt minimum.

Each coin receives a new randomized processing time between one and five minutes after a cycle. The exact next snapshot time is private and is never returned by a public route or rendered as a countdown.

This is a security property. A public schedule would let an attacker buy immediately before the snapshot and sell immediately afterward. A private randomized window forces anyone seeking a dividend to carry actual price risk while waiting for an unknown snapshot.

The reference implementation uses a Next.js application on Vercel, Supabase Postgres for state and locking, Helius for Solana RPC and token accounts, and the pinned pump.fun SDK for sharing-config decoding and fee claims.

Atomic, expiring database locks prevent concurrent workers from processing the same coin twice. Each dividend budget is derived from that coin’s current claim, never from the distribution wallet’s total balance.

• Hot-wallet exposure. Claimed fees pass through an online signer before settlement.
• Provider dependency. RPC or token-account data outages delay snapshots and dividends.
• Throughput ceiling. A single scheduled worker supports a finite number of frequently due coins before fan-out is required.
• Large holder sets. Coins beyond the configured pagination ceiling must wait for a dedicated top-holder data path.
• Market behavior. Random timing raises the cost of snapshot gaming but cannot eliminate all strategic trading.

This paper specifies the protocol’s intended behavior and trust assumptions. It is not financial advice, a promise of returns, or a substitute for an independent smart-contract and operational security review.