Overview
LayPipe is a Robinhood Chain coin launcher built around a Uniswap v4 hook. Each launch creates a fixed-supply token, opens a permanent one-sided PIPEDOG pool, and configures its fee route in one flow.
The product UI uses explicitly labeled fixtures. No demo coin shown on the Board represents an actual LayPipe deployment.
Launches
The intended factory creates a token with a fixed one-billion supply and deposits the whole supply into its PIPEDOG-quoted v4 pool. The hook prevents liquidity removal; there is no separate graduation or migration step.
- Choose the token identity and optional PIPEDOG first buy.
- Select creator-fee or self-burn mode.
- Approve only the exact PIPEDOG launch fee and first-buy amount.
- Create the token and initialize its PIPEDOG pair.
- Lock the liquidity path and emit indexable launch events.
PIPEDOG has no permit support. A live wallet must grant the exact ERC-20 allowance required for that launch or buy, never an unlimited approval. Native ETH pays network gas only.
The inherited enrollment-based dividend mode is intentionally blocked by the current factory implementation. Creator-fee and self-burn launches remain the only supported modes until a complete-holder reward design receives a separate review.
The permanent v4 launch curve is implemented locally, but its starting price, depth, and execution bounds still need fork-backed liquidity testing before any production release.
Trading fees
A fixed 1% fee is collected in PIPEDOG. The creator lane receives 0.7%; the LayPipe protocol router receives 0.3%.
The launch owner can claim accrued PIPEDOG.
Accrued PIPEDOG buys the launched coin from its own pool and permanently burns the received tokens.
Permissionless keepers
Hook sweeps and protocol-router actions are public. The router’s two permissionless routing lanes can pay a configured PIPEDOG keeper bounty deducted from the lane being processed. Sweeping platform fees out of an inactive launch pool is unbountied, so production operations must monitor and trigger that step when creators stop claiming.
Self-burns use capped, visible PIPEDOG market orders without an oracle or minimum output. The caps limit order size, but do not eliminate sandwiching or price movement. Review those limits against live liquidity before enabling launches. Protocol PIPEDOG distributions are direct transfers, not market orders.
The gross protocol lane is already PIPEDOG. It assigns 25% directly to 0x000000000000000000000000000000000000dEaD, 25% to treasury, and 50% to operations. Eligible keeper bounties are deducted from the two permissionless routing lanes. PIPEDOG has no native burn function, so the dead-address transfer removes tokens from usable circulation without reducing ERC-20 totalSupply.
Readiness
“Live” requires verified contract addresses, an end-to-end launch on Robinhood Chain, indexed events, and a completed security review.
The factory can be upgraded for future launches, the hook owner can change the platform-fee destination, and the router owner can pause or migrate platform PIPEDOG. Production ownership should move to a reviewed Safe or timelock before launch.
Contract registry
Only the protocol asset is configured today. LayPipe deployment fields remain deliberately blank rather than pointing at the original LetsCash system.
- PIPEDOG
- 0x5Cb6F181081301b44905F3ae15419112ecaBd8A6
- LayPipe factory
- Pending deployment
- LayPipe v4 hook
- Pending deployment
- PIPEDOG fee router
- Pending deployment