mirror of https://github.com/bitcoin/bitcoin.git synced 2026-01-21 07:39:08 +01:00

Files

Russell Yanofsky 77e4b06572 refactor: Get rid of Wallet::IsWalletFlagSet method

Replace by privateKeysDisabled method to avoid need for GUI to reference
internal wallet flags.

Also remove adjacent WalletModel canGetAddresses wrapper that serves no purpose
and make Wallet::canGetAddresses non-const so it can be implemented by IPC
classes in #10102.

2020-03-19 15:26:04 -05:00

chain.cpp

[validation interface] Remove vtxConflicted from BlockConnected

2020-03-11 18:38:33 -04:00

chain.h

[validation interface] Remove vtxConflicted from BlockConnected

2020-03-11 18:38:33 -04: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

[mempool] Remove NotifyEntryAdded and NotifyEntryRemoved callbacks

2020-03-11 18:38:33 -04:00

node.h

scripted-diff: Bump copyright of files changed in 2019

2019-12-30 10:42:20 +13: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.