tech

A thin, boring pipeline between trading fees and real assets.

rewardpad adds no new bonding curve, no new token standard and no custody. It is a commitment layer: it records what a coin promised its holders, then executes that promise with claims, swaps and transfers that anyone can verify.

browser                     rewardpad server                solana
────────                    ────────────────                ──────
mint keypair ──────────────► build create tx ──────────────► pump.fun program
wallet signature ──────────► relay signed tx ──────────────► mainnet
                            index coin + reward asset
                            ▲
scheduled claim job ────────┴──► claim creator fees ───────► bonding curve
                                 swap SOL → RWA mint ──────► jupiter
                                 batch transfer ───────────► holder wallets

Launch path

non-custodial

Mint keypair is generated in your browser. Metadata and image go to IPFS, the create instruction is built against the pump.fun program, and the transaction is signed by both the mint keypair and your wallet before we relay it to an RPC node.

Indexing

live

Every coin launched through rewardpad is written to our index with its committed reward asset. Market cap, price, bonding-curve status and holder counts are refreshed from pump.fun and Solana RPC on every coin view.

Fee claiming

scheduled

Creator fees accrue on the bonding curve. A scheduled job claims them per coin, records the SOL amount, and queues a swap. Claims are idempotent and logged with signatures.

Swap layer

jupiter

Claimed SOL routes through Jupiter into the coin's committed RWA mint. Slippage limits and minimum batch sizes prevent burning value on tiny claims.

Distribution

on-chain

Holder snapshots come from token accounts at claim time. Payouts are pro-rata, batched into transfer transactions, and every batch is published on the coin's reward panel with its signature.

Trust boundary

verifiable

We never take custody of a coin, its liquidity, or your keys. Everything a user signs is built server-side and signed client-side; every distribution is verifiable on an explorer.