Beta Request
Apply to bury a coin before the public cemetery gates open.
This is a product preview for the future manual beta flow. It shows what Crypto Graveyard may ask for before approving controlled test burials. The form is not live, does not submit data, and does not provide wallet addresses.
> form.submissions = disabled
> wallets.generated = false
> beta.review_required = true
> secrets.requested = never
Wallet proof options
The beta request can let users choose how they want to prove control without exposing secrets.
Never ask for
Consent checklist
These are the plain-language confirmations a real beta form should require before anyone receives burial instructions.
I understand no official wallet transfer happens until Crypto Graveyard approves the beta request.
I will never share seed phrases, private keys, passwords, or recovery words.
I understand public memorials may show pseudonym, token, chain, quantity, masked wallet, and transaction details.
I understand Crypto Graveyard does not verify tax losses, charitable deductions, cost basis, or token value.
Review queue flow
Step 1
Request received
The future system records token, chain, pseudonym, and consent choices without asking for secrets.
Step 2
Safety review
Unsupported chains, suspicious token contracts, impersonation attempts, and confusing tax-language claims get filtered before any transfer.
Step 3
Burial instructions
Only approved beta testers receive the exact official instructions for that controlled burial.
Step 4
Memorial draft
After the transfer is confirmed, the site can generate a memorial draft with confidence labels and display choices.
Next backend milestone
The real version needs storage, moderation, and email before submissions open.
Once the intake fields are approved, the next technical step is deciding where beta requests live: database records, email notifications, admin review, and status pages.