What we know. What we don’t. What needs verifying.
This record separates the creator’s reported history from independently verified onchain evidence. No market metrics, treasury balances, burns, or liquidity locks are inferred.
Archived for transparency. Earlier project liquidity positions were withdrawn; this is not an active-pool recommendation.
Creator-supplied burn reference
Supporting reference supplied by the creator. The displayed percentage is not independently verified burn evidence. Capture date not provided; transaction receipts are pending.
CREATOR-SUPPLIED RECORDS
BURN EVIDENCE.
The creator supplied these screenshots on November 13, 2026. Submission date is not the transaction date. The two success screens do not identify their token; matching them to $DADSDEFISPACE requires checking the receipt and transfer logs. Explorer confirmation is pending.
Success screen · 4,999,998 tokens
The tool displays a successful removal of 4,999,998 tokens. Token, network, destination, and receipt details have not been independently confirmed.
Base explorer link provided for checking; network attribution pending.
DADSDEFISPACE · burn form
Shows the project contract and 1,000,000 entered for burning to 0x000000000000000000000000000000000000dEaD. This form alone is not a completed receipt.
KITO · separate asset
Shows Kito Keeper of Stats and 25,000,000 entered. This is a different token and is excluded from DADSDEFISPACE burn totals.
The creator-reported 2.6% of released supply is not recalculated from these screenshots. A supply basis and matched onchain receipts are still needed. Transfers to a dead address may reduce accessible circulation without reducing the contract’s totalSupply value.
BUILD LOG / NOVEMBER 13, 2026
SHIPPED. NEXT.
Shipped: streamlined navigation, Zora and Uniswap buy links, linked creator artwork, illustrated whitepaper, and a source-labelled burn evidence archive.
Next: match burn receipts, document funding allocations, and evaluate liquidity and staking arrangements. These remain pending; no vault or new liquidity deployment is announced here.
How future records will be published
Each executed transaction should identify its date, action, amount, network, transaction hash, source wallet, funding source, and supporting context. Unverified submissions remain labelled until checked. Material changes to roadmap or partner status should include the announcement date and evidence.
This first version has no public submission form or live blockchain feed. Shared content is maintained in the site’s editable content file.