Explicit custody
The txttostonk Treasury owns each StonkFun Fee Key and temporarily holds creator revenue.
txttostonkSYNCING VIEWRESOLVING PUBLIC STATE
txttostonkThe Treasury holds Fee Keys and creator fees. Automatic launches use a separate limited-balance hot wallet; the main treasury and recovery keys remain outside the server. Creator ownership is proven through X and a signed payout-wallet challenge.
txttostonk, StonkFun, X, and legitimate wallet support will not need your recovery phrase to compose or review a launch.
The txttostonk Treasury owns each StonkFun Fee Key and temporarily holds creator revenue.
Only a limited-balance launcher can authorize a StonkFun launch; the main treasury key stays separate.
Pairs are validated by exact StonkFun mint and launchability, not by ticker alone.
Tweet IDs are unique, so the same social intent cannot create multiple drafts.
A recorded payment signature blocks preparation or submission for that draft.
Collected creator fees are accounted in base units: 90% creator and 10% txttostonk.
Prepared transaction data expires before stale transaction context can be reused.
Ambiguous conflicts stop the flow and require signature reconciliation.
X OAuth proves the author; a signed Phantom message binds the withdrawal address.
Live automation fails closed unless the exact fee transfer is below the configured per-launch lamport cap.
AUTO_LAUNCH_ENABLED and MOCK_LAUNCH are independent kill switches for automation and real-funds behavior.
Designed
Documented safety architecture and state transitions.
Implemented
Treasury matching, pair validation, image validation, 90/10 math, idempotency, and mock-safe routes exist in code.
Tested
Automated and browser checks are reported for each release.
Deployed
The website is deployed with mock launch mode enabled.
Proven with real funds
Not claimed. This release does not authorize real-funds testing.
Independently audited
Not claimed. No verified third-party audit evidence is present.