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
    • 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
  • Why Use Audited & Battle-Tested Contracts?
  • Security & Reliability
  • Lower Costs & Faster Development
  • Where to Find Reusable & Audited Contracts
  • Xion Mainnet Contracts Repository
  • Commonly Used CosmWasm Contracts

Was this helpful?

Edit on GitHub
  1. developers
  2. Building for Mainnet

Building with Audited & Battle-Tested Contracts

PreviousXion Testnet: Your Development PlaygroundNextCommunity Engagement: Building Support for Your dApp

Last updated 1 month ago

Was this helpful?

To ensure security, efficiency, and a smoother path to Mainnet approval, developers should prioritize using audited and battle-tested smart contracts whenever possible. Instead of building everything from scratch, integrating trusted, widely used contracts as building blocks can reduce risks, lower costs, and increase the likelihood of governance approval.

Why Use Audited & Battle-Tested Contracts?

Security & Reliability

Audited contracts provide verified security, having undergone professional reviews to identify and eliminate 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. While this repository previously housed all token contracts and various standards, these have since been migrated to dedicated repositories. The cw-plus repository continues to serve as a valuable reference point, directing developers to these essential, community-proven contract implementations.

Lower Costs & Faster Development

Using pre-audited contracts offers significant advantages across your development lifecycle. First and foremost, it dramatically reduces costs - security audits are expensive, and building on verified code minimizes the amount of new code requiring review. This established foundation also streamlines governance approval for Mainnet deployment, as committees can more readily trust contracts with proven security credentials.

Beyond cost savings, these battle-tested solutions accelerate development by providing ready-made functionality out of the box. Instead of reinventing core components, your team can focus their energy on creating unique, value-added features that differentiate your dApp. The cw-plus contracts exemplify this efficiency, offering standardized implementations that have been optimized through extensive real-world use.

Where to Find Reusable & Audited Contracts

Developers can leverage the following repositories to find contracts that are audited, widely used, or community-validated:

Xion Mainnet Contracts Repository

  • – This repository lists all contracts deployed on Mainnet along with their Code IDs, making it easy for developers to instantiate existing contracts instead of deploying new ones.

  • Before using a contract on Mainnet, you should first test its equivalent on Testnet. Ensure your integration works correctly before submitting a governance proposal for Mainnet deployment. Within the contracts repository you will see the version being used under the release column and the link will take you to the actual code you will need to deploy on Testnet.

Commonly Used CosmWasm Contracts

These repositories contain battle-tested smart contracts that have been used across multiple projects in the Cosmos ecosystem. The list does not end here and so we encourage exploring additional repositories for specialized needs.

– Standardized CosmWasm contracts, including CW20 (tokens), CW721 (NFTs), multisigs, and more.

– Lightweight alternatives to CW-Plus contracts with reduced complexity.

– Specialized token contracts that expand on CW20 and CW721 standards.

– A collection of NFT-specific smart contracts that follow the CW721 standard.

cw-plus
cw-20
NFT
Xion Contracts Repository
CW-Plus
CW-Minus
CW-Tokens
Public Awesome CW-NFTs