Transparency
Accounting you can check yourself.
FluxLoop publishes its processing pipeline, ledger invariants, and the data needed to re-derive every draw. The frontend never decides balances, prize amounts, or eligibility.
Integration status
- Solana RPCUnconfiguredTransaction indexing & signature verification
- Treasury addressUnconfiguredPublic treasury account for independent verification
- Database (Supabase)UnconfiguredPersistent ledger, rounds, audit log
- Randomness providerUnconfiguredCommit–reveal with future blockhash or VRF
- Gift card fulfillmentUnconfiguredLicensed provider required — none connected
- Stock rewardsUnconfiguredDisabled pending authorized provider & legal review
Fee events acceptedDemo data
909Fee events rejectedDemo data
47Never counted toward balancesLedger invariantDemo data
BalancedSum of all buckets equals total fees receivedProcessing pipeline
- 1Discover fee transfers to the treasury address
- 2Verify finality, destination, and source adapter
- 3Deduplicate by signature + instruction index
- 4Apply published allocation rules
- 5Update the append-only ledger
- 6Reserve funds for approved prizes
- 7Check whether the next round is funded
- 8Freeze and hash the eligibility snapshot
- 9Reveal committed seed + mix future entropy
- 10Record result and payout obligation
- 11Submit payout or fulfillment
- 12Confirm completion, publish record
Jobs are idempotent and retry-safe; each step is keyed so a repeated run cannot double-count or double-pay.
Rejected events by reason
Demo data- Failed or not finalized27
- Duplicate signature13
- Wrong destination7
Verifiable draws
Before each round, the server publishes a hash commitment of a secret seed. After the eligibility snapshot is frozen, the seed is revealed and mixed with entropy that did not exist at commit time (a future blockhash). Anyone can recompute the snapshot hash, the randomness, and the selected winner in their own browser.
Verify a round