Daira-Emma Hopwood
Daira-Emma Hopwood
My theory is that `cargo` tries too hard to avoid building a given crate `X` more than once in any given build, even if it's a top-level build. So if...
This works for me with rustc 1.56.1. What versions of rustc and cargo are you using?
> We should consider a "BYO branch ID" mode, where the caller can pass in a consensus branch ID obtained from another source (e.g. a lightwalletd server) to use. This...
Concrete proposal: bit 20 (mask 0x00100000) indicates whether a consensus branch ID requires wallet support other than just changing the ID. This bit happens to be set for Sapling, Blossom,...
In Engineering Mob, @str4d mentioned that he wanted to do something more complicated that would make it harder for uncooperative forks to end up choosing a consensus branch ID in...
This only seems interesting because [Ledger apparently ran into it as a divergence between Zebra and zcashd `getrawtransaction` output](https://github.com/ZcashFoundation/zebra/issues/9671). Zcash launched well after P2PKH and P2SH became the commonly used...
The output that triggered the report was an early (mainnet block height 5) CPU mining output: https://github.com/ZcashFoundation/zebra/issues/9671#issuecomment-3094535121 The zcashd CPU miner [stopped producing such outputs](https://github.com/zcash/zcash/pull/1965) (in favour of P2PKH) in...
Ok, any further changes are just editorial. I think this can be closed for now.
This is due to a violation of the following [block consensus rule](https://zips.z.cash/protocol/protocol.pdf#blockheader): > For each block at block height 2 or greater on Mainnet, or block height 653606 or greater...
This is unlikely to be fixed within the remaining life of zcashd, especially as this only applies to a platform that is less commonly used to run servers and is...