Russell Yanofsky
ea961c3d72
Route calls during node initialization and shutdown that would happen between a node process and wallet processes through the serializable `Chain::Client` interface, rather than `WalletInitInterface` which is now simpler and only deals with early initialization and parameter interaction. This commit mostly does not change behavior. The only change is that the "Wallet disabled!" and "No wallet support compiled in!" messages are now logged earlier during startup.
65 lines
1.8 KiB
C++
65 lines
1.8 KiB
C++
// Copyright (c) 2018 The Bitcoin Core developers
|
|
// Distributed under the MIT software license, see the accompanying
|
|
// file COPYING or http://www.opensource.org/licenses/mit-license.php.
|
|
|
|
#ifndef BITCOIN_INTERFACES_CHAIN_H
|
|
#define BITCOIN_INTERFACES_CHAIN_H
|
|
|
|
#include <memory>
|
|
#include <string>
|
|
#include <vector>
|
|
|
|
class CScheduler;
|
|
|
|
namespace interfaces {
|
|
|
|
//! Interface for giving wallet processes access to blockchain state.
|
|
class Chain
|
|
{
|
|
public:
|
|
virtual ~Chain() {}
|
|
};
|
|
|
|
//! Interface to let node manage chain clients (wallets, or maybe tools for
|
|
//! monitoring and analysis in the future).
|
|
class ChainClient
|
|
{
|
|
public:
|
|
virtual ~ChainClient() {}
|
|
|
|
//! Register rpcs.
|
|
virtual void registerRpcs() = 0;
|
|
|
|
//! Check for errors before loading.
|
|
virtual bool verify() = 0;
|
|
|
|
//! Load saved state.
|
|
virtual bool load() = 0;
|
|
|
|
//! Start client execution and provide a scheduler.
|
|
virtual void start(CScheduler& scheduler) = 0;
|
|
|
|
//! Save state to disk.
|
|
virtual void flush() = 0;
|
|
|
|
//! Shut down client.
|
|
virtual void stop() = 0;
|
|
};
|
|
|
|
//! Return implementation of Chain interface.
|
|
std::unique_ptr<Chain> MakeChain();
|
|
|
|
//! Return implementation of ChainClient interface for a wallet client. This
|
|
//! function will be undefined in builds where ENABLE_WALLET is false.
|
|
//!
|
|
//! Currently, wallets are the only chain clients. But in the future, other
|
|
//! types of chain clients could be added, such as tools for monitoring,
|
|
//! analysis, or fee estimation. These clients need to expose their own
|
|
//! MakeXXXClient functions returning their implementations of the ChainClient
|
|
//! interface.
|
|
std::unique_ptr<ChainClient> MakeWalletClient(Chain& chain, std::vector<std::string> wallet_filenames);
|
|
|
|
} // namespace interfaces
|
|
|
|
#endif // BITCOIN_INTERFACES_CHAIN_H
|