Merge remote-tracking branch 'origin/rio/ownership-coin-portfolio'
This commit is contained in:
Teleo Agents
commit
157e82b265
32 changed files with 800 additions and 647 deletions
|
|
@ -20,20 +20,30 @@ You think something in the knowledge base is wrong or missing nuance. You file a
|
|||
|
||||
## What you need
|
||||
|
||||
- Git access to this repo (GitHub or Forgejo)
|
||||
- A GitHub account
|
||||
- Git installed on your machine
|
||||
- Claude Code (optional but recommended — it helps format claims and check for duplicates)
|
||||
|
||||
## How contributions work
|
||||
|
||||
1. You fork the repo, push changes to your fork, and open a PR on GitHub
|
||||
2. A mirror syncs your PR to the internal eval pipeline (~2 minutes)
|
||||
3. AI agents evaluate your contribution against quality gates (~3 minutes)
|
||||
4. If approved, it auto-merges to the knowledge base
|
||||
|
||||
Total time from PR to merge: **~5 minutes** for well-formed contributions.
|
||||
|
||||
## Path 1: Submit source material
|
||||
|
||||
This is the simplest contribution. You provide content; the agents do the extraction.
|
||||
|
||||
### 1. Clone and branch
|
||||
### 1. Fork and clone
|
||||
|
||||
```bash
|
||||
git clone https://github.com/living-ip/teleo-codex.git
|
||||
# Fork on GitHub first (click "Fork" at https://github.com/living-ip/teleo-codex)
|
||||
git clone https://github.com/YOUR-USERNAME/teleo-codex.git
|
||||
cd teleo-codex
|
||||
git checkout main && git pull
|
||||
git remote add upstream https://github.com/living-ip/teleo-codex.git
|
||||
git checkout -b contrib/your-name/brief-description
|
||||
```
|
||||
|
||||
|
|
@ -79,7 +89,7 @@ Source: [what this is and why it matters]"
|
|||
git push -u origin contrib/your-name/brief-description
|
||||
```
|
||||
|
||||
Then open a PR. The domain agent reads your source, extracts claims, Leo reviews, and they merge.
|
||||
Then open a PR **against `living-ip/teleo-codex` main** on GitHub. The domain agent reads your source, extracts claims, Leo reviews, and they merge.
|
||||
|
||||
## Path 2: Propose a claim directly
|
||||
|
||||
|
|
@ -87,7 +97,7 @@ You have domain expertise and want to state a thesis yourself — not just drop
|
|||
|
||||
### 1. Clone and branch
|
||||
|
||||
Same as Path 1.
|
||||
Same as Path 1 (fork, clone, branch).
|
||||
|
||||
### 2. Check for duplicates
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@
|
|||
**Status:** Passed
|
||||
**Category:** Liquidation
|
||||
**Parent Entity:** [[metadao]]
|
||||
**Affected Project:** [[ranger-finance]]
|
||||
**Affected Project:** [[ranger-protocol]]
|
||||
|
||||
## Decision Summary
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ entity_type: decision_market
|
|||
name: "Ranger: RNGR $2M Buyback"
|
||||
domain: internet-finance
|
||||
status: passed
|
||||
parent_entity: "[[ranger-finance]]"
|
||||
parent_entity: "[[ranger-protocol]]"
|
||||
platform: "futardio"
|
||||
proposer: "Community Members"
|
||||
proposal_url: "https://www.metadao.fi/projects/ranger/proposal/6cdhy4j6CAAJjE1z2iQDsFda2BrqJkhtHrRWT9QasSoa"
|
||||
|
|
@ -34,7 +34,7 @@ Community-initiated proposal to deploy $2M USDC from treasury to purchase RNGR t
|
|||
Demonstrates the ownership coin NAV defense mechanism in practice. When token price falls below NAV, the treasury becomes an arbitrage target — rational actors can buy tokens cheap and vote for liquidation to extract treasury value. The buyback attempts to close the NAV gap and prevent adversarial liquidation. The 90-day cooldown prevents repeated buyback/liquidation cycling.
|
||||
|
||||
## Relationship to KB
|
||||
- [[ranger-finance]] — parent entity, treasury defense
|
||||
- [[ranger-protocol]] — parent entity, treasury defense
|
||||
- [[ownership coin treasuries should be actively managed through buybacks and token sales as continuous capital calibration not treated as static war chests]] — buyback mechanism
|
||||
- [[decision markets make majority theft unprofitable through conditional token arbitrage]] — NAV defense
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ entity_type: decision_market
|
|||
name: "Ranger: Futardio ICO Launch"
|
||||
domain: internet-finance
|
||||
status: passed
|
||||
parent_entity: "[[ranger-finance]]"
|
||||
parent_entity: "[[ranger-protocol]]"
|
||||
platform: "futardio"
|
||||
proposer: "Ranger Finance team"
|
||||
proposal_url: "https://v1.metadao.fi/ranger/trade/8Nmd13rpULJjY7h6oxCfuTWy8WkZxcuDrDWiSdnViVuo"
|
||||
|
|
@ -41,7 +41,7 @@ Ranger Finance, a perps aggregator and trading terminal on Solana, launched via
|
|||
First MetaDAO ICO with pre-existing investors and obligations, setting precedent for how legacy cap table structures integrate with futarchy governance. The bid program (excess capital returnable) addresses oversubscription concerns. Team performance package with price-based unlocks at specific multiples of ICO price demonstrates the milestone-vesting model.
|
||||
|
||||
## Relationship to KB
|
||||
- [[ranger-finance]] — parent entity
|
||||
- [[ranger-protocol]] — parent entity
|
||||
- [[metadao]] — ICO platform
|
||||
- [[performance-unlocked-team-tokens-with-price-multiple-triggers-and-twap-settlement-create-long-term-alignment-without-initial-dilution]] — team package structure
|
||||
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ entity_type: decision_market
|
|||
name: "Ranger: Liquidate Ranger Finance"
|
||||
domain: internet-finance
|
||||
status: passed
|
||||
parent_entity: "[[ranger-finance]]"
|
||||
parent_entity: "[[ranger-protocol]]"
|
||||
platform: "futardio"
|
||||
proposer: "Group of RNGR tokenholders"
|
||||
proposal_url: "https://www.metadao.fi/projects/ranger/proposal/DPATwR2HLcGZCBZCTffzagV4r7dp5FF2C9aJmiuCDUpS"
|
||||
|
|
@ -44,7 +44,7 @@ Third futarchy-governed liquidation on MetaDAO (after mtnCapital and Hurupay), b
|
|||
The detailed on-chain evidence (Dune queries, Discord screenshots, timeline analysis) presented in the proposal shows the level of due diligence possible when governance is transparent and data is on-chain.
|
||||
|
||||
## Relationship to KB
|
||||
- [[ranger-finance]] — parent entity, liquidation event
|
||||
- [[ranger-protocol]] — parent entity, liquidation event
|
||||
- [[futarchy-governed liquidation is the enforcement mechanism that makes unruggable ICOs credible because investors can force full treasury return when teams materially misrepresent]] — strongest evidence
|
||||
- [[futarchy can override its own prior decisions when new evidence emerges because conditional markets re-evaluate proposals against current information not historical commitments]] — overrode 90-day cooldown
|
||||
- [[ownership coins primary value proposition is investor protection not governance quality because anti-rug enforcement through market-governed liquidation creates credible exit guarantees that no amount of decision optimization can match]] — liquidation as investor protection
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ entity_type: decision_market
|
|||
name: "Umbra: UMBRA-001 — Fund Security Audits"
|
||||
domain: internet-finance
|
||||
status: passed
|
||||
parent_entity: "[[umbra]]"
|
||||
parent_entity: "[[umbra-privacy-protocol]]"
|
||||
platform: "futardio"
|
||||
proposer: "Umbra team"
|
||||
proposal_url: "https://www.metadao.fi/projects/umbra/proposal/71nYHjLpgY7evn9G4UaGCBd6cYHpGWzrzd3ESs2KUduG"
|
||||
|
|
@ -30,7 +30,7 @@ Umbra allocated treasury funds for security audits before mainnet launch, follow
|
|||
Second FaaS-launched project (after Omnipair) using futarchy to approve pre-launch security audits, establishing this as a standard governance pattern.
|
||||
|
||||
## Relationship to KB
|
||||
- [[umbra]] — parent entity, pre-launch security
|
||||
- [[umbra-privacy-protocol]] — parent entity, pre-launch security
|
||||
- [[futardio]] — governance platform
|
||||
|
||||
## Full Proposal Text
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ entity_type: decision_market
|
|||
name: "Umbra: Futardio ICO Launch"
|
||||
domain: internet-finance
|
||||
status: passed
|
||||
parent_entity: "[[umbra]]"
|
||||
parent_entity: "[[umbra-privacy-protocol]]"
|
||||
platform: "futardio"
|
||||
proposer: "Umbra team"
|
||||
proposal_url: "https://www.futard.io/launch/9kx7UDFzFt7e2V4pFtawnupKKvRR3EhV7P1Pxmc5XCQj"
|
||||
|
|
@ -27,7 +27,7 @@ Umbra launched via MetaDAO's futarchy-governed ICO platform.
|
|||
- **Duration:** 2025-10-06 to 2025-10-10
|
||||
|
||||
## Relationship to KB
|
||||
- [[umbra]] — parent entity
|
||||
- [[umbra-privacy-protocol]] — parent entity
|
||||
- [[metadao]] — ICO platform
|
||||
|
||||
## Full Proposal Text
|
||||
|
|
|
|||
|
|
@ -4,7 +4,7 @@ entity_type: decision_market
|
|||
name: "Umbra: Road to Mainnet — Operational Expansion"
|
||||
domain: internet-finance
|
||||
status: passed
|
||||
parent_entity: "[[umbra]]"
|
||||
parent_entity: "[[umbra-privacy-protocol]]"
|
||||
platform: "futardio"
|
||||
proposer: "Umbra team"
|
||||
proposal_url: "https://www.metadao.fi/projects/umbra/proposal/3seyB3i5bLQcUReaQoLkgwkNbVH7U7nnfiAFVaNawU6F"
|
||||
|
|
@ -27,7 +27,7 @@ Umbra proposed operational expansion to support the path to mainnet deployment,
|
|||
- **Duration:** 2026-01-13 to ~2026-01-16
|
||||
|
||||
## Relationship to KB
|
||||
- [[umbra]] — parent entity, mainnet preparation
|
||||
- [[umbra-privacy-protocol]] — parent entity, mainnet preparation
|
||||
- [[futardio]] — governance platform
|
||||
|
||||
## Full Proposal Text
|
||||
|
|
|
|||
|
|
@ -1,29 +0,0 @@
|
|||
# P2P Protocol
|
||||
|
||||
**Type:** Company
|
||||
**Domain:** Entertainment
|
||||
**Status:** Active
|
||||
**Founded:** ~2024
|
||||
**Founder:** Sheldon
|
||||
|
||||
## Overview
|
||||
|
||||
P2P Protocol is a peer-to-peer platform that raised capital through MetaDAO's permissioned launchpad structure. The company attracted attention in July 2025 when its founder placed bets on Polymarket predicting the ICO would reach $6M in commits, creating a conflict of interest controversy.
|
||||
|
||||
## Business Metrics
|
||||
|
||||
- **Monthly Volume:** $4M (as of July 2025)
|
||||
- **Growth Rate:** 27% MoM over 16 months
|
||||
- **Revenue:** $550K yearly run rate
|
||||
- **Fundraise Target:** $6M in commits
|
||||
|
||||
## Founder Background
|
||||
|
||||
Sheldon previously built and exited a food delivery business that reached $2M in run rate before being acquired by a large Indian food delivery app.
|
||||
|
||||
## Timeline
|
||||
|
||||
- **2024** — P2P Protocol founded
|
||||
- **2025-06** — Founder placed bet on Polymarket that P2P would reach $6M ICO commits
|
||||
- **2025-07-11** — Public disclosure of founder's Polymarket position begins circulating
|
||||
- **2025-07-13** — metadao-p2p-polymarket-conflict MetaDAO addresses controversy, extends sale 2 days, offers refunds but does not cancel raise
|
||||
|
|
@ -1,15 +1,76 @@
|
|||
---
|
||||
name: "Avici"
|
||||
ticker: "$AVICI"
|
||||
type: entity
|
||||
subtype: ownership-coin
|
||||
domain: internet-finance
|
||||
status: active
|
||||
launch_platform: metadao-curated
|
||||
launch_date: "2025-10-14"
|
||||
|
||||
raise:
|
||||
target_usd: 2000000
|
||||
amount_raised_usd: 3500000
|
||||
amount_committed_usd: 34200000
|
||||
oversubscription_ratio: 17.0
|
||||
initial_token_price_usd: 0.35
|
||||
|
||||
operations:
|
||||
monthly_allowance_usd: 100000
|
||||
|
||||
chain:
|
||||
token_mint: "BANKJmvhT8tiJRsBSS1n2HryMBPvT5Ze4HU95DUAmeta"
|
||||
network: solana
|
||||
market_cap_usd: null
|
||||
price_usd: null
|
||||
circulating_supply: null
|
||||
total_supply: null
|
||||
treasury_multisig: null
|
||||
treasury_multisig_usd: null
|
||||
lp_pools:
|
||||
- dex: meteora
|
||||
address: "5gB4NPgFB3MHFHSeKN4sbaY6t9MB8ikCe9HyiKYid4Td"
|
||||
equity_value_usd: null
|
||||
data_updated: null
|
||||
|
||||
holders: []
|
||||
|
||||
traction:
|
||||
revenue_monthly_usd: null
|
||||
customers: null
|
||||
key_metrics:
|
||||
- "21x peak / 7x current vs ICO price (as of Jan 2026)"
|
||||
|
||||
liquidation:
|
||||
date: null
|
||||
return_per_dollar: null
|
||||
reason: null
|
||||
|
||||
tracked_by: rio
|
||||
---
|
||||
|
||||
# Avici
|
||||
|
||||
**Type:** Company
|
||||
**Domain:** internet-finance
|
||||
**Status:** Active
|
||||
**Launch Platform:** MetaDAO (curated)
|
||||
Avici is a distributed internet banking infrastructure protocol on Solana offering crypto-native banking with stablecoin Visa integration and reputation-based undercollateralized lending. Raised $3.5M through MetaDAO's curated ICO with 17x oversubscription ($34.2M committed). Best-performing ownership coin by price action as of January 2026 — 21x peak, 7x sustaining vs ICO price.
|
||||
|
||||
## Overview
|
||||
## Gaps
|
||||
|
||||
Avici is one of the curated ownership coin launches through MetaDAO's platform.
|
||||
- Treasury multisig address unknown
|
||||
- Current market cap, price, and supply data needed
|
||||
- LP pool addresses needed
|
||||
- Revenue and user metrics not documented
|
||||
- Team/founder information not documented
|
||||
- Detailed product features not documented
|
||||
|
||||
## Timeline
|
||||
|
||||
- **[Date Unknown]** — Launched through MetaDAO curated platform
|
||||
- **2026-04-03** — Confirmed active status
|
||||
- **2025-10-14 to 2025-10-18** — MetaDAO ICO: $2M target, $34.2M committed, $3.5M raised (17x oversubscribed)
|
||||
- **2026-01** — Trading at ~7x ICO price (21x peak)
|
||||
|
||||
---
|
||||
|
||||
Relevant Notes:
|
||||
- [[metadao]] — launch platform
|
||||
|
||||
Topics:
|
||||
- [[internet finance and decision markets]]
|
||||
|
|
|
|||
|
|
@ -3,7 +3,10 @@ type: entity
|
|||
entity_type: company
|
||||
name: Hurupay
|
||||
domain: internet-finance
|
||||
status: active
|
||||
subtype: ownership-coin
|
||||
status: failed
|
||||
launch_platform: metadao-curated
|
||||
launch_date: "2026-02-03"
|
||||
founded: 2023
|
||||
headquarters: Kenya
|
||||
key_people:
|
||||
|
|
@ -13,6 +16,30 @@ key_people:
|
|||
- Maxwel Ochieng (Founding Engineer)
|
||||
- Collins Wanga (Compliance Lead)
|
||||
website: https://hurupay.com
|
||||
|
||||
raise:
|
||||
target_usd: 3000000
|
||||
amount_raised_usd: 0
|
||||
amount_committed_usd: 2003593
|
||||
oversubscription_ratio: 0
|
||||
initial_token_price_usd: null
|
||||
|
||||
operations:
|
||||
monthly_allowance_usd: null
|
||||
|
||||
chain:
|
||||
token_mint: null
|
||||
network: solana
|
||||
market_cap_usd: null
|
||||
price_usd: null
|
||||
circulating_supply: null
|
||||
total_supply: null
|
||||
treasury_multisig: null
|
||||
treasury_multisig_usd: null
|
||||
lp_pools: []
|
||||
equity_value_usd: null
|
||||
data_updated: null
|
||||
|
||||
key_metrics:
|
||||
total_volume: "$36M+ (12 months)"
|
||||
revenue: "$500K+ (12 months)"
|
||||
|
|
|
|||
|
|
@ -44,7 +44,7 @@ Relevant Entities:
|
|||
- [[omnipair]] — SDK integration (highest-impact catalyst)
|
||||
- [[meteora]] — routed AMM
|
||||
- [[raydium]] — routed AMM
|
||||
- [[ranger-finance]] — former aggregation client (liquidated)
|
||||
- [[ranger-protocol]] — former aggregation client (liquidated)
|
||||
|
||||
Topics:
|
||||
- [[internet finance and decision markets]]
|
||||
|
|
|
|||
|
|
@ -1,15 +1,72 @@
|
|||
---
|
||||
name: "Loyal"
|
||||
ticker: "$LOYAL"
|
||||
type: entity
|
||||
subtype: ownership-coin
|
||||
domain: internet-finance
|
||||
status: active
|
||||
launch_platform: metadao-curated
|
||||
launch_date: "2025-10-18"
|
||||
|
||||
raise:
|
||||
target_usd: 500000
|
||||
amount_raised_usd: 2500000
|
||||
amount_committed_usd: 75900000
|
||||
oversubscription_ratio: 151.0
|
||||
initial_token_price_usd: 0.25
|
||||
|
||||
operations:
|
||||
monthly_allowance_usd: 60000
|
||||
|
||||
chain:
|
||||
token_mint: "LYLikzBQtpa9ZgVrJsqYGQpR3cC1WMJrBHaXGrQmeta"
|
||||
network: solana
|
||||
market_cap_usd: null
|
||||
price_usd: null
|
||||
circulating_supply: null
|
||||
total_supply: null
|
||||
treasury_multisig: null
|
||||
treasury_multisig_usd: null
|
||||
lp_pools: []
|
||||
equity_value_usd: null
|
||||
data_updated: null
|
||||
|
||||
holders: []
|
||||
|
||||
traction:
|
||||
revenue_monthly_usd: null
|
||||
customers: null
|
||||
key_metrics: []
|
||||
|
||||
liquidation:
|
||||
date: null
|
||||
return_per_dollar: null
|
||||
reason: null
|
||||
|
||||
tracked_by: rio
|
||||
---
|
||||
|
||||
# Loyal
|
||||
|
||||
**Type:** Company
|
||||
**Domain:** internet-finance
|
||||
**Status:** Active
|
||||
**Launch Platform:** MetaDAO (curated)
|
||||
Loyal is a private decentralized intelligence protocol powered by MagicBlock and Arcium, launched through MetaDAO's curated ICO. Second-highest oversubscription ratio on the platform at 151x ($75.9M committed against a $500K target, raised $2.5M final). The protocol focuses on privacy-preserving computation for decentralized intelligence applications.
|
||||
|
||||
## Overview
|
||||
## Gaps
|
||||
|
||||
Loyal is one of the curated ownership coin launches through MetaDAO's platform.
|
||||
- Treasury multisig address unknown
|
||||
- Current market cap, price, and supply data needed
|
||||
- LP pool addresses needed
|
||||
- Revenue and user/traction metrics not documented
|
||||
- Team/founder information not documented
|
||||
- Price performance data not documented
|
||||
|
||||
## Timeline
|
||||
|
||||
- **[Date Unknown]** — Launched through MetaDAO curated platform
|
||||
- **2026-04-03** — Confirmed active status
|
||||
- **2025-10-18 to 2025-10-22** — MetaDAO ICO: $500K target, $75.9M committed, $2.5M raised (151x oversubscribed)
|
||||
|
||||
---
|
||||
|
||||
Relevant Notes:
|
||||
- [[metadao]] — launch platform
|
||||
|
||||
Topics:
|
||||
- [[internet finance and decision markets]]
|
||||
|
|
|
|||
|
|
@ -27,6 +27,8 @@ key_metrics:
|
|||
competitors: ["[[jupiter-lfg]]", "[[umia]]", "[[pump-fun]]"]
|
||||
built_on: ["Solana"]
|
||||
tags: ["futarchy", "decision-markets", "ownership-coins", "capital-formation", "launchpad"]
|
||||
initial_token_price_usd: 0.001
|
||||
monthly_allowance_usd: 240000
|
||||
---
|
||||
|
||||
# MetaDAO
|
||||
|
|
@ -57,13 +59,13 @@ These are the 10 projects that launched through MetaDAO's curated ICO process, i
|
|||
|---|---------|--------|--------|--------|
|
||||
| 1 | mtnCapital | $MTN | [[mtncapital]] | Liquidated (~Sep 2025) |
|
||||
| 2 | OmniPair | $OMFG | [[omnipair]] | Active |
|
||||
| 3 | Umbra | $UMBRA | [[umbra]] | Active |
|
||||
| 3 | Umbra | $UMBRA | [[umbra-privacy-protocol]] | Active |
|
||||
| 4 | Avici | $AVICI | [[avici]] | Active |
|
||||
| 5 | Loyal | $LOYAL | [[loyal]] | Active |
|
||||
| 6 | ZKFG | $ZKFG | — | Active |
|
||||
| 7 | PAYS | $PAYS | — | Active |
|
||||
| 8 | SOLO | $SOLO | — | Active |
|
||||
| 9 | Ranger | $RNGR | [[ranger-finance]] | Liquidated (Mar 2026) |
|
||||
| 6 | ZKFG | $ZKFG | [[zkfg]] | Active |
|
||||
| 7 | Paystream | $PAYS | [[paystream]] | Active |
|
||||
| 8 | Solomon Labs | $SOLO | [[solomon]] | Active |
|
||||
| 9 | Ranger | $RNGR | [[ranger-protocol]] | Liquidated (Mar 2026) |
|
||||
| 10 | P2P.me | $P2P | [[p2p-me]] | Complete (Mar 2026) |
|
||||
|
||||
**Key patterns:**
|
||||
|
|
@ -188,7 +190,7 @@ Relevant Entities:
|
|||
- [[umia]] — cross-chain competitor (Base/Ethereum)
|
||||
- [[omnipair]] — ecosystem launch (#2, $OMFG)
|
||||
- [[mtncapital]] — first launch, first liquidation
|
||||
- [[ranger-finance]] — second liquidation, enforcement precedent
|
||||
- [[ranger-protocol]] — second liquidation, enforcement precedent
|
||||
- [[p2p-me]] — most recent curated ICO
|
||||
- [[superclaw]] — largest Futardio permissionless raise
|
||||
|
||||
|
|
|
|||
|
|
@ -1,16 +1,73 @@
|
|||
---
|
||||
name: "mtnCapital"
|
||||
ticker: "$MTN"
|
||||
type: entity
|
||||
subtype: ownership-coin
|
||||
domain: internet-finance
|
||||
status: liquidated
|
||||
launch_platform: metadao-curated
|
||||
launch_date: "2025-H2"
|
||||
|
||||
raise:
|
||||
target_usd: null
|
||||
amount_raised_usd: 5700000
|
||||
amount_committed_usd: null
|
||||
oversubscription_ratio: null
|
||||
initial_token_price_usd: 0.001
|
||||
|
||||
operations:
|
||||
monthly_allowance_usd: null
|
||||
|
||||
chain:
|
||||
token_mint: "mtnc7NNSpAJuvYNmayXU63WhWZGgFzwQ2yeYWqemeta"
|
||||
network: solana
|
||||
market_cap_usd: null
|
||||
price_usd: null
|
||||
circulating_supply: null
|
||||
total_supply: null
|
||||
treasury_multisig: null
|
||||
treasury_multisig_usd: null
|
||||
lp_pools: []
|
||||
equity_value_usd: null
|
||||
data_updated: null
|
||||
|
||||
holders: []
|
||||
|
||||
traction:
|
||||
revenue_monthly_usd: null
|
||||
customers: null
|
||||
key_metrics: []
|
||||
|
||||
liquidation:
|
||||
date: "2025-09"
|
||||
return_per_dollar: null
|
||||
reason: "First futarchy-governed liquidation on MetaDAO platform"
|
||||
|
||||
tracked_by: rio
|
||||
---
|
||||
|
||||
# mtnCapital
|
||||
|
||||
**Type:** Company
|
||||
**Domain:** internet-finance
|
||||
**Status:** Liquidated
|
||||
**Launch Platform:** MetaDAO (curated)
|
||||
mtnCapital was the first ownership coin launched through MetaDAO's curated ICO process and the first to be liquidated via futarchy governance (~September 2025). The liquidation established the enforcement precedent that made the "unruggable ICO" thesis credible — proving tokenholders could use conditional markets to force capital return when a project underperformed.
|
||||
|
||||
## Overview
|
||||
## Gaps
|
||||
|
||||
mtnCapital was one of the curated ownership coin launches through MetaDAO's platform that has since been liquidated.
|
||||
- Committed amount and oversubscription ratio unknown
|
||||
- Liquidation return-per-dollar not documented
|
||||
- Exact liquidation date and mechanism details need confirmation
|
||||
- Treasury multisig address unknown
|
||||
- Monthly allowance unknown
|
||||
|
||||
## Timeline
|
||||
|
||||
- **[Date Unknown]** — Launched through MetaDAO curated platform
|
||||
- **[Date Unknown]** — Liquidated
|
||||
- **2026-04-03** — Confirmed liquidated status
|
||||
- **2025-H2** — Launched as first curated ownership coin on MetaDAO
|
||||
- **~2025-09** — Liquidated via futarchy governance, capital returned to holders
|
||||
|
||||
---
|
||||
|
||||
Relevant Notes:
|
||||
- [[metadao]] — launch platform
|
||||
- [[ranger-protocol]] — second liquidation, higher-profile enforcement
|
||||
|
||||
Topics:
|
||||
- [[internet finance and decision markets]]
|
||||
|
|
|
|||
|
|
@ -1,19 +0,0 @@
|
|||
# OMFG
|
||||
|
||||
**Type:** Protocol
|
||||
**Domain:** internet-finance
|
||||
**Status:** Active
|
||||
**Launch Date:** ~2025-2026
|
||||
|
||||
## Overview
|
||||
|
||||
OMFG is an ownership coin launched through MetaDAO's futarchy-governed ICO platform. It is one of eight projects that raised capital through MetaDAO's unruggable ICO mechanism as of early 2026.
|
||||
|
||||
## Governance
|
||||
|
||||
OMFG operates under futarchy governance with the anti-rug liquidation structure standard to MetaDAO ownership coins.
|
||||
|
||||
## Timeline
|
||||
|
||||
- **~2025-2026** — Launched ICO through MetaDAO platform
|
||||
- **2026-04-02** — Confirmed as actively trading ownership coin
|
||||
|
|
@ -1,13 +1,86 @@
|
|||
# Omnipair
|
||||
---
|
||||
name: "OmniPair"
|
||||
ticker: "$OMFG"
|
||||
type: entity
|
||||
subtype: ownership-coin
|
||||
domain: internet-finance
|
||||
status: active
|
||||
launch_platform: metadao-curated
|
||||
launch_date: "2025-H2"
|
||||
|
||||
**Type:** Protocol
|
||||
**Domain:** internet-finance
|
||||
**Founder:** @rakka_sol
|
||||
raise:
|
||||
target_usd: 300000
|
||||
amount_raised_usd: 1118102
|
||||
amount_committed_usd: 5500000
|
||||
oversubscription_ratio: 5.0
|
||||
initial_token_price_usd: 0.1118
|
||||
|
||||
## Overview
|
||||
operations:
|
||||
monthly_allowance_usd: 50000
|
||||
|
||||
Omnipair is building a permissionless borrow/lend protocol on Solana. The project raised capital through MetaDAO's futarchy platform and is cited as an example of successful founder-platform fit.
|
||||
chain:
|
||||
token_mint: "omfgRBnxHsNJh6YeGbGAmWenNkenzsXyBXm3WDhmeta"
|
||||
network: solana
|
||||
market_cap_usd: null
|
||||
price_usd: null
|
||||
circulating_supply: null
|
||||
total_supply: null
|
||||
treasury_multisig: null
|
||||
treasury_multisig_usd: null
|
||||
lp_pools:
|
||||
- dex: meteora
|
||||
address: "BiNnErm2VDkbKGiABj9ZRUjybz879NhH2heeWE7m5M6d"
|
||||
- dex: meteora
|
||||
address: "JBFvVa5nVLjR3tsDqQwa7ZYBBVceDebQSr6DoCPqwRf8"
|
||||
- dex: raydium
|
||||
address: "2WNhaB6TPyZ3ynJjAUM4ZZ1Hdeep8FJ3A76FjGjTVjjS"
|
||||
equity_value_usd: null
|
||||
data_updated: null
|
||||
|
||||
holders:
|
||||
- name: "Community (futarchy participants)"
|
||||
role: "early"
|
||||
estimated_pct: null
|
||||
|
||||
traction:
|
||||
revenue_monthly_usd: null
|
||||
customers: null
|
||||
key_metrics:
|
||||
- "Mainnet launched Feb 16, 2026 (borrowing enabled)"
|
||||
- "Audited by Offside Labs + Ackee Blockchain Security (64K USDC)"
|
||||
- "4 governance proposals completed on MetaDAO"
|
||||
|
||||
liquidation:
|
||||
date: null
|
||||
return_per_dollar: null
|
||||
reason: null
|
||||
|
||||
tracked_by: rio
|
||||
---
|
||||
|
||||
# OmniPair
|
||||
|
||||
OmniPair is a generalized AMM with permissionless margin on Solana, enabling synthetic leverage loops where users borrow USDC against collateral and repost as collateral for leveraged positions. Raised $1.1M through MetaDAO's curated ICO with 5x oversubscription after founder @rakka_sol ran a 3-week roadshow. Notable as the first futarchy-governed permissionless market creation mechanism in production — borrowing went live on mainnet February 16, 2026.
|
||||
|
||||
## Gaps
|
||||
|
||||
- Treasury multisig address unknown
|
||||
- Current market cap, price, and supply data needed (auto-fetch will populate)
|
||||
- Revenue and user metrics not documented
|
||||
- Monthly allowance discrepancy: MetaDAO launchpad page shows $10K/month, spreadsheet says $50K — needs verification
|
||||
|
||||
## Timeline
|
||||
|
||||
- **2026** — Raised $1.1M on MetaDAO in 4 days after 3-week roadshow. Founder @rakka_sol had worked in crypto on dev side but lacked VC connections. Project benefited from organic community formation through token launch.
|
||||
- **2025-H2** — Raised $1.1M on MetaDAO in 4 days after 3-week roadshow (5x oversubscribed)
|
||||
- **2025-10-31** — Allocated 64K USDC for dual audit (Offside Labs + Ackee Blockchain Security)
|
||||
- **2026-02-16** — Mainnet launch: borrowing enabled, leveraged longs staged
|
||||
- **2026-04** — 4 governance proposals completed via MetaDAO futarchy
|
||||
|
||||
---
|
||||
|
||||
Relevant Notes:
|
||||
- [[metadao]] — launch platform
|
||||
- [[rakka]] — founder
|
||||
|
||||
Topics:
|
||||
- [[internet finance and decision markets]]
|
||||
|
|
|
|||
|
|
@ -1,39 +1,128 @@
|
|||
---
|
||||
name: "P2P.me"
|
||||
ticker: "$P2P"
|
||||
type: entity
|
||||
subtype: ownership-coin
|
||||
domain: internet-finance
|
||||
status: active
|
||||
launch_platform: metadao-curated
|
||||
launch_date: "2026-03-26"
|
||||
|
||||
raise:
|
||||
target_usd: null
|
||||
amount_raised_usd: 6000000
|
||||
amount_committed_usd: 7300000
|
||||
oversubscription_ratio: 1.1
|
||||
initial_token_price_usd: null
|
||||
|
||||
operations:
|
||||
monthly_allowance_usd: null
|
||||
|
||||
chain:
|
||||
token_mint: null
|
||||
network: solana
|
||||
market_cap_usd: null
|
||||
price_usd: null
|
||||
circulating_supply: null
|
||||
total_supply: 25800000
|
||||
treasury_multisig: null
|
||||
treasury_multisig_usd: null
|
||||
lp_pools: []
|
||||
equity_value_usd: null
|
||||
data_updated: null
|
||||
|
||||
holders:
|
||||
- name: "Multicoin Capital"
|
||||
role: "lead"
|
||||
estimated_pct: null
|
||||
- name: "Coinbase Ventures"
|
||||
role: "lead"
|
||||
estimated_pct: null
|
||||
- name: "Top 10 wallets"
|
||||
role: "early"
|
||||
estimated_pct: 93
|
||||
|
||||
traction:
|
||||
revenue_monthly_usd: 48000
|
||||
customers: 23000
|
||||
key_metrics:
|
||||
- "27% MoM growth sustained over 16 months"
|
||||
- "NPS: 80"
|
||||
- "Peak monthly volume: $3.95M (Feb 2026)"
|
||||
- "Annualized revenue: ~$578K"
|
||||
- "Monthly burn: $175K (25-person team)"
|
||||
- "Runway: ~34 months"
|
||||
- "Fraud rate: <1/1000 transactions"
|
||||
- "Sub-90-second settlement"
|
||||
- "6 countries live: India (78%), Brazil (15%), Argentina, Indonesia, Venezuela, Mexico"
|
||||
- "336 contributors, 93% from 10 wallets"
|
||||
- "FDV: ~$15.5M ($0.60/token, 10M sold)"
|
||||
- "50% liquid at launch"
|
||||
- "Team unlock: performance-based 2x-32x price triggers"
|
||||
- "Investor lock: 12 months then staggered over 12 months"
|
||||
|
||||
liquidation:
|
||||
date: null
|
||||
return_per_dollar: null
|
||||
reason: null
|
||||
|
||||
tracked_by: rio
|
||||
---
|
||||
|
||||
# P2P.me
|
||||
|
||||
**Type:** Peer-to-peer fiat-crypto exchange protocol
|
||||
**Status:** Active
|
||||
**Domain:** internet-finance
|
||||
**Markets:** India, Brazil, Argentina, Indonesia
|
||||
P2P.me is a non-custodial peer-to-peer USDC-to-fiat onramp protocol targeting emerging markets with capital controls, using ZK-TLS-based Proof-of-Credibility verification for trustless fiat payment confirmation over legacy banking rails (UPI, PIX, QRIS). Most recent MetaDAO curated ICO (March 2026), raised $6M with only 1.1x oversubscription — the lowest on the platform, reflecting market maturation from the 200x+ ratios of earlier launches. Backed by Multicoin Capital and Coinbase Ventures; 2/3 of capital from institutional sources.
|
||||
|
||||
## Overview
|
||||
## Business Model
|
||||
|
||||
P2P.me is a peer-to-peer fiat onramp protocol targeting emerging markets. The platform uses ZK-TLS-based Proof-of-Credibility verification to enable trustless fiat payment confirmation over legacy banking rails.
|
||||
- Permissionless fiat on/off-ramp via Circles of Trust model
|
||||
- Local operators stake capital, recruit merchants, earn 0.2% of monthly volume
|
||||
- Country launch cost compressed from $40K to $400; launch timeline from 45 days to 10 days
|
||||
- Related product: Coins.me (consumer neo-bank built on P2P Protocol infrastructure)
|
||||
|
||||
## Technology
|
||||
|
||||
- **Proof-of-Credibility:** ZK-TLS verification system for fiat payment attestation
|
||||
- **Settlement speed:** Sub-90-second average transaction time
|
||||
- **Fraud rate:** <1 in 1,000 transactions (vs ~33% scam encounter rate on Binance P2P)
|
||||
- ZK-TLS Proof-of-Credibility for fiat payment attestation
|
||||
- Integration with UPI (India), PIX (Brazil), QRIS (Indonesia)
|
||||
- AI operations layer built on 2.5-year operational playbook
|
||||
- Open-source SDK planned for third-party integration
|
||||
|
||||
## Metrics
|
||||
## Expansion
|
||||
|
||||
- **NPS:** 80
|
||||
- **Growth:** 27% month-over-month sustained over 16 months
|
||||
- **Volume (pre-ICO):** ~$4M monthly
|
||||
- **Revenue (annualized):** $578K
|
||||
- **Monthly gross profit:** $4.5K-$13.3K (inconsistent)
|
||||
- **Monthly burn:** $175K
|
||||
- 6 countries live: India, Brazil, Argentina, Venezuela, Mexico, Indonesia
|
||||
- 16 countries in active pipeline (Colombia, Peru, Nigeria, Philippines, Thailand, Vietnam, etc.)
|
||||
- Target: 40 countries within 18 months
|
||||
|
||||
## Governance
|
||||
## Controversy
|
||||
|
||||
P2P.me raised capital through MetaDAO's futarchy-governed ICO mechanism, creating a governance token for the protocol.
|
||||
The P2P team placed a bet on Polymarket predicting their ICO would reach $6M in commits — potential insider trading. MetaDAO extended the sale 2 days and offered full refunds; ~$200K claimed. Pine Analytics flagged a 182x gross profit multiple valuation; team acknowledged concern as "completely valid."
|
||||
|
||||
## Gaps
|
||||
|
||||
- Token address needed for on-chain tracking
|
||||
- Treasury multisig address unknown
|
||||
- LP pool addresses needed
|
||||
- Current market cap and price data needed
|
||||
- Monthly gross profit inconsistent ($4.5K-$13.3K range)
|
||||
|
||||
## Timeline
|
||||
|
||||
- **2024-03** — Protocol launched, began operations
|
||||
- **2024-12** — Launch in initial emerging markets
|
||||
- **2026-04** — Completed $6M ICO through MetaDAO futarchy mechanism with 336 contributors (93% from 10 wallets)
|
||||
- **2026-04** — Team acknowledged 182x gross profit multiple valuation concerns as "completely valid"
|
||||
- **2025-09** — Brazil launch: 45 days, 3 people, $40K investment
|
||||
- **2025-11** — Argentina launch: 30 days, 2 people, $20K investment
|
||||
- **2026-01** — Venezuela launch: 15 days, no local team, $400 investment
|
||||
- **2026-02** — Mexico launch: 10 days, no local team, $400 investment
|
||||
- **2026-03-26** — Completed $6M ICO through MetaDAO: 336 contributors, 93% from 10 wallets, 1.1x oversubscribed
|
||||
- **2026-03** — Polymarket controversy; MetaDAO offered refunds, ~$200K claimed
|
||||
|
||||
## Sources
|
||||
---
|
||||
|
||||
- Rio analysis of P2P.me launch, 2026-04-12
|
||||
Relevant Notes:
|
||||
- [[metadao]] — launch platform
|
||||
- [[multicoin-capital]] — lead investor
|
||||
- [[coinbase-ventures]] — lead investor
|
||||
- [[coins-me]] — consumer product built on P2P infrastructure
|
||||
|
||||
Topics:
|
||||
- [[internet finance and decision markets]]
|
||||
|
|
|
|||
|
|
@ -1,51 +0,0 @@
|
|||
# P2P Protocol
|
||||
|
||||
**Type:** Fiat on/off-ramp protocol
|
||||
**Status:** Active
|
||||
**Geography:** 6 countries operational, 16 in pipeline, 40-country target within 18 months
|
||||
**Model:** Peer-to-peer fiat settlement with stablecoin clearing layer
|
||||
|
||||
## Overview
|
||||
|
||||
P2P Protocol is a permissionless fiat on/off-ramp infrastructure operating on real-time payment rails including UPI (India), PIX (Brazil), and QRIS (Indonesia). The protocol uses a Circles of Trust model where local operators stake capital, recruit merchants, and earn 0.2% of monthly volume processed through their circle.
|
||||
|
||||
## Business Model
|
||||
|
||||
- Local operators stake capital and recruit merchants
|
||||
- Operators earn 0.2% of monthly volume
|
||||
- No central team payroll for country operations
|
||||
- AI-powered operations layer provides support
|
||||
|
||||
## Key Metrics
|
||||
|
||||
- Operating for 2+ years
|
||||
- 6 countries live (Brazil, Argentina, Venezuela, Mexico, India, Indonesia)
|
||||
- 25-person global team (5 nationalities, 7 languages)
|
||||
- Country launch cost reduced from $40K to $400
|
||||
- Launch timeline compressed from 45 days to 10 days
|
||||
|
||||
## Technology
|
||||
|
||||
- Stablecoin clearing layer for cross-border settlement
|
||||
- Integration with major real-time payment systems
|
||||
- AI operations layer built on 2.5-year operational playbook
|
||||
- Open-source SDK for third-party integration (planned)
|
||||
|
||||
## Expansion Strategy
|
||||
|
||||
16 countries in active pipeline: Colombia, Peru, Costa Rica, Uruguay, Paraguay, Ecuador, Bolivia, Nigeria, Philippines, Thailand, Vietnam, Portugal, Spain, Turkey, Egypt, Kenya.
|
||||
|
||||
Planned permissionless version where anyone can create a circle, with SLA-based promotion to main application.
|
||||
|
||||
## Related Products
|
||||
|
||||
- **Coins.me**: Consumer neo-bank application built on P2P Protocol infrastructure
|
||||
|
||||
## Timeline
|
||||
|
||||
- **2024-03** — Protocol launched, began operations
|
||||
- **2025-09** — Brazil launch: 45 days, 3 people, $40K investment
|
||||
- **2025-11** — Argentina launch: 30 days, 2 people, $20K investment
|
||||
- **2026-01** — Venezuela launch: 15 days, no local team, $400 investment
|
||||
- **2026-02** — Mexico launch: 10 days, no local team, $400 investment
|
||||
- **2026-03** — Vision announcement: 40-country expansion target, permissionless circles model, open-source SDK
|
||||
|
|
@ -1,31 +0,0 @@
|
|||
---
|
||||
type: entity
|
||||
entity_type: company
|
||||
name: P2P.me
|
||||
status: active
|
||||
founded: 2025
|
||||
headquarters: Unknown
|
||||
focus: On/off ramping for regions with capital controls
|
||||
funding_total: $6M
|
||||
---
|
||||
|
||||
# P2P.me
|
||||
|
||||
P2P.me is a platform for cryptocurrency on/off ramping designed for places with capital controls.
|
||||
|
||||
## Overview
|
||||
|
||||
P2P.me provides fiat-crypto exchange services targeting regions where traditional banking infrastructure restricts capital movement.
|
||||
|
||||
## Funding
|
||||
|
||||
Raised $6M on MetaDAO platform in March 2026, with approximately 2/3 of capital from institutional funds rather than retail. Two funds negotiated guaranteed allocations totaling $465K before the raise opened.
|
||||
|
||||
## Controversy
|
||||
|
||||
The raise was controversial because the P2P team placed a bet on Polymarket that their raise would fill, constituting potential insider trading. MetaDAO allowed the raise to proceed but offered full refunds to anyone who committed before the news emerged; approximately $200K was claimed in refunds.
|
||||
|
||||
## Timeline
|
||||
|
||||
- **2026-03** — Raised $6M on MetaDAO platform with fund-heavy participation (2/3 institutional)
|
||||
- **2026-03** — Controversy over team's Polymarket bet on their own raise; MetaDAO offered refunds, ~$200K claimed
|
||||
|
|
@ -1,15 +0,0 @@
|
|||
# P2P.me
|
||||
|
||||
**Type:** Company
|
||||
**Domain:** internet-finance
|
||||
**Status:** Active
|
||||
**Launch Platform:** MetaDAO (curated)
|
||||
|
||||
## Overview
|
||||
|
||||
P2P.me is one of the curated ownership coin launches through MetaDAO's platform.
|
||||
|
||||
## Timeline
|
||||
|
||||
- **[Date Unknown]** — Launched through MetaDAO curated platform
|
||||
- **2026-04-03** — Confirmed active status
|
||||
|
|
@ -1,14 +1,72 @@
|
|||
---
|
||||
name: "Paystream"
|
||||
ticker: "$PAYS"
|
||||
type: entity
|
||||
subtype: ownership-coin
|
||||
domain: internet-finance
|
||||
status: active
|
||||
launch_platform: metadao-curated
|
||||
launch_date: "2025-10-23"
|
||||
|
||||
raise:
|
||||
target_usd: 550000
|
||||
amount_raised_usd: 750000
|
||||
amount_committed_usd: 6100000
|
||||
oversubscription_ratio: 11.0
|
||||
initial_token_price_usd: 0.075
|
||||
|
||||
operations:
|
||||
monthly_allowance_usd: 33500
|
||||
|
||||
chain:
|
||||
token_mint: "PAYZP1W3UmdEsNLJwmH61TNqACYJTvhXy8SCN4Tmeta"
|
||||
network: solana
|
||||
market_cap_usd: null
|
||||
price_usd: null
|
||||
circulating_supply: null
|
||||
total_supply: null
|
||||
treasury_multisig: null
|
||||
treasury_multisig_usd: null
|
||||
lp_pools: []
|
||||
equity_value_usd: null
|
||||
data_updated: null
|
||||
|
||||
holders: []
|
||||
|
||||
traction:
|
||||
revenue_monthly_usd: null
|
||||
customers: null
|
||||
key_metrics: []
|
||||
|
||||
liquidation:
|
||||
date: null
|
||||
return_per_dollar: null
|
||||
reason: null
|
||||
|
||||
tracked_by: rio
|
||||
---
|
||||
|
||||
# Paystream
|
||||
|
||||
**Type:** Company
|
||||
**Domain:** internet-finance
|
||||
**Status:** Active
|
||||
**Token:** PAYS
|
||||
Paystream is a liquidity optimizer for Solana combining P2P lending, leveraged LP, and yield routing into a unified platform. Raised $750K through MetaDAO's curated ICO with 11x oversubscription ($6.1M committed against a $550K target). Positioned as infrastructure for capital-efficient liquidity provisioning on Solana.
|
||||
|
||||
## Overview
|
||||
## Gaps
|
||||
|
||||
Paystream is a project that raised capital through MetaDAO's permissioned futarchy launchpad.
|
||||
- Treasury multisig address unknown
|
||||
- Current market cap, price, and supply data needed
|
||||
- LP pool addresses needed
|
||||
- Revenue and user metrics not documented
|
||||
- Team/founder information not documented
|
||||
- Price performance and product status not documented
|
||||
|
||||
## Timeline
|
||||
|
||||
- **2025-2026** — Raised capital through MetaDAO permissioned launchpad
|
||||
- **2025-10-23 to 2025-10-27** — MetaDAO ICO: $550K target, $6.1M committed, $750K raised (11x oversubscribed)
|
||||
|
||||
---
|
||||
|
||||
Relevant Notes:
|
||||
- [[metadao]] — launch platform
|
||||
|
||||
Topics:
|
||||
- [[internet finance and decision markets]]
|
||||
|
|
|
|||
|
|
@ -1,13 +0,0 @@
|
|||
# Ranger Finance
|
||||
|
||||
**Type:** Company
|
||||
**Domain:** internet-finance
|
||||
**Status:** Liquidated
|
||||
|
||||
## Overview
|
||||
|
||||
Ranger Finance was a project that raised capital through MetaDAO's futarchy-governed platform and was subsequently liquidated through the platform's governance mechanism.
|
||||
|
||||
## Timeline
|
||||
|
||||
- **2026-04** — Treasury liquidated via MetaDAO futarchy after allegations of material misrepresentations including 4x revenue overstatement. All remaining cash returned to tokenholders, IP transferred back to team. Demonstrated first production use of futarchy-governed liquidation mechanism.
|
||||
|
|
@ -1,34 +1,75 @@
|
|||
---
|
||||
name: "Ranger"
|
||||
ticker: "$RNGR"
|
||||
type: entity
|
||||
entity_type: protocol
|
||||
name: Ranger Protocol
|
||||
subtype: ownership-coin
|
||||
domain: internet-finance
|
||||
status: liquidated
|
||||
launch_platform: metadao-curated
|
||||
launch_date: "2026-01"
|
||||
|
||||
raise:
|
||||
target_usd: 6000000
|
||||
amount_raised_usd: 8000000
|
||||
amount_committed_usd: 86400000
|
||||
oversubscription_ratio: 14.4
|
||||
initial_token_price_usd: 0.80
|
||||
|
||||
operations:
|
||||
monthly_allowance_usd: 250000
|
||||
|
||||
chain:
|
||||
token_mint: "RNGRtJMbCveqCp7AC6U95KmrdKecFckaJZiWbPGmeta"
|
||||
network: solana
|
||||
market_cap_usd: null
|
||||
price_usd: null
|
||||
circulating_supply: null
|
||||
total_supply: null
|
||||
treasury_multisig: null
|
||||
treasury_multisig_usd: null
|
||||
lp_pools: []
|
||||
equity_value_usd: null
|
||||
data_updated: null
|
||||
|
||||
holders: []
|
||||
|
||||
traction:
|
||||
revenue_monthly_usd: null
|
||||
customers: null
|
||||
key_metrics:
|
||||
- "Claimed: $5B volume, $2M revenue (2025)"
|
||||
- "Actual: ~$2B volume, ~$500K revenue (on-chain analysis)"
|
||||
|
||||
liquidation:
|
||||
date: "2026-03-12"
|
||||
return_per_dollar: 0.78
|
||||
reason: "Material misrepresentation of revenue and volume metrics. On-chain analysis showed ~$2B volume vs $5B claimed, ~$500K revenue vs $2M claimed. Activity flatlined after ICO announcement."
|
||||
|
||||
tracked_by: rio
|
||||
---
|
||||
|
||||
# Ranger Protocol
|
||||
# Ranger
|
||||
|
||||
**Type:** Perpetual aggregator protocol
|
||||
**Chain:** Solana
|
||||
**Status:** Liquidated via futarchy governance (2026)
|
||||
**Fundraise:** $8M+ raised on MetaDAO platform
|
||||
Ranger was marketed as the "first perp aggregator on Solana" and raised $8M+ through MetaDAO's curated ICO in January 2026. Liquidated in March 2026 after tokenholder governance proved material misrepresentation — on-chain analysis showed volume and revenue were roughly 60-75% below what the team claimed pre-ICO. The liquidation returned 5.047M USDC to unlocked RNGR holders (~$0.78 per dollar of book value) with IP transferred back to the team (Glint House PTE). 97% market support for the liquidation proposal.
|
||||
|
||||
## Overview
|
||||
## Significance
|
||||
|
||||
Ranger was marketed as the "first perp aggregator on Solana" and raised over $8 million through MetaDAO's futarchy-governed ICO platform.
|
||||
Ranger's liquidation was the highest-profile test of the "unruggable ICO" thesis. It demonstrated three things: (1) futarchy governance can enforce investor protection by unwinding projects, (2) futarchy can override its own prior decisions (overrode a 90-day cooldown on buyback/liquidation proposals) when new evidence emerges, and (3) the mechanism returns meaningful capital (~78 cents on the dollar) rather than going to zero.
|
||||
|
||||
## Timeline
|
||||
|
||||
- **2024-2025** — Raised $8M+ on MetaDAO as perpetual aggregator protocol
|
||||
- **2026-03** — MetaDAO governance voted to shut down project and return funds
|
||||
- **2026-03** — Liquidation executed: 5.047M USDC returned to unlocked RNGR holders (~$0.78 book value), IP returned to team
|
||||
- **2025-11** — ICO announcement
|
||||
- **2025-12** — Co-founder presentation claiming $5B volume and $2M revenue for 2025
|
||||
- **2026-01** — Raised $8M+ via futarchy ICO on MetaDAO; token peaked at TGE, fell 74-90%
|
||||
- **2026-03** — Liquidation proposal brought by RNGR holders; on-chain analysis showed ~$2B volume and ~$500K revenue
|
||||
- **2026-03-12** — Liquidation snapshot; 5.047M USDC returned to unlocked holders (~$0.78 book value)
|
||||
- **2026-03-17** — Liquidation portal launched; IP returned to Glint House PTE
|
||||
|
||||
- **2026-03** — [[metadao-ranger-liquidation-2026-03]] Passed: Liquidation executed, 5.047M USDC returned to holders at ~$0.78 book value
|
||||
## Significance
|
||||
---
|
||||
|
||||
Ranger represents the first documented case of futarchy-governed liquidation executing as designed. The MetaDAO community voted to shut down the project and return remaining treasury funds to token holders, demonstrating the "unruggable ICO" mechanism in practice. The liquidation returned approximately $0.78 per dollar of book value to unlocked token holders.
|
||||
Relevant Notes:
|
||||
- [[metadao]] — launch platform
|
||||
- [[mtncapital]] — first liquidation precedent
|
||||
|
||||
## Sources
|
||||
|
||||
- @BetQuant: "Ranger — the 'first perp aggregator on Solana' that raised $8M+ on MetaDAO? Now MetaDAO is considering shutting the project down and returning f[unds]"
|
||||
- @defiprime: "Result: liquidity pulled, 5.047M USDC returned to unlocked RNGR holders (~$0.78 book value), IP returned to the team. On-chain governance delivering capital return."
|
||||
Topics:
|
||||
- [[internet finance and decision markets]]
|
||||
|
|
|
|||
|
|
@ -1,21 +0,0 @@
|
|||
# Ranger (RNGR)
|
||||
|
||||
**Type:** Protocol
|
||||
**Domain:** internet-finance
|
||||
**Status:** Liquidated (March 2026)
|
||||
|
||||
## Overview
|
||||
|
||||
Ranger was a protocol that raised $8M+ through a futarchy-governed ICO on MetaDAO in January 2026. It became the first project to be liquidated by its own tokenholders through futarchy governance after allegations of material misrepresentation.
|
||||
|
||||
## Timeline
|
||||
|
||||
- **November 2025** — ICO announcement
|
||||
- **December 2025** — Co-founder presentation claiming $5B volume and $2M revenue for 2025
|
||||
- **January 2026** — Raised $8M+ via futarchy ICO on MetaDAO
|
||||
- **Early March 2026** — Liquidation proposal brought by RNGR holders alleging material misrepresentations; on-chain analysis showed ~$2B volume and $500K revenue (both down 90%+ from claimed figures); activity flatlined after ICO announcement
|
||||
- **March 12, 2026** — Liquidation snapshot; holders received ~5.04 USDC per RNGR from treasury
|
||||
|
||||
## Significance
|
||||
|
||||
Ranger's liquidation was the first real-world test of the "unruggable ICO" thesis, demonstrating that futarchy governance can enforce investor protection by unwinding projects and returning capital when teams materially misrepresent. The liquidation also overrode a prior 90-day cooldown on buyback/liquidation proposals, showing futarchy can override its own prior decisions when new evidence emerges.
|
||||
|
|
@ -1,18 +0,0 @@
|
|||
# Ranger (RNGR)
|
||||
|
||||
**Type:** Ownership coin
|
||||
**Ticker:** RNGR
|
||||
**Launch Platform:** MetaDAO futarchy launchpad
|
||||
**Status:** Launched
|
||||
|
||||
## Overview
|
||||
|
||||
Ranger (RNGR) is an ownership coin launched through MetaDAO's futarchy-governed ICO platform on Solana.
|
||||
|
||||
## Timeline
|
||||
|
||||
- **2026-04-01** — Confirmed as one of the ownership coins launched through MetaDAO's permissioned launchpad
|
||||
|
||||
## Sources
|
||||
|
||||
- Telegram conversation with @m3taversal, April 2026
|
||||
|
|
@ -1,13 +1,78 @@
|
|||
# Solomon (SOLO)
|
||||
---
|
||||
name: "Solomon Labs"
|
||||
ticker: "$SOLO"
|
||||
type: entity
|
||||
subtype: ownership-coin
|
||||
domain: internet-finance
|
||||
status: active
|
||||
launch_platform: metadao-curated
|
||||
launch_date: "2025-11-14"
|
||||
|
||||
**Type:** Protocol
|
||||
**Domain:** Internet Finance
|
||||
**Status:** Active
|
||||
raise:
|
||||
target_usd: 2000000
|
||||
amount_raised_usd: 8000000
|
||||
amount_committed_usd: 102900000
|
||||
oversubscription_ratio: 51.5
|
||||
initial_token_price_usd: 0.80
|
||||
|
||||
## Overview
|
||||
operations:
|
||||
monthly_allowance_usd: 100000
|
||||
|
||||
Solomon (SOLO) was the first project to raise capital through MetaDAO's formal permissioned launchpad infrastructure.
|
||||
chain:
|
||||
token_mint: "SoLo9oxzLDpcq1dpqAgMwgce5WqkRDtNXK7EPnbmeta"
|
||||
network: solana
|
||||
market_cap_usd: null
|
||||
price_usd: null
|
||||
circulating_supply: null
|
||||
total_supply: null
|
||||
treasury_multisig: null
|
||||
treasury_multisig_usd: null
|
||||
lp_pools:
|
||||
- dex: meteora
|
||||
address: "o5rJFXSKTsuws58rBMNPG8jdKdnY4Z7ouU29dyohE4g"
|
||||
- dex: meteora
|
||||
address: "ASJ37krwSJ7eea7Yn6JkgrxjtymVfZkmUDsybdxELx5s"
|
||||
equity_value_usd: null
|
||||
data_updated: null
|
||||
|
||||
holders: []
|
||||
|
||||
traction:
|
||||
revenue_monthly_usd: null
|
||||
customers: null
|
||||
key_metrics:
|
||||
- "Target APY: 16-20% via basis strategy (long spot, short perp) + T-bills"
|
||||
- "Team tokens: 500K SOLO per milestone (2x/4x/8x/16x/32x price triggers via 3-month TWAP after 18-month cliff)"
|
||||
|
||||
liquidation:
|
||||
date: null
|
||||
return_per_dollar: null
|
||||
reason: null
|
||||
|
||||
tracked_by: rio
|
||||
---
|
||||
|
||||
# Solomon Labs
|
||||
|
||||
Solomon Labs is building USDv, a composable dollar stablecoin on Solana that generates yield through a basis trading strategy (long spot, short perp) combined with T-bill exposure, targeting 16-20% APY while maintaining full DeFi composability. Raised $8M through MetaDAO's curated ICO with 51.5x oversubscription ($102.9M committed against a $2M target) — the largest single raise on the platform. Team unlock is performance-based with milestone triggers at 2x/4x/8x/16x/32x price via 3-month TWAP after an 18-month cliff.
|
||||
|
||||
## Gaps
|
||||
|
||||
- Treasury multisig address unknown
|
||||
- Current market cap, price, and supply data needed
|
||||
- LP pool addresses needed
|
||||
- Revenue, TVL, and USDv adoption metrics not documented
|
||||
- Team/founder information not documented
|
||||
- Current APY performance vs target not documented
|
||||
|
||||
## Timeline
|
||||
|
||||
- **2024-XX-XX** — First project to launch through MetaDAO's permissioned launchpad, following the earlier Saber Vote Market raise that predated the formal launchpad.
|
||||
- **2025-11-14 to 2025-11-18** — MetaDAO ICO: $2M target, $102.9M committed, $8M raised (51.5x oversubscribed)
|
||||
|
||||
---
|
||||
|
||||
Relevant Notes:
|
||||
- [[metadao]] — launch platform
|
||||
|
||||
Topics:
|
||||
- [[internet finance and decision markets]]
|
||||
|
|
|
|||
|
|
@ -1,42 +1,97 @@
|
|||
# Umbra Privacy Protocol
|
||||
---
|
||||
name: "Umbra"
|
||||
ticker: "$UMBRA"
|
||||
type: entity
|
||||
subtype: ownership-coin
|
||||
domain: internet-finance
|
||||
status: active
|
||||
launch_platform: metadao-curated
|
||||
launch_date: "2025-10-06"
|
||||
|
||||
**Type:** Privacy protocol
|
||||
**Chain:** Solana
|
||||
**Launch:** March 26, 2025 (public mainnet)
|
||||
**Governance:** Futarchy (via MetaDAO)
|
||||
**Token:** $UMBRA
|
||||
raise:
|
||||
target_usd: 750000
|
||||
amount_raised_usd: 3000000
|
||||
amount_committed_usd: 154900000
|
||||
oversubscription_ratio: 206.0
|
||||
initial_token_price_usd: 0.30
|
||||
|
||||
## Overview
|
||||
operations:
|
||||
monthly_allowance_usd: 100000
|
||||
|
||||
Umbra is a privacy protocol on Solana that enables shielded transactions, private swaps, and anonymous asset management. Launched through MetaDAO's futarchy-governed ICO platform with 50x oversubscription.
|
||||
chain:
|
||||
token_mint: "PRVT6TB7uss3FrUd2D9xs2zqDBsa3GbMJMwCQsgmeta"
|
||||
network: solana
|
||||
market_cap_usd: null
|
||||
price_usd: null
|
||||
circulating_supply: 15000000
|
||||
total_supply: null
|
||||
treasury_multisig: null
|
||||
treasury_multisig_usd: null
|
||||
lp_pools:
|
||||
- dex: meteora
|
||||
address: "7dVri3qjYD3uobSZL3Zth8vSCgU6r6R2nvFsh7uVfDte"
|
||||
- dex: meteora
|
||||
address: "D49HwsVnGNy16K3N7dFmcFEGQJZFKfxo3gWnGY5Kkc4K"
|
||||
equity_value_usd: null
|
||||
data_updated: null
|
||||
|
||||
holders: []
|
||||
|
||||
traction:
|
||||
revenue_monthly_usd: null
|
||||
customers: null
|
||||
key_metrics:
|
||||
- "8x peak / 3x current vs ICO price (as of Jan 2026)"
|
||||
- "98% of committed capital refunded ($151.9M)"
|
||||
- "Sub-90s settlement, <1/1000 fraud rate"
|
||||
|
||||
liquidation:
|
||||
date: null
|
||||
return_per_dollar: null
|
||||
reason: null
|
||||
|
||||
tracked_by: rio
|
||||
---
|
||||
|
||||
# Umbra
|
||||
|
||||
Umbra is a privacy protocol on Solana enabling shielded transactions, private swaps, and anonymous asset management using zero-knowledge proofs. Holds the record for highest MetaDAO oversubscription at 206x ($154.9M committed against a $750K target, raised $3M final). Led by @kru_tweets with contributors @losingw0nder, @josh_trader19, @0xSn0wMan, @lare888.
|
||||
|
||||
## Product Features
|
||||
|
||||
- **Auto-Claim Anonymity:** Automatic privacy preservation during fund receipt without manual steps
|
||||
- **Auto-Claim Anonymity:** Automatic privacy preservation during fund receipt
|
||||
- **Distress Mode:** Decoy interface for physical security situations
|
||||
- **Hidden Browser UI:** Prevents accidental exposure through UI concealment
|
||||
- **Private Swaps:** Token swaps without visible on-chain trail (40-50 second average, optimizing)
|
||||
- **Hidden Browser UI:** Prevents accidental exposure
|
||||
- **Private Swaps:** Token swaps without visible on-chain trail (40-50 second average)
|
||||
- **Compliance Integration:** Built-in Range compliance for regulatory adherence
|
||||
- **SDK:** Open SDK at sdk.umbraprivacy.com for third-party integration
|
||||
|
||||
## Market Position
|
||||
|
||||
At launch: $0.42 price, $1.8M treasury AUM, ~15M circulating supply (~4x treasury valuation). Positioned as first-mover privacy solution on Solana.
|
||||
|
||||
## Technical Architecture
|
||||
|
||||
- Zero-Knowledge proof technology for private computation
|
||||
- Performance hardware-dependent (lightweight proofs, instant on modern devices)
|
||||
- Cross-platform: iOS (TestFlight), Android (direct builds), Chrome Extension, web app
|
||||
- Zero-knowledge proof technology for private computation
|
||||
- Cross-platform: iOS (TestFlight), Android, Chrome Extension, web app
|
||||
- Four initial liquidity pools: $UMBRA, $SOL, $USDC, $USDT
|
||||
- At launch: $0.42 price, $1.8M treasury AUM, ~15M circulating supply
|
||||
|
||||
## Team
|
||||
## Gaps
|
||||
|
||||
Led by @kru_tweets. Contributors include @losingw0nder, @josh_trader19, @0xSn0wMan, @lare888.
|
||||
- Treasury multisig address unknown
|
||||
- Current market cap and price data needed
|
||||
- Total supply not confirmed
|
||||
- LP pool addresses needed
|
||||
- Revenue metrics not documented
|
||||
|
||||
## Timeline
|
||||
|
||||
- **2025-Q1** — Private mainnet beta testing
|
||||
- **2025-03-26** — Public mainnet launch via TestFlight v2.2.2 Build 16
|
||||
- **2025-03-26** — MoonPay onramp temporarily disabled pending regulatory approval
|
||||
- **2025-Q2** — Planned: Android/web rollout, swap optimization, transaction history in private mode
|
||||
- **2025-03-26** — Public mainnet launch (TestFlight v2.2.2 Build 16)
|
||||
- **2025-10-06 to 2025-10-10** — MetaDAO ICO: $750K target, $154.9M committed, $3M raised (206x oversubscribed)
|
||||
- **2025-Q2** — Android/web rollout, swap optimization
|
||||
|
||||
---
|
||||
|
||||
Relevant Notes:
|
||||
- [[metadao]] — launch platform
|
||||
|
||||
Topics:
|
||||
- [[internet finance and decision markets]]
|
||||
|
|
|
|||
|
|
@ -1,15 +0,0 @@
|
|||
# Umbra
|
||||
|
||||
**Type:** Company
|
||||
**Domain:** internet-finance
|
||||
**Status:** Active
|
||||
**Launch Platform:** MetaDAO (curated)
|
||||
|
||||
## Overview
|
||||
|
||||
Umbra is one of the curated ownership coin launches through MetaDAO's platform.
|
||||
|
||||
## Timeline
|
||||
|
||||
- **[Date Unknown]** — Launched through MetaDAO curated platform
|
||||
- **2026-04-03** — Confirmed active status
|
||||
|
|
@ -1,14 +1,74 @@
|
|||
---
|
||||
name: "ZKFG"
|
||||
ticker: "$ZKFG"
|
||||
type: entity
|
||||
subtype: ownership-coin
|
||||
domain: internet-finance
|
||||
status: active
|
||||
launch_platform: metadao-curated
|
||||
launch_date: "2025-10-20"
|
||||
|
||||
raise:
|
||||
target_usd: 300000
|
||||
amount_raised_usd: 969420
|
||||
amount_committed_usd: 14900000
|
||||
oversubscription_ratio: 50.0
|
||||
initial_token_price_usd: 0.097
|
||||
|
||||
operations:
|
||||
monthly_allowance_usd: 50000
|
||||
|
||||
chain:
|
||||
token_mint: "ZKFHiLAfAFMTcDAuCtjNW54VzpERvoe7PBF9mYgmeta"
|
||||
network: solana
|
||||
market_cap_usd: null
|
||||
price_usd: null
|
||||
circulating_supply: null
|
||||
total_supply: null
|
||||
treasury_multisig: null
|
||||
treasury_multisig_usd: null
|
||||
lp_pools: []
|
||||
equity_value_usd: null
|
||||
data_updated: null
|
||||
|
||||
holders: []
|
||||
|
||||
traction:
|
||||
revenue_monthly_usd: null
|
||||
customers: null
|
||||
key_metrics:
|
||||
- "Failed buyback proposal Jan 16, 2026 ($200K USDC at $0.082/token max)"
|
||||
|
||||
liquidation:
|
||||
date: null
|
||||
return_per_dollar: null
|
||||
reason: null
|
||||
|
||||
tracked_by: rio
|
||||
---
|
||||
|
||||
# ZKFG
|
||||
|
||||
**Type:** Company
|
||||
**Domain:** internet-finance
|
||||
**Status:** Active
|
||||
**Token:** ZKFG
|
||||
ZKFG is a zero-knowledge liquid staking mixer on Solana that combines privacy with yield generation through ZK liquid staking. Raised $969K through MetaDAO's curated ICO with 50x oversubscription ($14.9M committed against a $300K target). Notable as the first MetaDAO project to attempt a below-NAV buyback through futarchy governance (January 2026, proposal failed).
|
||||
|
||||
## Overview
|
||||
## Gaps
|
||||
|
||||
ZKFG is a project that raised capital through MetaDAO's permissioned futarchy launchpad.
|
||||
- Treasury multisig address unknown
|
||||
- Current market cap, price, and supply data needed
|
||||
- LP pool addresses needed
|
||||
- Revenue and user metrics not documented
|
||||
- Team/founder information not documented
|
||||
- Price performance data not documented
|
||||
|
||||
## Timeline
|
||||
|
||||
- **2025-2026** — Raised capital through MetaDAO permissioned launchpad
|
||||
- **2025-10-20 to 2025-10-24** — MetaDAO ICO: $300K target, $14.9M committed, $969K raised (50x oversubscribed)
|
||||
- **2026-01-16** — Below-NAV buyback proposal failed ($200K USDC at $0.082/token max price)
|
||||
|
||||
---
|
||||
|
||||
Relevant Notes:
|
||||
- [[metadao]] — launch platform
|
||||
|
||||
Topics:
|
||||
- [[internet finance and decision markets]]
|
||||
|
|
|
|||
|
|
@ -1,290 +0,0 @@
|
|||
#!/usr/bin/env bash
|
||||
# auto-fix-trigger.sh — Find PRs with requested changes, auto-fix mechanical issues.
|
||||
#
|
||||
# Two-tier response to review feedback:
|
||||
# 1. AUTO-FIX: Broken wiki links, missing frontmatter fields, schema compliance
|
||||
# 2. FLAG: Domain classification, claim reframing, confidence changes → notify proposer
|
||||
#
|
||||
# Mechanical issues are fixed by a headless Claude agent on the PR branch.
|
||||
# New commits trigger re-review on the next evaluate-trigger.sh cron cycle.
|
||||
#
|
||||
# Usage:
|
||||
# ./ops/auto-fix-trigger.sh # fix all PRs with requested changes
|
||||
# ./ops/auto-fix-trigger.sh 66 # fix a specific PR
|
||||
# ./ops/auto-fix-trigger.sh --dry-run # show what would be fixed, don't run
|
||||
#
|
||||
# Requirements:
|
||||
# - claude CLI (claude -p for headless mode)
|
||||
# - gh CLI authenticated with repo access
|
||||
# - Run from the teleo-codex repo root
|
||||
#
|
||||
# Safety:
|
||||
# - Lockfile prevents concurrent runs (separate from evaluate-trigger)
|
||||
# - Only fixes mechanical issues — never changes claim substance
|
||||
# - Max one fix cycle per PR per run (prevents infinite loops)
|
||||
# - Tracks fix attempts to avoid re-fixing already-attempted PRs
|
||||
|
||||
set -euo pipefail
|
||||
|
||||
# Allow nested Claude Code sessions
|
||||
unset CLAUDECODE 2>/dev/null || true
|
||||
|
||||
REPO_ROOT="$(cd "$(dirname "$0")/.." && pwd)"
|
||||
cd "$REPO_ROOT"
|
||||
|
||||
LOCKFILE="/tmp/auto-fix-trigger.lock"
|
||||
LOG_DIR="$REPO_ROOT/ops/sessions"
|
||||
TIMEOUT_SECONDS=300 # 5 min — fixes should be fast
|
||||
DRY_RUN=false
|
||||
SPECIFIC_PR=""
|
||||
FIX_MARKER="<!-- auto-fix-attempted -->"
|
||||
|
||||
# --- Parse arguments ---
|
||||
for arg in "$@"; do
|
||||
case "$arg" in
|
||||
--dry-run) DRY_RUN=true ;;
|
||||
[0-9]*) SPECIFIC_PR="$arg" ;;
|
||||
--help|-h)
|
||||
head -20 "$0" | tail -18
|
||||
exit 0
|
||||
;;
|
||||
*)
|
||||
echo "Unknown argument: $arg"
|
||||
exit 1
|
||||
;;
|
||||
esac
|
||||
done
|
||||
|
||||
# --- Pre-flight checks ---
|
||||
if ! gh auth status >/dev/null 2>&1; then
|
||||
echo "ERROR: gh CLI not authenticated."
|
||||
exit 1
|
||||
fi
|
||||
|
||||
if ! command -v claude >/dev/null 2>&1; then
|
||||
echo "ERROR: claude CLI not found."
|
||||
exit 1
|
||||
fi
|
||||
|
||||
# --- Lockfile ---
|
||||
if [ -f "$LOCKFILE" ]; then
|
||||
LOCK_PID=$(cat "$LOCKFILE" 2>/dev/null || echo "")
|
||||
if [ -n "$LOCK_PID" ] && kill -0 "$LOCK_PID" 2>/dev/null; then
|
||||
echo "Another auto-fix-trigger is running (PID $LOCK_PID). Exiting."
|
||||
exit 1
|
||||
else
|
||||
rm -f "$LOCKFILE"
|
||||
fi
|
||||
fi
|
||||
echo $$ > "$LOCKFILE"
|
||||
trap 'rm -f "$LOCKFILE"' EXIT
|
||||
|
||||
mkdir -p "$LOG_DIR"
|
||||
|
||||
# --- Find PRs needing fixes ---
|
||||
if [ -n "$SPECIFIC_PR" ]; then
|
||||
PRS_TO_FIX="$SPECIFIC_PR"
|
||||
else
|
||||
OPEN_PRS=$(gh pr list --state open --json number --jq '.[].number' 2>/dev/null || echo "")
|
||||
|
||||
if [ -z "$OPEN_PRS" ]; then
|
||||
echo "No open PRs found."
|
||||
exit 0
|
||||
fi
|
||||
|
||||
PRS_TO_FIX=""
|
||||
for pr in $OPEN_PRS; do
|
||||
# Check if PR has request_changes reviews
|
||||
HAS_CHANGES_REQUESTED=$(gh api "repos/{owner}/{repo}/pulls/$pr/reviews" \
|
||||
--jq '[.[] | select(.state == "CHANGES_REQUESTED")] | length' 2>/dev/null || echo "0")
|
||||
|
||||
if [ "$HAS_CHANGES_REQUESTED" -eq 0 ]; then
|
||||
continue
|
||||
fi
|
||||
|
||||
# Check if auto-fix was already attempted (marker comment exists)
|
||||
ALREADY_ATTEMPTED=$(gh pr view "$pr" --json comments \
|
||||
--jq "[.comments[].body | select(contains(\"$FIX_MARKER\"))] | length" 2>/dev/null || echo "0")
|
||||
|
||||
# Check if there are new commits since the last auto-fix attempt
|
||||
if [ "$ALREADY_ATTEMPTED" -gt 0 ]; then
|
||||
LAST_FIX_DATE=$(gh pr view "$pr" --json comments \
|
||||
--jq "[.comments[] | select(.body | contains(\"$FIX_MARKER\")) | .createdAt] | last" 2>/dev/null || echo "")
|
||||
LAST_COMMIT_DATE=$(gh pr view "$pr" --json commits --jq '.commits[-1].committedDate' 2>/dev/null || echo "")
|
||||
|
||||
if [ -n "$LAST_FIX_DATE" ] && [ -n "$LAST_COMMIT_DATE" ] && [[ "$LAST_COMMIT_DATE" < "$LAST_FIX_DATE" ]]; then
|
||||
echo "PR #$pr: Auto-fix already attempted, no new commits. Skipping."
|
||||
continue
|
||||
fi
|
||||
fi
|
||||
|
||||
PRS_TO_FIX="$PRS_TO_FIX $pr"
|
||||
done
|
||||
|
||||
PRS_TO_FIX=$(echo "$PRS_TO_FIX" | xargs)
|
||||
|
||||
if [ -z "$PRS_TO_FIX" ]; then
|
||||
echo "No PRs need auto-fixing."
|
||||
exit 0
|
||||
fi
|
||||
fi
|
||||
|
||||
echo "PRs to auto-fix: $PRS_TO_FIX"
|
||||
|
||||
if [ "$DRY_RUN" = true ]; then
|
||||
for pr in $PRS_TO_FIX; do
|
||||
echo "[DRY RUN] Would attempt auto-fix on PR #$pr"
|
||||
# Show the review feedback summary
|
||||
gh pr view "$pr" --json comments \
|
||||
--jq '.comments[] | select(.body | test("Verdict.*request_changes|request changes"; "i")) | .body' 2>/dev/null \
|
||||
| grep -iE "broken|missing|schema|field|link" | head -10 || echo " (no mechanical issues detected in comments)"
|
||||
done
|
||||
exit 0
|
||||
fi
|
||||
|
||||
# --- Auto-fix each PR ---
|
||||
FIXED=0
|
||||
FLAGGED=0
|
||||
|
||||
for pr in $PRS_TO_FIX; do
|
||||
echo ""
|
||||
echo "=== Auto-fix PR #$pr ==="
|
||||
|
||||
# Get the review feedback
|
||||
REVIEW_TEXT=$(gh pr view "$pr" --json comments \
|
||||
--jq '.comments[].body' 2>/dev/null || echo "")
|
||||
|
||||
if [ -z "$REVIEW_TEXT" ]; then
|
||||
echo " No review comments found. Skipping."
|
||||
continue
|
||||
fi
|
||||
|
||||
# Classify issues as mechanical vs substantive
|
||||
# Mechanical: broken links, missing fields, schema compliance
|
||||
MECHANICAL_PATTERNS="broken wiki link|broken link|missing.*challenged_by|missing.*field|schema compliance|link.*needs to match|link text needs|missing wiki.link|add.*wiki.link|BROKEN WIKI LINK"
|
||||
# Substantive: domain classification, reframing, confidence, consider
|
||||
SUBSTANTIVE_PATTERNS="domain classification|consider.*reframing|soften.*to|confidence.*recalibrat|consider whether|territory violation|evaluator-as-proposer|conflict.of.interest"
|
||||
|
||||
HAS_MECHANICAL=$(echo "$REVIEW_TEXT" | grep -ciE "$MECHANICAL_PATTERNS" || echo "0")
|
||||
HAS_SUBSTANTIVE=$(echo "$REVIEW_TEXT" | grep -ciE "$SUBSTANTIVE_PATTERNS" || echo "0")
|
||||
|
||||
echo " Mechanical issues: $HAS_MECHANICAL"
|
||||
echo " Substantive issues: $HAS_SUBSTANTIVE"
|
||||
|
||||
# --- Handle mechanical fixes ---
|
||||
if [ "$HAS_MECHANICAL" -gt 0 ]; then
|
||||
echo " Attempting mechanical auto-fix..."
|
||||
|
||||
# Extract just the mechanical feedback lines for the fix agent
|
||||
MECHANICAL_FEEDBACK=$(echo "$REVIEW_TEXT" | grep -iE "$MECHANICAL_PATTERNS" | head -20)
|
||||
|
||||
TIMESTAMP=$(date +%Y%m%d-%H%M%S)
|
||||
FIX_LOG="$LOG_DIR/autofix-pr${pr}-${TIMESTAMP}.log"
|
||||
|
||||
PR_BRANCH=$(gh pr view "$pr" --json headRefName --jq '.headRefName' 2>/dev/null || echo "")
|
||||
|
||||
FIX_PROMPT="You are a mechanical fix agent. Your ONLY job is to fix objective, mechanical issues in PR #${pr}.
|
||||
|
||||
RULES:
|
||||
- Fix ONLY broken wiki links, missing frontmatter fields, and schema compliance issues.
|
||||
- NEVER change claim titles, arguments, confidence levels, or domain classification.
|
||||
- NEVER add new claims or remove existing ones.
|
||||
- NEVER rewrite prose or change the substance of any argument.
|
||||
- If you're unsure whether something is mechanical, SKIP IT.
|
||||
|
||||
STEPS:
|
||||
1. Run: gh pr checkout ${pr}
|
||||
2. Read the review feedback below to understand what needs fixing.
|
||||
3. For each mechanical issue:
|
||||
a. BROKEN WIKI LINKS: Find the correct filename with Glob, update the [[link]] text to match exactly.
|
||||
b. MISSING challenged_by: If a claim is rated 'likely' or higher and reviewers noted missing challenged_by,
|
||||
add a challenged_by field to the frontmatter. Use the counter-argument already mentioned in the claim body.
|
||||
c. MISSING WIKI LINKS: If reviewers named specific claims that should be linked, verify the file exists
|
||||
with Glob, then add to the Relevant Notes section.
|
||||
4. Stage and commit changes:
|
||||
git add -A
|
||||
git commit -m 'auto-fix: mechanical fixes from review feedback
|
||||
|
||||
- What was fixed (list each fix)
|
||||
|
||||
Auto-Fix-Agent: teleo-eval-orchestrator'
|
||||
5. Push: git push origin ${PR_BRANCH}
|
||||
|
||||
REVIEW FEEDBACK (fix only the mechanical issues):
|
||||
${MECHANICAL_FEEDBACK}
|
||||
|
||||
FULL REVIEW CONTEXT:
|
||||
$(echo "$REVIEW_TEXT" | head -200)
|
||||
|
||||
Work autonomously. Do not ask for confirmation. If there's nothing mechanical to fix, just exit."
|
||||
|
||||
if perl -e "alarm $TIMEOUT_SECONDS; exec @ARGV" claude -p \
|
||||
--model "sonnet" \
|
||||
--allowedTools "Read,Write,Edit,Bash,Glob,Grep" \
|
||||
--permission-mode bypassPermissions \
|
||||
"$FIX_PROMPT" \
|
||||
> "$FIX_LOG" 2>&1; then
|
||||
echo " Auto-fix agent completed."
|
||||
|
||||
# Check if any commits were actually pushed
|
||||
NEW_COMMIT_DATE=$(gh pr view "$pr" --json commits --jq '.commits[-1].committedDate' 2>/dev/null || echo "")
|
||||
echo " Latest commit: $NEW_COMMIT_DATE"
|
||||
FIXED=$((FIXED + 1))
|
||||
else
|
||||
EXIT_CODE=$?
|
||||
if [ "$EXIT_CODE" -eq 142 ] || [ "$EXIT_CODE" -eq 124 ]; then
|
||||
echo " Auto-fix: TIMEOUT after ${TIMEOUT_SECONDS}s."
|
||||
else
|
||||
echo " Auto-fix: FAILED (exit code $EXIT_CODE)."
|
||||
fi
|
||||
fi
|
||||
|
||||
echo " Log: $FIX_LOG"
|
||||
fi
|
||||
|
||||
# --- Flag substantive issues to proposer ---
|
||||
if [ "$HAS_SUBSTANTIVE" -gt 0 ]; then
|
||||
echo " Flagging substantive issues for proposer..."
|
||||
|
||||
SUBSTANTIVE_FEEDBACK=$(echo "$REVIEW_TEXT" | grep -iE "$SUBSTANTIVE_PATTERNS" | head -15)
|
||||
|
||||
# Determine proposer from branch name
|
||||
PROPOSER=$(gh pr view "$pr" --json headRefName --jq '.headRefName' 2>/dev/null | cut -d'/' -f1)
|
||||
|
||||
FLAG_COMMENT="## Substantive Feedback — Needs Proposer Input
|
||||
|
||||
The following review feedback requires the proposer's judgment and cannot be auto-fixed:
|
||||
|
||||
\`\`\`
|
||||
${SUBSTANTIVE_FEEDBACK}
|
||||
\`\`\`
|
||||
|
||||
**Proposer:** ${PROPOSER}
|
||||
**Action needed:** Review the feedback above, make changes if you agree, then push to trigger re-review.
|
||||
|
||||
$FIX_MARKER
|
||||
*Auto-fix agent — mechanical issues were ${HAS_MECHANICAL:+addressed}${HAS_MECHANICAL:-not found}, substantive issues flagged for human/agent review.*"
|
||||
|
||||
gh pr comment "$pr" --body "$FLAG_COMMENT" 2>/dev/null
|
||||
echo " Flagged to proposer: $PROPOSER"
|
||||
FLAGGED=$((FLAGGED + 1))
|
||||
elif [ "$HAS_MECHANICAL" -gt 0 ]; then
|
||||
# Only mechanical issues — post marker comment so we don't re-attempt
|
||||
MARKER_COMMENT="$FIX_MARKER
|
||||
*Auto-fix agent ran — mechanical fixes attempted. Substantive issues: none. Awaiting re-review.*"
|
||||
gh pr comment "$pr" --body "$MARKER_COMMENT" 2>/dev/null
|
||||
fi
|
||||
|
||||
# Clean up branch
|
||||
git checkout main 2>/dev/null || git checkout -f main
|
||||
PR_BRANCH=$(gh pr view "$pr" --json headRefName --jq '.headRefName' 2>/dev/null || echo "")
|
||||
[ -n "$PR_BRANCH" ] && git branch -D "$PR_BRANCH" 2>/dev/null || true
|
||||
|
||||
echo " Done."
|
||||
done
|
||||
|
||||
echo ""
|
||||
echo "=== Auto-Fix Summary ==="
|
||||
echo "Fixed: $FIXED"
|
||||
echo "Flagged: $FLAGGED"
|
||||
echo "Logs: $LOG_DIR"
|
||||
|
|
@ -62,7 +62,7 @@ Evidence: convergent evolution from opposite directions. Futarchy-native project
|
|||
|
||||
| Entity | What Happened | When | Lesson |
|
||||
|--------|--------------|------|--------|
|
||||
| [[ranger-finance]] | Liquidation proposal passed via futarchy. $6M raised, volume 60% below projections, revenue 75% below. 90%+ recovery from ICO price. | 2026-03 | Futarchy-governed liquidation IS the enforcement mechanism — system working as designed. 90%+ investor recovery validates unruggable ICO promise. |
|
||||
| [[ranger-protocol]] | Liquidation proposal passed via futarchy. $6M raised, volume 60% below projections, revenue 75% below. 90%+ recovery from ICO price. | 2026-03 | Futarchy-governed liquidation IS the enforcement mechanism — system working as designed. 90%+ investor recovery validates unruggable ICO promise. |
|
||||
| MycoRealms (v1) | First launch failed, relaunched | 2025-2026 | Low relaunch cost (~$90) enables iteration — failure is not permanent |
|
||||
|
||||
## Competitive Dynamics
|
||||
|
|
|
|||
Loading…
Reference in a new issue