The Allora Network is a state-of-the-art protocol that uses decentralized AI and machine learning (ML) to build, extract, and deploy predictions among its participants. It offers actors who wish to use AI predictions a formalized way to obtain the output of state-of-the-art ML models on-chain and to pay the operators of AI/ML nodes who create these predictions. That way, Allora bridges the information gap between data owners, data processors, AI/ML predictors, market analysts, and the end-users or consumers who have the means to execute on these insights.
The AI/ML agents within the Allora Network use their data and algorithms to broadcast their predictions across a peer-to-peer network, and they ingest these predictions to assess the predictions from all other agents. The network consensus mechanism combines these predictions and assessments, and distributes rewards to the agents according to the quality of their predictions and assessments. This carefully designed incentive mechanism enables Allora to continually learn and improve, adjusting to the market as it evolves.
For the latest documentation, please go to https://docs.allora.network/
Binary can be Installed for Linux or Mac (check releases for Windows)
Specify a version to install if desired.
curl -sSL https://raw.githubusercontent.com/allora-network/allora-chain/main/install.sh | bash -s -- v0.0.8
Ensure ~/.local/bin
is in your PATH.
allorad
will be available.
git clone -b <latest-release-tag> https://github.com/allora-network/allora-chain.git
cd allora-chain && make install
Note: Depending on your go
setup you may need to add $GOPATH/bin
to your $PATH
.
export PATH=$PATH:$(go env GOPATH)/bin
To run a local node for testing purposes, execute the following commands:
make init
allorad start
scripts/l1_node.sh
, you will see the log in the output of the script.
NOTE: scripts/l1_node.sh
will generate keys for the node. For production environments you need to use a proper keys storage, and follow secrets management best practices.
docker compose pull
docker compose up
run docker compose up -d
to run detached.
NOTE: Don't forget to pull the images first, to ensure that you're using the latest images.
docker compose logs -f
After the node is running you can exec RPC calls to it.
For instance, check its status:
curl -so- http://localhost:26657/status | jq .
With curl -so- http://localhost:26657/status | jq .result.sync_info.catching_up
you can check if the node syncing or not.
You can refer to the Allora documentation for detailled instructions on running a full node and staking a validator.
-
Run and sync a full Allora node following the instructions.
-
Wait until the node is fully synced
Verify that your node has finished synching and it is caught up with the network:
curl -so- http://localhost:26657/status | jq .result.sync_info.catching_up
Wait until you see the output: "false"
- Fund account.
l1_node.sh
script generates keys, you can find created account information in data/*.account_info
. Get the address from the file and fund, on testnets you can use faucet https://faucet.${NETWORK}.allora.network
.
- Stake validator (detailled instructions here)
Here's an example with Values which starts with a stake of 10000000uallo.
All the following command needs to be executed inside the validator container.
Run docker compose exec validator0 bash
to get shell of the validator.
You can change --moniker=...
with a human readable name you choose for your validator.
and --from=
- is the account name in the keyring, you can list all availble keys with allorad --home=$APP_HOME keys --keyring-backend=test list
Create stake info file:
cat > stake-validator.json << EOF
{
"pubkey": $(allorad --home=$APP_HOME comet show-validator),
"amount": "1000000uallo",
"moniker": "validator0",
"commission-rate": "0.1",
"commission-max-rate": "0.2",
"commission-max-change-rate": "0.01",
"min-self-delegation": "1"
}
EOF
Stake the validator
allorad tx staking create-validator ./stake-validator.json \
--chain-id=testnet \
--home="$APP_HOME" \
--keyring-backend=test \
--from=validator0
The command will output tx hash, you can check its status in the explorer: https://explorer.testnet.allora.network:8443/allora-testnet/tx/$TX_HASH
- Verify validator setup
VAL_PUBKEY=$(allorad --home=$APP_HOME comet show-validator | jq -r .key)
allorad --home=$APP_HOME q staking validators -o=json | \
jq '.validators[] | select(.consensus_pubkey.value=="'$VAL_PUBKEY'")'
- this command should return you all the information about the validator. Similar to the following:
{
"operator_address": "allovaloper1n8t4ffvwstysveuf3ccx9jqf3c6y7kte48qcxm",
"consensus_pubkey": {
"type": "tendermint/PubKeyEd25519",
"value": "gOl6fwPc19BtkmiOGjjharfe6eyniaxdkfyqiko3/cQ="
},
"status": 3,
"tokens": "1000000",
"delegator_shares": "1000000000000000000000000",
"description": {
"moniker": "val2"
},
"unbonding_time": "1970-01-01T00:00:00Z",
"commission": {
"commission_rates": {
"rate": "100000000000000000",
"max_rate": "200000000000000000",
"max_change_rate": "10000000000000000"
},
"update_time": "2024-02-26T22:50:31.187119394Z"
},
"min_self_delegation": "1"
}
NOTE: please allow 30-60 seconds for the output to be updated
allorad --home=$APP_HOME status | jq -r '.validator_info.voting_power'
- Output should be > 0
If you need to delete a validator from the chain, you just need to unbound the stake.
allorad --home="$APP_HOME" \
tx staking unbond ${VALIDATOR_OPERATOR_ADDRESS} \
${STAKE_AMOUNT}uallo --from ${VALIDATOR_ACCOUNT_KEY_NAME} \
--keyring-backend=test --chain-id ${NETWORK}