BTQ Node CLI Wallet - Slave Keys
Here's the adapted guide for managing BTQ CLI wallets with Slave keys
BTQ Node CLI Wallet - Slave Keys
The BTQ wallet is an XMSS Merkle tree constructed using the private key to generate leaves. Each "leaf" can also generate a tree of OTS Slave keys that can be used to sign transactions. This allows further expansion of a BTQ wallet, extending the number of transactions you can process before needing to regenerate a new wallet.
To create a slaves.json
file, you will need a BTQ wallet.json
file and a working installation of BTQ. See the guide for creating a BTQ CLI Wallet.
Currently, the only way to generate a slaves.json
file is by using the command line utility btq
. This can be installed by following the BTQ Node Guide. You will need shell access and be logged into the computer running btq
.
Create a slaves.json
slaves.json
To generate a slaves.json
file, you need to be connected to an active and synced node. This can be a local node or any of the peers shown in your node's peer list. You also need a wallet to use for the slaves file.
Assuming you have a synced node running on the local computer and a wallet.json
file in the local directory, you can simply enter:
You will be asked a few questions. You can generate a maximum of 100 slaves with a single master OTS key, which is used to sign the slaves.json
file onto the network, validating the keys.
Example prompts:
Number of Slaves
Tree Height
Available Keys
With slaves.json
8
256
6,553,600
10
1,024
104,857,600
12
4,096
1,677,721,600
14
16,384
26,843,545,600
16
65,536
429,496,729,600
18
262,144
6.871947674×10¹²
This guide ensures you can effectively manage and expand your BTQ CLI wallet using Slave keys.
Last updated