Overview
DVD is a playful, verifiable burn mechanic. A client-side agent bounces the classic DVD logo in an overlay. Perfect corner hits activate a burn hook: the backend signals initiation and, upon developer wallet signature via Phantom and oracle attestation, a 0.5% Developer Supply burn is executed on-chain. The UI is observer-only; all state changes are server-signed and oracle-verified. After each confirmed burn, the app displays the transaction signature and slot as proof.
Tokenomics
- Ticker: $DVD
- Supply Policy: Deflationary via burns only (no minting)
- Burn per Corner: 0.5% of Developer Supply (executed after hook, signature, and oracle attestation)
- Proof: Each burn returns a transaction signature & slot; explorer links are provided
- Oracle: Server-signed attestation is required for every burn
- Safety: Cooldowns, per-call cap (≤0.5% Dev Supply), and optional daily cap
- Transparency: Public burn feed and on-chain verification
Notes: There is no team-administered preset allocation or vesting schedule. “Developer Supply” refers only to the holdings controlled by the DVD Treasury wallet. Burns do not affect third-party wallets.
Passive Income Module (PDF Bouncer)
DVD is building a paid placement system: users can upload a PDF to replace the DVD logo for a timed slot while it bounces on-screen. Clicking the bouncing asset opens a link provided by the payer.
- Pricing:
0.01 SOL
per 15 minutes - Queueing: If a slot is already purchased, new purchases are queued FIFO for the next available window
- Attribution: The UI shows the active placement window and a click-through link
- Revenue use: Proceeds go to the DVD Treasury and are used for market buybacks of $DVD from circulating supply
- Controls: Content checks, abuse guardrails, refunds on failed displays
Roadmap — Q4 2025
- Mainnet readiness: Backend signer online, Phantom treasury configured, SOL for fees
- Live mint wiring: Treasury funded post-launch; automatic creation of the associated token account (ATA)
- Burn Proof UI: Display tx signature & slot with explorer links; “awaiting attestation” banner prior to confirmation
- Oracle attestation v1: Server-side HMAC over
txId|slot|amount
; display attestation hash - Safety rails: Cooldowns, per-call burn cap (≤0.5% Dev Supply), optional daily cap
- Logging & monitoring: Structured logs for burn attempts, successes, and failures
- PDF Bouncer alpha: Upload, queueing, timed display, payouts to treasury, public earnings counter
- Transparency: Public burn feed with links; clear Terms & Risk disclosure page
- Docs refresh: Update litepaper + FAQs to reflect live status and operations
Proof of Burn
Each burn emits a verifiable on-chain record. Lifecycle: hook initiated → developer signature (Phantom) → oracle attestation → on-chain burn. The app then shows:
Wire burn hook successfully initiated, awaiting Oracle attestation and developer signature via Phantom Wallet to execute a 0.5% burn of the Developer Supply. Transaction signature and slot are displayed below for proof.
Users can cross-check each burn on Solana Explorer by searching the provided transaction ID. Prior to treasury funding, the UI remains observer-only and indicates “awaiting attestation & signature”.
Governance & Safety
Burn parameters (corner detection thresholds, cooldowns, caps) are initially controlled off-chain by the developer wallet for operational safety. Treasury spends and contract upgrades will be executed transparently with public announcements. Over time, community input will inform parameter updates and the publication of a formal governance path.