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
Andrew Chow 2bc4c3eaf9 Notify the GUI that the keypool has changed to set the receive button 
Whenever the keypool changes (new keys generated, new seed set,
keypool runs out, etc.), notify the GUI that the keypool has changed. The
receive button can then be enabled and disabled as necessary.
2019-01-23 15:18:03 -05:00
..
chain.cpp Remove uses of cs_main in wallet code 2018-11-06 11:44:40 -04:00
chain.h Remove uses of cs_main in wallet code 2018-11-06 11:44:40 -04:00
handler.cpp scripted-diff: Move util files to separate directory. 2018-11-04 22:46:07 -08:00
handler.h scripted-diff: Avoid interface keyword to fix windows gitian build 2018-04-07 03:42:02 -04:00
node.cpp net: move BanMan to its own files 2019-01-16 13:54:18 -05:00
node.h net: move BanMan to its own files 2019-01-16 13:54:18 -05:00
README.md Add skeleton chain and client classes 2018-11-06 11:44:40 -04:00
wallet.cpp Notify the GUI that the keypool has changed to set the receive button 2019-01-23 15:18:03 -05:00
wallet.h Notify the GUI that the keypool has changed to set the receive button 2019-01-23 15:18:03 -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 #10973.

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

  • 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.