Struct epic_wallet_api::Owner [−][src]
pub struct Owner<L, C, K> where
L: WalletLCProvider<'static, C, K> + 'static,
C: NodeClient + 'static,
K: Keychain + 'static, {
pub wallet_inst: Arc<Mutex<Box<dyn WalletInst<'static, L, C, K>>>>,
pub doctest_mode: bool,
pub shared_key: Arc<Mutex<Option<SecretKey>>>,
pub updater_running: Arc<AtomicBool>,
// some fields omitted
}
Expand description
Main interface into all wallet API functions. Wallet APIs are split into two seperate blocks of functionality called the ‘Owner’ and ‘Foreign’ APIs
- The ‘Owner’ API is intended to expose methods that are to be used by the wallet owner only. It is vital that this API is not exposed to anyone other than the owner of the wallet (i.e. the person with access to the seed and password.
Methods in both APIs are intended to be ‘single use’, that is to say each method will ‘open’ the wallet (load the keychain with its master seed), perform its operation, then ‘close’ the wallet (unloading references to the keychain and master seed).
Fields
wallet_inst: Arc<Mutex<Box<dyn WalletInst<'static, L, C, K>>>>
contain all methods to manage the wallet
doctest_mode: bool
Flag to normalize some output during testing. Can mostly be ignored.
Share ECDH key
updater_running: Arc<AtomicBool>
Stop state for update thread
Implementations
impl<L, C, K> Owner<L, C, K> where
L: WalletLCProvider<'static, C, K> + 'static,
C: NodeClient,
K: Keychain,
impl<L, C, K> Owner<L, C, K> where
L: WalletLCProvider<'static, C, K> + 'static,
C: NodeClient,
K: Keychain,
Create a new API instance with the given wallet instance. All subsequent API calls will operate on this instance of the wallet.
Each method will call the WalletBackend
’s
open_with_credentials
(initialising a keychain with the master seed,) perform its operation, then close the keychain
with a call to close
Arguments
wallet_in
- A reference-counted mutex containing an implementation of theWalletBackend
trait.
Returns
- An instance of the OwnerApi holding a reference to the provided wallet
Example
use epic_wallet_util::epic_keychain as keychain;
use epic_wallet_util::epic_util as util;
use epic_wallet_api as api;
use epic_wallet_config as config;
use epic_wallet_impls as impls;
use epic_wallet_libwallet as libwallet;
use keychain::ExtKeychain;
use tempfile::tempdir;
use std::sync::Arc;
use util::{Mutex, ZeroingString};
use api::Owner;
use config::WalletConfig;
use impls::{DefaultWalletImpl, DefaultLCProvider, HTTPNodeClient};
use libwallet::WalletInst;
let mut wallet_config = WalletConfig::default();
// A NodeClient must first be created to handle communication between
// the wallet and the node.
let node_client = HTTPNodeClient::new(&wallet_config.check_node_api_http_addr, None);
// impls::DefaultWalletImpl is provided for convenience in instantiating the wallet
// It contains the LMDBBackend, DefaultLCProvider (lifecycle) and ExtKeychain used
// by the reference wallet implementation.
// These traits can be replaced with alternative implementations if desired
let mut wallet = Box::new(DefaultWalletImpl::<'static, HTTPNodeClient>::new(node_client.clone()).unwrap())
as Box<WalletInst<'static, DefaultLCProvider<HTTPNodeClient, ExtKeychain>, HTTPNodeClient, ExtKeychain>>;
// Wallet LifeCycle Provider provides all functions init wallet and work with seeds, etc...
let lc = wallet.lc_provider().unwrap();
// The top level wallet directory should be set manually (in the reference implementation,
// this is provided in the WalletConfig)
let _ = lc.set_top_level_directory(&wallet_config.data_file_dir);
// Wallet must be opened with the password (TBD)
let pw = ZeroingString::from("wallet_password");
lc.open_wallet(None, pw, false, false);
// All wallet functions operate on an Arc::Mutex to allow multithreading where needed
let mut wallet = Arc::new(Mutex::new(wallet));
let api_owner = Owner::new(wallet.clone());
// .. perform wallet operations
Returns a list of accounts stored in the wallet (i.e. mappings between user-specified labels and BIP32 derivation paths.
Arguments
keychain_mask
- Wallet secret mask to XOR against the stored wallet seed before using, if being used.
Returns
- Result Containing:
- A Vector of
AcctPathMapping
data - or
libwallet::Error
if an error is encountered.
Remarks
- A wallet should always have the path with the label ‘default’ path defined, with path m/0/0
- This method does not need to use the wallet seed or keychain.
Example
Set up as in new
method above.
let api_owner = Owner::new(wallet.clone());
let result = api_owner.accounts(None);
if let Ok(accts) = result {
//...
}
Creates a new ‘account’, which is a mapping of a user-specified label to a BIP32 path
Arguments
keychain_mask
- Wallet secret mask to XOR against the stored wallet seed before using, if being used.label
- A human readable label to which to map the new BIP32 Path
Returns
- Result Containing:
- A Keychain Identifier for the new path
- or
libwallet::Error
if an error is encountered.
Remarks
-
Wallets should be initialised with the ‘default’ path mapped to
m/0/0
-
Each call to this function will increment the first element of the path so the first call will create an account at
m/1/0
and the second atm/2/0
etc. . . -
The account path is used throughout as the parent key for most key-derivation operations. See
set_active_account
for further details. -
This function does not need to use the root wallet seed or keychain.
Example
Set up as in new
method above.
let api_owner = Owner::new(wallet.clone());
let result = api_owner.create_account_path(None, "account1");
if let Ok(identifier) = result {
//...
}
Sets the wallet’s currently active account. This sets the BIP32 parent path used for most key-derivation operations.
Arguments
keychain_mask
- Wallet secret mask to XOR against the stored wallet seed before using, if being used.label
- The human readable label for the account. Accounts can be retrieved via theaccount
method
Returns
- Result Containing:
Ok(())
if the path was correctly set- or
libwallet::Error
if an error is encountered.
Remarks
-
Wallet parent paths are 2 path elements long, e.g.
m/0/0
is the path labelled ‘default’. Keys derived from this parent path are 3 elements long, e.g. the secret keys derived from them/0/0
path will be at pathsm/0/0/0
,m/0/0/1
etc… -
This function does not need to use the root wallet seed or keychain.
Example
Set up as in new
method above.
let api_owner = Owner::new(wallet.clone());
let result = api_owner.create_account_path(None, "account1");
if let Ok(identifier) = result {
// set the account active
let result2 = api_owner.set_active_account(None, "account1");
}
Returns a list of outputs from the active account in the wallet.
Arguments
keychain_mask
- Wallet secret mask to XOR against the stored wallet seed before using, if being used.include_spent
- Iftrue
, outputs that have been marked as ‘spent’ in the wallet will be returned. Iffalse
, spent outputs will omitted from the results.refresh_from_node
- If true, the wallet will attempt to contact a node (via theNodeClient
provided during wallet instantiation). Iffalse
, the results will contain output information that may be out-of-date (from the last time the wallet’s output set was refreshed against the node). Note this setting is ignored if the updater process is running via a call tostart_updater
tx_id
- IfSome(i)
, only return the outputs associated with the transaction log entry of idi
.
Returns
(bool, Vec<OutputCommitMapping>)
- A tuple:- The first
bool
element indicates whether the data was successfully refreshed from the node (note this may be false even if therefresh_from_node
argument was set totrue
. - The second element contains a vector of OutputCommitMapping of which each element is a mapping between the wallet’s internal OutputData and the Output commitment as identified in the chain’s UTXO set
Example
Set up as in new
method above.
let api_owner = Owner::new(wallet.clone());
let show_spent = false;
let update_from_node = true;
let tx_id = None;
let result = api_owner.retrieve_outputs(None, show_spent, update_from_node, tx_id);
if let Ok((was_updated, output_mappings)) = result {
//...
}
Returns a list of Transaction Log Entries from the active account in the wallet.
Arguments
keychain_mask
- Wallet secret mask to XOR against the stored wallet seed before using, if being used.refresh_from_node
- If true, the wallet will attempt to contact a node (via theNodeClient
provided during wallet instantiation). Iffalse
, the results will contain transaction information that may be out-of-date (from the last time the wallet’s output set was refreshed against the node). Note this setting is ignored if the updater process is running via a call tostart_updater
tx_id
- IfSome(i)
, only return the transactions associated with the transaction log entry of idi
.tx_slate_id
- IfSome(uuid)
, only return transactions associated with the givenSlate
uuid.
Returns
(bool, Vec<TxLogEntry)
- A tuple:- The first
bool
element indicates whether the data was successfully refreshed from the node (note this may be false even if therefresh_from_node
argument was set totrue
. - The second element contains the set of retrieved TxLogEntries
Example
Set up as in new
method above.
let api_owner = Owner::new(wallet.clone());
let update_from_node = true;
let tx_id = None;
let tx_slate_id = None;
// Return all TxLogEntries
let result = api_owner.retrieve_txs(None, update_from_node, tx_id, tx_slate_id);
if let Ok((was_updated, tx_log_entries)) = result {
//...
}
Returns summary information from the active account in the wallet.
Arguments
keychain_mask
- Wallet secret mask to XOR against the stored wallet seed before using, if being used.refresh_from_node
- If true, the wallet will attempt to contact a node (via theNodeClient
provided during wallet instantiation). Iffalse
, the results will contain transaction information that may be out-of-date (from the last time the wallet’s output set was refreshed against the node). Note this setting is ignored if the updater process is running via a call tostart_updater
minimum_confirmations
- The minimum number of confirmations an output should have before it’s included in the ‘amount_currently_spendable’ total
Returns
- (
bool
,WalletInfo
) - A tuple: - The first
bool
element indicates whether the data was successfully refreshed from the node (note this may be false even if therefresh_from_node
argument was set totrue
. - The second element contains the Summary
WalletInfo
Example
Set up as in new
method above.
let mut api_owner = Owner::new(wallet.clone());
let update_from_node = true;
let minimum_confirmations=10;
// Return summary info for active account
let result = api_owner.retrieve_summary_info(None, update_from_node, minimum_confirmations);
if let Ok((was_updated, summary_info)) = result {
//...
}
pub fn init_send_tx(
&self,
keychain_mask: Option<&SecretKey>,
args: InitTxArgs
) -> Result<Slate, Error>
pub fn init_send_tx(
&self,
keychain_mask: Option<&SecretKey>,
args: InitTxArgs
) -> Result<Slate, Error>
Initiates a new transaction as the sender, creating a new
Slate
object containing
the sender’s inputs, change outputs, and public signature data. This slate can
then be sent to the recipient to continue the transaction via the
Foreign API’s receive_tx
method.
When a transaction is created, the wallet must also lock inputs (and create unconfirmed
outputs) corresponding to the transaction created in the slate, so that the wallet doesn’t
attempt to re-spend outputs that are already included in a transaction before the transaction
is confirmed. This method also returns a function that will perform that locking, and it is
up to the caller to decide the best time to call the lock function
(via the tx_lock_outputs
method).
If the exchange method is intended to be synchronous (such as via a direct http call,)
then the lock call can wait until the response is confirmed. If it is asynchronous, (such
as via file transfer,) the lock call should happen immediately (before the file is sent
to the recipient).
If the send_args
InitTxSendArgs
,
of the args
, field is Some, this
function will attempt to perform a synchronous send to the recipient specified in the dest
field according to the method
field, and will also finalize and post the transaction if
the finalize
field is set.
Arguments
keychain_mask
- Wallet secret mask to XOR against the stored wallet seed before using, if being used.args
-InitTxArgs
, transaction initialization arguments. See struct documentation for further detail.
Returns
- a result containing:
- The transaction Slate,
which can be forwarded to the recieving party by any means. Once the caller is relatively
certain that the transaction has been sent to the recipient, the associated wallet
transaction outputs should be locked via a call to
tx_lock_outputs
. This must be called before callingfinalize_tx
. - or
libwallet::Error
if an error is encountered.
Remarks
- This method requires an active connection to a node, and will fail with error if a node cannot be contacted to refresh output statuses.
- This method will store a partially completed transaction in the wallet’s transaction log,
which will be updated on the corresponding call to
finalize_tx
.
Example
Set up as in new method above.
let mut api_owner = Owner::new(wallet.clone());
// Attempt to create a transaction using the 'default' account
let args = InitTxArgs {
src_acct_name: None,
amount: 2_000_000_000,
minimum_confirmations: 2,
max_outputs: 500,
num_change_outputs: 1,
selection_strategy_is_use_all: false,
message: Some("Have some Epics. Love, Yeastplume".to_owned()),
..Default::default()
};
let result = api_owner.init_send_tx(
None,
args,
);
if let Ok(slate) = result {
// Send slate somehow
// ...
// Lock our outputs if we're happy the slate was (or is being) sent
api_owner.tx_lock_outputs(None, &slate, 0);
}
pub fn issue_invoice_tx(
&self,
keychain_mask: Option<&SecretKey>,
args: IssueInvoiceTxArgs
) -> Result<Slate, Error>
pub fn issue_invoice_tx(
&self,
keychain_mask: Option<&SecretKey>,
args: IssueInvoiceTxArgs
) -> Result<Slate, Error>
Issues a new invoice transaction slate, essentially a request for payment
.
The slate created by this function will contain the amount, an output for the amount,
as well as round 1 of singature creation complete. The slate should then be send
to the payer, who should add their inputs and signature data and return the slate
via the Foreign API’s finalize_invoice_tx
method.
Arguments
keychain_mask
- Wallet secret mask to XOR against the stored wallet seed before using, if being used.args
-IssueInvoiceTxArgs
, invoice transaction initialization arguments. See struct documentation for further detail.
Returns
- ``Ok(
slate
)` if successful, containing the updated slate. - or
libwallet::Error
if an error is encountered.
Example
Set up as in new
method above.
let mut api_owner = Owner::new(wallet.clone());
let args = IssueInvoiceTxArgs {
amount: 60_000_000_000,
..Default::default()
};
let result = api_owner.issue_invoice_tx(None, args);
if let Ok(slate) = result {
// if okay, send to the payer to add their inputs
// . . .
}
pub fn process_invoice_tx(
&self,
keychain_mask: Option<&SecretKey>,
slate: &Slate,
args: InitTxArgs
) -> Result<Slate, Error>
pub fn process_invoice_tx(
&self,
keychain_mask: Option<&SecretKey>,
slate: &Slate,
args: InitTxArgs
) -> Result<Slate, Error>
Processes an invoice tranaction created by another party, essentially
a request for payment
. The incoming slate should contain a requested
amount, an output created by the invoicer convering the amount, and
part 1 of signature creation completed. This function will add inputs
equalling the amount + fees, as well as perform round 1 and 2 of signature
creation.
Callers should note that no prompting of the user will be done by this function it is up to the caller to present the request for payment to the user and verify that payment should go ahead.
This function also stores the final transaction in the user’s wallet files for retrieval
via the get_stored_tx
function.
Arguments
keychain_mask
- Wallet secret mask to XOR against the stored wallet seed before using, if being used.slate
- The transactionSlate
. The payer should have filled in round 1 and 2.args
-InitTxArgs
, transaction initialization arguments. See struct documentation for further detail.
Returns
- ``Ok(
slate
)` if successful, containing the updated slate. - or
libwallet::Error
if an error is encountered.
Example
Set up as in new
method above.
let mut api_owner = Owner::new(wallet.clone());
// . . .
// The slate has been recieved from the invoicer, somehow
let args = InitTxArgs {
src_acct_name: None,
amount: slate.amount,
minimum_confirmations: 2,
max_outputs: 500,
num_change_outputs: 1,
selection_strategy_is_use_all: false,
..Default::default()
};
let result = api_owner.process_invoice_tx(None, &slate, args);
if let Ok(slate) = result {
// If result okay, send back to the invoicer
// . . .
}
Locks the outputs associated with the inputs to the transaction in the given
Slate
,
making them unavailable for use in further transactions. This function is called
by the sender, (or more generally, all parties who have put inputs into the transaction,)
and must be called before the corresponding call to finalize_tx
that completes the transaction.
Outputs will generally remain locked until they are removed from the chain,
at which point they will become Spent
. It is commonplace for transactions not to complete
for various reasons over which a particular wallet has no control. For this reason,
cancel_tx
can be used to manually unlock outputs
and return them to the Unspent
state.
Arguments
keychain_mask
- Wallet secret mask to XOR against the stored wallet seed before using, if being used.slate
- The transactionSlate
. Allparticipant_id
- The participant id, generally 0 for the party putting in funds, 1 for the party receiving. elements in theinput
vector of thetx
field that are found in the wallet’s currently active account will be set to statusLocked
Returns
- Ok(()) if successful
- or
libwallet::Error
if an error is encountered.
Example
Set up as in new
method above.
let mut api_owner = Owner::new(wallet.clone());
let args = InitTxArgs {
src_acct_name: None,
amount: 2_000_000_000,
minimum_confirmations: 10,
max_outputs: 500,
num_change_outputs: 1,
selection_strategy_is_use_all: false,
message: Some("Remember to lock this when we're happy this is sent".to_owned()),
..Default::default()
};
let result = api_owner.init_send_tx(
None,
args,
);
if let Ok(slate) = result {
// Send slate somehow
// ...
// Lock our outputs if we're happy the slate was (or is being) sent
api_owner.tx_lock_outputs(None, &slate, 0);
}
Finalizes a transaction, after all parties have filled in both rounds of Slate generation. This step adds all participants partial signatures to create the final signature, resulting in a final transaction that is ready to post to a node.
Note that this function DOES NOT POST the transaction to a node
for validation. This is done in separately via the
post_tx
function.
This function also stores the final transaction in the user’s wallet files for retrieval
via the get_stored_tx
function.
Arguments
keychain_mask
- Wallet secret mask to XOR against the stored wallet seed before using, if being used.slate
- The transactionSlate
. All participants must have filled in both rounds, and the sender should have locked their outputs (via thetx_lock_outputs
function).
Returns
- ``Ok(
slate
)` if successful, containing the new finalized slate. - or
libwallet::Error
if an error is encountered.
Example
Set up as in new
method above.
let mut api_owner = Owner::new(wallet.clone());
let args = InitTxArgs {
src_acct_name: None,
amount: 2_000_000_000,
minimum_confirmations: 10,
max_outputs: 500,
num_change_outputs: 1,
selection_strategy_is_use_all: false,
message: Some("Finalize this tx now".to_owned()),
..Default::default()
};
let result = api_owner.init_send_tx(
None,
args,
);
if let Ok(slate) = result {
// Send slate somehow
// ...
// Lock our outputs if we're happy the slate was (or is being) sent
let res = api_owner.tx_lock_outputs(None, &slate, 0);
//
// Retrieve slate back from recipient
//
let res = api_owner.finalize_tx(None, &slate);
}
Posts a completed transaction to the listening node for validation and inclusion in a block for mining.
Arguments
keychain_mask
- Wallet secret mask to XOR against the stored wallet seed before using, if being used.tx
- A completedTransaction
, typically thetx
field in the transactionSlate
.fluff
- Instruct the node whether to use the Dandelion protocol when posting the transaction. Iftrue
, the node should skip the Dandelion phase and broadcast the transaction to all peers immediately. Iffalse
, the node will follow dandelion logic and initiate the stem phase.
Returns
Ok(())
if successful- or
libwallet::Error
if an error is encountered.
Example
Set up as in new
method above.
let mut api_owner = Owner::new(wallet.clone());
let args = InitTxArgs {
src_acct_name: None,
amount: 2_000_000_000,
minimum_confirmations: 10,
max_outputs: 500,
num_change_outputs: 1,
selection_strategy_is_use_all: false,
message: Some("Post this tx".to_owned()),
..Default::default()
};
let result = api_owner.init_send_tx(
None,
args,
);
if let Ok(slate) = result {
// Send slate somehow
// ...
// Lock our outputs if we're happy the slate was (or is being) sent
let res = api_owner.tx_lock_outputs(None, &slate, 0);
//
// Retrieve slate back from recipient
//
let res = api_owner.finalize_tx(None, &slate);
let res = api_owner.post_tx(None, &slate.tx, true);
}
Cancels a transaction. This entails:
- Setting the transaction status to either
TxSentCancelled
orTxReceivedCancelled
- Deleting all change outputs or recipient outputs associated with the transaction
- Setting the status of all assocatied inputs from
Locked
toSpent
so they can be used in new transactions.
Transactions can be cancelled by transaction log id or slate id (call with either set to Some, not both)
Arguments
-
keychain_mask
- Wallet secret mask to XOR against the stored wallet seed before using, if being used. -
tx_id
- If present, cancel by theTxLogEntry
id for the transaction. -
tx_slate_id
- If present, cancel by the Slate id.
Returns
Ok(())
if successful- or
libwallet::Error
if an error is encountered.
Example
Set up as in new
method above.
let mut api_owner = Owner::new(wallet.clone());
let args = InitTxArgs {
src_acct_name: None,
amount: 2_000_000_000,
minimum_confirmations: 10,
max_outputs: 500,
num_change_outputs: 1,
selection_strategy_is_use_all: false,
message: Some("Cancel this tx".to_owned()),
..Default::default()
};
let result = api_owner.init_send_tx(
None,
args,
);
if let Ok(slate) = result {
// Send slate somehow
// ...
// Lock our outputs if we're happy the slate was (or is being) sent
let res = api_owner.tx_lock_outputs(None, &slate, 0);
//
// We didn't get the slate back, or something else went wrong
//
let res = api_owner.cancel_tx(None, None, Some(slate.id.clone()));
}
pub fn get_stored_tx(
&self,
keychain_mask: Option<&SecretKey>,
tx_log_entry: &TxLogEntry
) -> Result<Option<Transaction>, Error>
pub fn get_stored_tx(
&self,
keychain_mask: Option<&SecretKey>,
tx_log_entry: &TxLogEntry
) -> Result<Option<Transaction>, Error>
Retrieves the stored transaction associated with a TxLogEntry. Can be used even after the transaction has completed.
Arguments
keychain_mask
- Wallet secret mask to XOR against the stored wallet seed before using, if being used.tx_log_entry
- ATxLogEntry
Returns
- Ok with the stored
Transaction
if successful - or
libwallet::Error
if an error is encountered.
Example
Set up as in new
method above.
let api_owner = Owner::new(wallet.clone());
let update_from_node = true;
let tx_id = None;
let tx_slate_id = None;
// Return all TxLogEntries
let result = api_owner.retrieve_txs(None, update_from_node, tx_id, tx_slate_id);
if let Ok((was_updated, tx_log_entries)) = result {
let stored_tx = api_owner.get_stored_tx(None, &tx_log_entries[0]).unwrap();
//...
}
Verifies all messages in the slate match their public keys.
The optional messages themselves are part of the participant_data
field within the slate.
Messages are signed with the same key used to sign for the paricipant’s inputs, and can thus be
verified with the public key found in the public_blind_excess
field. This function is a
simple helper to returns whether all signatures in the participant data match their public
keys.
Arguments
keychain_mask
- Wallet secret mask to XOR against the stored wallet seed before using, if being used.slate
- The transactionSlate
.
Returns
Ok(())
if successful and the signatures validate- or
libwallet::Error
if an error is encountered.
Example
Set up as in new
method above.
let mut api_owner = Owner::new(wallet.clone());
let args = InitTxArgs {
src_acct_name: None,
amount: 2_000_000_000,
minimum_confirmations: 10,
max_outputs: 500,
num_change_outputs: 1,
selection_strategy_is_use_all: false,
message: Some("Just verify messages".to_owned()),
..Default::default()
};
let result = api_owner.init_send_tx(
None,
args,
);
if let Ok(slate) = result {
// Send slate somehow
// ...
// Lock our outputs if we're happy the slate was (or is being) sent
let res = api_owner.tx_lock_outputs(None, &slate, 0);
//
// Retrieve slate back from recipient
//
let res = api_owner.verify_slate_messages(None, &slate);
}
Scans the entire UTXO set from the node, identify which outputs belong to the given wallet update the wallet state to be consistent with what’s currently in the UTXO set.
This function can be used to repair wallet state, particularly by restoring outputs that may be missing if the wallet owner has cancelled transactions locally that were then successfully posted to the chain.
This operation scans the entire chain, and is expected to be time intensive. It is imperative that no other processes should be trying to use the wallet at the same time this function is running.
When an output is found that doesn’t exist in the wallet, a corresponding TxLogEntry is created.
Arguments
keychain_mask
- Wallet secret mask to XOR against the stored wallet seed before using, if being used.start_height
- If provided, the height of the first block from which to start scanning. The scan will start from block 1 if this is not provided.delete_unconfirmed
- iffalse
, the scan process will be non-destructive, and mostly limited to restoring missing outputs. It will leave unconfirmed transaction logs entries and unconfirmed outputs intact. Iftrue
, the process will unlock all locked outputs, restore all missing outputs, and mark any outputs that have been marked ‘Spent’ but are still in the UTXO set as ‘Unspent’ (as can happen during a fork). It will also attempt to cancel any transaction log entries associated with any locked outputs or outputs incorrectly marked ‘Spent’. Note this completely removes all outstanding transactions, so users should be very aware what will happen if this flag is set. Note that if transactions/outputs are removed that later confirm on the chain, another call to this function will restore them.
Returns
Ok(())
if successful- or
libwallet::Error
if an error is encountered.
Example
Set up as in new
method above.
let mut api_owner = Owner::new(wallet.clone());
let result = api_owner.scan(
None,
Some(20000),
false,
);
if let Ok(_) = result {
// Wallet outputs should be consistent with what's on chain
// ...
}
pub fn node_height(
&self,
keychain_mask: Option<&SecretKey>
) -> Result<NodeHeightResult, Error>
pub fn node_height(
&self,
keychain_mask: Option<&SecretKey>
) -> Result<NodeHeightResult, Error>
Retrieves the last known height known by the wallet. This is determined as follows:
- If the wallet can successfully contact its configured node, the reported node
height is returned, and the
updated_from_node
field in the response istrue
- If the wallet cannot contact the node, this function returns the maximum height
of all outputs contained within the wallet, and the
updated_from_node
fields in the response is set to false.
Clients should generally ensure the updated_from_node
field is returned as
true
before assuming the height for any operation.
Arguments
keychain_mask
- Wallet secret mask to XOR against the stored wallet seed before using, if being used.
Returns
- Ok with a
NodeHeightResult
if successful. If the height result was obtained from the configured node,updated_from_node
will be set totrue
- or
libwallet::Error
if an error is encountered.
Example
Set up as in new
method above.
let api_owner = Owner::new(wallet.clone());
let result = api_owner.node_height(None);
if let Ok(node_height_result) = result {
if node_height_result.updated_from_node {
//we can assume node_height_result.height is relatively safe to use
}
//...
}
Retrieve the top-level directory for the wallet. This directory should contain the
epic-wallet.toml
file and the wallet_data
directory that contains the wallet
seed + data files. Future versions of the wallet API will support multiple wallets
within the top level directory.
The top level directory defaults to (in order of precedence):
- The current directory, from which
epic-wallet
or the main process was run, if it contains aepic-wallet.toml
file. - ~/.epic/
/ otherwise
Arguments
- None
Returns
- Ok with a String value representing the full path to the top level wallet dierctory
- or
libwallet::Error
if an error is encountered.
Example
Set up as in new
method above.
let api_owner = Owner::new(wallet.clone());
let result = api_owner.get_top_level_directory();
if let Ok(dir) = result {
println!("Top level directory is: {}", dir);
//...
}
Set the top-level directory for the wallet. This directory can be empty, and will be created
during a subsequent calls to create_config
Set get_top_level_directory
for a
description of the top level directory and default paths.
Arguments
dir
: The new top-level directory path (either relative to current directory or absolute.
Returns
- Ok if successful
- or
libwallet::Error
if an error is encountered.
Example
Set up as in new
method above.
let dir = "path/to/wallet/dir";
let api_owner = Owner::new(wallet.clone());
let result = api_owner.set_top_level_directory(dir);
if let Ok(dir) = result {
//...
}
pub fn create_config(
&self,
chain_type: &ChainTypes,
wallet_config: Option<WalletConfig>,
logging_config: Option<LoggingConfig>,
tor_config: Option<TorConfig>
) -> Result<(), Error>
pub fn create_config(
&self,
chain_type: &ChainTypes,
wallet_config: Option<WalletConfig>,
logging_config: Option<LoggingConfig>,
tor_config: Option<TorConfig>
) -> Result<(), Error>
Create a epic-wallet.toml
configuration file in the top-level directory for the
specified chain type.
A custom WalletConfig
and/or epic LoggingConfig
may optionally be provided, otherwise defaults will be used.
Paths in the configuration file will be updated to reflect the top level directory, so path-related values in the optional configuration structs will be ignored.
Arguments
chain_type
: The chain type to use in creation of the configuration file. This can beAutomatedTesting
UserTesting
Floonet
Mainnet
Returns
- Ok if successful
- or
libwallet::Error
if an error is encountered.
Example
Set up as in new
method above.
use epic_core::global::ChainTypes;
let dir = "path/to/wallet/dir";
let api_owner = Owner::new(wallet.clone());
let _ = api_owner.set_top_level_directory(dir);
let result = api_owner.create_config(&ChainTypes::Mainnet, None, None, None);
if let Ok(_) = result {
//...
}
Creates a new wallet seed and empty wallet database in the wallet_data
directory of
the top level directory.
Paths in the configuration file will be updated to reflect the top level directory, so path-related values in the optional configuration structs will be ignored.
The wallet files must not already exist, and ~The epic-wallet.toml
file must exist
in the top level directory (can be created via a call to
create_config
)
Arguments
name
: Reserved for future use, useNone
for the time being.mnemonic
: If present, restore the wallet seed from the given mnemonic instead of creating a new random seed.mnemonic_length
: Desired length of mnemonic in bytes (16 or 32, either 12 or 24 words). Use 0 if mnemonic isn’t being used.password
: The password used to encrypt/decrypt thewallet.seed
file
Returns
- Ok if successful
- or
libwallet::Error
if an error is encountered.
Example
Set up as in new
method above.
use epic_core::global::ChainTypes;
// note that the WalletInst struct does not necessarily need to contain an
// instantiated wallet
let dir = "path/to/wallet/dir";
let api_owner = Owner::new(wallet.clone());
let _ = api_owner.set_top_level_directory(dir);
// Create configuration
let result = api_owner.create_config(&ChainTypes::Mainnet, None, None, None);
// create new wallet wirh random seed
let pw = ZeroingString::from("my_password");
let result = api_owner.create_wallet(None, None, 0, pw);
if let Ok(r) = result {
//...
}
Opens
a wallet, populating the internal keychain with the encrypted seed, and optionally
returning a keychain_mask
token to the caller to provide in all future calls.
If using a mask, the seed will be stored in-memory XORed against the keychain_mask
, and
will not be useable if the mask is not provided.
Arguments
name
: Reserved for future use, useNone
for the time being.password
: The password to use to open the wallet a new random seed.use_mask
: Whether to create and return a mask which much be provided in all future API calls.
Returns
- Ok if successful
- or
libwallet::Error
if an error is encountered.
Example
Set up as in new
method above.
use epic_core::global::ChainTypes;
// note that the WalletInst struct does not necessarily need to contain an
// instantiated wallet
let dir = "path/to/wallet/dir";
let api_owner = Owner::new(wallet.clone());
let _ = api_owner.set_top_level_directory(dir);
// Create configuration
let result = api_owner.create_config(&ChainTypes::Mainnet, None, None, None);
// create new wallet wirh random seed
let pw = ZeroingString::from("my_password");
let _ = api_owner.create_wallet(None, None, 0, pw.clone());
let result = api_owner.open_wallet(None, pw, true);
if let Ok(m) = result {
// use this mask in all subsequent calls
let mask = m;
}
Close
a wallet, removing the master seed from memory.
Arguments
name
: Reserved for future use, useNone
for the time being.
Returns
- Ok if successful
- or
libwallet::Error
if an error is encountered.
Example
Set up as in new
method above.
use epic_core::global::ChainTypes;
// Set up as above
let res = api_owner.close_wallet(None);
if let Ok(_) = res {
// ...
}
Return the BIP39 mnemonic for the given wallet. This function will decrypt the wallet’s seed file with the given password, and thus does not need the wallet to be open.
Arguments
name
: Reserved for future use, useNone
for the time being.password
: The password used to encrypt the seed file.
Returns
- Ok(BIP-39 mneminc) if successful
- or
libwallet::Error
if an error is encountered.
Example
Set up as in new
method above.
use epic_core::global::ChainTypes;
// Set up as above
let pw = ZeroingString::from("my_password");
let res = api_owner.get_mnemonic(None, pw);
if let Ok(mne) = res {
// ...
}
Changes a wallet’s password, meaning the old seed file is decrypted with the old password, and a new seed file is created with the same mnemonic and encrypted with the new password.
This function temporarily backs up the old seed file until a test-decryption of the new file is confirmed to contain the same seed as the original seed file, at which point the backup is deleted. If this operation fails for an unknown reason, the backup file will still exist in the wallet’s data directory encrypted with the old password.
Arguments
name
: Reserved for future use, useNone
for the time being.old
: The password used to encrypt the existing seed file (i.e. old password)new
: The password to be used to encrypt the new seed file
Returns
- Ok(()) if successful
- or
libwallet::Error
if an error is encountered.
Example
Set up as in new
method above.
use epic_core::global::ChainTypes;
// Set up as above
let old = ZeroingString::from("my_password");
let new = ZeroingString::from("new_password");
let res = api_owner.change_password(None, old, new);
if let Ok(mne) = res {
// ...
}
Deletes a wallet, removing the config file, seed file and all data files. Obviously, use with extreme caution and plenty of user warning
Highly recommended that the wallet be explicitly closed first via the close_wallet
function.
Arguments
name
: Reserved for future use, useNone
for the time being.
Returns
- Ok if successful
- or
libwallet::Error
if an error is encountered.
Example
Set up as in new
method above.
use epic_core::global::ChainTypes;
// Set up as above
let res = api_owner.delete_wallet(None);
if let Ok(_) = res {
// ...
}
Starts a background wallet update thread, which performs the wallet update process automatically at the frequency specified.
The updater process is as follows:
- Reconcile the wallet outputs against the node’s current UTXO set, confirming transactions if needs be.
- Look up transactions by kernel in cases where it’s necessary (for instance, when there are no change outputs for a transaction and transaction status can’t be inferred from the output state.
- Incrementally perform a scan of the UTXO set, correcting outputs and transactions where their local state differs from what’s on-chain. The wallet stores the last position scanned, and will scan back 100 blocks worth of UTXOs on each update, to correct any differences due to forks or otherwise.
Note that an update process can take a long time, particularly when the entire
UTXO set is being scanned for correctness. The wallet status can be determined by
calling the get_updater_messages
.
Arguments
keychain_mask
- Wallet secret mask to XOR against the stored wallet seed before using, if being used.frequency
: The frequency at which to call the update process. Note this is time elapsed since the last successful update process. If calling via the JSON-RPC api, this represents milliseconds.
Returns
- Ok if successful
- or
libwallet::Error
if an error is encountered.
Example
Set up as in new
method above.
use epic_core::global::ChainTypes;
use std::time::Duration;
// Set up as above
let res = api_owner.start_updater(None, Duration::from_secs(60));
if let Ok(_) = res {
// ...
}
Stops the background update thread. If the updater is currently updating, the thread will stop after the next update
Arguments
- None
Returns
- Ok if successful
- or
libwallet::Error
if an error is encountered.
Example
Set up as in new
method above.
use epic_core::global::ChainTypes;
use std::time::Duration;
// Set up as above
let res = api_owner.start_updater(None, Duration::from_secs(60));
if let Ok(_) = res {
// ...
}
let res = api_owner.stop_updater();
Retrieve messages from the updater thread, up to count
number of messages.
The resulting array will be ordered newest messages first. The updater will
store a maximum of 10,000 messages, after which it will start removing the oldest
messages as newer ones are created.
Messages retrieved via this method are removed from the internal queue, so calling this function at a specified interval should result in a complete message history.
Arguments
count
- The number of messages to retrieve.
Returns
- Ok with a Vec of
StatusMessage
- or
libwallet::Error
if an error is encountered.
Example
Set up as in new
method above.
use epic_core::global::ChainTypes;
use std::time::Duration;
// Set up as above
let res = api_owner.start_updater(None, Duration::from_secs(60));
let messages = api_owner.get_updater_messages(10000);
if let Ok(_) = res {
// ...
}
Retrieve the public proof “addresses” associated with the active account at the given derivation path.
In this case, an “address” means a Dalek ed25519 public key corresponding to a private key derived as follows:
e.g. The default parent account is at
m/0/0
With output blinding factors created as
m/0/0/0
m/0/0/1
etc…
The corresponding public address derivation path would be at:
m/0/1
With addresses created as:
m/0/1/0
m/0/1/1
etc…
Note that these addresses correspond to the public keys used in the addresses of TOR hidden services configured by the wallet listener.
Arguments
keychain_mask
- Wallet secret mask to XOR against the stored wallet seed before using, ifderivation_index
- The index along the derivation path to retrieve an address for
Returns
- Ok with a DalekPublicKey representing the address
- or
libwallet::Error
if an error is encountered.
Example
Set up as in new
method above.
use epic_core::global::ChainTypes;
use std::time::Duration;
// Set up as above
let res = api_owner.get_public_proof_address(None, 0);
if let Ok(_) = res {
// ...
}
Helper function to convert an Onion v3 address to a payment proof address (essentially exctacting and verifying the public key)
Arguments
address_v3
- An V3 Onion address
Returns
- Ok(DalekPublicKey) representing the public key associated with the address, if successful
- or
libwallet::Error
if an error is encountered or the address provided is invalid
Example
Set up as in new
method above.
use epic_core::global::ChainTypes;
use std::time::Duration;
// Set up as above
let res = api_owner.proof_address_from_onion_v3(
"2a6at2obto3uvkpkitqp4wxcg6u36qf534eucbskqciturczzc5suyid"
);
if let Ok(_) = res {
// ...
}
let res = api_owner.stop_updater();
Trait Implementations
impl<'a, L, C, K> OwnerRpc for Owner<L, C, K> where
L: WalletLCProvider<'static, C, K>,
C: NodeClient + 'static,
K: Keychain + 'static,
impl<'a, L, C, K> OwnerRpc for Owner<L, C, K> where
L: WalletLCProvider<'static, C, K>,
C: NodeClient + 'static,
K: Keychain + 'static,
The V2 Owner API (OwnerRpc) will be removed in epic-wallet 4.0.0. Please migrate to the V3 (OwnerRpcS) API as soon as possible.
Networked version of Owner::accounts. Read more
Networked version of Owner::create_account_path. Read more
Networked version of Owner::set_active_account. Read more
Networked version of Owner::retrieve_outputs. Read more
Networked version of Owner::retrieve_txs. Read more
fn retrieve_summary_info(
&self,
refresh_from_node: bool,
minimum_confirmations: u64
) -> Result<(bool, WalletInfo), ErrorKind>
fn retrieve_summary_info(
&self,
refresh_from_node: bool,
minimum_confirmations: u64
) -> Result<(bool, WalletInfo), ErrorKind>
Networked version of Owner::retrieve_summary_info. Read more
Networked version of Owner::init_send_tx. Read more
Networked version of Owner::issue_invoice_tx. Read more
fn process_invoice_tx(
&self,
in_slate: VersionedSlate,
args: InitTxArgs
) -> Result<VersionedSlate, ErrorKind>
fn process_invoice_tx(
&self,
in_slate: VersionedSlate,
args: InitTxArgs
) -> Result<VersionedSlate, ErrorKind>
Networked version of Owner::process_invoice_tx. Read more
Networked version of Owner::finalize_tx. Read more
fn tx_lock_outputs(
&self,
slate: VersionedSlate,
participant_id: usize
) -> Result<(), ErrorKind>
fn tx_lock_outputs(
&self,
slate: VersionedSlate,
participant_id: usize
) -> Result<(), ErrorKind>
Networked version of Owner::tx_lock_outputs. Read more
Networked version of Owner::cancel_tx. Read more
Networked version of Owner::get_stored_tx. Read more
Networked version of Owner::post_tx. Read more
Networked version of Owner::verify_slate_messages. Read more
Networked version of Owner::scan. Read more
Networked version of Owner::node_height. Read more
impl<L, C, K> OwnerRpcS for Owner<L, C, K> where
L: WalletLCProvider<'static, C, K>,
C: NodeClient + 'static,
K: Keychain + 'static,
impl<L, C, K> OwnerRpcS for Owner<L, C, K> where
L: WalletLCProvider<'static, C, K>,
C: NodeClient + 'static,
K: Keychain + 'static,
Networked version of Owner::accounts. Read more
Networked version of Owner::create_account_path. Read more
Networked version of Owner::set_active_account. Read more
Networked version of Owner::retrieve_outputs. Read more
Networked version of Owner::retrieve_txs. Read more
Networked version of Owner::retrieve_summary_info. Read more
Networked version of Owner::init_send_tx. Read more
fn issue_invoice_tx(
&self,
token: Token,
args: IssueInvoiceTxArgs
) -> Result<VersionedSlate, ErrorKind>
fn issue_invoice_tx(
&self,
token: Token,
args: IssueInvoiceTxArgs
) -> Result<VersionedSlate, ErrorKind>
Networked version of Owner::issue_invoice_tx. Read more
fn process_invoice_tx(
&self,
token: Token,
in_slate: VersionedSlate,
args: InitTxArgs
) -> Result<VersionedSlate, ErrorKind>
fn process_invoice_tx(
&self,
token: Token,
in_slate: VersionedSlate,
args: InitTxArgs
) -> Result<VersionedSlate, ErrorKind>
Networked version of Owner::process_invoice_tx. Read more
fn finalize_tx(
&self,
token: Token,
in_slate: VersionedSlate
) -> Result<VersionedSlate, ErrorKind>
fn finalize_tx(
&self,
token: Token,
in_slate: VersionedSlate
) -> Result<VersionedSlate, ErrorKind>
Networked version of Owner::finalize_tx. Read more
fn tx_lock_outputs(
&self,
token: Token,
in_slate: VersionedSlate,
participant_id: usize
) -> Result<(), ErrorKind>
fn tx_lock_outputs(
&self,
token: Token,
in_slate: VersionedSlate,
participant_id: usize
) -> Result<(), ErrorKind>
Networked version of Owner::tx_lock_outputs. Read more
Networked version of Owner::cancel_tx. Read more
fn get_stored_tx(
&self,
token: Token,
tx: &TxLogEntry
) -> Result<Option<TransactionV3>, ErrorKind>
fn get_stored_tx(
&self,
token: Token,
tx: &TxLogEntry
) -> Result<Option<TransactionV3>, ErrorKind>
Networked version of Owner::get_stored_tx. Read more
Networked version of Owner::post_tx. Read more
Networked version of Owner::verify_slate_messages. Read more
Networked version of Owner::scan. Read more
Networked version of Owner::node_height. Read more
Initializes the secure JSON-RPC API. This function must be called and a shared key established before any other OwnerAPI JSON-RPC function can be called. Read more
Networked version of Owner::get_top_level_directory. Read more
Networked version of Owner::set_top_level_directory. Read more
fn create_config(
&self,
chain_type: ChainTypes,
wallet_config: Option<WalletConfig>,
logging_config: Option<LoggingConfig>,
tor_config: Option<TorConfig>
) -> Result<(), ErrorKind>
fn create_config(
&self,
chain_type: ChainTypes,
wallet_config: Option<WalletConfig>,
logging_config: Option<LoggingConfig>,
tor_config: Option<TorConfig>
) -> Result<(), ErrorKind>
Networked version of Owner::create_config. Read more
Networked version of Owner::create_wallet. Read more
Networked version of Owner::open_wallet. Read more
Networked version of Owner::close_wallet. Read more
Networked version of Owner::get_mnemonic. Read more
Networked version of Owner::change_password. Read more
Networked version of Owner::delete_wallet. Read more
Networked version of Owner::start_updated. Read more
Networked version of Owner::stop_updater. Read more
Networked version of Owner::get_updater_messages. Read more
fn get_public_proof_address(
&self,
token: Token,
derivation_index: u32
) -> Result<PubAddress, ErrorKind>
fn get_public_proof_address(
&self,
token: Token,
derivation_index: u32
) -> Result<PubAddress, ErrorKind>
Networked version of Owner::get_public_proof_address. Read more
Networked version of Owner::proof_address_from_onion_v3. Read more
Networked version of Owner::set_tor_config. Read more
Auto Trait Implementations
impl<L, C, K> !RefUnwindSafe for Owner<L, C, K>
impl<L, C, K> !UnwindSafe for Owner<L, C, K>
Blanket Implementations
Mutably borrows from an owned value. Read more
impl<T> SafeBorrow<T> for T where
T: ?Sized,
impl<T> SafeBorrow<T> for T where
T: ?Sized,
pub fn borrow_replacement(ptr: &T) -> &T
pub fn borrow_replacement(ptr: &T) -> &T
Given ptr
, which was obtained from a prior call to Self::borrow()
,
return a value with the same nominal lifetime which is guaranteed to
survive mutations to Self
. Read more