D17 documentation
Understand the launch mechanism, participate safely, deploy a launch, inspect every contract, or integrate the optional read API.
D17 is an open-source, non-custodial launch experiment. It uses participant-owned lockers, five timed rounds, published refund windows, permissionless finalization, and permanently locked launch liquidity. The website reads public state and asks your wallet to sign; it never holds a key or a participant's funds.
What it does
A creator publishes one immutable launch configuration. Participants commit WETH through their own locker contracts, can leave during the published refund windows, and claim tokens if the launch succeeds. The official pool opens after settlement and its protocol LP tokens remain in a vault with no withdrawal path.
The mechanism is designed to make the important facts inspectable before anyone signs:
- the supply split must add up exactly;
- five round allocations and timings are fixed at deployment;
- rounds 1–2 refund without a penalty, rounds 3–4 use the published global refund percentage, and round 5 has no ordinary refund window;
- failed launches expose a permanent full-refund path;
- no unsettled participant can block finalization, pool creation, or trading;
- settlement does not expire; and
- the creator cannot later mint more tokens, change the launch terms, or withdraw protocol LP tokens.
Start with your role
The shortest useful guide
- Choose a network. Sepolia is for test assets. Ethereum mainnet uses real ETH and WETH.
- Choose a read mode. Run the web app directly against your own RPC, or run the optional indexed read API for faster snapshots and realtime updates.
- Read the launch rules. Check token identity, supply split, treasury, round schedule, refund policy, and the canonical rules hash.
- Sign only in your wallet. The web app and read API never need a private key. Contract transactions go wallet → chain.
- Keep the contract addresses. If a site disappears, your locker and launch remain on-chain and can be called from another interface.
Experimental software
D17 is a hobby/open-source experiment, not investment advice or a promise that a launch is valuable. The contracts have extensive automated and test-network evidence, but this documentation does not claim a formal professional audit. Verify addresses, transaction targets, rules, and source before risking real funds.
Where to go next
- Five-minute start — run the app locally and understand the two read modes.
- Participant and trader guide — commit, refund, settle, withdraw, and trade.
- Deployer guide — configure and create a launch in one transaction.
- Contract architecture — responsibilities, invariants, deployments, and every ABI entry.
- Read API — REST, WebSocket, SSE, self-hosting, and operational limits.
- Interactive API reference — the complete Scalar/OpenAPI surface.