Core Trading
Fixed-price listings with a non-custodial architecture — NFTs remain in the seller's wallet until purchase completes. One-click purchases with transparent fee breakdown shown before transaction confirmation. Atomic settlement ensures NFT transfer, payment, fees, and burn all occur in a single transaction with no partial states.
ERC-721 and ERC-1155 fully supported. Sellers can cancel or update listings at any time. Batch operations allow listing multiple NFTs from a collection in a single transaction. Creator royalties are automatically enforced based on on-chain metadata using EIP-2981.
- Fixed-price listings: sellers set specific $APE price
- Non-custodial: NFTs stay in seller wallet until sale completes
- Instant listing updates and cancellations
- Batch operations: list multiple NFTs in one transaction
- One-click purchase with transparent fee breakdown upfront
- Atomic settlement: NFT + payment + fees + burn in single tx
- EIP-2981 creator royalty enforcement — automatic, on-chain
- ERC-721 support for standard 1-of-1 NFTs
- ERC-1155 support for semi-fungible and edition collections
Native Minting
Integrated minting capabilities designed to streamline creator onboarding and ensure all new NFT launches on ApeChain contribute to the burn mechanism from day one. The MintFactory contract deploys standardized ERC-721 and ERC-1155 contracts — creators don't need to write or audit their own Solidity code.
Creators receive approximately 99.5% of mint revenue (the 0.5% platform fee is routed through FeeRouter with 25% burned). Secondary royalties set at collection creation are enforced on-chain for all subsequent trades. Custom mint page generation with collection branding included.
- Web-based contract deployment — no coding required
- Standardized ERC-721 and ERC-1155 deployment templates
- Configurable supply caps, mint prices, per-wallet limits
- Optional allowlist/whitelist for phased launches
- IPFS integration for metadata and asset hosting
- Automatic 0.5% fee routing with 25% burn — integrated
- Creator receives 99.5% of mint revenue minus burned portion
- Custom mint page generation with collection branding
- Real-time mint analytics and holder distribution dashboard
Competition System
Long-horizon competitions running 90–120 days with clearly defined metrics and reward structures announced at competition start. Eligible activities: NFT purchases (volume and frequency), NFT sales (successful listings and sales), NFT mints (participation in new launches), and active participation (regular platform usage over the period).
The long duration is a deliberate anti-gaming mechanism. Fees accumulate significantly over 90+ days, making circular wash-trading economically unfeasible — the accumulated platform fees would exceed the value of any prize. Metrics consider both volume and frequency, not just total value. Wallet age and historical activity may factor into scoring algorithms.
- 90–120 day competition periods — long duration defeats wash trading
- Eligible: NFT purchases, sales, mints, and active participation
- Multi-metric scoring: volume AND frequency, not just total value
- Wallet age and historical activity may factor into scoring
- Prize pools funded entirely by protocol treasury (no new tokens)
- BAYC/MAYC/Otherside NFTs purchased on secondary markets
- On-chain reward distribution via CompetitionManager.sol
- Public real-time leaderboard with transparent scoring
- Prize pools scale automatically with treasury balance
Analytics & Transparency
A fully public analytics dashboard requiring no authentication — open to any user, researcher, or integrator. Every metric sourced directly from on-chain data via the event indexer. Burns are publicly verifiable by querying the zero address balance or listening to BurnExecuted events directly on-chain.
- Real-time total $APE burned — live counter from on-chain events
- Daily, weekly, monthly burn charts with transaction links
- Marketplace volume statistics: 24hr, 7d, 30d, all-time
- Active users and transaction count metrics
- Collection leaderboards by volume
- Competition rankings and per-user scoring
- Creator collection analytics and holder distribution
- API endpoints for third-party integrations
- Historical reports on burn totals, volume trends, collection stats
Security Architecture
Defense-in-depth with multiple protection layers: third-party audits, public code review, and operational security best practices. All fund-handling contracts undergo independent third-party security review with specific focus on fee accounting correctness, burn mechanism integrity, settlement safety, fund flow verification, admin risk assessment, and upgrade path security.
Following the professional audit and implementation of all recommended fixes, contracts enter a 10–14 day public open-source review window. Complete source code published to GitHub. Audit report findings and resolutions publicly disclosed. Bug bounty program may be announced with rewards for critical findings. Competition activation is delayed until this window completes.
- Independent third-party Solidity security audit — all five contracts
- Audit scope: fees, burns, settlement, fund flows, admin risks, upgrades
- 10–14 day public open-source review window post-audit
- All findings publicly disclosed regardless of severity
- Reentrancy guards on all fund-handling functions
- Integer overflow protection throughout
- 3-of-5 or 4-of-7 Gnosis Safe multisig treasury
- 24–48hr timelock on all critical administrative functions
- Gradual rollout with initial transaction limits
Infrastructure & Wallets
React-based single-page application built with TypeScript, Tailwind CSS, and Vite. Web3 libraries (ethers.js or viem) for blockchain interaction. Direct contract interaction — no backend intermediaries for transactions. IPFS hosting for maximum censorship resistance and uptime.
- MetaMask — primary ApeChain wallet, direct connection
- WalletConnect v2 — mobile and hardware wallet support
- Coinbase Wallet — broadest user base access
- Network switching for ApeChain mainnet and testnet
- The Graph or SubQuery event indexer — open-source subgraph
- Multiple RPC endpoints with automatic failover
- Transaction status tracking with retry and error handling
- IPFS-hosted frontend for decentralized access
- Sentry error monitoring and analytics tracking
- Mobile-responsive, tested across Chrome, Firefox, Safari, Brave