This is a step-by-step guide for installing a Bitcoin Core node as a Hot Wallet source for CAS. While you can operate a node on any suitable server, this guide is based upon a VPS using Digital Ocean. The intricacies of node installation (and operation) in a different environment are outside the scope of our support, and in such situations you should seek assistance from the Bitcoin Core community.
| Panel | ||||||
|---|---|---|---|---|---|---|
| ||||||
This guide is based on VPS installation only! |
This guide has been updated for Bitcoin Core version: 0.20.1
...
Save all the information securely. You'll need every detail in the steps to follow.
The RPC User = AnyNameYouWantHere
The RPC Password = Kq66rZya7MNpCU_e0zZSgjR2Mb7rBeyX9QSeGhwPMeY=
The cookie/token ("rpcauth") will only be required in the Bitcoin Core configuration file (next step).
| Tip |
|---|
The RPC Password is required for CAS - noted in Step 6. |
The cookie/token is a secure hash of your password. The point is to hide your password on the node server to other users of the node. If your node is secure, then using the cookie is simply added security in the event of a server breach, however if your server is breached - you have a bigger problem than an exposed password - and that hash will afford very little protection.
The password is sent to the RPC server software by CAS, and must be kept encrypted while traveling over the Internet. This is accomplished using “tunnels”.
...
3. Create the Bitcoin Core configuration file.
...
| Code Block |
|---|
server=1
daemon=1
addresstype=legacy
rpcport=8332
rpcauth=ThisIsAnExample:77cf8c03b15219cafb1e72ae9329d5fd$72de450660cdb6dd2689cd2cba4091646a5e8005490dec07dc577b6dad67770e |
Replace the “rpcauth” line with the cookie/token you generated in the previous step.
Exit the nano editor with Control+X and save your changes.
The CAS parameter “port” is the same as the “rpcport” specified in this step.
...
4. Start the bitcoind daemon:
...
Click here for instructions to install the GB Wallet Tunnel Server.
Perfect for the GB CloudThe CAS “host” parameter used will be this node’s public IP.
The CAS “port” parameter will be the same port specified as the “rpcport” in Step 3 (above).
Option 2: Creating an SSH tunnel:
If you're running your own CAS server, then you You may elect to use a SSH tunnel for secure RPC communication with the node. We also discourage running any software on your CAS server (except for CAS itself) and this includes Bitcoin Core. The solution is use port forwarding to enable access to your separate Bitcoin Core node. We recommend "dialing out" from CAS to the node.
...
| Tip |
|---|
Follow this link to see configuration instructions for Bitcoin Core with CAS. |
...
Additional Notes:
Remote Procedure Call (RPC) Reference:
More information about the RPC API: https://developer.bitcoin.org/reference/rpc/index.html
...
| Warning |
|---|
The instructions given in this guide do not enable “pruning nodes”.
|
Backups
Backup is a matter of copying the wallet file normally located in $HOME/.bitcoin/wallet.dat .
The wallet.dat file can change over time because:
New Transactions: when you receive or send Bitcoin, new transactions are recorded in the wallet file.
New Addresses: if you generate new addresses for receiving Bitcoin are added to the wallet file.
Private Key Generation: new private keys (for new addresses) are stored in the wallet file.
A file backup would be the most comprehensive recovery option in the event of catastrophe. Since the file is so sensitive though, having multiple copies also increases your hack risks. Secure your backups!
Private Keys
It is not recommended to print or expose your private key, especially in a terminal or any other insecure environment. However, if you absolutely need to retrieve your private key for a specific address using bitcoin-cli, you can use the dumpprivkey command.
| Code Block |
|---|
bitcoin-cli dumpprivkey "your_bitcoin_address" |
Replace
"your_bitcoin_address"with the actual address for which you want to retrieve the private key. This command will output the private key associated with that address.Be extremely cautious with this operation. Anyone with access to your private key can control your Bitcoin funds associated with that address. We generally recommended you use hardware wallets or other secure methods for managing your private keys.
Related articles
| Filter by label (Content by label) | |||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Page Properties | ||
|---|---|---|
| ||
|