diff options
| author | MarcoFalke <falke.marco@gmail.com> | 2018-09-18 19:49:24 -0400 |
|---|---|---|
| committer | MarcoFalke <falke.marco@gmail.com> | 2018-09-18 19:50:00 -0400 |
| commit | d26278988fbfc71dc558f7b2c60a184e8091450b (patch) | |
| tree | a45ac6290c3c430b546c83a6aa5b7e51ffb0d3d7 /share | |
| parent | 24f095df4506c599fe770309efd1c5b8048420e5 (diff) | |
| parent | a2eb6f540538d32725aecf678301a96247db6fd9 (diff) | |
Merge #13152: [rpc] Add getnodeaddresses RPC command
a2eb6f5405 [rpc] Add getnodeaddresses RPC command (chris-belcher)
Pull request description:
Implements issue https://github.com/bitcoin/bitcoin/issues/9463
New getnodeaddresses call gives access via RPC to the peers known by the node. It may be useful for bitcoin wallets to broadcast their transactions over tor for improved privacy without using the centralized DNS seeds. getnodeaddresses is very similar to the getaddr p2p method.
Please advise me on the best approach for writing an automated test. By my reading the getaddr p2p method also isn't really tested.
Tree-SHA512: ad03abf518847476495b76a2f5394b8030aa86654429167fa618e21460abb505c10ef9817ec1b80472320d41d0aff5dc94a8efce023aaaaf5e81386aa92b852b
Diffstat (limited to 'share')
0 files changed, 0 insertions, 0 deletions