New decision records with full proposal text for projects that previously had zero governance documentation in the KB. Omnipair (4): - OMFG-001: Increase Allowance to $50K/mo (Passed, 2025-10-03) - OMFG-002: Fund Security Audits $64K (Passed, 2025-10-31) - OMFG-003: Migrate to V0.6 (Passed, 2026-02-16) - OMFG-004: Strategic Ecosystem Investment $20K (Passed, 2026-03-12) Ranger (3): - ICO Launch: $86.4M committed, $6M min (Complete, 2026-01-06) - $2M Buyback at NAV (Passed, 2026-01-12) - Liquidation: contested, citing misrepresentation (Passed, 2026-03-02) Solomon (3): - ICO Launch: $102.9M committed, $8M raised (Complete, 2025-11-14) - DP-00001: Treasury Subcommittee + $150K Legal (Passed, 2026-03-05) - DP-00002: SOLO Acquisition + Incentives Reserve (Passed, 2026-03-13) Loyal (3): - ICO Launch: $75.9M committed (Complete, 2025-10-18) - $1.5M Buyback at NAV (Passed, 2025-11-26) - Liquidity Adjustment: burn 810K tokens (Passed, 2025-12-23) ZKLSOL (4): - ICO Launch: $969K raised (Complete, 2025-10-20) - Burn Team Performance Package (Passed, 2025-11-22) - $200K Buyback (Passed, 2026-01-16) - Restructuring Proposal (Passed, 2026-02-07) Umbra (3): - ICO Launch: $154.9M committed, $3M raised (Complete, 2025-10-06) - UMBRA-001: Fund Security Audits $105K (Passed, 2025-11-12) - Road to Mainnet operational expansion (Passed, 2026-01-13) Futardio cult (3): - ICO Launch: $11.4M committed (Complete, 2026-03-03) - FUTARDIO-001: Omnibus — 90% token burn + $50/mo spend (Passed, 2026-03-04) - $10K Meteora DLMM Liquidity Pool (Passed, 2026-03-17) Kyros (1): - Burn 4.42M unclaimed airdrop tokens (Passed, 2026-01-13) Jito DAO (1): - JTO Vault / TipRouter NCN per JIP-10 (Passed, 2025-01-13) Marinade (1): - SAM Bid Routing to MNDE Stakers per MIP.5 (Passed, 2025-02-04) Pentagon-Agent: Rio <5551F5AF-0C5C-429F-8915-1FE74A00E019>
44 lines
2.1 KiB
Markdown
44 lines
2.1 KiB
Markdown
---
|
|
type: decision
|
|
entity_type: decision_market
|
|
name: "Jito DAO: Should JTO Vault Be Added To TipRouter NCN?"
|
|
domain: internet-finance
|
|
status: passed
|
|
parent_entity: "[[jito]]"
|
|
platform: "futardio"
|
|
proposer: "Jito community"
|
|
proposal_url: "https://v1.metadao.fi/jito/trade/CJW4iZPT14sVNzoc4Yibx1LbnY12sA75gZCP9HZk11UA"
|
|
proposal_date: 2025-01-13
|
|
resolution_date: 2025-01-16
|
|
category: "strategy"
|
|
summary: "Sanction adding JTO Vault to TipRouter NCN per JIP-10 specifications — Jito DAO's first use of futarchy for governance"
|
|
tracked_by: rio
|
|
created: 2026-03-24
|
|
---
|
|
|
|
# Jito DAO: Should JTO Vault Be Added To TipRouter NCN?
|
|
|
|
## Summary
|
|
Jito DAO used MetaDAO's futarchy mechanism to decide whether to add a JTO Vault to the TipRouter NCN (Node Consensus Network) per JIP-10 specifications. This represents Jito's first use of futarchy for a governance decision, extending futarchy adoption beyond the MetaDAO ecosystem into one of Solana's largest DeFi protocols.
|
|
|
|
## Market Data
|
|
- **Outcome:** Passed
|
|
- **Proposal Account:** CJW4iZPT14sVNzoc4Yibx1LbnY12sA75gZCP9HZk11UA
|
|
- **Duration:** 2025-01-13 to ~2025-01-16
|
|
- **Reference:** JIP-10 on Jito governance forum
|
|
|
|
## Significance
|
|
First futarchy governance decision by Jito DAO, one of Solana's largest protocols. Demonstrates FaaS adoption for technical protocol decisions (NCN vault configuration) beyond the typical grants/treasury/hiring use cases. The decision was framed via an existing Jito Improvement Proposal (JIP-10), showing futarchy complementing rather than replacing traditional governance forums.
|
|
|
|
## Relationship to KB
|
|
- [[jito]] — parent entity (new entity needed)
|
|
- [[futarchy adoption faces friction from token price psychology proposal complexity and liquidity requirements]] — Jito adoption extends futarchy to major DeFi protocols
|
|
- [[futardio]] — governance platform
|
|
|
|
## Full Proposal Text
|
|
|
|
*Source: futard.io, tabled 2025-01-13*
|
|
|
|
If approved, this proposal would sanction the addition of a JTO Vault to the TipRouter NCN according to the specifications laid out in JIP-10.
|
|
|
|
Reference: https://forum.jito.network/t/jip-10-decision-market-on-whether-to-adopt-jto-in-the-tiprouter-ncn-protocol-development/463
|