Jeremy Rand
> Isn't this something for upstream Bitcoin? @domob1812 Theoretically yes, but in practice they won't care because Bitcoin legacy addresses start with 1 or 3, while uppercase Bitcoin Bech32 addresses...
@domob1812 As I alluded to on the forum, there are some edge cases introduced by P2SH and SegWit (mostly SegWit) that I'd like to make sure we have test cases...
> In addition, the activation of the soft forks should not by itself cause any issues even if there were bugs. We only need to make sure that all interactions...
@domob1812 AFAIK the softforks activated here are P2SH, CSV, and SegWit, correct? Are there any others? P2SH and SegWit now have unit tests to verify that they don't misbehave with...
@YihaoPeng @wangchun Just checking, have BTC.COM and F2Pool upgraded to Namecoin Core 0.18.0 yet? (I'm reaching out to mining pools to gauge how much hashrate has already upgraded.)
@YihaoPeng All of BTC.com's Namecoin blocks today have been valid (followed the softfork correctly) except for the most recent two, block hashes `aa90328f456dc560da1291f78c32e48b20009808d5e2bb482914818e7af8c9c8` and `4d6b4840cc84e7e4a83eebf0a34754e6439a52b5dc008000a4c6b911d00a87c6`. Can you please check your...
> I am currently using the Windows version 13.99 with the QT GUI. Will this be affected? I use it mainly for domains. @jrkenn 0.13.99 will not enforce the softfork,...
Foxyproxy will almost certainly cause problems, because it uses the same method of forcing proxy usage that FreeSpeechMe uses. It might be possible to work around it by making FreeSpeechMe...
@domob1812 Thoughts on this proposal? My understanding from talking to @brandonrobertz is that the `minConf` field mentioned in this proposal is blocking some improvements on the Qt name tab. (Brandon...
> Thus, what about the following three encoding options: @domob1812 ACK, as long as ASCII is the default (with the possibility that we might switch to hex being the default...