Beta review blueprint

Review Process

No burial instructions until the request survives the gatekeeper.

This page defines the future manual review queue: statuses, safety checks, admin notes, and user-facing messages. It keeps the beta request flow understandable before any database, email, or real wallet instructions go live.

Review terminalplanned

> request.storage = planned

> admin.queue = mockup

> auto_wallet_instructions = false

> reviewer.required = true

Safety default: Every new request starts closed. The cemetery does not hand out shovels automatically.

Status model

Request lifecycle

These are the states the backend should eventually support before any real user can complete a beta burial.

Received

The request exists, but no burial instructions have been sent.

Needs Info

The request is missing token details, wallet proof preference, contact info, or display consent.

Approved for Instructions

The request passed manual review and can receive controlled beta burial instructions.

Awaiting Transfer

The participant has instructions, but the burial transaction has not been confirmed yet.

Memorial Drafting

The transfer is confirmed and the memorial record, confidence labels, and eulogy are being prepared.

Published

The memorial page is live and eligible for the relevant demo or beta leaderboards.

Declined

The request is unsupported, unsafe, unverifiable, spammy, or too confusing to process.

Manual review checks

Token contract or mint address is present and matches the stated chain.

User selected a safe wallet-control proof method.

No private keys, seed phrases, passwords, or exchange logins were submitted.

Display consent is clear before any wallet or transaction details appear publicly.

The request avoids tax-loss guarantees, charitable-donation claims, and investment language.

Large-value claims are labeled as unverified unless supporting documentation is reviewed.

Unsupported chains or suspicious token contracts are paused before any instructions are sent.

Request record shape

The real backend should store enough to review and audit requests without collecting dangerous secrets or pretending to verify tax outcomes.

Request ID
Pseudonym
Contact method
Chain and token contract
Stated quantity
Sending wallet address
Proof method
Display consent flags
Internal review notes
Status history
Reviewer
Timestamps

Admin queue preview

What the first review screen might show

Sample rows only. This is the human-in-the-loop layer before wallet instructions, watcher automation, and public memorial generation.

Request

CG-BETA-0041

MoonBagMike

Token

MoonRocket Inu

Base

Status

Needs Info

Reviewer note

Missing wallet proof preference

Request

CG-BETA-0042

VaultWizard

Token

Yield Phantom

Polygon

Status

Approved

Reviewer note

Ready for controlled instructions

Request

CG-BETA-0043

RugHistorian

Token

SafeMars Classic

Ethereum

Status

Review

Reviewer note

High notional claim needs confidence label

Request

CG-BETA-0044

DustGoblin

Token

Unknown Reflection Token

BNB Chain

Status

Paused

Reviewer note

Unsupported chain in early beta

User message templates

Status changes should be boringly clear. The fun belongs in the memorial, not in the operational instructions.

Request received

We received your beta request. Do not send tokens yet. Crypto Graveyard will only provide instructions after manual review.

Need more information

We need one more detail before review can continue. Never send seed phrases, private keys, passwords, or recovery words.

Approved for instructions

Your request is approved for a controlled beta burial. Follow only the instructions shown on CryptoGraveyard.io.

Memorial ready

Your burial record is ready for review. Confirm the display choices before the public memorial page goes live.

Declined or paused

This request cannot be processed in the current beta because the chain, token, or claim is unsupported or unclear.

Next technical milestone

Turn the preview form into a stored request only after the review model is approved.

The next build can add a database-backed request model, admin review surface, and email/status notifications. Until then, this remains a blueprint.