From the Whitepaper: Timestamps prove that the data must have existed at the time"

From the Whitepaper: Timestamps prove that the data must have existed at the time"

The whitepaper says exactly this: "The timestamp proves that the data must have existed at the time, obviously, in order to get into the hash. Each timestamp includes the previous timestamp in its hash, forming a chain, with each additional timestamp reinforcing the ones before it."

It seems to me that you could put any time you want in the timestamp. Is it the next sentence about "reinforcing" that is key to his meaning?

http://ift.tt/2C8p6c7

Comments

Post a Comment

Popular posts from this blog

How to discover startup flags or command-line options for bitcoind?

How to discover startup flags or command-line options for bitcoind? I'd like to query the Bitcoin daemon (bitcoind) to find out what startup flags (command-line options) were sent to it on startup (or the current state if it has changed, e.g. -server=0/1 changing). For example, I may want to know if -addresstype, -disablewallet, -rescan, or -uacomment=<cmt> or some other flag has been set. Or for Namecoin, it would be very useful to know if -namehistory has been set. Is there an RPC or any other method to find out? Or, to ask the question a different way... src/bitcoind.cpp's bool AppInit(int argc, char* argv[]) method calls ParseParameters(argc, argv);, which is in src/util.cpp. In src/util.cpp we have: map<string, string> mapArgs; static map<string, vector<string> > _mapMultiArgs; const map<string, vector<string> >& mapMultiArgs = _mapMultiArgs; To store flags/options/args. I'd basically just like to get whatever is in tho...
Read more

How to use Bitssa to your advantage?

How to use Bitssa to your advantage? Bitssa is a global multi-cryptocurrency exchange that provides you the unique opportunity to trade your cryptocurrency with cryptocurrency and also fiat currency with cryptocurrency. All you need to do is sign up on Bitssa , complete the registration formality, create a wallet address and start trading on the market page. Get wallet free of cost as soon as you signup with bitssa . We are not makers and takers our users decide the price on the exchange. Instant execution of your orders as soon as your price matches. Try Bitssa and you will love it. Also, For better experience, try the Bitssa mobile app. https://ift.tt/2LvrgC7
Read more

Bitcoin HD Wallets with hardened derivation and watch-only addresses

Bitcoin HD Wallets with hardened derivation and watch-only addresses I'm learning about the details of how HD wallets work. After reading the BIP32 and BIP44 documents thoroughly and supplementing it with Mastering Bitcoin there's still on aspect that I can't figure out. Say I derive an extended private key with the BIP44 first account, first address path path: m/44'/0'/0'/0/0 and then I convert the extended private key into an extended public key. Based on what I've read so far proper way would be to take the extended public key and work with an entirely non-hardened path like: M/0/1 , M/0/2 ? Is this the correct way to do it ? My problem is that a public key of M/44'/0'/0'/0/1 will not be the same as M/0/1. I'm just trying to make sure I'm using the derivation paths correctly. Thanks a lot! http://bit.ly/2DpBKlI
Read more