Created by Demipoet. Let's connect at Farcaster! ... Don't have Farcaster account yet? Create your FC account here.
Current Version: 1.4.16 (Sunset) as of April 18, 2024
Want to refer to the old PDF Guide: 🔗
| No. | The NEW CLI Commands in Quilibrium 1.5.0 |
|---|---|
| 1. | General Command Syntax - 🔗 |
| 2. | Querying Balance - 🔗 |
| 3. | Querying Individual Coins - 🔗 |
| 4. | Creating a Pending Transaction - 🔗 |
| 5. | Accepting a Pending Transaction - 🔗 |
| 6. | Performing a Mutual Transfer - 🔗 |
| 7. | Claiming Rewards - 🔗 |
| No. | Setting up your Quilibrium Node |
|---|---|
| 1. | Secure your Node hardware (VPS) - 🔗 |
| 2. | SSH for the first time to your new VPS - 🔗 |
| 3. | Prerequisite software - 🔗 |
| 4. | Configure Linux network device settings - 🔗 |
| 5. | Clone the Quilibrium CeremonyClient Repository - 🔗 |
| 6. 6.B. |
Import your Voucher Hex - 🔗 - Run go run once to Create your Q Wallet and .config` folder - 🔗 |
| 7. | Configure your Node Network Firewall - 🔗 |
| 8. - - |
Configure your config.yml - 🔗 - Enable gRPC to enable gRPC Function Calls for your Node - 🔗 - Enable Stats Collection by Opt-In - 🔗 |
| 9. - - |
Safekeep the Q Wallet Private Key and Encryption Key - 🔗 - keys.yml - 🔗 - config.yml - 🔗 |
| 10. | Build the node Binary in /root/go/bin Folder - 🔗 |
| 11. - |
Create System Service for your Q Node - 🔗 - Start your Q Node - 🔗 |
| No. | Managing your Quilibrium Node |
|---|---|
| 1. | Monitor trace/info logs of your Q Node service - 🔗 |
| 2. - - - |
Control your Q Node via service commands - 🔗 - Start your Q Node - 🔗 - Stop your Q Node - 🔗 - Check status of your Q Node - 🔗 |
| 3. - |
Upgrading your Q Node to latest release - 🔗 - Complete upgrade code script - 🔗 |
| 4. | Purging your node, keeping the same Peer ID - 🔗 |
| 5. | Using gRPCurl For More Information on Q Network - 🔗 |
| 6. | FAQ - 🔗 |
With the release of Quilibrium 1.5.0, the node application will come with the /client folder for you to have better visibility on your node's conditions, earned rewards and perform transfer transactions.
The CLI tooling itself will be relatively simple, and the commands can be run as follows (assuming a build in the accompanying /client folder rather than go run ./...:
client [--config=<other path than ../node/.config/>] <app> <cmd> <param1> <param2> <...>
The command line tool takes arguments in either decimal (xx.xxxxx) format or raw unit (0x00000) format. Note that raw units are a multiple of QUIL: 1 QUIL = 0x1DCD65000 units
Command:
qclient token balance
Response:
$ qclient token balance
50.0 QUIL (Account 0x23c0f371e9faa7be4ffedd616361e0c9aeb776ae4d7f3a37605ecbfa40a55a90)Users may wish to view the individual coins:
Command:
qclient token coins
Response:
$ qclient token coins
25.0 QUIL (Coin 0x1148092cdce78c721835601ef39f9c2cd8b48b7787cbea032dd3913a4106a58d)
25.0 QUIL (Coin 0x2dda9dc9770a1e5a01974fcd5af2a77147d0f19fb4935a1df677ec6050be0a9e)Quilibrium's token application has two modes: a two-stage transfer/accept (or reject), or a single-stage mutual transfer.
Command:
qclient token transfer <ToAccount> <RefundAccount> <Amount|OfCoin>
Response:
To perform a two-stage transfer, you have two options:
$ qclient token transfer <ToAccount> <RefundAccount> <Amount>
<Amount> QUIL (Pending Transaction 0x0382e4da0c7c0133a1b53453b05096272b80c1575c6828d0211c4e371f7c81bb)or
$ qclient token transfer <ToAccount> <RefundAccount> <OfCoin>
<Amount> QUIL (Pending Transaction 0x0382e4da0c7c0133a1b53453b05096272b80c1575c6828d0211c4e371f7c81bb)Omitting the RefundAccount will simply provide your own originating account. The option to specify exists so that you can maintain anonymity when sending by creating a fresh account to receive the refund. The RefundAccount cannot be the same as the ToAccount.
The first is a user-friendly version of a transfer, akin to what account-based networks like Ethereum and Solana do, where you operate on a balance. Behind the scenes, the client is actually splitting and/or merging coins as needed in order to create the requisite amount to send as a discrete coin. The second is an application-aware version of a transfer, akin to what UTXO-based networks like Bitcoin do, where you operate on the raw coin balance under a specific address. If you have good reason to manage coins separately (yet under the control of the same managing account), you will want to use the second option in conjunction with split/merge operations if needed:
$ qclient token split <OfCoin> <LeftAmount> <RightAmount>
<LeftAmount> QUIL (Coin 0x024479f49f03dc53fd702198cd9b548c9e96004e19ef6a4e9c5211a9795ba34d)
<RightAmount> QUIL (Coin 0x0140e01731256793bba03914f3844d645fbece26553acdea8ac4de4d84f91690)
$ qclient token merge <LeftCoin> <RightCoin>
<Total> QUIL (Coin 0x151f4ae225e20759077e1724e4c5d0feae26c477fd10d728dfea962eec79b83f)To accept a pending transaction, you simply run:
$ qclient token accept <PendingTransaction>
<Amount> QUIL (Coin 0x2688997f2776ab5993894ed04fcdac05577cf2494ddfedf356ebf8bd3de464ab)The same applies for rejecting a pending transaction
$ qclient token reject <PendingTransaction>
<Amount> QUIL (PendingTransaction 0x27fff099dee515ece193d2af09b164864e4bb60c19eb6719b5bc981f92151009)This creates a separate pending transaction because if the refund address is specified by the originator, and were they to specify another of your own addresses, it would be no different than accepting.
Pending transactions introduce friction, but without that friction, users can be spammed coins they don't want, or sent coins from an address they do not wish to interact with. If both parties agree in advance to transact, they can perform a mutual transfer, where both parties must be online, but can avoid having to deal with the two-phase transaction. This is great for maintaining privacy (each party's account is private) as well as ensuring a timely completion of a transaction:
On the receiver's side:
$ qclient token mutual-receive <ExpectedAmount>
Rendezvous: 0x2ad567e4fc1ac335a8d3d6077de2ee998aff996b51936da04ee1b0f5dc196a4f
Awaiting sender...and after the sender connects:
Awaiting sender... OK
<Amount> QUIL (Coin 0x0525c76ecdc6ef21c2eb75df628b52396adcf402ba26a518ac395db8f5874a82)On the sender's side:
$ qclient token mutual-transfer <Rendezvous> <Amount>
Confirming rendezvous... OK
<Amount> QUIL (Coin [private])or if using the raw Coin address:
$ qclient token mutual-transfer <Rendezvous> <OfCoin>
Confirming rendezvous... OK
<Amount> QUIL (Coin [private])This will likely be the first unique experience Quilibrium provides to users already familiar with other networks, as privacy preservation is an immediately obvious and first class experience here by showing the user what it can (or cannot) see.
Tokens issued after 1.5.0 are issued by nodes providing their proofs to the Mint Authority functionality of the token application. Claiming those rewards can be configured to be performed automatically (default, generates a new Coin every claim and merges them), or in lump sums at intervals, manually. It is recommended for ease of management that the defaults are applied, so that in the event of hardware failure no rewards go unclaimed.
If you wish to do it manually however, you will need to run:
$ qclient token mint all
<Amount> QUIL (Coin 0x162ad88c319060b4f5ea6dbf9a0c2cd82d3d70dfc22d5fc99ca5371083d68416)After Cassie has done some intensive testing, and working with the folks over at CherryServers, We are happy to announce that they are offering customized server instances for Q node runners.
CherryServers is a Europe-based crypto-friendly bare metal and cloud provider. We are proud to be one of the few service providers who openly embrace web3 as we believe in the principles of free internet, decentralization, and the freedom of choice without being tied down to any particular vendor. With over 20 years of experience and a strong reputation, we have established several successful partnerships within the blockchain field. We're excited to announce our latest partnership with Quilibrium to assist their node running community by offering stable infrastructure to enable high performance node hosting. We are excited to offer the following configurations, which have been validated for Quilibrium node hosting:
Sign-up link: link
- Cloud VDS 4: CPU: 4 x Intel Gold 6230R @ 2.10Ghz (8 vCores), RAM: 32GB, Disk Storage: NVMe 200GB, Backup: 50GB, Bandwidth: 1Gbps uplink, Egress Traffic: 10TB, Ingress unmetered, 96.12 USD/monthly
- E3-1240V3: CPU: E3-1240v3, 4c/8t - 3.4GHz, RAM: 16GB ECC DDRIII , Disk Storage: 2x SSD 250GB, OS Disk: SSD 250GB, Backup: 100GB, Bandwidth: 1Gbps uplink, Egress Traffic: 10TB, Ingress unmetered, 106.92 USD/monthly
- E3-1240V5: CPU: E3-1240v5, 4c/8t - 3.5GHz, RAM: 32GB ECC DDR4, Disk Storage: 2x SSD 250GB, OS Disk: SSD 250GB, Backup: 100GB, Bandwidth: 3Gbps uplink, Egress Traffic: 30TB, Ingress unmetered, 106.81 USD/monthly
- E5-1620V4: CPU: E5-1620v4, 4c/8t - 3.5GHz, RAM: 32GB ECC DDR4, Disk Storage: 2x SSD 250GB, OS Disk: SSD 250GB, Backup: 100GB, Bandwidth: 3Gbps uplink, Egress Traffic: 30TB, Ingress unmetered, 124.20 USD/monthly
- E5-1650V3: CPU: E5-1650v3, 6c/12t - 3.5GHz, RAM: 64GB Registered ECC DDR4, Disk Storage: 2x SSD 250GB, OS Disk: SSD 250GB, Backup: 100GB, Bandwidth: 1Gbps uplink, Egress Traffic: 30TB, Ingress unmetered, 125.66 USD/monthly
- E5-1650V4: CPU: E5-1650v4, 6c/12t - 3.6GHz, RAM: 64GB Registered ECC DDR4, Disk Storage: 2x SSD 500GB, OS Disk: SSD 500GB, Backup: 100GB, Bandwidth: 3Gbps uplink, Egress Traffic: 30TB, Ingress unmetered, 132.68 USD/monthly
- E5-1650V3: CPU: E5-1650v3, 6c/12t - 3.5GHz, RAM: 64GB Registered ECC DDR4, Disk Storage: 2x SSD 250GB, OS Disk: SSD 250GB, Backup: 100GB, Bandwidth: 1Gbps uplink, Egress Traffic: 30TB, Ingress unmetered, 125.66 USD/monthly
For the Dawn phase, a server must have a minimum of:
16GB of RAM, preferably 32 GB, 250GB of storage, preferably via SSD, 50MBps symmetric bandwidth, ie 50 download, 50 upload For Intel/AMD, the baseline processor is a Skylake processor @ 3.4GHz with 12 dedicated cores. For ARM, the M1 line of Apple is a good reference, but this has to be a dedicated machine.
With Dusk, these minimum requirements will reduce significantly.
Downloading and install PuTTY: http://putty.org/ or just use your Terminal if you are running MacOS or Linux
Put your IP address into terminal client & click open Click "Accept" Type "root" & click enter Type your password & click enter
SSH into your VPS
Return to top
To SSH into a VPS, run:
ssh root@<ip_address_of_VPS>
The authenticity of host (<ip_address>) can't be established.
ED25519 key fingerprint is SHA256:xxxxxxx
This key is not known by another names
Are you sure you want to continue connecting (yes/no/[fingerprint])?
yes
Warning: Permanently added '<ip_address>' (ED25519) to the list of known hosts. Connection closed by <ip_address> port 22.
Enter the root password SSH into your VPS again:
ssh root@<ip_address_of_VPS>
Enter the root password.
Make sure you are using the root user as this guide is tailored
Run apt update to fetch the latest version of the package list from Ubuntu's software repository
sudo apt -q update
sudo apt install git -y
git --version
It must show:
git version 2.34.1
The release right now (as of 1.2.14) does not support its project builds with go1.21.x nor go1.19.x. It has to be go1.20.x.
wget https://go.dev/dl/go1.20.14.linux-amd64.tar.gz
OR
wget https://go.dev/dl/go1.20.14.linux-arm64.tar.gz
The project support both AMD and ARM.
KNOWN ISSUE FOR CherryServers, For some of their IP addresses, Google.com blocks them and this will prevent you from downloading (wget) the go1.20.14 gzip file from the URL above. To solve this, unfortunately, the only way is to cancel your new VDS and order a new one so that you get a new Primary IP address. I know this because I experienced this when I purchased my Cloud VDS4.
sudo tar -xvf go1.20.14.linux-amd64.tar.gz
sudo mv go /usr/local
sudo rm go1.20.14.linux-amd64.tar.gz
sudo vim ~/.bashrc
Press i to start inserting text into ~/.bashrc file
Scroll until the end of the file, and insert the following in new lines at the end:
GOROOT=/usr/local/go
GOPATH=$HOME/go
PATH=$GOPATH/bin:$GOROOT/bin:$PATH
Press esc to stop the insert-text mode
Press shift + :wq, and press enter or return on the keyboard
Run:
source ~/.bashrc
go version
It must show:
go version go1.20.14 linux/amd64
Return to top
Purpose: to optimize throughput (bandwidth) and latency for large parallel jobs typical of networks like Q
Run:
sudo vim /etc/sysctl.conf
Press i to start inserting text into /etc/sysctl.conf file
Scroll until the end of the file, and insert the following in new lines at the end:
# Increase buffer sizes for better network performance
net.core.rmem_max=600000000
net.core.wmem_max=600000000
Press esc to stop the insert-text mode
Press shift + :wq, and press enter or return on the keyboard
Run:
sudo sysctl -p
Reboot your VPS
reboot
You will be disconnected from your VPS as the VPS reboots
SSH into your VPS again:
ssh root@<ip_address_of_VPS>
Enter the root password
Return to top
Run:
cd ~
git clone https://github.com/QuilibriumNetwork/ceremonyclient.git
Go to the ceremonyclient/node folder
cd ceremonyclient/node
Return to top
Note: Only applicable for those who has an offline voucher (from April 2023 offline declaration for the Freedom of Internet ceremony).
If you do not have a voucher, skip this section and do Section VI.B.
Run:
sudo vim /root/voucher.hex
Press i to start inserting text into voucher.hex file
Copy-paste the 228-character voucher hex into the file
Press esc to stop the insert-text mode
Press shift + :wq, and press enter or return on the keyboard
Run:
GOEXPERIMENT=arenas go run ./... -import-priv-key `cat /root/voucher.hex`
Take note of your Peer ID. The Peer ID may act as your Q Wallet later on.
It will be one of the last lines in the response, starts with 'Qm' with a label Peer ID.
Return to top
Note: Only applicable if you skipped Section VI, because you do not have an offline voucher, and you are installing a fresh Q Node.
Run:
cd ~/ceremonyclient/node
GOEXPERIMENT=arenas go run ./...
As this will trigger for your Q Node to starup, all you really need right now is for the startup script to create you the .config folder inside ~/ceremonyclient/node - to have the 2 files - config.yml and keys.yml created.
Once you see the logs start to trail, you would want to stop the node for now.
You need to open a new terminal window and SSH into your VPS again as root.
Run:
ps aux
and look for the PID of the /root/go/bin/node.
Once you know the PID of the node app, run:
kill -9 <PID>
This will kill the process for the node app. You may proceed to the next section.
Return to top
Run:
sudo ufw enable
Type y and press enter or return on keyboard
Run:
sudo ufw allow 22
sudo ufw allow 8336
sudo ufw allow 443
sudo ufw statusResponse for the status command should be:
> To Action From
> -- ------ -----
> 22 ALLOW Anywhere
> 8336 ALLOW Anywhere
> 443 ALLOW Anywhere
> 22 (v6) ALLOW Anywhere (v6)
> 8336 (v6) ALLOW Anywhere (v6)
> 443 (v6) ALLOW Anywhere (v6)
Note: This interface, while read-only, is unauthenticated and not rate-limited. It is recommended that you only enable them if you are properly controlling access via firewall or only query via localhost (i.e. if port 8337 is used for gRPC calls, best not to allow it on your firewall configuration later and only trigger gRPC calls on localhost).
Go to ceremonyclient/node folder.
cd ~/ceremonyclient/node
Run:
sudo vim .config/config.ymlPress i to start inserting text into config.yml file
On the line, right about the end of file, there is a field listenGrpcMultiaddr: “”, replace it with
listenGrpcMultiaddr: /ip4/127.0.0.1/tcp/8337Press esc to stop the insert-text mode
Press shift + :wq, and press enter or return on the keyboard
Go to ceremonyclient/node folder.
cd ~/ceremonyclient/node
Run:
sudo vim .config/config.ymlPress i to start inserting text into config.yml file
On the line, right about the middle part of file, there is a field engine, append a sub-field called statsMultiaddr
engine:
statsMultiaddr: "/dns/stats.quilibrium.com/tcp/443"Press esc to stop the insert-text mode
Press shift + :wq, and press enter or return on the keyboard
Go to ceremonyclient/node folder.
cd ~/ceremonyclient/node
Run:
sudo vim .config/keys.ymlCopy the following lines on an external file or note on your personal desktop/laptop.
default-proving-key:
id: default-proving-key
type: 0
privateKey: abcde258a29d0eabcde8eaed9741c404133c35f4d781d5c16dff83d4b55efghije77092b91308b6c5b03f39866e01891e643583e5fb00f3f81f3538e19bc25edb931c6ce5d30df1d76de2b4714d2256f49f8e3a141a114ff049d9b1f2c2d3bfc43ba027bac9077thisisafakeprivatekeyc6c5962c1975fe82980fac3b4aa85c1a8bd8cdf4f5163f01405abcde
publicKey: abcde0486a744fc63thisisafakeprivatekeyd8df16af8e287f8bb7fbc9206e24cb7f054a53cacda84fca62337f9e2b3dca20f9121cbxxxxxPress shift + :q, and press enter or return on the keyboard
Go to ceremonyclient/node folder.
cd ~/ceremonyclient/node
Run:
sudo vim .config/config.ymlCopy all text, found in the config.yml file, on an external file or note on your personal desktop/laptop.
key:
keyManagerType: file
keyManagerFile:
path: .config/keys.yml
createIfMissing: false
encryptionKey: abcde4fbef10d6b75c8a5d3xxxxx8c9298e0561c6xxxxxxef4ad345e279xxxxx
rest of the config.yml filePress shift + :q, and press enter or return on the keyboard
Return to top
Run:
GOEXPERIMENT=arenas go install ./...
This will build and compile the node app binary inside /root/go/bin/ folder
Verify that the node binary is built by running:
ls /root/go/bin
It must show
node
Doing this step allows your node to be run as a system service, whereas in case your node shuts down or gets signal killed for whatever reason, the service will enable auto-restarting your node.
The name of the system service we will make is called ceremonyclient
Run:
sudo vim /lib/systemd/system/ceremonyclient.service
Press i to start inserting text into ceremonyclient.service file
Copy and paste the following lines inside the file
[Unit]
Description=Ceremony Client Go App Service
[Service]
Type=simple
Restart=always
RestartSec=5s
WorkingDirectory=/root/ceremonyclient/node
Environment=GOEXPERIMENT=arenas
ExecStart=/root/go/bin/node ./...
[Install]
WantedBy=multi-user.target
Press esc to stop the insert-text mode
Press shift + :wq, and press enter or return on the keyboard
Run:
sudo journalctl -u ceremonyclient.service -f --no-hostname -o cat
While the ceremonyclient system service is not started, nothing will be shown and that is okay
Just maintain this terminal window while you use another window to start your service (in next Section XIII.1)
Run:
service ceremonyclient start
Note #1: If you have the monitoring window on Section XII open, you will notice after executing this start command that your Q Node will start up
Note #2: If you skipped Section VI above, please take note of your Peer ID on the logs shown in monitoring window
Run:
service ceremonyclient stop
Run:
service ceremonyclient status
Return to top
First, run:
service ceremonyclient status
Press ctrl + c on your keyboard twice, to exit the status section in the terminal
If the response says service is Inactive, proceed to git fetch command below.
If response says service is Active, run:
service ceremonyclient stop
Go to ceremonyclient folder.
cd ~/ceremonyclient
Check whether some files are updated in the ceremonyclient git repo, run:
git fetch origin
If there are files shown that are changed or different from your local copy, run:
git merge origin
Go to ceremonyclient/node folder.
cd ~/ceremonyclient/node
Next, do a go clean command to clear all previous build files. Run:
GOEXPERIMENT=arenas go clean -v -n -a ./...
Next, remove the compiled go binary file node, run:
rm /root/go/bin/node
ls /root/go/bin
The ls command should respond empty
Next, make a new build compiled binary file node, run:
GOEXPERIMENT=arenas go install ./...
Verify that the node binary is built again, run:
ls /root/go/bin
Response should show
node
Lastly, start your Q Node via the service command, run:
service ceremonyclient start
service ceremonyclient stop
cd ~/ceremonyclient
git fetch origin
git merge origin
cd ~/ceremonyclient/node
GOEXPERIMENT=arenas go clean -v -n -a ./...
rm /root/go/bin/node
ls /root/go/bin
GOEXPERIMENT=arenas go install ./...
ls /root/go/bin
service ceremonyclient start
The motivation for doing this, during this period as of March 12, 2024, is when your Q Node is seemingly stuck at a certain frame during syncing. This can be the case for the very suspect frame 4067. I added this section for those folks who has finally reached the limits of their patience with frame 4067 and want to start a fresh node, built up using the latest Q release (at the moment, 1.4.5).
Additional insights: I did this experiment myself and is showing good results. The new node never got stuck at 4067, but gets stuck in other frame numbers. Nevertheless, whenever I see this, I only need to stop and start the node and after some time, it moves on to higher frames.
Note: The steps below assume you have followed this guide to setup your Q node initially. Otherwise, the steps below may not be applicable to your node.
Here are the steps:
- Copy your config.yml and keys.yml into your
/rootfolder. command is
cp /root/ceremonyclient/node/.config/config.yml /root
cp /root/ceremonyclient/node/.config/keys.yml /root
- Go to root folder.
cd /root
- Next, delete the whole ceremonyclient folder.
IMPORTANT Note: Please make sure that you have the 2 .yml files inside/rootfolder by doing anls /rootcommand.
rm -rf /root/ceremonyclient
- Delete the node binary file.
rm /root/go/bin/node
- Git clone the repository again.
git clone https://github.com/QuilibriumNetwork/ceremonyclient.git
- Go to node folder.
cd ceremonyclient/node
- Create a .config directory
mkdir .config
- Copy the config.yml and keys.yml into the newly created .config folder
cp /root/keys.yml /root/ceremonyclient/node/.config/
cp /root/config.yml /root/ceremonyclient/node/.config/
- Compile the node binary file.
GOEXPERIMENT=arenas go install ./...
- Start the service.
service ceremonyclient start
To reiterate, this to me is not the final solution. I hope the next releases for Quilibrium will not have these issues anymore. However, if you still notice your node(s) get stuck in a certain frame, after following the steps above, do try to `service ceremonyclient stop` and `service ceremonyclient start` and do further monitoring.
Note: This section is not part of the installation or setup process for the Q Node. The commands within this section are used only after you have successfully completed the steps above and you just want to query for more information about your Q Node.
Reference: https://github.com/mscurtescu/ceremonyclient/wiki/gRPCurl-How-To
There are many ways to install gRPCurl (brew, docker, Go) and since we already have installed Go you may install gRPCurl from the source package
Run:
go install github.com/fullstorydev/grpcurl/cmd/grpcurl@latest
The command above takes care of installing the command in the bin sub-folder of $GOPATH
Verify your installation works, run:
grpcurl -help
As long as the terminal does not say unknown command, but something else, you have successfully installed gRPCurl
Run:
grpcurl -plaintext localhost:8337 quilibrium.node.node.pb.NodeService.GetNodeInfo
Response:
{
"peerId": "QmBgOwjQo6a12345Aq1fvc6wJ3xnTXNTzOLDLwFHyabcde==",
"maxFrame": "7658"
}
Run:
grpcurl -plaintext localhost:8337 quilibrium.node.node.pb.NodeService.GetTokenInfo
Response:
{
"confirmedTokenSupply": "AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACsuy4PqzEAA=",
"unconfirmedTokenSupply": "AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACsuxtRfqwAA=",
"ownedTokens": "AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA=",
"unconfirmedOwnedTokens": "AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA="
}
Values are encoded, but the ownedTokens and unconfirmedTokens are for sure equal to 0. Needs more decoding studies here.
Run:
grpcurl -plaintext -max-msg-sz 5000000 localhost:8337 quilibrium.node.node.pb.NodeService.GetPeerInfo | grep peerId | wc -l
Response:
11000
Run:
grpcurl -plaintext -max-msg-sz 5000000 localhost:8337 quilibrium.node.node.pb.NodeService.GetPeerInfo | less
Response:
{
"peerInfo": [
{
"peerId": "EiCIlJTLaQ+GE0ElmoCTb1wK/OWfWTzDA9hC1AyAmNNCew==",
"multiaddrs": [
""
],
"maxFrame": "1439",
"timestamp": "1708984499614",
"version": "AQIP",
"signature": "uOXC/WFc3tCsaqJKplle2q/oeUDGlwZf/ZrDdjWqn/Z3ZBUZZy2jwbB78vhFrNsArVuEw+x9eSWAVTq7ugE4ME5bUNUB4+7Gl6BtV8vPNwqh5NWbfNooKbHDNyees6MEi+VsM04wS4wf147SLiGPxicA",
"publicKey": "gMTEXXTwVMd9JGBTdJ3+eh/qIGuYapU+PGe7kg3HUgdlj4Ff8NBMVhHxoN/dYLnmpaquGOcqgKcA",
"totalDistance": "AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAET2HAgKu7BSR42UPY8a2MEk/qOTrCjR9shges9bZvO/Ng=="
},
{
"peerId": "EiA3Xnx1esdF2BJXwEuVFXw+gj5g5ss4ajJBQ3TNXWiAxA==",
"multiaddrs": [
""
],
"maxFrame": "6783",
"timestamp": "1704564573411",
"version": "AQIB",
"signature": "JOJoCRUmzizAlFjf3dXB8wAeEvFXsXCIl66A/sLu4hjIJktYzvZPAc83abLeG3Zm8WHhuhtnHH4AXHitiWGlqwtFbWCRE6TuDFioemJBKhRgwS3bLF3KIC0yWEcBSTM5hgJCDWe7oCSI2NV8n7mufRUA",
"publicKey": "prlfQeX4gLPLOz87HChd1zOWihxXeoVdUBMdBTjNmSYsYAGnJuMmGDdgZoipZWsrgsEbhnjKfa2A",
"totalDistance": "AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAHW0BTyd89JROjwc23I0r7qOJ7ROny+L+EWD1n6OHytKKw=="
},
This question is the most frequently asked of them all. Depending on when you joined in on the project, the answer will vary. At this point, fully-synchronized nodes should start accumulating a balance. We are working to improve synchronization so it's not an incredibly long slog to get there. Everyone who has been participating should see some balance when Dusk launches.
You should see the frame number your node is processing continually increase. This may be slow at first due to heavy fork reconciliation – think of each node with a prover key as being able to send valid frames, but the timereel as a means to choose between them. Because we have had many iterations and lots of early networking issues, we may be initial forks that your node must churn through. We're working on improving sync to be smarter about this so you don't have to reconcile all of them.
Don't run it on IaaS/PaaS providers like AWS/GCP/Azure. The egress fees will eat you alive. If you don't want to/can't run on your own hardware, VPS/ bare metal hosts do well. Be advised: Q uses a lot of bandwidth in this stage.
If you have git and go 1.20 installed, it's just these three steps:
git clone https://github.com/QuilibriumNetwork/ceremonyclient.git
cd ceremonyclient/node
GOEXPERIMENT=arenas go run ./...
If you don't, follow whatever guide for your operating system to install go 1.20 (MUST be 1.20.X, 1.19- won't work, 1.21+ won't either).
Wrong version of golang. Make sure you installed 1.20 (and it has priority on your PATH environment variable)
panic: error getting token info: rpc error: code = Unknown desc = get token info : get highest candidate data clock frame: item not found
goroutine 1 [running]:
main.main()
/root/ceremonyclient/node/main.go:101 +0x745
exit status 2
Nothing.
The -balance command tag when calling the GOEXPERIMENT=arenas go run ./... -balance has been deprecated since Dawn v1.2.9. Unless your node was upgraded to the latest version, yet upgraded from a version <1.2.9 (e.g. 1.2.7) (i.e. the very first version your node ran with was one older than 1.2.9), the -balance command tag will not work anymore and will face the error below.
The same error shows for the GetTokenInfo function if you were to call using gRpcUrl library (see image below)
You can still see your balance in the logs of a running node. In later releases, it is certain there will be a friendlier way to see a node’s $QUIL balance.
No. Tokens do not unlock until Dusk, nobody can transfer you QUIL or buy it from you.
Officially the core Quil dev team is just Cassie as of right now (making this an oddly third person statement), plus many folks who have submitted PRs to the core project, as well as related projects like Agost with quilibrium-rs, and Sir0uk with the nodekeeper dashboard. If you'd like to join in, there's loads of things to work on, please DM!
See 1st question