Run a Node - FAQ

Frequently Asked Questions: If you encounter any questions, we kindly ask you to check this section first. Thank you!

How shall I confirm my node is running correctly?

After running curl -sL1 https://nubit.sh | bash, you should see the following message:

/_____/  /_____/  /_____/  /_____/  /_____/ 
Started nubit DA node 
node version:
node type:      light
network:        nubit-alphatestnet-1
/_____/  /_____/  /_____/  /_____/  /_____/ 

For further check:

$HOME/nubit-node/bin/nubit das sampling-stats --node.store $HOME/.nubit-light-nubit-alphatestnet-1

You will receive a response similar to the following to verify that your node is running successfully:

{
  "result": {
    "head_of_sampled_chain": 143124,
    "head_of_catchup": 143124,
    "network_head_height": 143124,
    "concurrency": 0,
    "catch_up_done": true,
    "is_running": true
  }
}

To check whether the Nubit team records your light node, please go to: https://alpha.nubit.org/


How shall I check whether I am running the latest node?

If you have watched this hint during the execution of nubit.sh, you are running the latest node and we'll do a hot update after this version.

NAME: my_nubit_key
ADDRESS: nubit1xxxx
MNEMONIC (save this somewhere safe!!!): 
xxxx xxxx xxxx xxxx

** PUBKEY **
A9wxxxx

...

For early supporters who executed nubit.sh before this version, please re-execute curl -sL1 https://nubit.sh | bash again.


How shall I check my status if any error happens?

Currently, the light node uses an absolute path, and generally, there's no need to manually set environment variables. Here are some environment variable values for your reference. If any of them is broken, please go to $HOME/nubit-node and fix it. Thanks for your patience!

Environment VariableContent

NETWORK

nubit-alphatestnet-1

NODE_TYPE

light

NKEY

$HOME/nubit-node/bin/nkey

NUBIT

$HOME/nubit-node/bin/nubit

STORE

$HOME/.nubit-light-nubit-alphatestnet-1

AUTH_TYPE

admin

PEERS

/ip4/34.222.12.122/tcp/2121/p2p/12D3KooWJJWdaCB8GRMHuLiy1Y8FWTRCxDd5GVt6A2mFn8pryuf3

VALIDATOR_IP

validator.nubit-alphatestnet-1.com

GENESIS_HASH

AD1DB79213CA0EA005F82FACC395E34BE3CFCC086CD5C25A89FC64F871B3ABAE

NUBIT_CUSTOM

nubit-alphatestnet-1:AD1DB79213CA0EA005F82FACC395E34BE3CFCC086CD5C25A89FC64F871B3ABAE:/ip4/34.222.12.122/tcp/2121/p2p/12D3KooWJJWdaCB8GRMHuLiy1Y8FWTRCxDd5GVt6A2mFn8pryuf3


How shall I get my Nubit address?

You may run this command: (Make sure your light node is running!)

$HOME/nubit-node/bin/nubit state account-address  --node.store $HOME/.nubit-light-nubit-alphatestnet-1

How shall I get my light node PUBKEY

Everytime when you run curl -sL1 https://nubit.sh | bash to start the light node, the PUBKEY will appear in the very beginning, please save it carefully!

You may also run this command to check your PUBKEY: (Make sure your light node is running!)

$HOME/nubit-node/bin/nkey list --p2p.network nubit-alphatestnet-1 --node.type light

Your Nubit light node address PUBKEY will be shown in this area.

How shall I uninstall nubit-node?

The operation would never be reverted!

To uninstall nubit-node, please run the following command:

rm -rf $HOME/nubit-node
rm -rf $HOME/.nubit-light-nubit-alphatestnet-1

Please make sure to save your wallet and Nubit address mnemonic or key so you can re-import them later. For instructions on importing an existing key, please refer to Manage Keys.


How shall I watch my mnemonic again?

Please be careful not to share this mnemonic file as it is your private information. Don't share it with anyone else!

Use the following command to view your mnemonic:

cat $HOME/nubit-node/mnemonic.txt

How Shall I Replace the Current Address with Keplr Address?

First and foremost, please note that the addresses used for running a light node and participating in the Alpha Testnet Campaign can be independent. It is not necessary to unify them.

If you still wish to replace the current address with a Keplr address, please follow these steps:

  1. Delete the selected key

$HOME/nubit-node/bin/nkey delete my_nubit_key -f --node.type light --p2p.network nubit-alphatestnet-1

