Tree News

THORChain · 2026-11-15 07:55 UTC

Hey operators 👋 some nodes have fixed their BASE scanners with eRPC and we're only missing two more for the stuck BASE refund (REFUND:7A9843DD…, 14.88 BASE.ETH) 🙌 If your node's on this list, its Base RPC can't serve the receipts for Base block 53561521 (usually a pruned or snap-synced node): thor12su6q3yrs7lq60z79n4pt75vxtuntaem8xuhvu thor1xskml0m3c6z2p3r5cmfwzn72zdgxtc898lfzzy thor1rp6ll4p2qrj5k9mfelzmwv7ht0gv26pqxka8py thor1szdm49h0pq74jjc8adgk3evnkmsrwd5rtx0k68 thor1nw2jdqn5u8xsx4j0n4e8cmndapxqj47z8zhcs3 thor1m99a3vr6ckafl3wm842zx4k7nq5cempxnx44p8 thor159kkv6wf74teuxkm0vd4ude8eu9sucjytl63d0 thor10tsu3gfzgywyzuuyvmjmlpehdupdcrczemne9y Easy check, you want 35 receipts back, not null: curl -s -X POST <your-base-rpc> -H 'content-type: application/json' -d '{"jsonrpc":"2.0","id":1,"method":"eth_getBlockReceipts","params":["0x33148b1"]}' | head -c 300 Fix with eRPC from node-launcher master (git pull first). Its primary needs to be an RPC that has the old receipts, your own Base RPC goes in as the failover: kubectl -n <namespace> create secret generic base-rpc2 --from-literal=url='<your-base-rpc>' cat > erpc.yaml <<'X' erpc: enabled: true config: primary: endpoint: failover: enabled: true secretName: base-rpc2 secretKey: url thornode: bifrost: erpc: enabled: true X EXTRA_ARGS="-f erpc.yaml" NET=mainnet NAME=<namespace> TYPE=validator make install Or quickest: point BIFROST_CHAINS_BASE_RPC_HOST at Devel's cat > base-rpc.yaml <<'X' thornode: bifrost: env: BIFROST_CHAINS_BASE_RPC_HOST: X EXTRA_ARGS="-f base-rpc.yaml" NET=mainnet NAME=<namespace> TYPE=validator make install It retries every 300 blocks, so as soon as 2 of you fix it, it goes through. Thanks! 🙏

Loading the story on Tree News…