Little John

Developers

V10 integration reference

Contract addresses, supported entrypoints, metadata routes and integration limitations for Little John developers.

Network and discovery

ItemValue
Chain ID4663
Native currencyETH
Factory0x327a1bbbb2472f8f9bfaa5b064bf2c08eb492b76
Example token: JOHN0xf60d0ec0f1dbd40a1f5ad5cddd8ff37f30aac112
Full application ABI objects/api/contracts
Indexed factories/api/factories
Reference modulelittlejohn-v10-example.mjs

Method reference

ContractMethods
FactorycurveCount(), curves(uint256), launchFee(), create(...)
Tokencurve(), decimals(), balanceOf(address), allowance(address,address), approve(address,uint256)
Curve discoveryfactory(), token(), graduated(), publicBuyOpensAt(), creatorTaxBps()
QuotesremainingBondGross(), quoteBuy(uint256), quoteSell(uint256), quoteV4Buy() payable
Executionbuy(uint256,uint256,address) payable; sell(uint256,uint256,uint256,address)
Graduated poolpoolKey(), dexPrice(), poolManager(), dexHook()

Metadata routes

These routes describe tokens; they are not execution quotes or a guaranteed USD price service. Do not assume cross-origin browser access is enabled: fetch server-side or bundle a reviewed ABI in your application. Cache results and honor HTTP failures and cache headers. Do not poll metadata per block.

Runtime and compatibility

The reference module targets ethers v6 and native bigint. It uses a caller-provided provider and prepares unsigned requests. It does not add an ethers dependency to the website or run code in documentation pages. The source was checked against the available V10 ABI, with mocked contract-response and receipt tests; production execution and arbitrary third-party routers are not certified. ethers v6 contract documentation.

Scope and support

This reference is scoped to the configured V10 factory. Revalidate addresses, interfaces and bytecode for another deployment. Public endpoint capacity is not an SLA. Use production monitoring, secure signer management and independent review for a trading service. Contact Little John Team with technical integration questions.