▶️Cheat Sheet
Key management
Add new key
KEY_ALIAS="keysha"; namada wallet key gen --alias $KEY_ALIASRecover existing key
namada wallet key restore --alias $KEY_ALIAS --hd-path defaultList all keys
namada wallet key listQuery wallet balance
namada client balance --owner $KEY_ALIASAdd some token using faucet
https://faucet.heliax.click/Multisign
Generate key-1
namadaw key gen --alias my-key1Generate key-2
namadaw key gen --alias my-key2Generate implicit address
namadaw address gen --alias my-addressinit non-multisig account (single signer)
namadac init-account --alias my-multisig-alias --public-keys my-key1 --signing-keys my-key1init multisig account (at least 2 signers)
namadac init-account --alias my-multisig-alias --public-keys my-key1,my-key2 --signing-keys my-key1,my-key2 --threshold 2Submitting a multisignature transaction
mkdir tx_dumpsCreate transaction
namadac transfer --source my-multisig-alias --target some-established-account-alias --token NAM --amount 100 --signing-keys my-key1 --dump-tx --output-folder-path tx_dumpsSigning transaction
namadac transfer --source my-multisig-alias --target some-established-account-alias --token NAM --amount 100 --signing-keys my-key1 --dump-tx --output-folder-path tx_dumpsSave as a variable offline_signature
export SIGNATURE_ONE="offline_signature_FB7246E3FC43F59D8AEEC234EBFDB9DF1AC9BB7B14E536D05A7E2617CA41D4CD_0.tx"Submit Transaction
namadac tx --tx-path "tx_dumps/a45ef98a817290d6fc0efbd480bf66647ea8061aee1628ce09b4af4f4eeed1c2.tx" --signatures $SIGNATURE_ONE --signatures $SIGNATURE_TWO --owner my-multisig-alias --gas-payer my-key1Change the multisig threshold
namadac update-account --address my-multisig-address --threshold 1 --signing-keys my-key1,my-key2Check the threshold has been updated
namadac query-account --owner my-multisig-addressChange the public keys of a multisig account
namadac query-account --owner my-multisig-addressInitialize an established account
namada client init-account --alias establishment --public-keys keysha --signing-keys keysha --threshold 1MASP
Randomly generate a new spending key
namadaw masp gen-key --alias <your-spending-key-alias>Create a new payment address
namadaw masp gen-addr --key <your-spending-key-alias> --alias <your-payment-address-alias>Send your shielding transfer
namadac transfer --source <your-established-account-alias> --target <your-payment-address-alias> --token btc --amount <amount-to-shield>View balance
namadac balance --owner <your-spending-key-alias>Shielded transfer (once the user has a shielded balance, it can be transferred to another shielded address)
namadac transfer --source <your-spending-key-alias> --target <destination-payment-address> --token btc --amount <amount-to-transfer> --signing-keys <your-implicit-account-alias>Unshielding transfers (it is also possible to transfer the balance to a transparent account)
namadac transfer --source <your-spending-key-alias> --target <some-transparent-address-alias> --token btc --amount <amount-to-unshield> --signing-keys <your-implicit-account-alias>Validator Operations
Check sync status and node info
curl http://127.0.0.1:26657/status | jqStake funds
namada client bond --validator $ALIAS --amount 1500 --gas-limit 10000000Check your validator bond status
namada client bonds --owner $ALIASCheck all bonded nodes
namada client bonded-stakeFind all the slashes
namada client slashesSelf Unbonding
namada client unbond --validator $ALIAS --amount 0.3Non-self unbonding
namada client unbond --source aliace --validator $ALIAS --amount 1.2Withdrawing unbonded tokens
namada client withdraw --source aliace --validator $ALIASSync and Consensus
Check logs
sudo journalctl -u namadad -fCheck sync status and node info
curl http://127.0.0.1:26657/status | jqCheck consensus state
curl -s localhost:26657/consensus_state | jq .result.round_state.height_vote_set[0].prevotes_bit_arrayFull consensus state
curl -s localhost:12657/dump_consensus_stateYour validator votes (prevote)
curl -s http://localhost:26657/dump_consensus_state | jq '.result.round_state.votes[0].prevotes' | grep $(curl -s http://localhost:26657/status | jq -r '.result.validator_info.address[:12]')🚨 Maintenance
Remove node
Please, before proceeding with the next step! All chain data will be lost! Make sure you have backed up your priv_validator_key.json !
sudo systemctl stop namadad
sudo systemctl disable namadad
sudo rm -rf /etc/systemd/system/namadad.service
sudo systemctl daemon-reload
sudo rm $(which namada)
sudo rm -rf $HOME/.local/share/namada/public-testnet-15.0dacadb8d663Last updated
Was this helpful?