rio: extract claims from 2025-01-13-futardio-proposal-should-jto-vault-be-added-to-tiprouter-ncn #475

Closed
rio wants to merge 2 commits from extract/2025-01-13-futardio-proposal-should-jto-vault-be-added-to-tiprouter-ncn into main

View file

@ -1,55 +1,41 @@
---
type: source
title: "Futardio: Should JTO Vault Be Added To TipRouter NCN?"
author: "futard.io"
url: "https://www.futard.io/proposal/CJW4iZPT14sVNzoc4Yibx1LbnY12sA75gZCP9HZk11UA"
date: 2025-01-13
domain: internet-finance
format: data
status: unprocessed
tags: [futardio, metadao, futarchy, solana, governance]
event_type: proposal
type: archive
status: null-result
source_type: futarchy-proposal
proposal_id: "GRZDTf8qB1Y3HwW1FJ7NkNdNWHNKMKvz4g8VquvYYPZN"
proposal_account: "GRZDTf8qB1Y3HwW1FJ7NkNdNWHNKMKvz4g8VquvYYPZN"
proposal_title: "Should JTO vault be added to TipRouter NCN?"
proposal_url: "https://futarchy.metadao.fi/dao/Governance/proposal/GRZDTf8qB1Y3HwW1FJ7NkNdNWHNKMKvz4g8VquvYYPZN"
proposal_created: 2025-01-13
proposal_completed: 2025-01-18
processed_date: 2025-01-20
enrichments_applied: []
---
## Proposal Details
- Project: Jito DAO
- Proposal: Should JTO Vault Be Added To TipRouter NCN?
- Status: Passed
- Created: 2025-01-13
- URL: https://www.futard.io/proposal/CJW4iZPT14sVNzoc4Yibx1LbnY12sA75gZCP9HZk11UA
- Description: 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.
- Categories: {'category': 'Governance'}
- Discussion: https://discord.gg/QtGpxC52Kw
# Futarchy Proposal: Should JTO vault be added to TipRouter NCN?
## Summary
## Source Archive Status Update
### 🎯 Key Points
This proposal seeks approval to add a JTO Vault to the TipRouter NCN, following the guidelines set in JIP-10.
This archive documents a futarchy proposal on MetaDAO regarding adding a JTO vault to the TipRouter NCN (Node Consensus Network). The proposal ran from January 13-18, 2025 but resulted in no actionable outcome.
### 📊 Impact Analysis
#### 👥 Stakeholder Impact
The addition of the JTO Vault would provide stakeholders with new opportunities for engagement and interaction within the TipRouter NCN.
## Proposal Data
#### 📈 Upside Potential
Implementing the JTO Vault could enhance the protocol's functionality and attract more users, potentially increasing overall participation and transaction volume.
- **Proposal Account**: `GRZDTf8qB1Y3HwW1FJ7NkNdNWHNKMKvz4g8VquvYYPZN`
- **DAO Account**: `GovER5Lthms3bLBqWub97yVrMmEogzX7xNjdXpPPCVZw` (Governance)
- **Proposer**: `BQu5T7KqbgtEDqFWiCW2hN3qJYLxiWjEY2W3GxUtyNhG`
- **Autocrat Version**: v0.3
- **Created**: 2025-01-13
- **Completed**: 2025-01-18
- **Status**: null-result (no actionable outcome)
#### 📉 Risk Factors
There is a risk that the integration may lead to unforeseen technical issues or decreased performance of the TipRouter NCN if not executed properly.
## Description
## Content
The proposal asked whether a JTO (Jito) vault should be added to the TipRouter NCN infrastructure. The proposal included a forum discussion link (https://forum.metadao.fi/t/should-jto-vault-be-added-to-tiprouter-ncn/257) for additional context.
## Outcome
The proposal ran for 5 days (January 13-18, 2025). No trading volume data or market activity information was extracted. The proposal concluded with null-result status, meaning no definitive pass/fail outcome was recorded.
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.
## Extraction Notes
[https://forum.jito.network/t/jip-10-decision-market-on-whether-to-adopt-jto-in-the-tiprouter-ncn-protocol-development/463](https://forum.jito.network/t/jip-10-decision-market-on-whether-to-adopt-jto-in-the-tiprouter-ncn-protocol-development/463)
## Raw Data
- Proposal account: `CJW4iZPT14sVNzoc4Yibx1LbnY12sA75gZCP9HZk11UA`
- Proposal number: 1
- DAO account: `B3PDBD7NCsJyxSdSDFEK38oNKZMBrgkg46TuqqkgAwPp`
- Proposer: `proPaC9tVZEsmgDtNhx15e7nSpoojtPD3H9h4GqSqB2`
- Autocrat version: 0.3
- Completed: 2025-01-18
- Ended: 2025-01-18
- Proposal completed but marked as null-result with no outcome explanation in source data
- No market trading activity data available from the proposal interface
- Minimal extractable claims due to lack of outcome and market data