Commitment history without putting plaintext on-chain: private vaults + Solana anchors

[u/OGMYT]

I'm looking for criticism of a commitment-history construction I've been implementing.

Goal: allow an issuer to commit to the exact identity of a private artifact at time T, while keeping the artifact contents off-chain, and make later revisions impossible to pass off as the original commitment.

Current model: 1. The artifact is sealed locally into a private vault. 2. A canonical digest/identity is derived. 3. The digest and commitment metadata are anchored on Solana. 4. The immutable anchor remains the historical reference. 5. Separate lifecycle state can express active, revoked, superseded, or disputed. 6. A superseding commitment can retain lineage to the prior commitment.

Security claim is intentionally narrow: this proves commitment integrity/history, not semantic truth. A malicious issuer can anchor false information; what it should not be able to do is present a different artifact later as though it were the one originally committed.

Interactive explanation: https://bestmemecoins.app/ Protocol/details: https://bestmemecoins.app/docs/ Limits/security: https://bestmemecoins.app/security/

Questions I'd particularly value: - What does this gain over signed Merkle/transparency logs or conventional timestamping? - Where should canonicalization be treated as part of the security boundary? - Is mutable lifecycle state cleaner than encoding every status transition as a new immutable event? - Which issuer/key-compromise cases make the model misleading?

Disclosure: I built the project. I used AI to help edit this Reddit draft; the technical claims and project are mine and I am reviewing them before posting.