Jeremy Rand
> Latest Bitcoin Core master (and Namecoin Core with it) makes both of the above problems a fatal error that prevents launching at all. This symptom is probably a blocker...
Suggested mitigation strategy: 1. v28.0: Switch the incoming onion port. This resolves the immediate v28.0 blocker. It shouldn't cause a partition since virtually no one is exclusively connecting to onion...
OK, so my suggestion is that we use port `8534` as the new RPC port, port `8535` as the new P2P port, and `8536` as the new onion port. Rationale:...
OK thanks.
https://github.com/namecoin/namecoin-core/pull/562 removes the seed. I'm going to leave this issue open as a reminder to add a new seed once @jonasbits sets one up.
Thanks Rose! I'll review this in the next couple days.
Per discussion in the #namecoin-dev meeting last month, this PR is on hold to avoid colliding with ongoing collaboration with Q and IETF.
OK so initial reaction: the XML form changes here are really hard to review because there's too much happening in a single commit. For example, the text `Use <strong>d/</strong> prefix...
Based on code review of 7c1b67d50567e974053ce0a4b0b5fcc818d1f8fd, only a few small issues (see review above). Also please change the commit message to something more descriptive. I'll do a final round of...
> Should I fix the issues highlighted above now, or is it better if I wait for your final checks on the PR? @junekomeiji Feel free to fix them now.