{"type":"rich","version":"1.0","author_name":"npub1fvuxqdqg7klqqgy3yy8gdxjv4phu92sll5y8zqm2qe5qdrhxymhqf3vq7f","author_url":"https://nostr.ae/npub1fvuxqdqg7klqqgy3yy8gdxjv4phu92sll5y8zqm2qe5qdrhxymhqf3vq7f","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2016-05-11\n📝 Original message:On Tue, May 10, 2016 at 6:43 PM, Sergio Demian Lerner \u003c\nsergio.d.lerner at gmail.com\u003e wrote:\n\n\u003e\n\u003e\n\u003e You can find it here:\n\u003e https://bitslog.wordpress.com/2014/03/18/the-re-design-of-the-bitcoin-block-header/\n\u003e\n\u003e Basically, the idea is to put in the first 64 bytes a 4 byte hash of the\n\u003e second 64-byte chunk. That design also allows increased nonce space in the\n\u003e first 64 bytes.\n\u003e\n\u003e My mistake here. I didn't recalled correctly my own idea. The idea is to\ninclude in the second 64-byte chunk a 4-byte hash of the first chunk, not\nthe opposite.\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20160511/b0e9c92b/attachment.html\u003e"}
