Skip to content

Latest commit

 

History

505 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

RetroPick

The market creation layer for Monad.

RetroPick is an onchain launchpad with bonding-curve issuance, graduation and venue integrations. This monorepo contains distinct lifecycle layers: maintained application code, active V2 contracts, a frozen Monad Testnet V2 demonstration, research prototypes and reproducible release evidence. The historical Kuru deployment demonstrates a specific release; it must not be treated as proof of all current V2/V3 designs or unrestricted mainnet readiness.

Current code and architecture

Area Maintained entry point Status
Product frontend apps/retro-ui Canonical Vite + React app
Contract SDK and ABI packages/launchpad-sdk · apps/abi Typed wallet boundary; ABI catalog is derived
Read models / services Indexer · Media · Referrals Offchain support; no custodial economic writes
Active Launchpad V2 Solidity contracts/src/v2 Financial changes require isolated qualification
Frozen V2 testnet source contracts/legacy-v2 Immutable deployment provenance
Historical frontend apps/web Read-only / zero-write
Visual design donor apps/example-ui-ux Reference, not deployed product authority
PRISM / V3 research PRISM · research Separate qualification, not automatically production

Start with documentation navigation, contributor guide, contracts guide, and the rehabilitation audit. For safe changes, see cleanup decisions and test status.

Maintainer entry points

For local setup, code ownership, verification and safe changes, read CONTRIBUTING.md, apps ownership, and the 2026-11-09 repository audit. The earlier hygiene audit remains historical context. The canonical frontend is apps/retro-ui, not the read-only historical apps/web. Root pnpm dev, pnpm build, and pnpm check operate on the maintained workspace paths; historical Next.js commands are explicitly named *:legacy-web.

Run the web app

Node 24+ is recommended for full-workspace development (root minimum >=22.13); use pnpm 11.25.0:

pnpm install --frozen-lockfile
cp apps/retro-ui/.env.example apps/retro-ui/.env.local
pnpm dev  # canonical apps/retro-ui
pnpm check:app  # UI typecheck/tests/build
pnpm check:services  # SDK + indexer + media + referral (Node 24+)

The canonical frontend is apps/retro-ui. Configure its documented live data mode and public read infrastructure; never put credentials or signing keys in a browser environment. Wallets sign normal economic writes directly to chain. apps/web is legacy and excluded from this submission's demo and implementation work.

pnpm --filter @retropick/retro-ui typecheck
pnpm --filter @retropick/retro-ui build

Contracts require Foundry, recursive submodules, the separately built v4/Permit2 dependencies and a funded RPC endpoint for mandatory fork tests. See contract setup and release evidence. Never commit signing keys.

Historical Monad Testnet demo and provenance

The following descriptions, deployment addresses and transaction receipts document the frozen V2 Monad Testnet candidate. They are historical proof, not current liquidity, security-audit or production claims.

Smart contracts for hackathon judges

Review the frozen Legacy V2 smart contracts for the deployed Monad Testnet submission, including its Kuru integration. The archive guide and source manifest identify the recorded deployed revision: f0363249f4b74e58dde37d1241742ca5a92bcfe3.

Factory · Bonding curve · Coordinator · Kuru executor · Permanent liquidity lock

Ongoing V2 development in contracts/src/v2/ is separate from this frozen judging snapshot. The live deployment addresses and historical proof transactions below remain unchanged.

Recorded Monad Testnet capabilities

The canonical deployed candidate demonstrates:

  • ✅ Token issuance and bonding-curve buy/sell
  • ✅ Safe graduation and real Kuru market creation
  • ✅ Permanent custody for graduation LP shares and excess tokens
  • ✅ Permissionless completion/retry
  • ✅ Live testnet limit order, fill and cancel

Open the canonical live frontend. Historical team functional-test receipts demonstrate launch, curve trading, Kuru graduation and two-wallet order/fill/cancel; they are not organic volume or present orderbook depth. Fresh desktop/mobile checks and the current video status are recorded in the submission readiness report. The founder-recorded pitch remains founder-owned. Canonical Circle-USDC live smoke: BLOCKED_FUNDING.

Judge overview · Evidence map · Full deployment manifest · Metropolis requirements

Why Monad?

RetroPick produces two active phases: rapid bonding-curve transactions and post-graduation orderbook trading. Low-cost execution, fast settlement and responsive market state matter when many primary markets and secondary orderbooks operate simultaneously. This connects asset primitives, market infrastructure and settlement to Metropolis's Onchain Finance & Trading track.

Kuru's role in the recorded demo

RetroPick specializes in issuance, creator distribution, primary discovery and graduation safety. Kuru supplies the secondary orderbook, limit orders and market-making workflows. Our demo created an actual Kuru market, seeded its vault and executed an order, fill and cancel. Depth, spreads and execution quality remain market-dependent; neither integration nor permanent custody guarantees trading outcomes.

Deployed proof

Component Monad Testnet address
Factory 0xa7f18b9eceb0A9852b08408854A45D00fc682454
Coordinator 0xaD62309242EA65BB07C833669EC6a4ED23AF738F
Demo token 0x43e7e9b1b7d9A143573307b13D14B51580c18f15
Bonding curve 0x454A3A449d4e65CA5203d331905d167BA218E276
Kuru market 0x1F5dE72616a7fe645Cf45aC66dfce8Ac7452C57F
Kuru vault 0xc88DED06eB0081430Ff02d124C22b532e122CbE7
Permanent LP/excess lock 0x72ced84b20Bb8467c5547e3EbF85E62321B6a425

Six concise proof transactions: launch, bonding buy, graduation, order, fill, cancel. These are functional testnet transactions, not organic adoption.

Verified contract sources — seven exact runtime matches.

Engineering depth

Factory → single-ledger Coordinator → venue executor keeps lifecycle authority separate from venue work. Architectural extraction reduced Factory runtime from approximately 24,565 to 23,423 bytes. Exact integer terminal-quote constraints preserve completion liveness across valid trade histories; graduation LP/excess assets enter a permanent bound lock. Native/Circle Uniswap v4 compatibility remains in the release campaign.

Historical predeployment campaign: 145 passed / 0 failed / 0 skipped, fresh qualification fork 69,507,986. Release artifacts. Deployed bytecode source: f0363249f4b74e58dde37d1241742ca5a92bcfe3; main integration baseline: 84861f50494a79772cf6f97a5e710bcc24973d5e. Current repository release verification is recorded separately; source SHA is not a live readiness claim.

Hackathon scope and attribution

Pre-existing foundations include V1/shared Solidity dependencies and the visual frontend prototype. V2 delivery introduced Coordinator extraction, policy snapshots, completion liveness, Kuru graduation/protected custody, V4 migration and deployment/smoke tooling. This submission release connects the live frontend and judge evidence. Build-window claims must be assessed from public commit history; this repository is not entirely new hackathon code.

AI-assisted tools were used for engineering, testing and documentation; maintainers remain responsible for review and claims. Third-party notices: contracts, dependency licenses and frontend package/vendor notices. Original project source uses the MIT license; third-party licenses remain applicable.

Submission copy · Demo · Pitch · Q&A · Partnership plan · Growth

Releases

Packages

Used by

Contributors

Languages