I am taking Kaspa as part of a project for a cryptographic anchor of document has a lot. The idea is not to store documents in the chain, but only their hash so that they can demonstrate their integrity and the existence of a particular version at a given time. I think Kaspa’s speed and performance could make it a very interesting use case. Is anyone else exploring something similar?
I am convinced that I will have this wonderful community in the future and bring a lot of use to our network.
5 Likes
I like this idea a lot. Just hash the document locally, put that hash or a Merkle root into a Kaspa transaction, and later anyone can verify:
file → hash → proof → Kaspa txid
Where it gets more interesting is when this stops being a one-off timestamp and becomes a real registry.
For example:
- the same document has multiple versions
- an issuer needs to sign or control the seal
- a seal can be superseded or revoked
- many documents are batched together, but each user only reveals their own proof
- a verifier wants a standard proof package instead of manually checking raw tx data
- private documents should stay private, while the public chain only sees commitments
3 Likes
Many simple and complex things can be done using low costs and on a sovereign consensus that will soon be confirming the speed of the Internet, work on it
1 Like