cryptogera/litecoin
cryptogera/litecoin
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
litecoin/src/interfaces
History
Russell Yanofsky ab31b9d6fe Fix wallet unload race condition 
Currently it's possible for ReleaseWallet to delete the CWallet pointer while
it is processing BlockConnected, etc chain notifications.

To fix this, unregister from notifications earlier in UnloadWallet instead of
ReleaseWallet, and use a new RegisterSharedValidationInterface function to
prevent the CValidationInterface shared_ptr from being deleted until the last
notification is actually finished.
2020-03-27 15:17:35 +00:00
..
chain.cpp
Fix wallet unload race condition
2020-03-27 15:17:35 +00:00
chain.h
Fix wallet unload race condition
2020-03-27 15:17:35 +00: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: Change createWallet, fillPSBT argument order
2020-03-19 15:26:04 -05:00
node.h
refactor: Change createWallet, fillPSBT argument order
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: Change createWallet, fillPSBT argument order
2020-03-19 15:26:04 -05:00
wallet.h
refactor: Change createWallet, fillPSBT argument order
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.