ixobinary, you'll need the following:
ixobinary is installed into
$(go env GOPATH)/bin, so make sure
$(go env GOPATH)/binis in your PATH (e.g.
export PATH=$(go env GOPATH)/bin:$PATH).
ixobinary serves as the node client and the application client. In other words, the
ixobinary can be used to both run a node and interact with it.
v1.0.8printed to the console. Now that you have successfully installed the
ixobinary, the next step will be to add a couple test accounts.
-k), and the name of the blockchain (
-c). For example, to use the
oskeyring-backend with the name
validatorand the second account
delegator. You will create both accounts using the
testbackend, meaning both accounts will not be securely stored and should not be used in a production environment. When using the
testbackend, accounts are stored in the home directory (more on this in the next section).
datadirectories within the home directory. The
configdirectory is where configuration files for the node are stored and the
datadirectory is where the data for the blockchain is stored. The default home directory is
nodeis the name (or "moniker") of the node and
testis the chain ID. Feel free to change these values but make sure to use the same value for
chain-idin the following steps.
genesis.jsonfile was created within the
configdirectory. In this section, you will be adding two genesis accounts (accounts with an initial token balance) and a genesis transaction (a transaction that registers the validator account in the validator set).
genesis.jsonfile, you are ready to start the node. Starting a node with a new genesis file will create a new blockchain.
ixobinary. Let's delegate some
uixotokens to the validator and then collect the rewards.
uixotokens to the
validatoraccount from the
delegatoraccount and then collected the rewards.