For developers

Most visitors only need the user guides above — Discover, trading, Classic V3, Tax V4, fees, community, and safety. Those pages explain what people click and experience. They intentionally skip low-level contract internals.

If you are integrating programmatically — quoting routes, reading factories, or wiring wallet UX — open the developer documentation for network details, deployed addresses, and launch flows. That is the source of truth for builders.

A common mix-up: reading these friendly user docs and expecting ABI tables. User docs will not list every address here on purpose. Another mix-up: hardcoding addresses from Discord threads or random posts. Always verify the live deployment you intend to call before sending mainnet funds.

Where to go: /docs/developers from the docs nav, this page’s aside link, or by pasting the route. When your product quotes Peeps routes for end users, also read Fees, Classic launch (V3), and Tax launch (V4) so fee copy stays accurate — Classic V3 uses a 1% pool fee (70% creator / 30% protocol of LP fees); aggregator swaps may add 0.25%; gas is ETH and separate.

Where to go

• Developer docs live at /docs/developers
• Always verify addresses against the live deployment you intend to use
• Test on the correct chain before sending mainnet funds
• Read user-facing Fees and launch guides if you are building wallet UX that quotes Peeps routes

What belongs in developer docs

Expect network and chain IDs, factory / router style addresses, launch and swap flow notes, and integration caveats. Do not expect these user pages to replace that material — and do not ship a UI that hides fee or risk context from end users.

1. 1

   Open developer docs

   Navigate to /docs/developers from this page’s aside link, the docs nav, or by entering the route directly.

2. 2

   Confirm network and addresses

   Match chain IDs and contract addresses to the environment you are calling. Verify addresses from /docs/developers or deployments/4663.json before mainnet funds move.

3. 3

   Integrate carefully

   Build against documented launch and swap flows. Surface clear fee and risk copy in any UI you ship on top of Peeps — users deserve the same clarity these guides aim for.