Load the bundle
Use the versioned JSON or individual ABI files below.
Peak
Index every Peak launch directly from Avalanche using public contracts, events and ABIs. No API key, backend credential or wallet signature is required.
These are public Avalanche addresses. Mutable protocol roles should be read from the factory at runtime.
The factory’s TokenLaunched event is the canonical source of truth for tokens, pools, creators and reward vaults.
Use the versioned JSON or individual ABI files below.
No historical scan before the factory deployment is needed.
Store token, creator, quote token, pool and reward vault.
Resolve roles, enabled quotes and rewards directly on-chain.
import { Contract, JsonRpcProvider } from "ethers";
import peak from "./peak-v1.json" with { type: "json" };
const provider = new JsonRpcProvider(peak.network.publicRpc, peak.network.chainId);
const factory = new Contract(
peak.contracts.factory.address,
peak.abis.factory,
provider
);
const launches = await factory.queryFilter(
factory.filters.TokenLaunched(),
peak.indexer.startBlock
);
for (const { args, transactionHash, blockNumber } of launches) {
console.log({
token: args.token,
creator: args.creator,
quoteToken: args.quoteToken,
pool: args.pool,
rewardVault: args.rewardVault,
transactionHash,
blockNumber
});
}
Values below were verified from quoteConfigs. Integrators should still read the factory before accepting a new launch.
| Asset | Token | Oracle | Status |
|---|---|---|---|
| Loading quote configuration… | |||
Only data already readable from Avalanche is included.
No admin endpoint, deployer permission or backend session is exposed.
No API key, private key, Worker secret or signing material is shipped.
Mutable roles and quote status remain verifiable through factory view methods.
Replace each placeholder with URL-encoded values taken from TokenLaunched and ERC-20 metadata.
/market/?token={token}&pool={pool}&symbol={symbol}&name={name}"e={quote}Peakfun is built as composable, permissionless on-chain infrastructure on the Avalanche C-Chain (Chain ID 43114). The Peakfun Developer Portal provides trading bot authors, analytics platforms, DeFi aggregators, and wallet teams with every verified smart contract address, JSON ABI, function signature, and event schema required to integrate directly with Peakfun.
Because all token launches, swaps, fee claims, and token locks occur through public smart contracts, external developers never need private API keys or gatekept partner approvals to read market state or route transactions through Peakfun.
Developers can download the complete JSON ABIs for PeakLaunchFactory (token creation and pool initialization), PeakOrderManager (swap routing and quote estimation), and PeakRewardVault (creator and holder fee accounting) directly from the portal.
The developer documentation includes ready-to-run ethers.js and viem code snippets demonstrating how to subscribe to new token launch events, query pool reserves, and construct swap transactions on Avalanche mainnet.
No. Peakfun is 100% on-chain on the Avalanche C-Chain. Any developer can interact with Peakfun contracts and index events using standard Avalanche RPC endpoints and the public JSON ABIs.
You can download PeakLaunchFactory.json, PeakOrderManager.json, PeakRewardVault.json, and the machine-readable peak-v1.json manifest directly from the Peakfun Developers page.
All production Peakfun smart contracts are deployed on Avalanche C-Chain Mainnet with Chain ID 43114.