{"type":"rich","version":"1.0","author_name":"npub1tfk373zg9dnmtvxnpnq7s2dkdgj37rwfj3yrwld7830qltmv8qps8rfq0n","author_url":"https://nostr.ae/npub1tfk373zg9dnmtvxnpnq7s2dkdgj37rwfj3yrwld7830qltmv8qps8rfq0n","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2016-05-11\n📝 Original message:On Wednesday, May 11, 2016 12:20:55 PM Sergio Demian Lerner via bitcoin-dev \nwrote:\n\u003e On Tue, May 10, 2016 at 6:43 PM, Sergio Demian Lerner \u003c\n\u003e sergio.d.lerner at gmail.com\u003e wrote:\n\u003e \u003e You can find it here:\n\u003e \u003e https://bitslog.wordpress.com/2014/03/18/the-re-design-of-the-bitcoin-blo\n\u003e \u003e ck-header/\n\u003e \u003e \n\u003e \u003e Basically, the idea is to put in the first 64 bytes a 4 byte hash of the\n\u003e \u003e second 64-byte chunk. That design also allows increased nonce space in\n\u003e \u003e the first 64 bytes.\n\u003e \n\u003e My mistake here. I didn't recalled correctly my own idea. The idea is to\n\u003e include in the second 64-byte chunk a 4-byte hash of the first chunk, not\n\u003e the opposite.\n\nWhat if we XOR bytes 64..76 with the first 12 bytes of the SHA2 midstate? \nWould that work?\n\nLuke"}