diff options
| author | James O'Beirne <james.obeirne@gmail.com> | 2019-09-10 13:09:12 -0400 |
|---|---|---|
| committer | James O'Beirne <james.obeirne@gmail.com> | 2019-09-11 10:24:44 -0400 |
| commit | 82e53f37e1bfa6e34eac16b33329d70c3c0127da (patch) | |
| tree | f65e290eca64080b3e33370f37b26eebcff4c031 /test/functional/rpc_users.py | |
| parent | 1985c4efda56b48f6f9c04f39d69268ee8f0b40a (diff) | |
doc: add comments clarifying how local services are advertised
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.
Diffstat (limited to 'test/functional/rpc_users.py')
0 files changed, 0 insertions, 0 deletions