Jeremy Rand
Potential blockers: * https://github.com/namecoin/namecoin-core/issues/545 * Making sure Guix builds succeed and are reproducible. * Asking our QA team to briefly try the Guix binaries.
Other potential blockers: * Making sure Guix builds on ppc64le are reproducible with x86_64. * Update the seed node list.
@domob1812 can you cherry-pick https://github.com/namecoin/namecoin-core/pull/553 and https://github.com/namecoin/namecoin-core/pull/557 to the `28.x` branch? Other remaining blockers for tagging 28.0: * Making sure Guix builds on ppc64le are reproducible with x86_64. * This...
Based on discussion with upstream, I'm not going to block a 28.0 release on ppc64le build arch reproducibility. We will try to have this sorted out for 29.0. Given the...
Fixed merge conflict; feel free to review.
> Tor has some well-audited logic for creating circuits in advance without leaking shared state; I intend to copy their logic for Electrum's usage Correction -- I just talked to...
This PR now creates a pool of clean Interfaces for use by stream-isolated commands, which eliminates the latency issue. I've also added support for the remaining commands where stream isolation...
Alright, works for me. I'll see if I can send in a PR for removing the FIXME comment.
> > Do I have this right? Thoughts on what we should do? > > I'd really recommend not going our route of rebranding them - it actually causes confusion...
We should presumably check the P2P IP, P2P onion, and RPC ports for testnet and regtest for conflicts as well.