Orchard Authority Timeline

Roadmap

Born ripe. Stayed mad. Coming to Robinhood Chain.

Frunji is an illustrated identity collection rooted in The Orchard Incident — where every fruit woke up furious and never calmed down. Each Frunji is a unique angry produce generated from layered absurd traits. Managed by The Orchard Authority. Denied by The Orchard Authority.

PHASE 0
IN PROGRESS

Incident Documentation

Character lock, trait system, and contract preparation.

  • Concept locked: angry fruit base with tactical gear and slingshot accessories.
  • Full art system: 14+ trait layers, unique pieces generated and verified.
  • Smart contract preparation for Robinhood Chain deployment.
  • Orchard Clearance checkpoint live.
PHASE 1
LAUNCH

The Great Ripening

Community build-up, contract deploy, and the drop phase.

  • Warm up X account: release Orchard Incident Reports and trait reveals.
  • Deploy contract to Robinhood Chain at launch.
  • Claim portal: connect wallet, live claim counter tracking progress.
  • PFP verification and holder roles live.
PHASE 2
POST-DROP

Fruit Management Division

Expand the Frunji ecosystem and absurd content machine.

  • Holder-only channels and events.
  • Weekly Anger Forecast reports on X.
  • Community meme contests and remix culture.
  • Partner integrations with illustrated-native projects.
PHASE 3
POST-DROP

Maximum Inconvenience Protocol

The final evolution of the Frunji ecosystem.

  • Trait Remix Engine: combine traits from two Frunjis into a new grail.
  • Seasonal anger drops for existing holders.
  • On-chain orchard map: visual representation of holder distribution.
  • Deflationary mechanics through optional burn events.
01

Anger is organic.

Born ripe. Stayed mad. The blush never fades because there was never calm.

02

Positivity is suspicious.

Happiness is the enemy. The Orchard Authority monitors all optimism.

03

No proof needed.

Nobody has proof Frunjis caused your printer jam. Nobody needs proof.

04

The Orchard denies all allegations.

Official statements may contradict incident reports. This is normal.