DIGGD buries a message on Solana and digs it up when a token reaches a market cap, when a date arrives, or whichever comes first.

While a bone is buried, everyone sees its teaser, its token, its target and how deep the dig has gone. Nobody sees the text. When it comes up, anyone can read it and check it against the hash written on-chain when it was buried.

Lifecycle

• buried: sealed, waiting for its target or date.
• dug: the target held for two checks in a row, or the date arrived.

Bones cannot be edited or dug up early by their author. Check the conditions before you bury.

1. Open Bury a bone and write a public teaser and the buried message.
2. Paste a token mint and set a market cap, a date, or both. The target has to be at least 10% above the current market cap and at least $5,000.
3. Phantom asks you to approve one transaction. It writes the hash in a memo and costs a normal network fee. After the $DIGGD launch it also burns 50,000 $DIGGD.
4. Your bone goes into the yard with its own link. Share it.

If your wallet is the pump.fun creator of the token, the bone gets a Creator badge. Anyone else can bury on any token, without the badge.

The hash in the memo is the SHA-256 of these lines, joined with newlines:

The salt stays secret until the bone comes up, so short messages cannot be guessed from the hash. Open a dug-up bone and the site recomputes the hash in your browser. You can also do it yourself and compare it with the memo on Solscan.

Endpoint (streamable HTTP, JSON-RPC over POST). No key needed:

Tools

• list_bones { status?: "buried" | "dug" | "all", mint?, limit? }
• get_bone { id }
• check_token { mint }

• GET /v1/bones?status=buried|dug|all&mint=&limit=50
• GET /v1/bones/:id
• GET /v1/token/:mint
• POST /v1/bones { teaser, body, salt, mint?, targetUsd?, openAt?, tx }
• GET /v1/me, GET /v1/stats

Errors come back as { "error": "…" } with a 4xx status.

Here is exactly what you are trusting.

What nobody can do

• Change a bone. The text, the token, the target and the date are bound to the hash on Solana. A changed bone fails the check.
• Backdate a bone. The memo's block time proves when it was buried.

What you trust DIGGD with

• Keeping it under. Text is encrypted in the database, but the server holds the key, because it has to dig bones up by itself. It could technically read a buried bone. Do not bury anything that would hurt you if it leaked.
• Digging it up. The digger runs on our server and reads market caps from Jupiter. If either is down, the dig waits.
• Keeping it up. If the service shut down, buried text would be lost. The hash would stay on-chain.

DIGGD can take a bone out of the yard if it is abusive or dangerous. The hash stays on-chain. Phase 4 moves to encryption that needs no trusted key.

Reading bones safely

• A bone is only what its author wrote. An on-chain seal proves when it was written, not that it is true.
• A Creator badge means the pump.fun creator wallet signed it. It says nothing about whether the token is safe.
• Be careful with any link or address in a dug-up bone. Never connect a wallet to a site just because a bone told you to.

Can a wick dig up a bone?

The market cap has to stay at or above the target for two checks in a row, about 2 to 4 minutes. A single spike resets the count. A bone can still come up on a pump that holds for a few minutes and then fades.

What if the token never gets there?

The bone stays buried for good, unless you also set a date.

Can I dig up my own bone early?

No. You can read it from your wallet, but it stays buried for everyone else.

Why does a holder read first?

When a bone comes up, holders of 500,000 $DIGGD can read it right away. Everyone else waits 5 minutes.