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 App in 5 Minutes
        • Launch a User Map App on XION in 5 Minutes
        • React Native Mobile App on XION in 5 Minutes
    • Mobile App Development
      • Set up your XION Mobile Development Environment
      • Create Mobile App and Integrate Meta Account Authentication
      • Building a React Native Mobile App with Abstraxion (Xion.js)
    • 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
      • App 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
      • Governance
      • Valuts
      • SCV Audited Contracts
    • Web3 for Web2 Developers
      • Web2 vs Web3 App Architecture: A Comparison
      • Misconceptions and Misapplied Web2 Patterns
      • Recommended Architecture for Apps on XION
    • Building for Mainnet
      • Xion Testnet: Your Development Playground
      • Building with Audited & Battle-Tested Contracts
      • Community Engagement: Building Support for Your app
      • 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
      • Oracles
        • Creating a Smart Contract with Pyth Oracle Integration
      • Indexers: Optimized Data Retrieval
        • SubQuery
      • Use Cases
        • Building a Per-User Data Storage App
    • 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
  • Why Choose Audited & Proven Contracts?
  • Security & Reliability
  • Lower Costs & Faster Time to Market
  • Building for Mainnet

Was this helpful?

Edit on GitHub
  1. developers

Re-using Existing Contracts

PreviousInteract with XION via your Backend ServiceNextDeployed Contracts on XION

Last updated 2 days ago

Was this helpful?

Leveraging existing, battle-tested smart contracts can significantly accelerate development, reduce costs, and improve security. This section highlights a curated list of pre-built CosmWasm contracts that can be deployed out-of-the-box or integrated as modules within your custom smart contracts.

To ensure a secure and streamlined path to Mainnet approval, developers are strongly encouraged to adopt audited, widely used contracts where possible. Rather than building from scratch, using trusted components as building blocks minimizes risk, cuts audit expenses, and increases the likelihood of passing governance reviews.

Why Choose Audited & Proven Contracts?

Security & Reliability

Audited contracts offer vetted security, having undergone expert review to uncover and fix vulnerabilities. Battle-tested contracts offer proven reliability, having been extensively used and validated by the community over time.

A prime example is the collection of contracts. The cw-plus repository continues to serve as a valuable reference point, directing developers to these essential, community-proven contract implementations.

Lower Costs & Faster Time to Market

Pre-audited contracts drastically reduce audit scope and cost, as much of the core logic has already been verified. This accelerates the approval process for Mainnet deployment, where proven security is a major factor.

Additionally, these contracts provide production-ready functionality, allowing developers to focus on building differentiated features rather than reinventing the wheel. The cw-plus suite illustrates this perfectly, offering well-maintained, standardized modules refined through extensive adoption.

Building for Mainnet

We have also put together guides on how to . This section outlines the key differences between Testnet and Mainnet, the requirements for deployment, and best practices to ensure your contracts are approved and adopted by the community. We recommend reading through the contents of this section.

cw-plus
Build to get your Apps on Mainnet