⛓️StateSync/Snapshot

πŸ”₯StoryπŸ”₯

TESTNET

StateSync Story Testnet

SOOON

SnapShot Testnet - updated every 12 hours

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

cd $HOME
snap install lz4
sudo systemctl stop story story-geth
cp $HOME/.story/story/data/priv_validator_state.json $HOME/.story/story/priv_validator_state.json.backup
rm -rf $HOME/.story/story/data
rm -rf $HOME/.story/geth/odyssey/geth/chaindata
curl -o - -L https://story.snapshot.stavr.tech/story-snap.tar.lz4 | lz4 -c -d - | tar -x -C $HOME/.story/story/
curl -o - -L https://story.snapshot.stavr.tech/story_geth-snap.tar.lz4 | lz4 -c -d - | tar -x -C $HOME/.story/geth/odyssey/geth/
mv $HOME/.story/story/priv_validator_state.json.backup $HOME/.story/story/data/priv_validator_state.json
wget -O $HOME/.story/story/config/addrbook.json "https://raw.githubusercontent.com/111STAVR111/props/main/Story/addrbook.json"
sudo systemctl restart story-geth
sudo systemctl restart story && sudo journalctl -fu story -ocat

SnapShot Testnet Archive (updated every 2 days)

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

cd $HOME
snap install lz4
sudo systemctl stop story story-geth
cp $HOME/.story/story/data/priv_validator_state.json $HOME/.story/story/priv_validator_state.json.backup
rm -rf $HOME/.story/story/data 
rm -rf $HOME/.story/geth/odyssey/geth/chaindata
curl -o - -L https://story-archive.snapshot.stavr.tech/story-snap.tar.lz4 | lz4 -c -d - | tar -x -C $HOME/.story/story/
curl -o - -L https://story-archive.snapshot.stavr.tech/story_geth-snap.tar.lz4 | lz4 -c -d - | tar -x -C $HOME/.story/geth/odyssey/geth/
mv $HOME/.story/story/priv_validator_state.json.backup $HOME/.story/story/data/priv_validator_state.json
wget -O $HOME/.story/story/config/addrbook.json "https://raw.githubusercontent.com/111STAVR111/props/main/Story/addrbook.json"
sudo systemctl restart story-geth
sudo systemctl restart story && sudo journalctl -fu story -ocat

Live Peers (upd every 2h)

PEERS_URL="https://story-archive.snapshot.stavr.tech/peers-scan.txt"
update_peers() {
PEERS=$(curl -s $PEERS_URL | sed -n 's/^PEERS="\([^"]*\)"$/\1/p')
if [ -n "$PEERS" ]; then
sed -i -e "/^\[p2p\]/,/^\[/{s/^[[:space:]]*persistent_peers *=.*/persistent_peers = \"$PEERS\"/}" $HOME/.story/story/config/config.toml
echo -e "πŸ”₯Peers updated successfully πŸ”₯"
else
echo "Failed to get peer data. Check the URL or try again later."
fi
}
update_peers

Useful Tools

πŸ”₯API-TπŸ”₯: https://story.api.t.stavr.tech πŸ”₯RPC-TπŸ”₯: https://story.rpc.t.stavr.tech

ARCHIVE NODE

  • Addrbook-T (upd every 2h)

wget -O $HOME/.story/story/config/addrbook.json "https://story-archive.snapshot.stavr.tech/addrbook.json"
  • Genesis

wget -O $HOME/.story/story/config/genesis.json "https://raw.githubusercontent.com/111STAVR111/props/main/Story/genesis.json"
  • Auto_install_script-T

source <(curl -s https://raw.githubusercontent.com/111STAVR111/props/main/Story/storyt)

πŸ”₯Decentralization InfoπŸ”₯

RPC Scanning

We scan nodes in real time every 4 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