v24

v24 Latest

🔧 BitBadges Chain Upgrade — v24
📦 [Release v24](https://github.com/BitBadges/bitbadgeschain/releases/tag/v24) • 🆕 [Latest Release](https://github.com/BitBadges/bitbadgeschain/releases/latest)

Upgrade Name: v24
Upgrade Block Height: [INSERT_BLOCK_HEIGHT]
Estimated Time: [INSERT_DATE_TIME]

Summary of update: [INSERT_SUMMARY]

🚨 Important Instructions for Node Operators
To successfully upgrade your node to v24 please follow these steps:

Download the New Binary
Download the latest v24 binary from the [release page](https://github.com/BitBadges/bitbadgeschain/releases/tag/v24).

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

<your_node_home>/cosmovisor/upgrades/v24/bin/
Ensure Correct Naming
Rename the binary file to:

bitbadgeschaind
This is required for nodes using the default Cosmovisor configuration.

Check Executable Permissions
Ensure the binary is executable:

chmod +x <your_node_home>/cosmovisor/upgrades/v24/bin/bitbadgeschaind
Verify Setup
Run the following to confirm the version and setup:

<your_node_home>/cosmovisor/upgrades/v24/bin/bitbadgeschaind version
Cosmovisor Will Auto-Switch
Cosmovisor will automatically switch to the new binary at the specified block height. If your node does not have the correct setup, it will halt and could be slashed.

📚 For full setup and operational details, see the [Run a Node documentation](https://docs.bitbadges.io/for-developers/bitbadges-blockchain/run-a-node).

⚠️ CRITICAL: CosmWASM Removal and EVM Addition

This upgrade includes major architectural changes:

CosmWASM Removal:

• The CosmWASM module has been completely removed from the chain
• WASM stores (wasm-store and wasmx-store) are deleted during the upgrade
• No WASM library installation is required - the libwasmvm library is no longer needed
• If you previously had libwasmvm installed, you can optionally remove it (not required)

EVM Integration:

• Full Ethereum Virtual Machine (EVM) compatibility has been added via the cosmos/evm module
• New stores are added: evm, erc20, feemarket, and precisebank
• The chain now supports:
  • JSON-RPC API - Standard Ethereum JSON-RPC endpoints (port 8545)
  • ERC20 Wrapping - Native Cosmos coins can be wrapped as ERC20 tokens
  • Custom Precompiles - Direct access to tokenization, Gamm, and SendManager modules from Solidity
  • Dual Wallet Support - Same address works for both Cosmos and EVM transactions
  • EVM Chain IDs: Mainnet (50024), Testnet (50025), Local dev (90123)

Precompiles Available:

• Default Cosmos precompiles (0x0800-0x0806): Staking, Distribution, ICS20 (IBC), Vesting, Bank, Governance, Slashing
• Custom BitBadges precompiles:
  • 0x1001 - Tokenization precompile (create collections, transfer tokens, manage approvals)
  • 0x1002 - Gamm precompile (AMM liquidity pool operations)
  • 0x1003 - SendManager precompile (send native Cosmos coins from EVM)

📝 Notable Changes in v24

• CosmWASM removed - WASM and WASMX modules completely removed from the chain
• EVM integration added - Full Ethereum Virtual Machine compatibility via cosmos/evm module
• ERC20 support - Native Cosmos coins can be wrapped as ERC20 tokens
• Custom precompiles - Tokenization, Gamm, and SendManager accessible from Solidity smart contracts
• JSON-RPC API - Standard Ethereum JSON-RPC endpoints for Web3 compatibility
• Badges module renamed to tokenization - Module renamed throughout the codebase
• Store migrations - WASM stores deleted, EVM stores (evm, erc20, feemarket, precisebank) added

v23

v23 Latest

🔧 BitBadges Chain Upgrade — v23
📦 [Release v23](https://github.com/BitBadges/bitbadgeschain/releases/tag/v23) • 🆕 [Latest Release](https://github.com/BitBadges/bitbadgeschain/releases/latest)

Upgrade Name: v23
Upgrade Block Height: 8400000
Estimated Time: 1/28/2026, 1:58:28 PM EST

Summary of update: This upgrade removes support for alt-chain signatures, adds allowBackedMinting and allowSpecialWrapping flags that must be toggled on for special handling, and introduces ownershipCheckParty for dynamic stores.

🚨 Important Instructions for Node Operators
To successfully upgrade your node to v23 please follow these steps:

Download the New Binary
Download the latest v23 binary from the [release page](https://github.com/BitBadges/bitbadgeschain/releases/tag/v23).

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

<your_node_home>/cosmovisor/upgrades/v23/bin/
Ensure Correct Naming
Rename the binary file to:

bitbadgeschaind
This is required for nodes using the default Cosmovisor configuration.

Check Executable Permissions
Ensure the binary is executable:

chmod +x <your_node_home>/cosmovisor/upgrades/v23/bin/bitbadgeschaind
Verify Setup
Run the following to confirm the version and setup:

<your_node_home>/cosmovisor/upgrades/v23/bin/bitbadgeschaind version
Cosmovisor Will Auto-Switch
Cosmovisor will automatically switch to the new binary at the specified block height. If your node does not have the correct setup, it will halt and could be slashed.

📚 For full setup and operational details, see the [Run a Node documentation](https://docs.bitbadges.io/for-developers/bitbadges-blockchain/run-a-node).

📝 Notable Changes in v23

• Removed any support for alt-chain signatures
• Added allowBackedMinting and allowSpecialWrapping flags that must be toggled on for special handling
• Added ownershipCheckParty for dynamic stores

v22

v22 Latest

🔧 BitBadges Chain Upgrade — v22
📦 [Release v22](https://github.com/BitBadges/bitbadgeschain/releases/tag/v22) • 🆕 [Latest Release](https://github.com/BitBadges/bitbadgeschain/releases/latest)

Upgrade Name: v22
Upgrade Block Height: 8030000
Estimated Time: 1/9/2026, 11:27:42 AM EST

Summary of update: This upgrade introduces significant improvements to the BitBadges chain including a new sendmanager module for enhanced token routing, custom checker system for flexible validation, removal of timeline-based functionality for simplified API, and various other API simplifications. The sendmanager module enables alias denom routing for seamless handling of both standard coins and custom token types. Custom checkers allow developers to add validation logic at approval, transfer, and collection levels. The timeline removal simplifies the API by converting timeline-based fields (e.g., standardsTimeline → standards, managerTimeline → manager) to direct values, making the interface more straightforward. Additionally, several API changes simplify the codebase by removing deprecated fields and reverting to boolean-based dynamic stores.

🚨 Important Instructions for Node Operators
To successfully upgrade your node to v22 please follow these steps:

Download the New Binary
Download the latest v22 binary from the [release page](https://github.com/BitBadges/bitbadgeschain/releases/tag/v22).

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

<your_node_home>/cosmovisor/upgrades/v22/bin/
Ensure Correct Naming
Rename the binary file to:

bitbadgeschaind
This is required for nodes using the default Cosmovisor configuration.

Check Executable Permissions
Ensure the binary is executable:

chmod +x <your_node_home>/cosmovisor/upgrades/v22/bin/bitbadgeschaind
Verify Setup
Run the following to confirm the version and setup:

<your_node_home>/cosmovisor/upgrades/v22/bin/bitbadgeschaind version
Cosmovisor Will Auto-Switch
Cosmovisor will automatically switch to the new binary at the specified block height. If your node does not have the correct setup, it will halt and could be slashed.

📚 For full setup and operational details, see the [Run a Node documentation](https://docs.bitbadges.io/for-developers/bitbadges-blockchain/run-a-node).

📝 Notable Changes in v22

• New SendManager Module: Added a new sendmanager module that provides alias denom routing capabilities, allowing seamless handling of both standard Cosmos SDK coins and custom token types (e.g., badgeslp:). The module includes MsgSendWithAliasRouting and QueryBalance endpoints with full CLI support.
• Custom Checker System: Introduced a flexible custom checker system allowing developers to register custom validation logic at three levels: approval criteria checkers (for approval processing), global transfer checkers (for pre-transfer validation), and collection verifiers (for collection-level invariants). All checkers can be registered in app.go for easy integration.
• API Simplifications: Removed the numAttempts field from relevant objects to simplify the API and reduce complexity.
• Address List Changes: CreateAddressList objects no longer require the createdBy field, simplifying address list creation.
• Dynamic Stores Reverted to Booleans: Dynamic stores have been reverted back to using boolean values instead of more complex types, improving performance and simplicity.
• Prioritized Approvals Refinement: Prioritized approvals are now only used for special backing and/or minting scenarios, making the approval system more focused and efficient.
• SendManager Refactoring: Significant refactoring of token sending logic to use the new sendmanager module, improving code organization and maintainability while enabling better support for alias denoms.
• Timeline Functionality Removal: Removed all timeline-based functionality from the BitBadges API to simplify the interface. Timeline fields have been converted to direct values (e.g., standardsTimeline → standards, managerTimeline → manager, collectionMetadataTimeline → collectionMetadata). Permissions have been updated accordingly, with TimedUpdatePermission removed and TimedUpdateWithTokenIdsPermission migrated to TokenIdsActionPermission. Migration logic automatically extracts the current value from timeline fields at the block time and converts them to the simplified format. This change affects both the badges and maps modules, making the API more intuitive and easier to use.
• Hardcoded bb1 Addresses for Ownership Check Party: Added hardcoded bb1 addresses for ownershipCheckParty to improve validation and security.
• Voting Challenges and MsgCastVote: Introduced voting challenges functionality along with MsgCastVote message type to enable voting mechanisms within the chain.
• On-Chain Path/Alias/Denom Unit Metadata: Path, alias, and denom unit metadata are now stored on-chain, providing better accessibility and consistency.
• Path/Alias/Denom Split and Redesign: Implemented a split between alias and cosmos wrapper paths, with a redesign that includes amounts and refactoring for improved clarity and functionality.
• ETH Signature Leaf Handling: Added support for handling ETH signature leaves, enhancing cross-chain compatibility and validation capabilities.
• Precalculation Options Refactoring: Precalculation options have been moved to the precalculateBalancesFromApproval object, improving organization and making the API more intuitive.

v21

v21 Latest

🔧 BitBadges Chain Upgrade — v21
📦 [Release v21](https://github.com/BitBadges/bitbadgeschain/releases/tag/v21) • 🆕 [Latest Release](https://github.com/BitBadges/bitbadgeschain/releases/latest)

Upgrade Name: v21
Upgrade Block Height: 7510000
Estimated Time: 12/14/2025, 10:52:18 AM EST

Summary of update: This upgrade introduces the mustPrioritize flag for approval criteria to control auto-scan functionality, adds support for badgeslp wrapped denominations in coin transfers, and improves validation logic for better code quality and readability.

🚨 Important Instructions for Node Operators
To successfully upgrade your node to v21 please follow these steps:

Download the New Binary
Download the latest v21 binary from the [release page](https://github.com/BitBadges/bitbadgeschain/releases/tag/v21).

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

<your_node_home>/cosmovisor/upgrades/v21/bin/
Ensure Correct Naming
Rename the binary file to:

bitbadgeschaind
This is required for nodes using the default Cosmovisor configuration.

Check Executable Permissions
Ensure the binary is executable:

chmod +x <your_node_home>/cosmovisor/upgrades/v21/bin/bitbadgeschaind
Verify Setup
Run the following to confirm the version and setup:

<your_node_home>/cosmovisor/upgrades/v21/bin/bitbadgeschaind version
Cosmovisor Will Auto-Switch
Cosmovisor will automatically switch to the new binary at the specified block height. If your node does not have the correct setup, it will halt and could be slashed.

📚 For full setup and operational details, see the [Run a Node documentation](https://docs.bitbadges.io/for-developers/bitbadges-blockchain/run-a-node).

📝 Notable Changes in v21

• Added mustPrioritize flag to approval criteria (collection, incoming, and outgoing) to control auto-scan functionality - when set to true, approvals must be explicitly prioritized in PrioritizedApprovals to be used
• Added support for badgeslp wrapped denominations in coin transfers - badgeslp: prefixed denoms now use badge module transfer functions for underlying badge transfers (still subject to allowed denoms though)
• Improved validation logic for better code quality and readability with more restrictive checks
• Improved auto scannability functionality to not include amount threhsolds or max num transfer thresholds by default
• Fixed issue with IBC denom expansion in coin transfers

v20

v20 Latest

🔧 BitBadges Chain Upgrade — v20
📦 [Release v20](https://github.com/BitBadges/bitbadgeschain/releases/tag/v20) • 🆕 [Latest Release](https://github.com/BitBadges/bitbadgeschain/releases/latest)

Upgrade Name: v20
Upgrade Block Height: 7152000
Estimated Time: 11/26/2025, 12:42:06 PM EST

Summary of update: This upgrade introduces affiliate handling for gamm swaps and IBC hooks, deprecates native MsgTransferTokens affiliate address taking from protocol fees, fixes gamm amino names to match other modules, and includes minor tracking logic fixes.

🚨 Important Instructions for Node Operators
To successfully upgrade your node to v20 please follow these steps:

Download the New Binary
Download the latest v20 binary from the [release page](https://github.com/BitBadges/bitbadgeschain/releases/tag/v20).

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

<your_node_home>/cosmovisor/upgrades/v20/bin/
Ensure Correct Naming
Rename the binary file to:

bitbadgeschaind
This is required for nodes using the default Cosmovisor configuration.

Check Executable Permissions
Ensure the binary is executable:

chmod +x <your_node_home>/cosmovisor/upgrades/v20/bin/bitbadgeschaind
Verify Setup
Run the following to confirm the version and setup:

<your_node_home>/cosmovisor/upgrades/v20/bin/bitbadgeschaind version
Cosmovisor Will Auto-Switch
Cosmovisor will automatically switch to the new binary at the specified block height. If your node does not have the correct setup, it will halt and could be slashed.

📚 For full setup and operational details, see the [Run a Node documentation](https://docs.bitbadges.io/for-developers/bitbadges-blockchain/run-a-node).

📝 Notable Changes in v20

• Affiliates handling for gamm swaps and IBC hooks
• Deprecate native MsgTransferTokens affiliate address taking from the protocol fee
• Fix gamm amino names to match other modules
• Minor fixes within tracking logic
• Add alt time checks to approval criteria (collection, incoming, and outgoing) for denying transfers during specified UTC hours and days
• Add rate limit + taker fee
• More thorough error handling, especially via custom hooks

v19

v19 Latest

🔧 BitBadges Chain Upgrade — v19
📦 [Release v19](https://github.com/BitBadges/bitbadgeschain/releases/tag/v19) • 🆕 [Latest Release](https://github.com/BitBadges/bitbadgeschain/releases/latest)

Upgrade Name: v19
Upgrade Block Height: 7050000
Estimated Time: 11/21/2025, 4:28:32 AM EST

🚨 Important Instructions for Node Operators
To successfully upgrade your node to v19 please follow these steps:

Download the New Binary
Download the latest v19 binary from the [release page](https://github.com/BitBadges/bitbadgeschain/releases/tag/v19).

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

<your_node_home>/cosmovisor/upgrades/v19/bin/
Ensure Correct Naming
Rename the binary file to:

bitbadgeschaind
This is required for nodes using the default Cosmovisor configuration.

Check Executable Permissions
Ensure the binary is executable:

chmod +x <your_node_home>/cosmovisor/upgrades/v19/bin/bitbadgeschaind
Verify Setup
Run the following to confirm the version and setup:

<your_node_home>/cosmovisor/upgrades/v19/bin/bitbadgeschaind version
Cosmovisor Will Auto-Switch
Cosmovisor will automatically switch to the new binary at the specified block height. If your node does not have the correct setup, it will halt and could be slashed.

📚 For full setup and operational details, see the [Run a Node documentation](https://docs.bitbadges.io/for-developers/bitbadges-blockchain/run-a-node).

📝 Notable Changes in v19

• IBC hooks for swap and post-actions
• Add SwapExactAmountInWithIBCTransfer message to gamm module
• Remove unnecessary intermediate conversions for liquidity pools for badges <-> IBC
• Governance address can act as manager of any collection, if needed
• Fix handling of wrapping paths logic to treat it like a contract initiated by user rather than initiated by contract
• Add IBC backed paths as alternative form of minting
• Add liquidity pool invariant checks every swap for proof of reserves
• Add a no forceful post mint transfers invariant
• Add manager splitting module for an alternative to x/group for collection management
• Add global governance for protocol-reserved addresses (wasm entrypoints, pools, etc.)
• Add collection invariants for pool creation enabled/disabled
• Add wasm / pool address checks for approval criteria
• Add IBC rate limit module for rate limiting IBC transfers

v18

v18 Latest

🔧 BitBadges Chain Upgrade — v18
📦 [Release v18](https://github.com/BitBadges/bitbadgeschain/releases/tag/v18) • 🆕 [Latest Release](https://github.com/BitBadges/bitbadgeschain/releases/latest)

Upgrade Name: v18
Upgrade Block Height: 6930000
Estimated Time: 11/15/2025, 1:21:34 PM

Summary of update: Interface renaming from badges to tokens to align with the more global wording, and slight change in liquidity pool handling where transfers from the pool are now technically initiated by tx creator rather than pool address.

🚨 Important Instructions for Node Operators
To successfully upgrade your node to v18 please follow these steps:

Download the New Binary
Download the latest v18 binary from the [release page](https://github.com/BitBadges/bitbadgeschain/releases/tag/v18).

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

<your_node_home>/cosmovisor/upgrades/v18/bin/
Ensure Correct Naming
Rename the binary file to:

bitbadgeschaind
This is required for nodes using the default Cosmovisor configuration.

Check Executable Permissions
Ensure the binary is executable:

chmod +x <your_node_home>/cosmovisor/upgrades/v18/bin/bitbadgeschaind
Verify Setup
Run the following to confirm the version and setup:

<your_node_home>/cosmovisor/upgrades/v18/bin/bitbadgeschaind version
Cosmovisor Will Auto-Switch
Cosmovisor will automatically switch to the new binary at the specified block height. If your node does not have the correct setup, it will halt and could be slashed.

📚 For full setup and operational details, see the [Run a Node documentation](https://docs.bitbadges.io/for-developers/bitbadges-blockchain/run-a-node).

📝 Notable Changes in v18

• Interface renaming from badges to tokens to align with the more global wording
• Slight change in liquidity pool handling. Transfers from the pool are now technically initiated by tx creator rather than pool address

v17

v17 Latest

🔧 BitBadges Chain Upgrade — v17
📦 [Release v17](https://github.com/BitBadges/bitbadgeschain/releases/tag/v17) • 🆕 [Latest Release](https://github.com/BitBadges/bitbadgeschain/releases/latest)

Upgrade Name: v17
Upgrade Block Height: 6624000
Estimated Time: 10/31/2025, 3:22:42 PM

Summary of update: Minor bug fixes from v16 upgrade with invariants and adding support for x/group messages in the transaction serialization.

🚨 Important Instructions for Node Operators
To successfully upgrade your node to v17 please follow these steps:

Download the New Binary
Download the latest v17 binary from the [release page](https://github.com/BitBadges/bitbadgeschain/releases/tag/v17).

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

<your_node_home>/cosmovisor/upgrades/v17/bin/
Ensure Correct Naming
Rename the binary file to:

bitbadgeschaind
This is required for nodes using the default Cosmovisor configuration.

Check Executable Permissions
Ensure the binary is executable:

chmod +x <your_node_home>/cosmovisor/upgrades/v17/bin/bitbadgeschaind
Verify Setup
Run the following to confirm the version and setup:

<your_node_home>/cosmovisor/upgrades/v17/bin/bitbadgeschaind version
Cosmovisor Will Auto-Switch
Cosmovisor will automatically switch to the new binary at the specified block height. If your node does not have the correct setup, it will halt and could be slashed.

📚 For full setup and operational details, see the [Run a Node documentation](https://docs.bitbadges.io/for-developers/bitbadges-blockchain/run-a-node).

📝 Notable Changes in v17

• Minor bug fixes from v16 upgrade with invariants
• Adding support for x/group messages in the transaction serialization

v16

v16 Latest

🔧 BitBadges Chain Upgrade — v16
📦 [Release v16](https://github.com/BitBadges/bitbadgeschain/releases/tag/v16) • 🆕 [Latest Release](https://github.com/BitBadges/bitbadgeschain/releases/latest)

Upgrade Name: v16
Upgrade Block Height: 6435000

Summary of update: This upgrade includes SDK 0.53.4, code cleansing and changes, and deprecating off-chain balances.

🚨 Important Instructions for Node Operators
To successfully upgrade your node to v16 please follow these steps:

Download the New Binary
Download the latest v16 binary from the [release page](https://github.com/BitBadges/bitbadgeschain/releases/tag/v16).

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

<your_node_home>/cosmovisor/upgrades/v16/bin/
Ensure Correct Naming
Rename the binary file to:

bitbadgeschaind
This is required for nodes using the default Cosmovisor configuration.

Check Executable Permissions
Ensure the binary is executable:

chmod +x <your_node_home>/cosmovisor/upgrades/v16/bin/bitbadgeschaind
Verify Setup
Run the following to confirm the version and setup:

<your_node_home>/cosmovisor/upgrades/v16/bin/bitbadgeschaind version
Cosmovisor Will Auto-Switch
Cosmovisor will automatically switch to the new binary at the specified block height. If your node does not have the correct setup, it will halt and could be slashed.

📚 For full setup and operational details, see the [Run a Node documentation](https://docs.bitbadges.io/for-developers/bitbadges-blockchain/run-a-node).

📝 Notable Changes in v16

• SDK 0.53.4 upgrade
• Code cleansing and improvements
• Deprecating off-chain balances

v15

v15 Latest

🔧 BitBadges Chain Upgrade — v15
📦 [Release v15](https://github.com/BitBadges/bitbadgeschain/releases/tag/v15) • 🆕 [Latest Release](https://github.com/BitBadges/bitbadgeschain/releases/latest)

Upgrade Name: v15
Upgrade Block Height: 5913000
Estimated Time: 9/21/2025, 9:54:12 AM

Summary of update: Liquidity pool compatibility improvements and get the ball rolling on block time reductions

🚨 Important Instructions for Node Operators
To successfully upgrade your node to v15 please follow these steps:

Download the New Binary
Download the latest v15 binary from the [release page](https://github.com/BitBadges/bitbadgeschain/releases/tag/v15).

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

<your_node_home>/cosmovisor/upgrades/v15/bin/
Ensure Correct Naming
Rename the binary file to:

bitbadgeschaind
This is required for nodes using the default Cosmovisor configuration.

Check Executable Permissions
Ensure the binary is executable:

chmod +x <your_node_home>/cosmovisor/upgrades/v15/bin/bitbadgeschaind
Verify Setup
Run the following to confirm the version and setup:

<your_node_home>/cosmovisor/upgrades/v15/bin/bitbadgeschaind version
Cosmovisor Will Auto-Switch
Cosmovisor will automatically switch to the new binary at the specified block height. If your node does not have the correct setup, it will halt and could be slashed.

📚 For full setup and operational details, see the [Run a Node documentation](https://docs.bitbadges.io/for-developers/bitbadges-blockchain/run-a-node).

📝 Notable Changes in v15

• Handle miscellaneous liquidity pool compatibility issues for dynamic denominations and x/badges IBC wrapped denominations
• Change liquidity pool denom prefixes to badgeslp if not wrappable
• New GetWrappableBalances endpoint
• On-chain parameter changes for block time reduction from ~6 to ~3s
• Slashing window to 30k from 20k (Slight reduction in real time)
• Mint blocks per year adjusted to match 3s blocks