Receiving-wallet plan

Wallet Plan

Open the cemetery gates slowly. Make every burial traceable before it becomes theatrical.

The safest launch path is not to publish wallet addresses immediately. Crypto Graveyard should start with a manual beta, learn from a few controlled burials, and only then graduate into automated wallet watching and public cemetery wallets.

Recommended modemanual beta

> wallets.public = false

> tester.approval_required = true

> unsupported_tokens.auto_accept = false

> tax_claims.allowed = never

Gate rule: Until official wallets are published on this domain, no one should send tokens claiming they are burying them with Crypto Graveyard.

Wallet models

Three ways to receive dead coins

All three can work eventually. The trick is choosing the one that matches the project’s maturity instead of the one that feels flashiest.

Simple, but risky first

Permanent public wallets

Publish one official cemetery wallet per supported chain. This is easy to understand and good for a livestream, but attribution, spam, unsupported tokens, and impersonation risk are harder to control.

Best for

Later public launch

Cleaner attribution

Per-submission deposit addresses

Generate a unique deposit address or memo per burial request. This makes matching transfers to users easier, but it requires more backend infrastructure and careful operational security.

Best for

Automation phase

Recommended starting point

Manual review first

Start with a request form, review the token and chain manually, then provide burial instructions only for approved early participants. It is slower, but safer while the process is still being shaped.

Best for

Private beta

Phased launch path

Phase 0

No wallets published

Current state. The site explains the concept, but does not request or accept token transfers.

Phase 1

Manual beta burials

Invite a few known testers, review each burial manually, and publish sample-like memorial pages based on controlled real transactions.

Phase 2

Watcher-assisted flow

Run wallet watchers for a small chain set and reconcile transfers into a database before publishing memorials.

Phase 3

Public cemetery wallets

Publish official receiving wallets after monitoring, support docs, abuse handling, and display rules are working.

Candidate chains

The first chain should be cheap enough for testing, familiar enough for users, and easy enough to watch reliably.

Base

Low fees, Ethereum-style tooling, good candidate for early headstone and NFT work.

Polygon

Low fees and broad EVM support; good for inexpensive test burials.

Ethereum

Most recognized, but mainnet fees make it better for later or high-significance burials.

Solana

Popular and low cost, but requires a separate watcher and tooling path from EVM chains.

Public display policy

The burial should be public enough to be fun, but private enough that users are not accidentally doxxing their wallet history for internet points.

Use pseudonyms by default.
Mask wallet addresses unless the participant explicitly opts into public display.
Show transaction hashes only when useful and consented to.
Label values as sample, observed, estimated, documented, or unknown.
Never display a burial as a verified tax loss.

Open decisions

Which chain gets the first real test burial?

Should early testers apply before receiving instructions?

Will large claims require private documentation review?

What should happen when users send unsupported tokens?

When should a burial become eligible for the Hall of Fame?

Manual beta layer

The request-form preview is ready before any wallets are published.

It previews chain, token contract, wallet proof preference, pseudonym, and consent choices while keeping real transfers closed until an approved beta burial exists.