XION
DiscordGithub
  • Welcome to XION
  • XION'S Core
    • Concepts
      • Generalized Chain Abstraction
      • Intro to Account Abstraction
      • XION's Meta Accounts
      • Meta Accounts Design
      • Architecture & Tech Glossary
      • Use Cases
  • developers
    • Xion Quick Start
      • Zero to Dapp in 5 Minutes
        • Launch a User Map Dapp on XION in 5 Minutes
        • React Native Mobile Dapp on XION in 5 Minutes
      • Set Up Local Environment
        • Setting up your Local Smart Contract Development Environment for XION
          • Setting up your XION Smart Contract Development Environment on Windows (WSL2 + Ubuntu)
        • Set Up an Integrated Development Environment (IDE)
        • Interacting with Xion Chain using Xion Daemon
      • Your First Contract
        • Deploying Your First Smart Contract on XION
      • Gasless UX & Permission Grants
        • Enabling Gasless Transactions with Treasury Contracts
      • Your First DApp
        • Account Abstraction with Gasless Transactions
        • Interact with XION via your Backend Service
    • Mobile dapp Development on XION
      • Set up your XION Mobile Development Environment
      • Create Mobile Dapp and Integrate Meta Account Authentication
    • Re-using Existing Contracts
      • Deployed Contracts on XION
      • Non-Fungible Tokens (NFTs)
      • Fungible Tokens
      • Marketplace
      • Multisig
    • Web3 for Web2 Developers
      • Web2 vs Web3 App Architecture: A Comparison
      • Misconceptions and Misapplied Web2 Patterns
      • Recommended Architecture for Dapps on XION
    • Building for Mainnet
      • Xion Testnet: Your Development Playground
      • Building with Audited & Battle-Tested Contracts
      • Community Engagement: Building Support for Your dApp
      • Deploying to Xion Mainnet
        • Smart Contract Audits: Process, Costs & Support
        • Governance Process to Deploying Smart Contracts to Mainnet
    • Learn & Build
      • Token Factory
        • Creating, Minting, and Interacting with a Token Factory Token
        • Building a React dApp to Interact with Token Factory Tokens
        • Integrating a Token Factory Token in a Smart Contract
      • Websockets
        • WebSockets with Xion: Real-Time Communication
      • Mobile Development
        • Building a React Native Mobile App with Abstraxion (Xion.js)
      • Oracles
        • Creating a Smart Contract with Pyth Oracle Integration
      • Indexers: Optimized Data Retrieval
        • SubQuery
      • Use Cases
        • Building a Per-User Data Storage Dapp
    • Reference and Resources
      • Requesting XION Testnet Tokens
      • Public Endpoints & Resources
      • Block Explorers
      • Governance
        • Deploying Smart Contracts to Mainnet
      • Developer Tools: Abstract
      • IBC Denoms on XION Networks
      • Frequently Asked Questions
      • XION Token Contract Addresses on EVM Chains
  • Nodes & Validators
    • Run a Node
      • System Specifications
      • Build the Xion Daemon
      • Download the Xion Daemon
      • Configure the Xion Daemon
        • app.toml
        • client.toml
        • config.toml
      • Join the XION Network
        • xion-testnet-1
      • Confirm node is running
    • Become a Validator
      • Initial Setup
      • Obtain a XION Wallet Address
      • Obtain Funds
        • Testnet
      • Create Validator
    • IBC Relayers and Tokens
  • Others
    • Resources
Powered by GitBook
On this page

Was this helpful?

Edit on GitHub
  1. developers
  2. Re-using Existing Contracts

Multisig

Multisigs short for multi-signature contracts are smart contracts that require multiple parties to approve an action before it can be executed. Instead of relying on a single private key, control is distributed among a group, increasing security, transparency, and collaborative governance.

In the XION ecosystem and broader CosmWasm world, multisigs are commonly used for:

  • Decentralized treasury management

  • Protocol upgrades or governance decisions

  • Secure deployment of smart contracts

  • Joint ownership of high-value assets

Multisig Contracts

CW3 is the CosmWasm standard for multisig contracts. There are two main implementations: one for static membership and one for dynamic membership.

Contract
Voter Set Type
On-Chain Proposal Flow
Dynamic Membership
Ideal For

cw3-fixed-multisig

Fixed (K-of-N)

Yes

No

Small, static groups

cw3-flex-multisig

Linked to cw4-group

Yes

Yes

DAOs, evolving teams, flexible governance

1. cw3-fixed-multisig

A straightforward multisig implementation with a fixed list of members defined at instantiation. Features:

  • Fixed set of voters with configurable weights

  • On-chain proposal and approval tracking

  • Simple K-of-N signature logic

  • No dependency on external contracts

2. cw3-flex-multisig

An advanced multisig contract backed by a cw4-group contract for flexible, updateable membership. Features:

  • Dynamic voter set via linked cw4-group contract

  • Adjustable weights and thresholds

  • Allows adding/removing members without redeploying the multisig

  • More modular and governance-ready

PreviousMarketplaceNextWeb3 for Web2 Developers

Last updated 6 hours ago

Was this helpful?

Ideal for: Small teams or DAOs with a known and unchanging voter set 📦 Repo:

Ideal for: DAOs and organizations where the voting group may change over time 📦 Repo:

cw3-fixed-multisig
cw3-flex-multisig