Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Code Block
server=1
daemon=1
rpcport=8332
rpcauth=AnyNameYouWantHere:cbb36c03b15219cafb1e72ae9329d5fd$72de450660cdb6dd2689cd2cba4091646a5e8005490dec07dc577b6dad608a80
# enable RBF
walletrbf=1
  • Replace the “rpcauth” line with the cookie/token you generated in the previous step 2.

  • Exit the nano editor with Control+X and “Y” to save your changes.

  • The CAS parameter “port” is the same as the “rpcport” specified in this step (8332).

...

Tip

Configure your CAS Crypto Settings

...

Reference:

1. Remote Procedure Call (RPC)

...

:

More information about the RPC API: https://developer.bitcoin.org/reference/rpc/index.html

Note
Note

NOTE: the bitcoin-qt (

a

Core GUI wallet) is NOT supported

at this time

.

2. Important notes regarding pruning nodes:

A "pruning node" (or lightweight node) is a special configuration that may be applied to bitcoind. It is unsupported by General Bytes. It is a substantial security risk when operating a BATM. Per the Bitcoin wiki:

...

Warning

The instructions given in this guide do not enable “pruning nodes”.

  • Install a full node as recommended by the Bitcoin community.

...

Housekeeping Instructions

This data is outside the scope of GB Support, but is frequently asked.

RBF and CPFP

Deploying a Bitcoin Core node grants you the ability to modify your unconfirmed transaction fees. Without a node, you must rely on third-party services to “unstuck” a low-fee transaction.

CPFP (Child Pays For Parent) is no longer necessary for modern transactions using this Core version. It has been fully replaced by RBF (Replace By Fee) and is less reliable than RBF. Using the instructions from this article, your node is already configured to use RBF.

To verify that your node is creating RBF-compatible transactions by default, use:

Code Block
bitcoin-cli getmempoolinfo
  • The results should include this: "fullrbf": true

RBF Instructions:

Backups

Backup is a simple matter of executing this RPC call:

...