Gate
Shareable concept launch
Requirement
Safe public prototype with sample data only
Decision
Ready
Readiness map
Launch Checklist
The cemetery can look alive before the gates are open.
This page separates the shareable concept launch from the operational launch. The public site can be explored now with sample data, while real beta requests, wallets, burials, plaques, and collectibles stay behind clear readiness gates.
Launch terminalsafe prototype
Public prototype
Live
Sample-data site
Real wallets
Closed
No public receiving addresses
Beta backend
Planned
Not collecting requests yet
Tax claims
Never
Outside site scope
Current state: Shareable concept, yes. Real burial platform, not yet. The gates creak theatrically, but they remain locked.
Readiness gates
What can launch now, what must wait
Each gate answers a practical question: is this part safe to expose to the public, or does it need backend, review, wallet, consent, or legal-language work first?
Gate
Private beta requests
Requirement
Real form storage, review statuses, and no-secrets messaging
Decision
Not ready
Gate
First real burial
Requirement
Approved tester, official instructions, selected chain, and manual reconciliation
Decision
Not ready
Gate
Public wallet launch
Requirement
Watcher, database, abuse handling, display consent, and unsupported-token policy
Decision
Not ready
Gate
Awards with physical plaques
Requirement
Winner consent, private shipping workflow, and clear public award language
Decision
Not ready
Gate
NFT / SBT release
Requirement
Minting chain, metadata storage, provenance rules, and no-value-promise language
Decision
Not ready
Checklist groups
The operational map
The current prototype already has many public-facing pages. The next real work is the storage, review, wallet, and moderation machinery behind them.
Mostly ready
Public presence
The project can be shared as a sample-data concept site without accepting real burials.
Production domain connected
Done
Homepage explains sample-data mode
Done
About, FAQ, and safety language published
Done
Methodology page explains value labels
Done
Social preview artwork and logo polish
Next
Strong foundation
Trust and safety
The bright lines are visible: no secrets, no tax promises, no charity language, no live wallets yet.
No seed phrase / private key warnings
Done
No tax-loss verification claims
Done
No charitable-donation framing
Done
Pseudonym and masked-wallet defaults
Prototype
Abuse, spam, and impersonation rules
Next
Designed, not live
Controlled beta
The request and review flow is mapped out, but there is no storage, admin queue, or user messaging yet.
Beta request preview page
Done
Review process blueprint
Done
Request database schema
Next
Admin review screen
Next
Status notification templates
Next
Closed
Wallet operations
No receiving wallets should be published until the beta gate, chain choice, and monitoring process are ready.
Wallet policy page
Done
Pick first supported chain
Next
Create official receiving wallet procedure
Next
Wallet-control proof instructions
Next
Unsupported-token handling
Next
Sample only
Memorial system
The public-facing shape exists, but real memorials need durable records and reviewed source data.
Sample memorial route
Done
Certificate preview
Done
Coin profile templates
Done
Memorial database model
Next
AI eulogy generation workflow
Later
Concept preview
Media and collectibles
The fun layers are visible, but they should stay behind the core burial loop.
Livestream concept page
Done
Awards and plaque preview
Done
Headstone trait preview
Done
OBS-style overlay preview
Done
Production OBS browser source
Later
NFT / SBT minting plan
Later
Launch principles
These are the rules that keep the project moving forward without opening the parts that need operational maturity first.
Prototype before money
Let visitors understand the product with sample data before any real token transfer, paid collectible, or plaque fulfillment exists.
Manual before automatic
Use human review for early burials before publishing wallets or relying on automated watchers.
Labels before leaderboards
Define sample, observed, estimated, documented, unknown, and not-determined values before ranking real users.
Consent before clout
Give participants control over pseudonyms, masked wallets, public transaction links, and plaque shipping details.
Do not launch these accidentally
Do not publish receiving wallets before the review and watcher plan is ready.
Do not accept private keys, seed phrases, exchange logins, or remote access.
Do not advertise tax-loss harvesting, charitable deductions, or investment value.
Do not ship plaques without explicit winner consent and private fulfillment handling.
Do not mint NFTs/SBTs before metadata, provenance, and no-value-promise language are settled.
What “launch” means right now
Right now, launch means the public can understand Crypto Graveyard and follow the project. It does not mean users can bury tokens yet. That distinction is a feature, not a delay.
Can share the domain
Yes
Can browse sample data
Yes
Can submit real beta requests
No
Can send real tokens
No
Can receive awards
No
Next best build
After this, the practical next step is the real beta-request backend.
The public prototype is broad enough now. The next major shift is moving from sample pages to stored requests, admin review, and controlled instructions.