if you want to "notarize" a hash of some data, maybe just predefine a string representation, say "CliveBoultonCoin source hash of file "mySpecialFiles.zip" is sha2-256:Qmhsu4jdb3idntjeh4hebdk3nckf9blahblahblahblah" and make sure your storage period requirements are low enough or else use more bits or more quantum/cryotocurrency proof hashing. Especially don't use double sha256 to notarize anything important.
You can notarize strings for free on bitcoin using Todd's project. Likely you don't want a private perkeep instance, unless it's very well federated/duplicated between a circle of dependants, who might catch CryptoLocker all at once. Or you care only about correctness, but not about potential loss? If you want to long term store data, if it updates frequently / needs crypto coin integration maybe rather evaluate IPFS. Mostly relevant example: https://stackoverflow.com/questions/40998621/how-to-create-an-ipfs-compatible-multihash -- You received this message because you are subscribed to the Google Groups "Perkeep" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
