DEVELOPER HANDOFF / DATA CONTRACT

What this demo can—and cannot—prove.

This is a read-only transaction explorer, not an official $CONST payout ledger. It demonstrates the wallet lookup and receipt experience while the distribution attribution rule is still missing.

Current claim boundary

A row confirms a TAO balance increase to the searched wallet in a Solana transaction where an observed StonkFun payout-side account decreased. It does not prove that the transfer was funded by $CONST fees or that the recipient met $CONST eligibility rules.

01 / IMPLEMENTED

What works now

  • Search a public Solana wallet without connecting or signing.
  • Read its associated TAO token-account history in pages and link each matching transaction to a block explorer.
  • Sum matching TAO in raw units, then display the count and date range for pages loaded so far.
  • Recognize transfers from the platform account and one observed distributor account.

02 / NOT YET VERIFIED

What must stay qualified

  • The payout accounts serve more than one launch; TAO transfer records do not carry a dependable $CONST campaign identifier.
  • The “$20 minimum” timing and any lookback rule have not been confirmed.
  • Only the standard associated TAO account is searched. Closed or nonstandard accounts are outside this prototype.
  • RPC history can be incomplete or rate-limited. Totals cover loaded pages only, and unavailable transactions may cause undercounts.

03 / WHAT WE NEED FROM STONKFUN

The smallest useful data contract

Can StonkFun provide an API, export, or documented on-chain rule that identifies each $CONST distribution batch and its recipient transfers? The ideal record has:

  1. Project/token identifier ($CONST mint), distribution or batch ID, and payout timestamp.
  2. Recipient wallet, TAO amount in raw units, TAO mint, and transaction signature.
  3. Source/distributor wallet and whether it can change over time.
  4. Pagination/backfill coverage, correction behavior, and a stable way to join records to Solana receipts.

If an API is unavailable, a deterministic attribution rule plus a handful of known $CONST and non-$CONST payout signatures would let us validate a chain-only classifier.

04 / ELIGIBILITY QUESTION

How is the minimum applied?

Please confirm whether the stated $20 holding threshold is evaluated at each payout snapshot, over a lookback window, or by another rule; which price source is used; and whether transfers or holding-duration changes affect the amount. Until then the demo does not calculate expected rewards or mark wallets eligible/ineligible.