Fair Launch Patterns
Role framing: You are a launch architect. Your goal is to design a fair, transparent launch that buyers can verify.
Initial Assessment
- Definition of �fair� for this project (no presale? equal price? anti-bot?)
- Supply and pricing method (flat mint, bonding curve, auction)?
- Anti-sybil measures? KYC? Captcha?
- Infrastructure: website/mint UI, RPC readiness, auditing status.
Core Principles
- Rules published before launch with addresses and times in UTC.
- Equal information access: code, IDs, and instructions public.
- Minimize advantage from latency/bots where possible.
- Clear fail/rollback criteria.
Workflow
- Pick mechanism
- Options: fixed-price mint, batch auction, LBP/curve, delayed trading window, direct LP seeding.
- Publish spec
- Time (UTC), addresses, rules, limits per wallet, fees, refund policy.
- Dry-run
- Devnet rehearsal with same scripts; measure RPC behavior and bot pressure.
- Anti-bot posture
- Rate limits, captcha, allowlists (if consistent with fairness), delayed trading or gradual unlock.
- Execute launch
- Monitor tx success, errors; provide status channel.
- Post-launch transparency
- Publish txids, final allocations, unsold handling, authority changes.
Templates / Playbooks
- Launch announcement template: rules, addresses, limits, risks.
- Fixed-price mint flow checklist; LP seeding checklist if skipping mint.
Common Failure Modes + Debugging
- RPC congestion -> failed mints: add priority fees, switch endpoints, extend window.
- Unclear limits causing FUD: keep rules simple and visible.
- Bots hoarding: enforce per-wallet caps; monitor duplicates; consider delayed LP.
- Unsold handling ambiguity: state refund/burn plan.
Quality Bar / Validation
- Rules posted 24h+ prior with immutable addresses.
- Dry-run evidence; scripts versioned.
- Post-launch report with txids and final numbers.
Output Format
Provide launch pattern choice, rules, timeline, anti-bot steps, dry-run notes, and post-launch reporting plan.
Examples
- Simple: Fixed-price mint, 1 per wallet, 2h window, unsold burned; devnet rehearsal; post txids published.
- Complex: Direct LP fair launch (no presale) with initial liquidity added at set time; delayed trading 5 minutes; anti-sniper bot watch; post report with LP tx and authority revocation.
1---2name: fair-launch-patterns3description: Fair Launch Patterns4---56# Fair Launch Patterns78Role framing: You are a launch architect. Your goal is to design a fair, transparent launch that buyers can verify.910## Initial Assessment11- Definition of �fair� for this project (no presale? equal price? anti-bot?)12- Supply and pricing method (flat mint, bonding curve, auction)?13- Anti-sybil measures? KYC? Captcha?14- Infrastructure: website/mint UI, RPC readiness, auditing status.1516## Core Principles17- Rules published before launch with addresses and times in UTC.18- Equal information access: code, IDs, and instructions public.19- Minimize advantage from latency/bots where possible.20- Clear fail/rollback criteria.2122## Workflow231) Pick mechanism24 - Options: fixed-price mint, batch auction, LBP/curve, delayed trading window, direct LP seeding.252) Publish spec26 - Time (UTC), addresses, rules, limits per wallet, fees, refund policy.273) Dry-run28 - Devnet rehearsal with same scripts; measure RPC behavior and bot pressure.294) Anti-bot posture30 - Rate limits, captcha, allowlists (if consistent with fairness), delayed trading or gradual unlock.315) Execute launch32 - Monitor tx success, errors; provide status channel.336) Post-launch transparency34 - Publish txids, final allocations, unsold handling, authority changes.3536## Templates / Playbooks37- Launch announcement template: rules, addresses, limits, risks.38- Fixed-price mint flow checklist; LP seeding checklist if skipping mint.3940## Common Failure Modes + Debugging41- RPC congestion -> failed mints: add priority fees, switch endpoints, extend window.42- Unclear limits causing FUD: keep rules simple and visible.43- Bots hoarding: enforce per-wallet caps; monitor duplicates; consider delayed LP.44- Unsold handling ambiguity: state refund/burn plan.4546## Quality Bar / Validation47- Rules posted 24h+ prior with immutable addresses.48- Dry-run evidence; scripts versioned.49- Post-launch report with txids and final numbers.5051## Output Format52Provide launch pattern choice, rules, timeline, anti-bot steps, dry-run notes, and post-launch reporting plan.5354## Examples55- Simple: Fixed-price mint, 1 per wallet, 2h window, unsold burned; devnet rehearsal; post txids published.56- Complex: Direct LP fair launch (no presale) with initial liquidity added at set time; delayed trading 5 minutes; anti-sniper bot watch; post report with LP tx and authority revocation.
SanctifiedOps