Bitcoin Forum
July 31, 2024, 08:15:27 PM *
News: Help 1Dq create 15th anniversary forum artwork.
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: del  (Read 399 times)
danielW (OP)
Sr. Member
****
Offline Offline

Activity: 277
Merit: 255


View Profile
October 30, 2017, 08:18:06 AM
Last edit: June 14, 2018, 08:24:22 PM by danielW
 #1

del
amaclin1
Sr. Member
****
Offline Offline

Activity: 826
Merit: 313


View Profile
October 30, 2017, 10:07:30 AM
 #2

I.e. If I wanted to re-implement this myself what would I need to do?
I think you should hire Peter Todd or ask him what to do.  Grin

Quote
but still dont know how open timestamps actually works.
Hmmmm...
Have a look to https://app.originstamp.org/home
Let us call it "close timestamps" contrary to "open timestamps"
I think it is not very hard to compare these two projects and understand the technique.
If no, you must give up and switch to something else.
haltingprobability
Member
**
Offline Offline

Activity: 98
Merit: 26


View Profile
November 03, 2017, 04:35:17 AM
Last edit: November 03, 2017, 05:02:06 AM by haltingprobability
 #3

I'm guessing that they create an unspendable output with an OP_RETURN which allows you to embed arbitrary data in a transaction. So, they can aggregate a bunch of individual hashes into a single hash, then submit a Bitcoin transaction to an unspendable output with OP_RETURN that contains the literal bytes of the aggregated hash. So, for the cost of about 70-80 bytes or so (assuming compressed signatures), you can embed an unbounded number of hashes into a Bitcoin block, thus timestamping all of those hashes with that block.
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!