-
Notifications
You must be signed in to change notification settings - Fork 6
submit hashes doesn't get the proof on ethereum #3
Comments
At this moment we do not anchor hashes to the Ethereum blockchain, we anchor to our Chainpoint Calendar and to the Bitcoin blockchain. Based on what you described, if you are writing data to Ethereum and then you want to submit a hash of that data to the Chainpoint Network that is a possible path for you to take. The Chainpoint Network pays all Bitcoin anchoring fees. I'm closing this as its not a bug, but a question. Please feel free to use our support system in the future for similar questions: Cheers |
Thanks for quick response. One last question, where is the transaction address on bitcoin blockchain for the proof? I can only see an anchor id on verifying response. anything returned i can use to search on https://www.blockchain.com/explorer? |
Using the |
I'll look into it, thanks so much! |
You can also take a look at this RunKit example which demonstrates verifying a proof directly with Bitcoin (without asking a Chainpoint Node to verify): https://runkit.com/tierion/verify-a-chainpoint-proof-directly-using-bitcoin |
I just followed readme sample code to test the functionalities, what I've done is that I used a sha256 library to hash some json data to strings, then submit to calendar via this library, now after 10 hr, when I call getproof(), it only show me cal and btc completed. not eth. we are working on an ethereum project, we need to write some data proofs on ethereum platform so the end user can verify these data later. My question is:
The text was updated successfully, but these errors were encountered: