⛓️StateSync/Snapshot

🔥Celestia🔥

TESTNET

StateSync Celestia Testnet

RPC="https://celestia.rpc.t.stavr.tech:443"
LATEST_HEIGHT=$(curl -s $RPC/block | jq -r .result.block.header.height); \
BLOCK_HEIGHT=$((LATEST_HEIGHT - 1000)); \
TRUST_HASH=$(curl -s "$RPC/block?height=$BLOCK_HEIGHT" | jq -r .result.block_id.hash)

echo $LATEST_HEIGHT $BLOCK_HEIGHT $TRUST_HASH

sed -i.bak -E "s|^(enable[[:space:]]+=[[:space:]]+).*$|\1true| ; \
s|^(rpc_servers[[:space:]]+=[[:space:]]+).*$|\1\"$RPC,$RPC\"| ; \
s|^(trust_height[[:space:]]+=[[:space:]]+).*$|\1$BLOCK_HEIGHT| ; \
s|^(trust_hash[[:space:]]+=[[:space:]]+).*$|\1\"$TRUST_HASH\"| ; \
s|^(seeds[[:space:]]+=[[:space:]]+).*$|\1\"\"|" $HOME/.celestia-app/config/config.toml
sudo systemctl stop celestia-appd && celestia-appd tendermint unsafe-reset-all --home $HOME/.celestia-app
wget -O $HOME/.celestia-app/config/addrbook.json "https://raw.githubusercontent.com/111STAVR111/props/main/Celestia/Testnet/Node/addrbook.json"
sudo systemctl restart celestia-appd && sudo journalctl -fu celestia-appd -o cat

SnapShot Testnet - updated every 5 hours

You can check the size and time of snapshot creation with this command curl -sI https://celestia-t.snapshot.stavr.tech/celestia-t-snap.tar.lz4 | grep "last" && curl -sI https://celestia-t.snapshot.stavr.tech/celestia-t-snap.tar.lz4 | grep content-length | awk '{printf "%.2f GB\n", $2/1024/1024/1024}'

snap install lz4
sudo systemctl stop celestia-appd
cp $HOME/.celestia-app/data/priv_validator_state.json $HOME/.celestia-app/priv_validator_state.json.backup
rm -rf $HOME/.celestia-app/data
curl -o - -L https://celestia-t.snapshot.stavr.tech/celestia-t-snap.tar.lz4 | lz4 -c -d - | tar -x -C $HOME/.celestia-app --strip-components 2
mv $HOME/.celestia-app/priv_validator_state.json.backup $HOME/.celestia-app/data/priv_validator_state.json
wget -O $HOME/.celestia-app/config/addrbook.json "https://raw.githubusercontent.com/111STAVR111/props/main/Celestia/Testnet/Node/addrbook.json"
sudo systemctl restart celestia-appd && journalctl -fu celestia-appd -o cat

SnapShot Consensus Testnet (Archive) updated every 5 days

You can check the size and time of snapshot creation with this command curl -sI https://celestia-t.archive-snap.stavr.tech/celestia-t-archive.tar.lz4 | grep "last" && curl -sI https://celestia-t.archive-snap.stavr.tech/celestia-t-archive.tar.lz4 | grep content-length | awk '{printf "%.2f GB\n", $2/1024/1024/1024}'

cd $HOME
snap install lz4
sudo systemctl stop celestia-appd
cp $HOME/.celestia-app/data/priv_validator_state.json $HOME/.celestia-app/priv_validator_state.json.backup
rm -rf $HOME/.celestia-app/data
curl -o - -L https://celestia-t.archive-snap.stavr.tech/celestia-t-archive.tar.lz4 | lz4 -c -d - | tar -x -C $HOME/.celestia-app --strip-components 2
mv $HOME/.celestia-app/priv_validator_state.json.backup $HOME/.celestia-app/data/priv_validator_state.json
wget -O $HOME/.celestia-app/config/addrbook.json "https://raw.githubusercontent.com/111STAVR111/props/main/Celestia/Testnet/Node/addrbook.json"
sudo systemctl restart celestia-appd && journalctl -fu celestia-appd -o cat

Useful Tools

🔥EXPLORER-T🔥: https://explorer.stavr.tech/Celestia-Testnet Indexer "ON" 🔥API-T🔥: https://celestia.api.t.stavr.tech 🔥RPC-T🔥: https://celestia.rpc.t.stavr.tech Snapshot-interval = 1000

ARCHIVE NODE

  • Peer-T

d51838bb76758d58642c3a325ac664a964440bdf@celestia.peer.t.stavr.tech:10026
  • Addrbook-T

wget -O $HOME/.celestia-app/config/addrbook.json "https://raw.githubusercontent.com/111STAVR111/props/main/Celestia/Testnet/Node/addrbook.json"
  • Genesis-T

wget -O $HOME/.celestia-app/config/genesis.json https://celestia-t.genesis.stavr.tech/genesis.json
  • Auto_install_script-T

wget -O celest https://raw.githubusercontent.com/111STAVR111/props/main/Celestia/Testnet/Node/celest && chmod +x celest && ./celest

🔥RPC LOCATOR🔥

RPC Scanning

We scan nodes in real time every 24 hours. And we provide the final result of RPC endpoints. We cannot influence the operation of these nodes in any way.

If Voting Power is higher than 0 --> then the Node is a validator of the network and may be subject to attack and be a potential threat to the chain.
We marked such validators with a red symbol

Last updated