Replace my_nubit_key with the actual name of the key you wish to delete. We recommend exporting your key and saving it securely before deleting it, so you can restore it later if needed.

  1. Import the keplr key

$HOME/nubit-node/bin/nkey add my_keplr_key --recover --keyring-backend test --node.type light --p2p.network nubit-alphatestnet-1

Replace my_keplr_key with the actual name of the key you wish to import.

  1. List your keys

$HOME/nubit-node/bin/nkey list --p2p.network nubit-alphatestnet-1 --node.type light

List the current keys. Note that when running a light node, only the first key will be used.


Does running a light node create transactions?

A light node itself doesn't create transactions; it verifies and relays transactions created by wallets or other nodes. It's a more resource-efficient way to participate in the Bitcoin network while maintaining a level of security and decentralization.

To explore more interactions with Nubit DA such as transfer and submit blob, please get NUB first and refer to Interact with Nubit DA and Access Nubit DA Explorer.


Will running multiple nodes on the same IP address cause any issues?

Yes, running multiple nodes on the same IP address can cause issues. It is not recommended to do so.


Error: panic: reflect.Value.Addr of unaddressable value

// xxxx
panic: reflect.Value.Addr of unaddressable value

goroutine 1 [running]:
reflect.Value.Addr({0x0?, 0x0?, 0x140004bd550?})
        reflect/value.go:283 +0x64
// xxxx

Please add --rpc.skip-auth to your light node start command.


Error: node is running without state access

Q: Encountering the error node is running without state access. run with --core.ip \u003cCORE NODE IP\u003e to resolve when interacting with Nubit DA.

A: Running curl -sL1 https://nubit.sh | bash will help fix this bug automatically.

Then execute your desired command again. For example:

$HOME/nubit-node/bin/nubit state account-address --node.store $HOME/.nubit-light-nubit-alphatestnet-1

Error: invalid network specified: nubit-alphatestnet-1, allowed values: nubit

Your $NUBIT_CUSTOM is not specified. Running curl -sL1 https://nubit.sh | bash will help fix this bug automatically. For more details, please refer to environment variables.


Error: account nubitxxx not found

Q: Encountering the error "result: rpc error: code = NotFound desc = account nubit13gg52c3hg4xwqw8w5em6nuw87cc9ptls9p820m not found" when making transfers or submitting blobs / Why can't I find my Nubit address in the browser?

A: You need to claim some tokens from the faucet page. Please refer to Get NUB for more details.


Error: GLIBC Issue on Linux x86-64

Q: If you encounter the following error messages when executing the nubit binary on Ubuntu x86-64 (version 20.04 or earlier):

nubit: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by nubit)
nubit: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by nubit)

A: This issue is caused by the absence of GLIBC 2.32 / 2.34 in older versions of x86-64 Ubuntu. To resolve this issue, you can:

  1. Switch to an OS that includes GLIBC 2.32 / 2.34, such as ARM64 Ubuntu 20.04 or x86-64 Ubuntu 22.04.

  2. Or you can manually configure the GLIBC dependencies if you prefer to handle it yourself.


Error: nubit: command not found

Q: What preparations are needed when using `nubit state` to query addresses and balances, or encountering a "nubit: command not found" error when interacting with Nubit DA?

A: First, ensure that the node is continuously running. Running curl -sL1 https://nubit.sh | bash will help fix this bug automatically. For more details, please refer to environment variables.


Error: nubit-node: Permission denied

This is an affair due to user permission of your local env. Please grant enough permission to your current path, like:

sudo chmod 775 your_current_path

Error: store is in use

This error typically occurs because another light node is already running and has locked the store.


Error: head request to peer failed

Q: Why does the PEER ERROR appear when starting the light node?

A: Firstly, please note that this error does not affect the normal operation of your node.

The error may occur due to one of the following reasons:

  1. Scenario 1: The peer you are trying to connect to has registered their address on the p2p network but has subsequently stopped their node. This results in an inability to establish a connection.

  2. Scenario 2: The peer you are trying to connect to has restarted their light node after stopping it and deleting the $HOME/.nubit-light-nubit-alphatestnet-1 directory. This causes your key to change. Although your IP and port remain the same, the key change leads to authentication failure, and thus, the connection cannot be established.

We hope this clarifies the issue. If you have any further questions, please feel free to reach out to our support team.


Last updated