PantherSwarm
  • Introduction
    • What is Pantherswarm?
  • Development Road Map
  • Community Road Map
  • Swarm
    • Cub
  • Truffle Hog (scanner)
  • Panther AI
  • Wild Cat (Wallet Manager)
  • Tokenomics
    • $Panther
    • NFT Investor Pass / Liquidity Raise
  • System Architecture
    • Overview
    • Technology Stack
    • Data Flow
    • Ingestion
  • Ai Agents
  • Delivery
  • Contracts overview
  • Contracts Staking
  • Developers
    • Getting Started
    • Api
    • Security Audits
  • Dictionary
    • Dictionary: Key Terms
Powered by GitBook
On this page
  • Smart Contracts Overview
  • Key Contracts
  • Contract Interaction Flow

Contracts overview

Smart Contracts Overview

Panther utilizes several smart contracts deployed on the Hyperliquid EVM layer to manage its token, NFT collection, staking mechanisms, and revenue distribution. Security and reliability are top priorities in their design and implementation.

Key Contracts

  • PantherToken.sol ($PANTHER): The core ERC20 contract for the native utility token.

    • Handles token transfers, balances, approvals.

    • Fixed total supply.

  • PantherNFTPass.sol: The ERC721 contract for the NFT collection.

    • Handles minting, ownership tracking, metadata URI.

    • Implements royalty standards (e.g., EIP-2981) for secondary sales.

  • PantherTokenStaking.sol: Allows users to stake $PANTHER tokens.

    • Calculates and distributes revenue share rewards (W% pool) to stakers.

    • May handle emission rewards from the Ecosystem Fund (if applicable).

  • PantherNFTStaking.sol: Allows users to stake their Panther NFT Passes.

    • Calculates and distributes revenue share rewards (Z% pool) based on NFT tier multipliers.

  • RevenueDistributor.sol: Central contract responsible for receiving protocol revenue and splitting it according to the defined percentages (X%, Y%, Z%, W%, V% from Tokenomics).

    • Interacts with DEXs for token buybacks.

    • Sends funds to staking contracts and treasury.

  • (Phase 3) StrategyVault.sol (Conceptual): Future contracts that would manage user-deposited capital and execute automated trading/LP strategies based on AI agent signals. These will require separate, rigorous design and audits.

Contract Interaction Flow

(Diagram Placeholder: A visual diagram showing how revenue flows into RevenueDistributor, which then sends funds to Staking contracts, performs buybacks on a DEX, and sends funds to the Treasury)

  1. Protocol Revenue (NFT Royalties, future fees) is collected and periodically sent to the RevenueDistributor contract.

  2. RevenueDistributor splits funds based on pre-set parameters.

  3. Funds allocated for buybacks are used to purchase $PANTHER (or potentially NFTs) on a DEX; acquired tokens are handled according to policy (burn/redistribute).

  4. Funds allocated for revenue share are sent to the respective PantherTokenStaking and PantherNFTStaking contracts.

  5. Staking contracts make rewards claimable by users based on their staked amount and duration (and NFT tier).

  6. Funds allocated to Treasury/Ops are sent to the designated multi-sig wallet.

PreviousDeliveryNextContracts Staking