Retropex/bitcoin
1
0
Fork 0
mirror of https://github.com/Retropex/bitcoin.git synced 2025-08-04 05:54:48 +02:00
Code Issues Actions Packages Projects Releases Wiki Activity
a6d1ab8caa
bitcoin/src/interfaces
History
Andrew Chow dc174881ad Replace GetSigningProvider with GetSolvingProvider 
Not all ScriptPubKeyMans will be able to provide private keys,
but pubkeys and scripts should be. So only provide public-only
SigningProviders, i.e. ones that can help with Solving.
2020-03-09 11:16:20 -04:00
..
chain.cpp scripted-diff: Bump copyright of files changed in 2020 2020-01-15 02:18:00 +07:00
chain.h scripted-diff: Bump copyright of files changed in 2020 2020-01-15 02:18:00 +07: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 scripted-diff: Bump copyright of files changed in 2020 2020-01-15 02:18:00 +07: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 Replace GetSigningProvider with GetSolvingProvider 2020-03-09 11:16:20 -04:00
wallet.h Replace GetSigningProvider with GetSolvingProvider 2020-03-09 11:16:20 -04: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.