Proof specification
The exact statement a Bunkercoin fingerprint proves—and the statements it does not.
Domain-separated memo format
A v1 proof is a successful, finalized Solana transaction containing an instruction to the SPL Memo program whose parsed string exactly matches the namespace below. The digest is 64 lowercase hexadecimal characters.
The application creates version-0 transactions with one fee payer and one memo instruction. No value transfer, token approval, custom program, mint operation or priority-fee instruction is added. The signer is explicitly attached to the memo.
Program: MemoSq4gqABAXKb96qnH8TysNcWxMyWCqXgDLGmfcHr
Memo: bunkercoin:v1:sha256:<64 lowercase hexadecimal characters>Verification procedure
Read the transaction from Solana using finalized commitment. Require transaction metadata and a null execution error. Check the memo program, parse its exact namespace and digest, and inspect the transaction signers. Compare a locally recomputed digest against the memo.
The UI trusts the configured RPC for consensus state; it is not a local cryptographic light client. Cross-check another explorer or your own validator. A submitted signature is not displayed as finalized until the RPC confirms it. The index is optional and independently rebuildable.
Evidence limitations and privacy
A proof establishes that a signer published a digest in a finalized block. It does not establish who created the document, who legally owns it, whether it is true, whether it is still available, or whether any message crossed a physical radio link.
Hashing is not encryption. A digest of a guessable secret can be brute-forced. For confidential or low-entropy material, use a suitably designed salted commitment and preserve the salt privately. Never put private keys, passwords, personal identifiers or sensitive documents directly into an onchain memo.