True if okay to consolidate over this coin; false, otherwise
Convert a currency amount represented in base units (satoshi, wei, atoms, drops, stroops) to big units (btc, eth, rmg, xrp, xlm)
Convert a currency amount represented in big units (btc, eth, rmg, xrp, xlm) to base units (satoshi, wei, atoms, drops, stroops)
The cold wallet tool uses this function to derive an extended key that is based on the passed key and seed
Explain/parse transaction
Fetch fee estimate information from the server
The params passed into the function
The info returned from the merchant server
Generate a new keypair for this coin.
Seed from which the new keypair should be generated, otherwise a random seed is used
Parse an address string into address and destination tag
Factor between the coin's base unit and its smallest subdivison
Identifier for the blockchain which supports this coin
Get extra parameters for prebuilding a tx. Add things like hop transaction params
Identifier for the coin family
Get fee info from server
Complete human-readable name of this coin
URL of a well-known, public facing (non-bitgo) rippled instance which can be used for recovery
Prepare and validate all keychains from the keycard for recovery
Evaluates whether an address string is valid for this coin
Return wether the given m of n wallet signers/ key amounts are valid for the coin
Return boolean indicating whether input is valid public key for the coin.
the pub to be checked
is it valid?
Specifies what key we will need for signing - right now we just need the user key.
Create a new wallet object from a wallet data object
Construct a full, normalized address from an address and destination tag
Modify prebuild after receiving it from the server. Add things like nlocktime
Perform additional checks before adding a bitgo key. Base controller is a no-op, but coin-specific controller may do something
Coin-specific things done before signing a transaction, i.e. verification
Builds a funds recovery transaction without BitGo
Sign message with private key
Assemble keychain and half-sign prebuilt transaction
Bluebird
Ripple requires additional parameters for wallet generation to be sent to the server. The additional parameters are the root public key, which is the basis of the root address, two signed, and one half-signed initialization txs
Check whether a coin supports blockTarget for transactions to be included in
Flag for sending data along with transactions
True if okay to send tx data (ETH), false otherwise
Flag for sending value of 0.
True if okay to send 0 value, false otherwise
Check if address is a valid XRP address, and then make sure the root addresses match. This prevents attacks where an attack may switch out the new address for one of their own
Verify that a transaction prebuild complies with the original intention
Generated using TypeDoc
Flag for determining whether this coin supports account consolidations from its receive addresses to the root address.