Heard that cross-chain and Privacy-Preserving Computation is popular? We’re gonna do something different. How about a cross-chain airdrop? To celebrate the upcoming launch of the Oasis mainnet, Bit Cat plans to send out 10,000 ROSE to reward users who have delegated ADA to Bit Cat staking pool on the Cardano network.
1. From now until 2020–11–18 16:00 (UTC), delegate ADA to the CAT pool, and keep this delegation for 3 Epochs (15 days)
2. Snapshots of the delegation to CAT staking pool will be taken at 2020–11–18 16:00 (UTC) and 2020–12–1316:00 (UTC)。 If different lower amount will be taken count…
For node operators the oasis-node binary offers a command line interface for various operations. Let’s introduce some of the most commonly used. You can also view the help using the oasis-node --helpcommand.
Check node sync status:
oasis-node control is-synced -a unix:{sock_file_path} && echo "You are synced" || echo "You are not synced"Check balance/Check nonce:
oasis-node stake account info --stake.account.id {account_id} -a unix:{sock_file_path}Check token info:
oasis-node stake info -a unix:{sock_file_path}Lists all accounts with positive balance:
oasis-node stake list -a unix:{sock_file_path}Send token(sign):
oasis-node stake account gen_transfer \--genesis.file {serverdir}/etc/genesis.json \--signer file \--signer.dir {localhostdir}/entity/ \--stake.amount {amount}…
When running a Coda node, whether it is used for Produce block node or Snark node, it is most important to ensure that the node is not online for 24 hours. So how can you ensure that all Coda nodes are running properly? This article Bit Cat shares the approach we are using.
Get the current block height script (Coda node)
After Coda starts saving nodes, you can use:
coda client status
The command obtains the relevant information of the Coda node, such as:
