Namada Shielded Expedition

Published: 2024-02-06
Updated: 2024-02-16

Namada Shielded Expedition 에 post pilot으로 신청 후 참가
무작정 신청 후 공부해보자는 의미에서 시작함

제네시스 일정이 계속 밀리다가 지난주 시작했는데
꼭두새벽에 시작이라 제시간에 하진 못했고 어찌저찌 본딩까진 완료했는데 어짜피 밸리데이터 풀 들어가려면 스테이킹 금액이 한참 부족한거같아서 그냥 경험삼아 해보자 제대로 돌리는 사람들은 rpc에 도메인 걸어놓고 오픈 해버리는데 멋지다.

진행도중 문제가 생겨서 일정이 뒤로 밀리고 새로 시작함

v0.31.1로 바뀌어서 다시 컴파일하고 이후 스크립트 기록

# 빌드
make install

# 바이너리 옮기고
sudo mv ~/.cargo/bin/namada* /usr/local/bin
sudo cp /usr/local/bin/namada* ~/.local/bin/

# join network - 새로나온 chainid랑 제네시스파일로
export CHAIN_ID="shielded-expedition.88f17d1d14"
NAMADA_NETWORK_CONFIGS_SERVER="https://github.com/anoma/namada-shielded-expedition/releases/download/shielded-expedition.88f17d1d14" namada client utils join-network --chain-id $CHAIN_ID

# 기다리자
2024-02-06T02:38:54.466962Z  INFO namada_apps::node::ledger: Available logical cores: 12
2024-02-06T02:38:54.466993Z  INFO namada_apps::node::ledger: Using 6 threads for Rayon.
2024-02-06T02:38:54.467010Z  INFO namada_apps::node::ledger: Using 6 threads for Tokio.
2024-02-06T02:38:54.467663Z  INFO namada_apps::node::ledger: Waiting for ledger genesis time: DateTimeUtc(2024-02-06T18:00:00Z), time left: 55265.532339349s

제네시스 이후에 계속 작성…

2024-02-07

새벽3시쯤 시작했는데 4시쯤 돌려봄. 동기화가 안되는데 또 이슈가 있어서 기다려달라고 함. 정상화되면 다시 시작…

2024-02-08

정상화 후 버전 업데이트 됨(v0.31.2)

이슈 세부 내용 및 업데이트 안내 문서

validator node 업데이트

# 기존 체인 dir 백업 
# cd ~/.local/share/namada && mv shielded-expedition.88f17d1d14 shielded-expedition.88f17d1d14_backup
# -> 이 아니라 base_dir 을 비워야된다고함
mv ~/.local/share/namada ~/.local/share/namada_backup

# update & build
git pull
git checkout v0.31.2
make install

sudo mv ~/.cargo/bin/namada* /usr/local/bin
sudo cp /usr/local/bin/namada* ~/.local/bin/

# join network
export CHAIN_ID="shielded-expedition.88f17d1d14"
NAMADA_NETWORK_CONFIGS_SERVER="https://github.com/anoma/namada-shielded-expedition/releases/download/shielded-expedition.88f17d1d14" namada client utils join-network --chain-id $CHAIN_ID

seed, 피어 값 변경 & consensus timeout값 일시적으로 변경 (후 sync 다되면 다시 복구)

vi shielded-expedition.88f17d1d14/config.toml

seeds = "20e1000e88125698264454a884812746c2eb4807@testnet-seeds.lavenderfive.com:20056,tcp://3c12dd31adf945bd10d551713d8dc22795b7de0c@194.163.172.168:26656"
persistent_peers = "tcp://dc9f803d6a0cbe6c84d20a6d8e4d4e138ccc9635@195.3.222.156:26657,tcp://5890efc822a0fa02d289c6e47cd2ee6b9a4ac693@62.171.156.190:26656,3c12dd31adf945bd10d551713d8dc22795b7de0c@194.163.172.168:26656,tcp://bbde1b8adbb136b743018c7f92f5ee0162433fb6@65.109.39.125:26656,0707d78aca8514a48fffc09803c31e59e7f495ed@34.16.191.152:26656,195763c651dc4586e95beaf11b19346eb4d907fe@34.28.125.251:26656,4ff683191183da06859f4987733803838f69f8f2@218.155.161.169:30600,4f7276ddcb8abe1bcfc92454f925fbe59b819895@34.16.197.7:26656,6553e277ae9cd9098ee6bc518328427eea69eb5b@45.33.86.221:26656,0546acfa046274f76d1f77b72c567768bd2d5cca@185.172.191.9:26656,2c17c1914d5f21b366149caa33bf81e3b2037ba5@34.163.114.26:26656,10f764862481d7545323a4537da711dce111103e@34.155.116.21:26656,672d139bbbea0ec0370bc468529a8f882d5ce862@34.163.230.173:26656,e522f80c98a3997da1701e9e241e8405b17e90fc@34.38.40.86:26656,e1be9c2d3bfee05353f3f213742f3f03edbd3096@34.163.229.97:26656,89300a5836b15315ee4c7f70591a3dc9946fff5d@52.19.225.58:26656,1c134003c7aff4a266f2d7078bc19ceaf2554adf@34.32.50.165:26656,d4e7227050d08b12b0f11526dc1c51d2527cf973@34.32.54.215:26656,b6ffac4f7fcbfaff478e77884d995507a1cf4e1a@35.205.168.17:26656,5f4ed5790c2a0465eb14db751c2c64a2d0638605@34.32.46.90:26656,75513794710941cd05d6e16753959d84c9d11dc7@34.118.44.6:26656,0a9567cbe74911bcd8883b65e5f904ed487785fc@34.154.58.111:26656,b62a83c1bdddaa8e9bef7b1509a58bcab030245b@34.118.26.153:26656,3b15b3844da042f793ac160525ebfb8b79a292f1@136.243.40.38:26656,e3d260468a72078b46d32adb7175ee4b95e2ced2@5.78.77.122:26656"

...

timeout_propose = "300ms" #(used to be "3000ms")
timeout_propose_delta = "0ms" #(used to be "500ms")
timeout_prevote = "100ms" #(used to be "1000ms")
timeout_prevote_delta = "0ms" #(used to be "500ms")
timeout_precommit = "100ms" #(used to be "1000ms")
timeout_precommit_delta = "0ms" #(used to be "500ms")
timeout_commit = "1000ms" #(used to be "10000ms")

(sync 된 후 timeout값 복구)

key 재등록

namada wallet derive --alias "fver1004"

validator init

namada client init-validator   --alias "fver1004-validator"   --account-keys "fver1004"   --signing-keys "fver1004"   --commission-rate 0   --max-commission-rate-change 0
.05   --email "fver1004@gmail.com" --memo "tpknam1qzvehhjlzphkyk8mgle5zms2f0379whtznts6fsrx7w2yc9wtksmwtjp6ea"

# output
The keys for validator "fver1004-validator" were stored in the wallet:
  Validator account key "fver1004-validator-key"
  Consensus key "fver1004-validator-consensus-key"
The ledger node has been setup to use this validator's address and consensus key.
Your validator will be active in 2 epochs. Be sure to restart your node for the changes to take effect!

validator 상태 확인

namadac validator-state --validator fver1004-validator

# output
Validator tnam1q9aglu0v33e7fupevd5nn9805nlhh8ya3gffasce is either not a validator, or an epoch before the current epoch has been queried (and the validator state information is no longer stored)

bond

bond (memo 필수… 까먹고 memo 안적어서 한번더함)

namada client bond --source fver1004 --validator fver1004-validator --amount 1 --memo tpknam1qzvehhjlzphkyk8mgle5zms2f0379whtznts6fsrx7w2yc9wtksmwtjp6ea

bond 확인

namada client bonds --owner fver1004

별도의 faucet이 없는 줄 알았는데 어따쓰는거여(링크)

vote (문서링크)

# proposal 확인. 미션에 맞춰서 하면 됨
namada client query-proposal

namada client vote-proposal --proposal-id 8 --vote yay --address tnam1q9aglu0v33e7fupevd5nn9805nlhh8ya3gffasce --signing-keys fver1004 --memo tpknam1qzvehhjlzphkyk8mgle5z
ms2f0379whtznts6fsrx7w2yc9wtksmwtjp6ea

2024-02-09

체인이 또 멈추었고 다음주월요일에 다시 시작
코스모스쪽 릴레이어에 대해 공부해봐야겠다

2024-02-16

어느새 다시 가동되어서 진행중이었고 확인해보니 나는 jail 로 가버렸다
업데이트 v0.31.4버전으로 진행하는데 에러 발생

2024-02-15T15:01:07.030054Z ERROR namada_apps::node::ledger::broadcaster: Broadcaster failed to connect to CometBFT node
2024-02-15T15:01:07.030092Z ERROR namada_apps::node::ledger::broadcaster: Broadcaster unexpectedly shut down.