5 stars based on
Download or install the bitgo-cli NPM package inclusive dependencies. At this website you will find all NPM packages. This package provides a NodeJS program bitgowhich is a mostly complete command-line bitgo logout to BitGo wallets. It also contains some useful client-side-only commands for key generation. By default, bitgo will use the production Bitcoin network, and will authenticate with www.
In order to use BitGo's test environment at test. The testnet environment is a completely separate namespace from the BitGo production database.
You will need to set up separate accounts on test. Note that in the test environment, while standard Authy codes still work for 2FA, it is also possible to use a code of 7 zeroes. The tool bitgo logout one current login session per environment prod or test. Each session maintains the user's current auth token, and maintains a current wallet. All of the commands that operate on a wallet use this current wallet context.
In order to operate on a different wallet, it must first be selected using the wallet command. A number of the commands support outputting in JSON format as well as the normal human-readable format.
To enable JSON output, use the -j command line flag before the command, for example:. Many of the commands have interactive bitgo logout, prompting for needed information as they go.
Generally, these interactive prompts can be bypassed by providing the corresponding information through a command-line flag. Set the current auth token; this is an alternate way of changing sessions, or can be used to install a long-lived API token provided by BitGo:. List the wallets available to the user, with balances. Indicates which wallet is currently selected.
In order to transact, a BitGo session must first be unlocked, by providing an additional 2-step verification Authy code. The send command handles prompting for this automatically, bitgo logout the wallet can also be unlocked explicitly.
Share the current wallet with a user by giving them share, spend, or admin priviliges on the bitgo logout. If no wallet is specified, it will use the current wallet.
You must have admin status on the wallet to use bitgo logout command. Freeze a BitGo wallet. This command effectively time-locks a wallet, so that BitGo will refuse to sign any transactions until the freeze expires. Be careful when freezing a wallet, as there is no way to unfreeze a wallet without either waiting for the time to expire without help from BitGo bitgo logout. Remove a wallet from your BitGo account. If the wallet is bitgo logout, and you are not the last admin, it removes your access to the wallet but does not affect other users' access.
If you are the last admin on the wallet, it will mark the wallet as deleted and bitgo logout will not currently be recoverable without assistance from BitGo. Consolidate the unspents on the current wallet into fewer, bigger unspents, optionally setting the bitgo logout count of unspents.
This bitgo logout provides a guided flow, but the needed info may also be provided on the command line. Create a new BIP32 root key. This is a client-side only operation. It does not require bitgo logout user to be authenticated with BitGo, and does not contact the BitGo server.
Additional entropy may be provided on the command line. This is a client-side utility command which assists in generating a batch of BIP32 keys which are split using Shamir Secret Sharing, and have the shares encrypted with separate passwords each known by a separate person, generally.
It provides a guided flow, as bitgo logout as command-line args. Verifies the xpubs generated by the splitkeys command. Print a wallet's xprv, which is decrypted using the passphrase. If the wallet's encrypted keychain is not stored by BitGo, there will be no xprv to print. This is a guided flow with instructions. You will bitgo logout to provide 1 xprv and 1 xpub, or 2 xpubs in order to create the wallet. Please be aware that creating a wallet in this manner does not produce a recovery KeyCard.
You are fully responsible for backing up your keys. If you lose access to your keys and passcode, BitGo cannot help you recover your funds. Launch the BitGo shell, which simply allows you to run commands without prefixing them with bitgo. No other shell functionality is provided. Use Ctrl-C or Ctrl-D to exit. Prints all of the commands and subcommands that bitgo-cli responds to, along with short explanations of each bitgo logout.
Creates an unsigned transaction and saves it to a JSON file. This file can then be brought to an offline machine for signing using signtx. Sends a half-signed transaction on a wallet to BitGo for co-signing and propogation to the Bitcoin network. Takes input from a filename JSON constructed by signtx or a pure transaction hex. For bitgo logout on bitgo-cli, the following commands must be run before writing new code. Home Screenshots Log In. Name bitgo-cli Bitgo logout description BitGo command-line interface.
Installation NodeJS must be installed as a prerequisite. Sessions The tool maintains one current login session per environment prod or test. Output formats A number of the commands support bitgo logout in JSON format as well as the normal human-readable format. Bitgo logout enable JSON output, use the -j command line flag before the command, for example: Sessions expire in 60 minutes by default.
Email address of recipient: Spend limit is BTC Wallet password: BitGo will not sign any transactions on this wallet until the freeze expires. Type 'go' to confirm: Enter a BIP32 xprv below, or press return to generate one automatically. Your user key is encrypted locally with your password, and stored on BitGo's server.
User key xprv or xpub: Next, we need the backup keychain. Enter a BIP32 xpub below. It is recommended to generate the backup keychain on a different machine using reliable BIP32 key generation software.
For instance, you can use the 'keychain' sub-command to generate a keychain Bitgo logout key xpub: Can be performed offline. Loading the files please wait Please leave bitgo logout a message Send. There bitgo logout some processings in the backend. This can take some minutes.