Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

improve explanation of how to verify a document #6

Open
maraoz opened this issue Jun 5, 2014 · 3 comments
Open

improve explanation of how to verify a document #6

maraoz opened this issue Jun 5, 2014 · 3 comments
Labels

Comments

@maraoz
Copy link
Owner

maraoz commented Jun 5, 2014

No description provided.

@maraoz maraoz added the high label Jun 5, 2014
@felipecsl
Copy link

I was curious to know more about this. If you were to verify the existence of a document in the blockchain and coinsecrets.org didn't exist, how would you do about it? Do you have to just keep listening to transactions and analyze their contents, looking for OP_RETURN?
What about transactions that already happened? Would you have to go backwards to look into every single transaction?
BTW cheers for the nice work here!

@maraoz
Copy link
Owner Author

maraoz commented Nov 10, 2014

Yes, you only need the blockchain to prove the existence of the document once the transaction has been introduced into the blockchain. Services like blockchain.info, insight, and coinsecrets, are an easy way to check data in the blockchain, but you don't need to trust those. You can sync the blockchain from the p2p network and look at the transactions there.

@rsvp
Copy link
Contributor

rsvp commented Oct 31, 2015

@maraoz Hi !

I'm working through the API demo where: 15db6dbff590000ea13246e1c166802b690663c4e0635bfca78049d5a8762832
"timestamp":"2015-09-28 18:16:50"
"blockstamp":"2015-09-28 19:32:54"

To verify the above, I searched at blockchain.info for "0x444f4350524f4f4615db6dbff590000ea13246e1c166802b690663c4e0635bfca78049d5a8762832"
per the instructions:

      Find the transaction in the bitcoin blockchain containing an OP_RETURN
      output with the document's hash prepended by our marker bytes which are
      0x444f4350524f4f46 (or 'DOCPROOF' in ascii).

But nothing matches. Could you please clarify the instructions, and link
to a third-party webpage where we can actually see that the transaction
has occurred at said time.

Thanks very much.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants