github zeta-chain/node drain-mainnet-20261116-base-safe
Emergency drain — MAINNET build (2026-11-16, Base Safe receiver)

pre-releaseone hour ago

Emergency-drain MAINNET binaries (RFC 002). This is not a normal release. It is a dedicated temporary build that operators run only during the drain window and delete afterwards. Supersedes drain-mainnet-20260826.

What changed vs 20260826

The mainnet EVM receiver is now resolved per chain (Receivers.EVMFor(chainID) in pkg/drain/receivers.go). zetatool builds each payload tx to that address, and the zetaclient poller asserts tx.to against the same function. EVM chains that have not been drained yet now go to the Gnosis Safe. Ethereum, BSC and Polygon were already drained and keep the original receiver. BTC is unchanged.

Mainnet chain Receiver
Ethereum 1, BSC 56, Polygon 137 (already drained) 0x0a538985123729f48D70DBCaE82a7f47f1CbA8f8
Base 8453, Arbitrum 42161, Avalanche 43114 (and any other EVM chain) 0x919F207971b9Dea34150D095169388d25e167F1A (Gnosis Safe)
Bitcoin bc1qkl02lqffhmpf5hn3khnetc0ay9yyk4eajmlefy (unchanged)

Safe deployment: as of 2026-11-16 the Safe is deployed at the same address on Base, Arbitrum and Avalanche: same 123-byte proxy code (eth_getCode), the same 4 owners and threshold 1 on all three. Ethereum, BSC and Polygon have no Safe, which is fine because they keep 0x0a53….

Source

  • Client zetaclientd-drain: branch drain-build/mainnet-client-v37-base-safe (off drain-build/mainnet-client-v37 → release/zetaclient/v37), commit 7e589bbd1b45f078d189b4e48a2e0b76f840fc79, -tags pebbledb,ledger,drain. It matches live mainnet signers (zetaclient v37.0.12, zetacore v36.0.6), so it stays compatible with the go-tss ceremony. Review PR: #4652.
  • Server zetatool: branch drain-build/mainnet-server-main-base-safe (off drain-build/mainnet-server-main → main), commit c3cd02744e24a6a1c187138b5151f2fe3ec2f563. Review PR: #4653.
  • Built by workflow run 43967773384 (build-drain-artifacts.yml @ release/zetaclient/v38, inside goreleaser-cross:v1.22.7).

Verified (raw-byte grep, all 4 binaries)

  • glibc: max required 2.28.
  • Build tags (go version -m): client pebbledb,ledger,drain, zetatool pebbledb,ledger.
  • Client: Safe, 0x0a53…, BTC receiver and operator pubkey are present. Testnet anchors are absent.
  • The build log's checked-out commits match the branch HEADs above.
  • Operator pubkey: 0x03579d09c8a72ebf96e943c121926f3bfaf7600b9685eda7692786bf3cfca2c9fc. It is unchanged and still the reused testnet drill key; runbook §9 asks for a fresh key on mainnet.

Operators

Swap the binary the same way as for drain-mainnet-20260826. Download it, check it against SHA256SUMS, replace zetaclientd and restart. It stays dormant and unarmed: the poller does nothing until ZETACLIENT_DRAIN_URL/_NETWORK are set (plus --drain-armed per operator). Funds can only go to the compiled-in receivers. A spoofed payload server can change when a drain fires, never where the funds go.

ce42fd62a10c03d8b4530d09a7a6e6b730181f4da6ded664db6e781b6604dbb0  zetaclientd-drain-linux-amd64
7a718d68e1f0938fb9abe316bd59a8f6281bec8eabf00fea68ba327d2fc81c82  zetaclientd-drain-linux-arm64
0febdc3b88a3a7c1c0338fd52f74eecca17bce0478a43a270a3bc1faaf48b2d2  zetatool-linux-amd64
7a5b139b6af9a82c1d32671748740eef7b8004ef329808e5993ae881015a3c54  zetatool-linux-arm64

Don't miss a new node release

NewReleases is sending notifications on new releases.