Higher level wallet functions which can be used by callers to operate on the wallet, as well as helpers to invoke and instantiate wallets and listeners
lower-level wallet functions which build upon core::libtx to perform wallet operations
This module contains old slate versions and conversions to the newest slate version Used for serialization and deserialization of slates in a backwards compatible way. Versions earlier than V2 are removed for the 2.0.0 release, but versioning code remains for future needs
Map of named accounts to BIP32 paths
Holds the context for a single aggsig transaction
Node version info
Information about an output that's being tracked by the wallet. Must be enough to reconstruct the commitment associated with the ouput when the root private key is known.
Public data for each participant in the slate
Public message data (for serialising and storage)
A 'Slate' is passed around to all parties to build up all of the public transaction data needed to create a finalized transaction. Callers can pass the slate around by whatever means they choose, (but we can provide some binary or JSON serialization helpers here).
Optional transaction information, recorded when an event happens to add or remove funds from a wallet. One Transaction log entry maps to one or many outputs
Dummy wrapper for the hex-encoded serialized transaction.
a contained wallet info struct, so automated tests can parse wallet info can add more fields here over time as needed
Wallet errors, mostly wrappers around underlying crypto or I/O errors.
Status of an output that's being tracked by the wallet. Can either be unconfirmed, spent, unspent, or locked (when it's been used to generate a transaction but we don't have confirmation that the transaction was broadcasted or mined).
Types of transactions that can be contained within a TXLog entry
Encapsulate all wallet-node communication functions. No functions within libwallet should care about communication details
TODO: Wallets should implement this backend for their storage. All functions here expect that the wallet instance has instantiated itself or stored whatever credentials it needs
Combined trait to allow dynamic wallet dispatch
Batch trait to update the output data backend atomically. Trying to use a batch after commit MAY result in a panic. Due to this being a trait, the commit method can't take ownership. TODO: Should these be split into separate batch objects, for outputs, tx_log entries and meta/details?
Check / repair wallet contents assume wallet contents have been freshly updated with contents of latest block
Restore a wallet