rich1.0npub1tfk373zg9dnmtvxnpnq7s2dkdgj37rwfj3yrwld7830qltmv8qps8rfq0nhttps://nostr.ae/npub1tfk373zg9dnmtvxnpnq7s2dkdgj37rwfj3yrwld7830qltmv8qps8rfq0nnjumphttps://nostr.ae📅 Original date posted:2016-05-11 📝 Original message:On Wednesday, May 11, 2016 12:20:55 PM Sergio Demian Lerner via bitcoin-dev wrote: > On Tue, May 10, 2016 at 6:43 PM, Sergio Demian Lerner < > sergio.d.lerner at gmail.com> wrote: > > You can find it here: > > https://bitslog.wordpress.com/2014/03/18/the-re-design-of-the-bitcoin-blo > > ck-header/ > > > > Basically, the idea is to put in the first 64 bytes a 4 byte hash of the > > second 64-byte chunk. That design also allows increased nonce space in > > the first 64 bytes. > > My mistake here. I didn't recalled correctly my own idea. The idea is to > include in the second 64-byte chunk a 4-byte hash of the first chunk, not > the opposite. What if we XOR bytes 64..76 with the first 12 bytes of the SHA2 midstate? Would that work? Luke