Technical architecture

The web app reads offerings, profiles and rules from the ICO backend. All blockchain access goes through a single adapter interface. Today that adapter is read-only and reports every write capability (commit, claim, refund, create) as unavailable, which is why those buttons are disabled.

When the on-chain program exists, a real adapter will replace it, and an indexer will write commitments and allocations into the backend from confirmed transactions. See the technical roadmap.

Pump.fun integration checklist

1. Repeat the program-vault create-and-buy test on live Solana devnet (done only on a local copy so far; the public test SOL faucet was rate-limited).
2. Build the coin name, ticker, metadata link and creator on-chain from the offering record; the proof of concept accepted these from the caller, which is unsafe.
3. Fit the launch transaction under Solana's 1,232-byte limit with lookup tables (the proof of concept only fit after shortening the coin details).
4. Decide who receives leftover vault SOL and rounding dust, and how anyone else buying in the same block affects the result.
5. Measure the largest launch buy the curve and transaction limits allow; define partial-fill and slippage handling.
6. Confirm whether creator-reward sharing can be set at creation and whether it covers PumpSwap fees after graduation.
7. Read supported pair assets and launch modes at execution time instead of hardcoding them.
8. Prove idempotent launch on devnet: fixed mint per offering, on-chain launch flag, reconcile before any retry.
9. Legal review of Pump.fun's terms and of pooled launch purchases before any real funds.
10. Store mint address, Pump.fun URL, create signature, status, attempts, failure reason and settings snapshot once a real integration exists.