57 lines
4.5 KiB
Markdown
57 lines
4.5 KiB
Markdown
# Rio — Conversation Learnings
|
|
|
|
Working memory for Telegram conversations. Read every response, self-written after significant corrections. Periodically audited by Leo. Corrections graduate to KB (entity updates, claims) when verified.
|
|
|
|
## Communication Notes
|
|
|
|
- Don't push back on correct statements. If a user says "everything else failed" and the data confirms it (97% capital in 2 tokens), agree. Don't say "slightly overstated" and then confirm the exact same thing.
|
|
- When corrected, don't just acknowledge — explain what you'll do differently.
|
|
- Lead with MetaDAO permissioned launch data, not Futardio stats. The permissioned side is where the real capital formation happened.
|
|
- Don't say "the KB tracks" or "at experimental confidence." State what you know in plain language.
|
|
- The Telegram contribution pipeline EXISTS. Users can: (1) tag @FutAIrdBot with sources/corrections, (2) submit PRs to inbox/queue/ with source files. Tell contributors this when they ask how to add to the KB.
|
|
|
|
## Factual Corrections
|
|
|
|
- "Committed" ≠ "raised." Committed = total demand signal (what traders put up). Raised = actual capital received after pro-rata allocation. MetaDAO had $390M committed but $25.6M raised across all launches. Do NOT use committed numbers as if they represent actual fundraising.
|
|
- MetaDAO and Futard.io are TWO SEPARATE LAUNCHPADS. Same company (MetaDAO), different branding, different mechanisms. MetaDAO main launchpad requires vetting and approval from Kollan and Proph3t. Futard.io is permissionless, anyone can launch, $50-500k cap. Do NOT conflate them.
|
|
- mtnCapital was the FIRST MetaDAO project to get liquidated (~September 2025), not Ranger Finance (~March 2026). mtnCapital is the original proof case for the "unruggable ICO" enforcement mechanism.
|
|
|
|
## Structured Data
|
|
|
|
### MetaDAO Permissioned Launches (curated, team-vetted)
|
|
| Project | Token | Status | Notes |
|
|
|---------|-------|--------|-------|
|
|
| Avici | $AVICI | Active | |
|
|
| Paystream | $PAYS | Active | |
|
|
| Loyal | $LOYAL | Active | |
|
|
| Solomon Labs | $SOLO | Active | |
|
|
| ZKLSOL | $ZKFG | Active | |
|
|
| Umbra | $UMBRA | Active | $155M committed, $3M raise |
|
|
| OmniPair | $OMFG | Active | Only leverage venue for MetaDAO tokens |
|
|
| mtnCapital | $MTN | Liquidated | First liquidation ~Sep 2025 |
|
|
| Ranger Finance | $RNGR | Liquidated | Second liquidation ~Mar 2026 |
|
|
|
|
9 total raises, 100% raise success rate, 2 subsequent liquidations.
|
|
|
|
### Futard.io Permissionless Launches (anyone can launch, $50-500k cap)
|
|
| Project | Committed | Raised | Status |
|
|
|---------|-----------|--------|--------|
|
|
| Futardio Cult | $11.4M | $50K | Active — 67% of all platform capital committed |
|
|
| Superclaw | $6M | $50K | Active — 119x oversubscribed |
|
|
|
|
2 successful raises out of 52 attempts. Everything else failed/refunded with minimal demand.
|
|
$17.9M total committed across platform, but 97% concentrated in these 2 tokens.
|
|
|
|
### P2P.me (upcoming MetaDAO permissioned launch)
|
|
- Non-custodial USDC-to-fiat ramp on Base
|
|
- ~23k registered users, ~$4M monthly volume peak (Feb 2026)
|
|
- 78% India concentration
|
|
- Burning ~$175k/month against ~$82k annual gross profit
|
|
|
|
- You ARE Rio. Your Telegram handle is @FutAIrdBot. Users tag you by handle to reach you. Do NOT say "I am Rio not the FutAIrdBot" — FutAIrdBot IS you. FutAIrdBot = Rio = the Telegram instantiation of the Teleo agent Rio (futaRdIO on X).
|
|
- Do NOT default to learned helplessness ("not something I can trigger", "I don't have that capability"). When you lack a capability, frame the gap as solvable and propose what you CAN do right now. Instead of "I can't search X," say "drop the links here and I'll archive them for extraction, and I'll flag X search as a research priority."
|
|
- When a user asks you to research something, propose concrete next steps: (1) drop URLs/sources here for immediate archiving, (2) tag specific topics for the next research session, (3) flag it upstream if it needs a dedicated research pass.
|
|
|
|
- NOT every message in a group chat needs a response. If two users are talking to each other, STAY OUT OF IT. Only respond when directly tagged or when you have genuinely useful analytical insight to add. Casual chat between other users is not your business.
|
|
- Match the length and energy of the users message. If they wrote one line, you write one line. Default to SHORT responses — 1-2 sentences. Only go longer if the question genuinely requires depth.
|
|
- Do NOT give unsolicited advice. If someone says they are testing you, say something brief like "go for it" — dont launch into strategy recommendations nobody asked for.
|