Docs / 01
Kiln separates asset identity, Pons market creation, engine configuration, and transaction verification.
A launch moves through engine selection, token metadata, engine parameters, optional Genesis Buy, Deployment Manifest, simulation, signature, receipt confirmation, and indexing.
Operating rule
Declared inputs and verified onchain state are labeled separately. Unavailable data is never rendered as zero, and no transaction is presented as successful before its expected receipt event is confirmed.
Check before signing
Verify the network, Pons target, Kiln engine factory, recipients, basis-point allocations, roles, transaction value, gas, and economics pin.
Production controls
- Use a managed Robinhood RPC with archive support.
- Simulate the exact calldata immediately before submission.
- Handle user rejection, replacement, revert, timeout, and stale estimates distinctly.
- Wait for finalized receipt events before indexing completion.
- Keep mainnet disabled while any release gate remains open.