- Run Celestia Devnet
- Pre-Requisites
- Running a Celestia App
- Running a Celestia Node
- Data Availability Sampling(DAS)
If you haven't installed either of app/node, please navigate to each of them
git clone https://github.com/<your_github>/networks.gitThe following instructions assume that you are using Digital Ocean as a cloud provider. Though it should be straightforward to use another provider or even deploy on a local bare-metal server instead. Tested setups:
- One Digital Ocean Droplet on Ubuntu(1 CPU and 1Gb should be enough) and your local Linux-based(Ubuntu prefferably) OS
- Two Digital Ocean Droplets on Ubuntu(1 CPU and 1 Gb should be enough)
- Remember to update your firewall settings. You can check and execute
.networks/scripts/firewall_ubuntu.shscript
Please don't try to build celestia app on macOS Big Sur and higher due to this issue #134
- Creates an account using a script in networks repository
cd networks/scripts
node_name="MightyValidator"
./1_create_key.sh $node_name- After execution of the script, (O) passes account's address to (F)
- Initializes the celestia app chain using a script in networks repository
cd networks/scripts
./creator.sh- Adds (O)'s account address using command
celestia-appd add-genesis-account $O_acc_addr 800000000000celesNote: Currently, we've found an issue that genesis.json is using stake instead of celes token #158
Please, either manually change stake to celes in genesis.json or execute this script:
sudo apt-get install moreutils #contains sponge that we need
cd networks/scripts
./fix_genesis.sh ~/.celestia-app/config/genesis.json- Send the
genesis.jsonto (O). Location of genesis.json file can be find by these default path:
cd ~/.celestia-app/config/genesis.json- Copies
genesis.jsonfrom (F) to local.celestia-app/config/directory:
cp <path_to_downloaded_genesis.json>/genesis.json ~/.celestia-app/config/- Executes
gentxcommand in CLI:
celestia-appd gentx $node_name 5000000000celes --keyring-backend=test --chain-id devnet-2- Passes
gentx-<hash>.jsonfile to (F). Location of the file can be find in this default path:
cd .celestia-a
8000
pp/config/gentx/ && ls- Copies
gentx-<hash>.jsonfrom (O) to local.celestia-app/config/gentxdirectory - Executes command in CLI:
celestia-appd collect-gentxs- Send the updated version of
genesis.jsonto (O)
- Copies updated
genesis.jsonfrom (F) to local.celestia-app/config/directory:
cp <path_to_downloaded_genesis.json>/genesis.json ~/.celestia-app/config/celestia-appd start❕ If your node is having trouble finding peers to connect with, please update your seeds and peers in your config.toml
To check that all validators are communicating with each other correctly, please look for a same block height for each of a running validator (let’s say block height = 100)
To confirm that everything is ok, you have to check that commit hashes for same block height are the same for all validators.
- Creates an account using a script in networks repository
cd networks/scripts
node_name="chani"
./1_create_key.sh $node_name- Request some testnet tokens in Discord Faucet Channel
- Executes command in CLI:
celestia-appd init <moniker_name> --chain-id devnet-2Example:
celestia-appd init fremen --chain-id devnet-2- Copies
genesis.jsonfromnetworks/devnet-2repo to local.celestia-app/config/directory:
cp networks/devnet-2/genesis.json ~/.celestia-app/config/- Starts syncing the chain using command in CLI:
celestia-appd start --p2p.seeds 74c0c793db07edd9b9ec17b076cea1a02dca511f@46.101.28.34:26656Syncing finishes around 1-2 hours
- Execute command:
celestia-appd tx staking create-validator \
--amount=1000000000celes \
--pubkey=$(celestia-appd tendermint show-validator) \
--moniker=space \
--chain-id=devnet-2 \
--commission-rate=0.1 \
--commission-max-rate=0.2 \
--commission-max-change-rate=0.01 \
--min-self-delegation=1000000000 \
--from=$node_name \
--keyring-backend=testwhich should prompt for:
confirm transaction before signing and broadcasting [y/N]:Inputting y should provide an output similar to:
code: 0
codespace: ""
data: ""
gas_used: "0"
gas_wanted: "0"
height: "0"
info: ""
logs: []
raw_log: '[]'
timestamp: ""
tx: null
txhash: <tx-hash>You should now be able to see your validator from a block explorer such as http://celestia.observer:3080/validators.
If you get an error such as
Error: <keyname>: key not found,
this means your key, the field referenced by the --from option, does not exist.
You can fix this by adding your key manually to the keyring via:
celestia-appd keys add --recover <keyname>
followed by a prompt to enter a bip39 mnemonic, which is the mnemonic that was created as part of 1_create_key.sh script in the first step.
You'll also be asked for a passphrase which is an input you have to define.
After this fix repeat step 6.
You need to have the trusted hash in order to initialize the full celestia node In order to know the hash, you need to query the celestia-app:
curl -s http://localhost:26657/block?height=1 | grep -A1 block_id | grep hash- Initialize the full node
celestia full init --core.remote <ip:port of celestia-app> --headers.trusted-hash <hash_from_celestia_app>Example:
celestia full init --core.remote tcp://127.0.0.1:26657 --headers.trusted-hash 3BDFBD7E2D97215CFA600DD8B39AAEECC015E43FEE7B8A4D8A8B630E8B4D4006- Edit configurations
If you have multiple celestia full nodes, then you need to add them as mutual peers in the config.toml file and allow the peer exchange. This is needed in order for celestia full nodes communication between each other.
nano ~/.celestia-full/config.toml...
[P2P]
...
MutualPeers = ["/ip4/<ip>/tcp/2121/p2p/<pubKey>"] #add multiaddresses of other celestia full nodes
PeerExchange = true #change this line to true. Be default it's false
...
...- Start the full node
celestia full startNow, the celestia full node will start syncing headers and storing blocks from celestia app.
Note: At startup, we can see the multiaddress from celestia full node. This is needed for future light client connections and communication between celestia full nodes
Example:
/ip4/46.101.245.50/tcp/2122/p2p/12D3KooWKNBZvF93L92aTYs6jRyozicGmuu3cF9gotMtUCeHAPYNTo start the light client, we need to know 2 variables:
- Trusted peer’s multi address to connect to (a celestia full node is the case here)
- Trusted block hash from celestia-app
- Initialize the light client
celestia full init --headers.trusted-peer <full_node_multiaddress> --headers.trusted-hash <hash_from_celestia_app>Example:
celestia light init --headers.trusted-peer /ip4/46.101.245.50/tcp/2122/p2p12D3KooWKNBZvF93L92aTYs6jRyozicGmuu3cF9gotMtUCeHAPYN --headers.genesis-hash F10679041E3D55363405C1D3080B91004BCAE471F35F1FBABC345B8237AEFDA2 - Start the light client
celestia light startNow, the celestia light client will start syncing headers and do data availability sampling(DAS) from the full node.
This is a list of runnining components you need in order to successfully continue this chapter:
- celestia app validator
- celestia full node
- celestia light client
You will need 2 terminals in order to see how DASing works:
- In (ST) Submit a
payForMessagetransaction withcelestia-appd
celestia-appd tx payment payForMessage <hex_namespace> <hex_message> --from <node_name> --keyring-backend <keyring-name> --chain-id <chain_name> -yExample:
celestia-appd tx payment payForMessage 0102030405060708 68656c6c6f43656c6573746961444153 --from eva00 --keyring-backend test --chain-id devnet-2 -y- In (FT) you should see in logs how DAS is working
Example:
INFO das das/daser.go:96 sampling successful {"height": 81547, "hash": "DE0B0EB63193FC34225BD55CCD3841C701BE841F29523C428CE3685F72246D94", "square width": 2, "finished (s)": 0.000117466}