How PUSD rewards are paid

Only claimed creator fees fund these operations. PUSD remains redeemable 1:1 for USDG; the reserve is separate.

Your balance determines your share

For each pool, the worker reads every holder’s balance and total PUSD supply at one recorded canonical block. Holding duration does not multiply the reward. Contract wallets participate too.

holder reward = floor(holder pool × holder balance / total supply)

With 3,000 PUSD in circulation and 2,000 PUSD in your wallet, you receive two thirds of the 80% holder allocation. If the claimed fee is 30 units, the holder pool is 24 and your share is 16. The other 6 units fund buyback and burn.

Rounding is down to raw token units. Any remainder stays allocated to holders and carries forward. Previously computed pools retain their recorded policy, balances and transactions.

Claim, distribute, retry

After a successful canonical claim receipt, the same worker cycle computes holder shares, swaps their allocation into NVDA, and sends it to holders. There is no daily close or holding-time wait. The 20% allocation funds automatic PROJECT buyback and burn.

Fee claim interval

5 minutes (default)

Retry interval for unpaid balances

5 minutes (default)

The Telegram admin bot configures both intervals, the PROJECT token address, the Twitter profile and the developer key. The token and Twitter link appear in the header. The private key is encrypted server-side and is never returned by the public API.

Failed swaps or transfers remain recorded for retry. A submitted transaction is only pending; the ledger marks success after checking its receipt and canonical block.

Verify a payout

Open a pool’s proof on Transparency. Use its computedAtBlock for both calls below and compare its snapshotBlockHash with the canonical chain. Amounts in the proof use raw token units.

cast call 0x62c6521B8f0D6DAD2368d9a0122bdc1E0d204416 "balanceOf(address)(uint256)" $ME --block <computedAtBlock> --rpc-url $RPC
cast call 0x62c6521B8f0D6DAD2368d9a0122bdc1E0d204416 "totalSupply()(uint256)" --block <computedAtBlock> --rpc-url $RPC

The public ledger includes every claim, snapshot, payout and buyback transaction. The server computes the allocation using the developer key; SwapAndDisperse enforces the quoted minimum output and transfers.

Dependencies

Rewards depend on actual PROJECT creator fees, available liquidity, the payout token’s issuer, and the worker. Stock Tokens are not direct ownership of shares. The contracts are unaudited. Reward processing failures do not authorize spending the PUSD reserve.