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
      • Governance
      • Valuts
    • 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
  • Vault Contracts
  • 1. CW Vault Standard
  • 2. Vaultenator

Was this helpful?

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

Valuts

In Web3 and DeFi, vaults are smart contracts designed to hold and manage assets according to a predefined strategy or set of rules. They serve as automated safes for users’ funds, allowing for more complex behaviours such as yield generation, trading, hedging, time-locking, or role-based access.

Vaults can be:

  • Permissioned – where only specific users or contracts can interact

  • Governed – controlled by DAOs or multisigs for security and flexibility

Vault Contracts

Contract

Purpose

Features

Ideal For

Repo / Docs

CW Vault Standard

Defines a shared interface for vault contracts

Standard API, extensibility, deposit/withdraw, ownership logic

Creating custom vaults with consistent structure

Vaultenator

Vault with advanced financial strategies

Strategy execution, vault config, risk management, trading integrations

Options vaults, yield strategies, DeFi protocols

1. CW Vault Standard

A formalized specification for building interoperable vaults in CosmWasm. This standard defines a shared interface and behavior pattern for vault contracts.

Features:

  • Standardized vault API across projects

  • Easy integration with frontends and third-party protocols

  • Extensible logic for withdrawals, deposits, hooks, and ownership

  • Enables interoperability between vaults and external dApps

Ideal for: Developers creating custom vault contracts that want to follow a shared interface for tooling, composability, and ease of use.

2. Vaultenator

Features:

  • Administration: Handles opening and pausing of contracts.

  • Configuration: Manages contract configuration settings.

  • Ownership: Manages contract ownership details.

  • State Management: Maintains and updates the contract state.

  • CW4626 Compliance: Implements the standard interface for vaults in the CosmWasm ecosystem.

  • Tokenfactory Integration: Utilizes Tokenfactory denoms as vault share tokens.

Ideal for:

Developers seeking a foundational vault contract that complies with the CW4626 standard and leverages Tokenfactory for share token management.

PreviousGovernanceNextWeb3 for Web2 Developers

Last updated 1 day ago

Was this helpful?

📦 Repo / Docs:

Vaultenator is a vault implementation that adheres to the , utilizing the Tokenfactory module for managing vault share tokens.

📦 Repo:

cw-vault-standard
CosmWasm Vault Standard (CW4626)
vaultenator
cw-vault-standard
vaultenator