🧱 Cabal Protocol: Contract Overview
This section highlights the three main smart contracts that users interact with when using The Cabal protocol. These contracts form the interface layer of our secure token deployment and liquidity locking system.
⚠️ Note: While The Cabal operates with additional underlying contracts, this guide focuses only on the ones relevant for direct interaction.
🔗 Core Interaction Contracts
CabalFactory
Main contract for deploying new tokens and triggering liquidity setup.
CabalV3LiquidityLocker
Handles locking of Uniswap V3 LP NFTs and routing protocol/user fees.
CabalV4LiquidityLocker
Manages Uniswap V4 LP NFT locks and secure fee extraction from positions.
These are the only contracts users need to interact with directly. Whether you're deploying a token or managing your liquidity, all user flows are powered by one of these three contracts.
⚙️ How It Works
All token deployments go through
CabalFactoryIf your token uses Uniswap V3, liquidity is locked via
CabalV3LiquidityLockerIf your token uses Uniswap V4, liquidity is locked via
CabalV4LiquidityLocker
By keeping the architecture modular, we ensure your deployments are:
Secure (LP is always locked)
Permissionless (ownership is renounced)
Aligned with community standards (fees are automated and fair)
Dive deeper into each contract to understand how the system works from the ground up.
For more information, visit https://thecabal.app or join our community on Telegram.
Last updated