DROP DESK MANUAL
every data source, filter, allocation mode and sender mechanic on the drop desk, with the caveats spelled out.
bullprint endorses no token and touches no funds. not financial advice.
doctrine
four rules the whole desk is built on. one, zero custody: your wallet signs every transaction, bullprint never holds keys or funds. two, fail closed: a filter whose data source cannot be read refuses with a reason, it never silently passes everyone. three, addresses stay server side: previews carry counts and distributions only, addresses leave only through the auth-gated, publicly receipted export. four, honest coverage: every filter states what it can and cannot see, and wallets a filter cannot judge are kept and counted, never silently cut.
the snapshot
the base list is a daily full walk of every $ansem holder. rows are serialized canonically (sorted by address, one “address:raw” line each) and the sha256 over those exact bytes is published with the receipt, so anyone can re-derive and verify the list. structural wallets (cex, pools, burns, program-owned accounts) are flagged at walk time with reasons and removed by the infra filter at export.
snapshots are retained for a configurable window (currently 30 days) and every retained day feeds the behavior windows below. a new snapshot lands daily and every dependent dataset updates with it automatically.
filters, group by group
the funnel under the target panel shows every active gate in exact application order with its removal count; amber ticks mark gates that kept unjudgeable wallets. counts always reconcile: recipients plus every removal equals the snapshot row count, exactly.
allocation
amounts are computed in integer base units of the drop token, BigInt end to end, and every mode obeys one invariant: allocated sum plus remainder equals the total, exactly. floors are never sprinkled back, the remainder stays with the sender, visibly.
exports and receipts
exports need a signed-in bullpen session with a linked x handle, because every export is a public receipt: who, when, how many wallets, which snapshot, the file’s sha256, and a summary of the filters, on the ledger at the bottom of the desk before a single byte is served. quota: 10 a day.
the sender
the in-app sender re-runs your exact export, re-verifies its sha over the received bytes, derives and checks every recipient token account, then per batch: fresh blockhash, build, simulate first (a revert stops everything before anything is signed), sign in your wallet, broadcast, poll to confirmed. any failure stops the run loudly.
what updates when
the holder snapshot lands daily and re-checks every 15 minutes. behavior windows deepen with every new snapshot. the presence ledger updates at each snapshot persist. the classifier re-scans twice hourly, stamping only newly appeared wallets, and rewrites its fast-read mirror whenever anything changed. the observed-sellers ledger accrues live from the tape. every preview computes fresh against these stores, and every coverage badge shows the live reach at that moment.