diff options
| author | Wladimir J. van der Laan <laanwj@protonmail.com> | 2019-09-16 13:14:46 +0200 |
|---|---|---|
| committer | Wladimir J. van der Laan <laanwj@protonmail.com> | 2019-09-16 13:15:05 +0200 |
| commit | eb812257a3fd2b829131f9fead71ab030e87d9e7 (patch) | |
| tree | 3e55b5a9d29a89f11d0153621bafe377e50a40dd /test/functional/rpc_users.py | |
| parent | 871d3ae45b642c903ed9c54235c09d62f6cf9a16 (diff) | |
| parent | 82e53f37e1bfa6e34eac16b33329d70c3c0127da (diff) | |
Merge #16847: doc: add comments clarifying how local services are advertised
82e53f37e1bfa6e34eac16b33329d70c3c0127da doc: add comments clarifying how local services are advertised (James O'Beirne)
Pull request description:
Recent questions have come up regarding dynamic service registration
(see https://github.com/bitcoin/bitcoin/pull/16442#discussion_r308702676
and the assumeutxo project ~~which needs to dynamically flip NODE_NETWORK~~).
While investigating how dynamic service registration might work, I was
confused about how we convey local services to peers. This adds some
documentation that hopefully clarifies this process.
ACKs for top commit:
laanwj:
ACK 82e53f37e1bfa6e34eac16b33329d70c3c0127da
darosior:
ACK 82e53f37e1bfa6e34eac16b33329d70c3c0127da
Tree-SHA512: a30c1020387d7a75b5b3cdde45f8b7f2ae46293da97e6227b2ee17e290b93deb5b16c0bbc2b1676972300e5c3c2ad74eb8b3910d6b93e028dac1ae2700468ef9
Diffstat (limited to 'test/functional/rpc_users.py')
0 files changed, 0 insertions, 0 deletions