Skip to content

Choose a tag to compare

@github-actions github-actions released this 07 Sep 04:18
· 35 commits to master since this release
4a6a38c

🔧 BitBadges Chain Upgrade — v35
📦 Release v35 • 🆕 Latest Release

Upgrade Name: v35
Upgrade Block Height: Not scheduled — awaiting governance proposal
Estimated Time: To be announced

Summary: EIP-712 transaction signing fixes, bounded paid gas, EVM/native balance accounting repairs, and security hardening for token approvals, pools, manager splitters and IBC rate limits. Stage the v35 binary now; keep the current binary running until the approved upgrade height. Publishing this release does not activate the chain upgrade.


🚨 Important Instructions for Node Operators

To successfully upgrade your node to v35, please follow these steps:

1. Download the New Binary
Download the v35 binary for your platform and network from the release page, along with checksums.txt. Verify the download before installing it. Testnet binaries include testnet in the filename; do not use them on mainnet.

2. Place Binary in the Correct Path
Move the new binary to:

<your_node_home>/cosmovisor/upgrades/v35/bin/

3. Ensure Correct Naming
Rename the binary file to bitbadgeschaind. This is required for nodes using the default Cosmovisor configuration.

4. Check Executable Permissions

chmod +x <your_node_home>/cosmovisor/upgrades/v35/bin/bitbadgeschaind

5. Verify Setup

<your_node_home>/cosmovisor/upgrades/v35/bin/bitbadgeschaind version   # should print v35

6. Cosmovisor Will Auto-Switch
Cosmovisor will automatically switch to the new binary at the approved upgrade height. If your node does not have the correct setup, it will halt and incur downtime until repaired. Operators without Cosmovisor must coordinate the binary switch at that same height.

📚 For full setup and operational details, see the Run a Node documentation.


⚠️ Configuration and Compatibility

  • Set minimum-gas-prices = "10ubadge" in existing nodes' app.toml for v35. New defaults do not rewrite existing homes. CLI transactions should use --gas auto --gas-adjustment 1.5 --gas-prices 10ubadge.
  • ETH claim vouchers use the chain-bound v2 EIP-191 format only. Reissue pre-v35 vouchers with SDK 0.45.0's getETHSignatureChallengeMessage; no legacy fallback exists. Voucher signing is distinct from EIP-712 transaction signing.
  • IBC wildcard aggregation starts new window keys, resulting in a one-time quota reset. Review channel-specific rules before wildcard fallbacks. The separate proposed wildcard configuration is not automatically applied by v35.
  • Use SDK bitbadges@0.45.0 and the coordinated indexer/frontend changes for the original v35 flows. Sendmanager EIP-712 additionally requires published SDK 0.45.1 and consumer adoption. Deploy indexer before frontend and coordinate activation. Their PRs are merged; deployment is a separate operation.
  • Existing deployed ERC-3643 wrapper bytecode is not upgraded automatically.
  • This release does not change circuit-breaker state. Keep any currently disabled message types disabled until separately reviewed and approved.

📝 Notable Changes in v35

  • EIP-712 Cosmos transaction signing fixes, including empty typed-data structures. Tokenization, manager-splitter, sendmanager and the ten routed GAMM message registrations are included.
  • A 100,000,000 block gas limit and fee-market minimum of 10 ubadge per gas. Native precompile work and failed inner calls consume gas while state changes still roll back.
  • EVM/native balance settlement through precisebank, preserving native coin accounting and module permissions.
  • Stronger token approval, wrapper/backing, collection deletion, alias pool and mint-escrow protections. Pool operations no longer silently change the sender's outgoing self-approval.
  • Canonical address validation and migration, including manager-splitter delegate revocations and voting-scope collision handling.
  • Outbound IBC rate limiting, block-time windows, matched refund accounting and aggregate wildcard-channel quotas.
  • Public cosmos/evm v0.7.3 and cosmos/go-ethereum v1.17.2-cosmos-1.

Binaries

Platform Mainnet Testnet
Linux x86_64 bitbadgeschain-linux-amd64 bitbadgeschain-testnet-linux-amd64
Linux ARM64 bitbadgeschain-linux-arm64 bitbadgeschain-testnet-linux-arm64
macOS Intel bitbadgeschain-darwin-amd64 bitbadgeschain-testnet-darwin-amd64
macOS Apple Silicon bitbadgeschain-darwin-arm64 bitbadgeschain-testnet-darwin-arm64
Windows x86_64 bitbadgeschain-windows-amd64.exe bitbadgeschain-testnet-windows-amd64.exe

Verify

For all downloaded assets on Linux:

sha256sum --ignore-missing -c checksums.txt

On macOS, compare shasum -a 256 <downloaded-binary> with its entry in checksums.txt.

Source commit: 4a6a38c9b41cc8166b25deb3b1609c3d8e98fe08.

Validation

The reviewed source passed the full Go suite and a local v34→v35 upgrade, rollback, EVM and four-validator agreement rehearsal. Sampled near-100M-gas transactions passed in a local two-CPU/4-GiB container. SDK and registry-backed consumer checks passed. A full-mainnet snapshot/node rehearsal was explicitly excluded; no full-mainnet IAVL timing or exhaustive production-validator worst-case performance is claimed.

The release workflow passed and published ten mainnet/testnet platform binaries plus checksums. Published asset digests and all four downloaded Linux binaries were verified; the Linux ARM64 release binary passed a local block-production smoke test. Final wallet smoke, voucher issuer compatibility, validator configuration and governance scheduling remain rollout checks.