phantom/bitcoin
1
0
Fork 0
mirror of https://github.com/bitcoin/bitcoin.git synced 2025-01-27 19:47:30 -03:00
Code Issues Projects Releases Packages Wiki Activity Actions 1
bitcoin/src/interfaces
History
Russell Yanofsky 6ceb21909c refactor: Rename Chain::Notifications methods to be consistent with other interfaces methods 
This also simplifies #10102 removing overrides needed to deal with inconsistent
case convention
2020-03-19 15:26:04 -05:00
..
chain.cpp refactor: Rename Chain::Notifications methods to be consistent with other interfaces methods 2020-03-19 15:26:04 -05:00
chain.h refactor: Rename Chain::Notifications methods to be consistent with other interfaces methods 2020-03-19 15:26:04 -05:00
handler.cpp scripted-diff: Bump copyright of files changed in 2020 2020-01-15 02:18:00 +07:00
handler.h scripted-diff: Bump copyright of files changed in 2020 2020-01-15 02:18:00 +07:00
node.cpp refactor: Rename Node::disconnect methods 2020-03-19 15:26:04 -05:00
node.h refactor: Rename Node::disconnect methods 2020-03-19 15:26:04 -05:00
README.md Suggested interfaces::Chain cleanups from #15288 2019-03-04 15:57:58 -05:00
wallet.cpp refactor: Get rid of Wallet::IsWalletFlagSet method 2020-03-19 15:26:04 -05:00
wallet.h refactor: Get rid of Wallet::IsWalletFlagSet method 2020-03-19 15:26:04 -05:00

README.md

Internal c++ interfaces

The following interfaces are defined here:

  • Chain — used by wallet to access blockchain and mempool state. Added in #14437, #14711, #15288, and #10973.

  • ChainClient — used by node to start & stop Chain clients. Added in #14437.

  • Node — used by GUI to start & stop bitcoin node. Added in #10244.

  • Wallet — used by GUI to access wallets. Added in #10244.

  • Handler — returned by handleEvent methods on interfaces above and used to manage lifetimes of event handlers.

  • Init — used by multiprocess code to access interfaces above on startup. Added in #10102.

The interfaces above define boundaries between major components of bitcoin code (node, wallet, and gui), making it possible for them to run in different processes, and be tested, developed, and understood independently. These interfaces are not currently designed to be stable or to be used externally.