Developers
The two pages on writing extensions are still being written. The interfaces they describe exist and are in use; their reference documentation is not published yet. For anything urgent, the contact is [email protected].
Two kinds of building happen on Frontier, and neither requires permission.
Reading the platform
The data API is open: no account, no key, no rate agreement to negotiate. It serves the same data the app itself uses, including coins, trades, holders and fee configuration. The live feed the app connects to pushes those events as they happen; it is not open to third-party clients yet.
Bots are treated as users here rather than as a problem. A bot pays the same fees as anyone else, which makes its volume part of the same fee streams that pay creators and communities.
See API and live feed.
Writing extensions
The extension system is permissionless at the contract level. A developer implements a fee calculator or an observer, deploys it, and any creator can point a coin at it. The chain accepts anything that stays inside the safety constraints; the Frontier interface lists coins whose blocks have been reviewed.
Integrating with coins
Coins are ERC-20s and their markets are standard Uniswap V4 pools, reachable with the canonical routers and quoters. Three properties matter for any integration:
- Curve parameters are per coin. The factory's values are the protocol default, not a coin's own shape.
- A coin's fee is per pool. It may be flat, volatility-following, or temporarily raised by a declared window. Quote rather than assume.
- The pool is a dynamic-fee pool as far as Uniswap is concerned; the rate applied to a swap is whatever the hook returns for it.