AIBTC Working Group
  • AIBTC
  • Prompt2DAO
  • AIBTC Contracts
    • DAO Base Layer
    • DAO Extensions
      • Action Proposal Voting
      • Core Proposal Voting
      • DAO Charter
      • Onchain Messaging
      • Payment Processor
      • Timed Vault
      • Token Owner
      • Treasury
    • DAO Proposals
      • Action Proposals
      • Core Proposals
    • Agent Account
  • Agent Tools
    • Overview
    • Available Tools
      • Smart Wallet Tools
      • Agent Wallet Tools
      • DAO Tools
      • Database Tools
      • Faktory Tools
  • AIBTC Cache
    • Overview
    • Contract Calls
      • API Design
      • Endpoints
        • Decode Clarity Value
        • Read-Only Function Calls
        • Contract ABI
        • Known ABI Contracts
      • Clarity Value Types
      • Integration Examples
    • Cache Services
    • Error Handling
    • Utilities
  • Prompting
    • Action Proposal Prompts
    • Smart Wallet Prompts
  • Links
    • Common Terms
    • Our App
    • Discord
    • GitHub
    • Prompt2DAO on X
    • AIBTC on X
  • Documentation Templates
    • Smart Contract Documentation
    • Cache Service Documentation
    • Cache Endpoint Documentation
    • Agent Tool Documentation
    • Prompting Documentation
  • Example Implementations
    • Smart Contract Example
    • Cache Service Example
    • Cache Endpoint Example
    • Agent Tool Example
Powered by GitBook
On this page
  • How Extensions Work
  • Extension Architecture
  • Available Extensions
  • Adding New Extensions
  • Extension Security
  1. AIBTC Contracts

DAO Extensions

Overview of the DAO extension system

Extensions are modular components that provide specific functionality to the DAO. They allow the DAO to be customized and expanded without modifying the core contract.

How Extensions Work

Each extension:

  • Implements the extension trait

  • Can be enabled or disabled by the DAO

  • Has specific permissions and capabilities

  • Interacts with the DAO through a standardized interface

Extension Architecture

Extensions follow a consistent pattern:

  1. Trait Implementation: Each extension implements both the base extension trait and its own specialized trait

  2. Callback Function: All extensions have a standard callback function for DAO communication

  3. Permission Checks: Extensions verify that calls come from authorized sources

  4. Event Logging: Extensions emit events for important actions

  5. Error Handling: Extensions use standardized error codes

Available Extensions

Extension
Purpose
Key Features

Lower-threshold governance

Predefined actions, faster voting

Operational fund management

Periodic withdrawals, controlled spending

High-threshold governance

Arbitrary code execution, high security

Mission and values

On-chain organizational constitution

Communication

Verified DAO messages, permanent records

Revenue generation

Service payments, resource management

Token management

URI updates, ownership controls

Asset management

Multi-asset support, controlled access

Adding New Extensions

New extensions can be added to the DAO through core proposals. To create a new extension:

  1. Implement the extension trait

  2. Implement any specialized traits needed

  3. Follow the standard extension pattern

  4. Submit as a core proposal for DAO approval

Extension Security

Extensions follow these security principles:

  • Only the DAO can enable/disable extensions

  • Extensions verify caller permissions

  • Critical operations require DAO approval

  • Extensions use standardized error handling

  • Extensions emit events for all important actions

For detailed documentation on each extension, see the individual extension pages.

PreviousDAO Base LayerNextAction Proposal Voting

Last updated 1 month ago

Payments/Invoices
Action Proposals
Timed Vault
Core Proposals
DAO Charter
Onchain Messaging
Token Owner
Treasury