Jeremy Rand
We should add Cirrus tests for making sure ncdns can resolve Namecoin domains via Namecoin Core and Electrum-NMC (both in Regtest mode). This should be done via direct DNS requests...
ncdns makes available some meta-domains such as `this.x--nmc.bit` and `aia.x--nmc.bit`, which do not require a Namecoin node to resolve. We should test on Cirrus that these domains resolve properly, both...
It would be helpful if the seeder returned an `NS` record, corresponding to the domain name where the seeder is running. This would enable stuff like `dig NS seed.namecoin.libreisp.se` to...
Fixes https://github.com/gombadi/dnsseeder/issues/1 There's still a DNS leak (which I'll fix later), but this can at least establish peer connections over SOCKS, which is an improvement over the status quo.
Is there any reason why dnsseeder doesn't use the btcd/peer package for its connections to the P2P network? Seems like doing so might avoid duplicating code between btcd and dnsseeder.
It would be useful to support a SOCKSv5 proxy (e.g. Tor) for the P2P connections.
Fixes https://github.com/robertwb/bitcoin-taxes/issues/22 (Let me know if this documentation is incorrect.)
As far as I can tell, there's no Python code in the examples or tests folder that utilizes the DataReader API. This is unfortunate, both from a test coverage perspective...
## error log | 日志或报错信息 | ログ ``` $ cd tools/pnnx $ mkdir build $ cd build $ cmake .. CMake Warning (dev) at CMakeLists.txt:7 (project): cmake_minimum_required() should be called...
Visiting https://box86.org/ over Tor, I get "Your IP has been banned. Request blocked due to suspicious activity." Seems to be an OVHcloud misconfiguration. Could you please unblock Tor users?