Smart Contracts
PananaSwap is powered by a set of publicly deployed smart contracts that handle swap execution, fee enforcement, and routing behavior.
This section provides a high-level overview of how developers can understand and interact with these contracts.
Contract Architecture Overview
PananaSwap smart contracts are designed with a clear separation of responsibilities:
Execution contracts – perform on-chain swap execution
Fee logic – enforce protocol and VIP-based fees
Routing logic – determine valid execution paths
Settlement logic – deliver output tokens directly to users
All contracts operate without custodial control over user funds.
Public and Verifiable
All PananaSwap contracts are:
Publicly deployed on supported networks
Verifiable via standard blockchain explorers
Interactable using standard Web3 tooling
Developers can inspect contract bytecode, events, and transaction traces directly on-chain.
Network Deployments
PananaSwap deploys contracts independently on each supported network.
Ethereum Mainnet
Arbitrum
Base
Contract addresses are network-specific and should always be referenced explicitly when integrating.
Deterministic Behavior
Smart contract execution is deterministic:
Identical inputs result in identical execution paths
No per-user overrides exist
No off-chain parameters influence execution
This ensures predictable behavior for developers and integrators.
Fee Enforcement
Protocol fees are enforced at the contract level.
Fee logic is executed as part of swap execution
VIP-based fee tiers are applied automatically
Fee calculations are transparent and traceable
There are no interface-level or off-chain fee adjustments.
Events and Observability
Smart contracts emit events that can be used to:
Track swap executions
Monitor fee deductions
Aggregate volume and usage statistics
These events form the basis for analytics, dashboards, and external integrations.
External Protocol Interaction
PananaSwap contracts may interact with external liquidity protocols.
External protocol logic is not modified
Execution depends on available on-chain liquidity
Risks associated with external contracts remain inherent
Developers should account for these dependencies when building integrations.
Upgrade and Compatibility Considerations
Contracts may evolve over time.
New deployments may be introduced
Deprecated contracts may remain on-chain
Documentation is updated to reflect material changes
Backward compatibility is considered where feasible, but not guaranteed.
Integration Responsibility
Developers integrating with PananaSwap are responsible for:
Selecting the correct network and contract addresses
Handling reverted transactions
Managing gas estimation and slippage
PananaSwap does not provide guarantees for third-party integrations.
Last updated