mirror of https://github.com/bitcoin/bitcoin.git synced 2025-12-04 17:52:25 +01:00

Files

Russell Yanofsky 642ad31b41 Add loadwallet and createwallet RPC load_on_startup options

This maintains a persistent list of wallets stored in settings that will
automatically be loaded on startup. Being able to load a wallet automatically
on startup will be more useful in the GUI when the option to create wallets is
added in #15006, but it's reasonable to expose this feature by RPC as well.

2020-08-13 09:44:48 -04:00

chain.cpp

Add loadwallet and createwallet RPC load_on_startup options

2020-08-13 09:44:48 -04:00

chain.h

Add loadwallet and createwallet RPC load_on_startup options

2020-08-13 09:44:48 -04:00

handler.cpp

scripted-diff: Bump copyright headers

2020-04-16 13:33:09 -04:00

handler.h

scripted-diff: Bump copyright headers

2020-04-16 13:33:09 -04:00

node.cpp

Add BlockAndHeaderTipInfo to the node interface/appInit

2020-08-12 16:44:06 +02:00

node.h

Add BlockAndHeaderTipInfo to the node interface/appInit

2020-08-12 16:44:06 +02:00

README.md

Suggested interfaces::Chain cleanups from #15288

2019-03-04 15:57:58 -05:00

wallet.cpp

wallet: Pass unused args to StartWallets

2020-07-09 13:07:37 +02:00

wallet.h

Merge #19396 : refactor: Remove confusing OutputType::CHANGE_AUTO

2020-07-02 16:10:49 +02: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.