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
    • Mobile dapp Development on XION
      • Set up your XION Mobile Development Environment
      • Create Mobile Dapp and Integrate Meta Account Authentication
    • Getting Started (Advanced)
      • 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
      • Dapp Development
        • Account Abstraction with Gasless Transactions
        • Interact with XION via your Backend Service
    • Re-using Existing Contracts
      • Deployed Contracts on XION
      • Non-Fungible Tokens (NFTs)
      • Fungible Tokens
      • Marketplace
      • Multisig
      • Proxy Contracts
      • Membership Management
    • 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

Membership Management

PreviousProxy ContractsNextWeb3 for Web2 Developers

Last updated 1 day ago

Was this helpful?

On-chain group membership management can be useful in governance systems, access control, and permissioned modules. These contracts track who is in a group and how much voting weight each member has, forming the backbone for more complex systems like multisigs (CW3), DAOs, and role-based permissions.

Membership Contracts

Contract
Membership Type
Voting Power Source
Admin Controlled
Staking Required
Use Case

cw4-group

Appointed (manual)

Configured weights

Yes

No

Static groups, multisig backends, role-based access

cw4-stake

Dynamic (via staking)

Token stake

No (stake-based)

Yes

Token-based DAOs, governance by stake

1. cw4-group

A core implementation of the CW4 specification for managing static or admin-controlled groups. Features:

  • Manages a list of members and their voting weights

  • Admin can add, remove, or update members

  • Queryable by external contracts (like CW3 multisigs)

  • Fully compatible with CW3 for governance use

Ideal for: DAOs, governance systems, and multisigs where membership is appointed by an admin or another smart contract 📦 Repo:

2. cw4-stake

An alternative CW4 implementation that calculates group membership based on staked tokens instead of manual assignment. Features:

  • Membership and weight derived from staked token amounts

  • Staking and unstaking adjust voting power dynamically

  • Fully implements the CW4 spec and integrates with CW3 contracts

  • Allows DAO participation to be directly tied to token economics

Ideal for: Token-weighted governance, DAOs with dynamic membership, and voting systems where stake = influence 📦 Repo:

cw4-group
cw4-stake