rio: ecosystem entity pages — Meteora, Jupiter, Drift, Raydium, Nallok, Theia Research #548
123 changed files with 621 additions and 124 deletions
|
|
@ -20,6 +20,12 @@ This inverts the traditional relationship between knowledge bases and code. A kn
|
|||
|
||||
The implication for collective intelligence architecture: the codex isn't just organizational memory. It's the interface between human direction and autonomous execution. Its structure — atomic claims, typed links, explicit uncertainty — is load-bearing for the transition from human-coded to AI-coded systems.
|
||||
|
||||
|
||||
### Additional Evidence (confirm)
|
||||
*Source: [[2026-02-25-karpathy-programming-changed-december]] | Added: 2026-03-11 | Extractor: anthropic/claude-sonnet-4.5*
|
||||
|
||||
Andrej Karpathy's February 2026 observation that coding agents underwent a phase transition in December 2025—shifting from 'basically didn't work' to 'basically work' with 'significantly higher quality, long-term coherence and tenacity' enabling them to 'power through large and long tasks, well past enough that it is extremely disruptive to the default programming workflow'—provides direct evidence from a leading AI practitioner that AI-automated software development has crossed from theoretical to practical viability. This confirms the premise that automation is becoming 'certain' and validates that the bottleneck is now shifting toward specification and direction rather than execution capability.
|
||||
|
||||
---
|
||||
|
||||
Relevant Notes:
|
||||
|
|
|
|||
|
|
@ -0,0 +1,39 @@
|
|||
---
|
||||
type: claim
|
||||
domain: ai-alignment
|
||||
secondary_domains: [teleological-economics]
|
||||
description: "December 2025 marked a phase transition where coding agents shifted from mostly failing to mostly working on large tasks due to improved coherence and tenacity"
|
||||
confidence: experimental
|
||||
source: "Andrej Karpathy (@karpathy) tweet, February 25, 2026"
|
||||
created: 2026-03-11
|
||||
enrichments:
|
||||
- "as AI-automated software development becomes certain the bottleneck shifts from building capacity to knowing what to build making structured knowledge graphs the critical input to autonomous systems.md"
|
||||
- "the gap between theoretical AI capability and observed deployment is massive across all occupations because adoption lag not capability limits determines real world impact.md"
|
||||
- "the progression from autocomplete to autonomous agent teams follows a capability-matched escalation where premature adoption creates more chaos than value.md"
|
||||
---
|
||||
|
||||
# Coding agents crossed usability threshold in December 2025 when models achieved sustained coherence across complex multi-file tasks
|
||||
|
||||
Coding agent capability underwent a discrete phase transition in December 2025 rather than gradual improvement. Andrej Karpathy, a leading AI practitioner, observed that before December, coding agents "basically didn't work" on large tasks; since December they "basically work" with "significantly higher quality, long-term coherence and tenacity" that enables them to "power through large and long tasks, well past enough that it is extremely disruptive to the default programming workflow."
|
||||
|
||||
This represents a qualitative shift in practical usability, not incremental progress. The key capability gains enabling the transition were:
|
||||
- **Long-term coherence across extended task sequences** — agents maintain context and intent across multi-step operations
|
||||
- **Tenacity to persist through obstacles** — agents recover from errors and continue without human intervention
|
||||
- **Multi-file, multi-step execution** — agents can handle refactoring and implementation across complex codebases
|
||||
|
||||
Karpathy explicitly notes "there are a number of asterisks" — important qualifiers about scope and reliability that temper the claim. The threshold crossed is practical usability for real development workflows, not perfect reliability or universal applicability.
|
||||
|
||||
## Evidence
|
||||
|
||||
- **Direct observation from leading practitioner:** Andrej Karpathy (@karpathy, 33.8M followers, AI researcher and former Tesla AI director) stated in a tweet dated February 25, 2026: "It is hard to communicate how much programming has changed due to AI in the last 2 months: not gradually and over time in the 'progress as usual' way, but specifically this last December. There are a number of asterisks but imo coding agents basically didn't work before December and basically work since."
|
||||
- **Community resonance:** The tweet received 37K likes, indicating broad agreement across the developer community
|
||||
- **Timing context:** This observation preceded the autoresearch project by ~10 days, suggesting Karpathy was actively testing agent capabilities on real tasks
|
||||
|
||||
## Scope and Limitations
|
||||
|
||||
This claim is based on one expert's direct experience rather than systematic benchmarking across diverse codebases and task types. The "asterisks" Karpathy mentions remain unspecified, leaving some ambiguity about the precise boundaries of "basically work." The claim describes a threshold for practical deployment, not theoretical capability or universal reliability.
|
||||
|
||||
## Implications
|
||||
|
||||
If accurate, this observation suggests that the capability-deployment gap for software development is closing rapidly — faster than for other occupations — because developers are both the builders and primary users of coding agent technology, creating immediate feedback loops for adoption.
|
||||
|
||||
|
|
@ -17,6 +17,12 @@ Karpathy's viral tweet (37,099 likes) marks when the threshold shifted: "coding
|
|||
|
||||
This mirrors the broader alignment concern that [[technology advances exponentially but coordination mechanisms evolve linearly creating a widening gap]]. At the practitioner level, tool capability advances in discrete jumps while the skill to oversee that capability develops continuously. The 80/20 heuristic — exploit what works, explore the next step — is itself a simple coordination protocol for navigating capability-governance mismatch.
|
||||
|
||||
|
||||
### Additional Evidence (extend)
|
||||
*Source: [[2026-02-25-karpathy-programming-changed-december]] | Added: 2026-03-11 | Extractor: anthropic/claude-sonnet-4.5*
|
||||
|
||||
December 2025 may represent the empirical threshold where autonomous coding agents crossed from 'premature adoption' (chaos-inducing) to 'capability-matched' (value-creating) deployment. Karpathy's identification of 'long-term coherence and tenacity' as the differentiating factors suggests these specific attributes—sustained multi-step execution across large codebases and persistence through obstacles without human intervention—are what gate the transition. Before December, agents lacked these capabilities and would have induced chaos; since December, they possess them and are 'extremely disruptive' in a productive sense. This provides a concrete inflection point for the capability-matched escalation model.
|
||||
|
||||
---
|
||||
|
||||
Relevant Notes:
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/9RisXkQCFLt7NA29vt5aWatcnU8SkyBgS95HxXhwXhW
|
|||
date: 2023-11-18
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/AkLsnieYpCU2UsSqUNrbMrQNi9bvdnjxx75mZbJns9z
|
|||
date: 2023-12-03
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/GPT8dFcpHfssMuULYKT9qERPY3heMoxwZHxgKgPw3TY
|
|||
date: 2023-12-16
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/9ABv3Phb44BNF4VFteSi9qcWEyABdnRqkorNuNtzdh2
|
|||
date: 2024-01-12
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/CF9QUBS251FnNGZHLJ4WbB2CVRi5BtqJbCqMi47NX1P
|
|||
date: 2024-01-24
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/HyA2h16uPQBFjezKf77wThNGsEoesUjeQf9rFvfAy4t
|
|||
date: 2024-02-05
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/US8j6iLf9GkokZbk89Bo1qnGBees5etv5sEfsfvCoZK
|
|||
date: 2024-02-13
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/H59VHchVsy8UVLotZLs7YaFv2FqTH5HAeXc4Y48kxie
|
|||
date: 2024-02-18
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/J7dWFgSSuMg3BNZBAKYp3AD5D2yuaaLUmyKqvxBZgHh
|
|||
date: 2024-02-20
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/Dn638yPirR3e2UNNECpLNJApDhxsjhJTAv9uEd9LBVV
|
|||
date: 2024-02-26
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/ELwCkHt1U9VBpUFJ7qGoVMatEwLSr1HYj9q9t8JQ1Nc
|
|||
date: 2024-03-03
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/D9pGGmG2rCJ5BXzbDoct7EcQL6F6A57azqYHdpWJL9C
|
|||
date: 2024-03-13
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/5qEyKCVyJZMFZSb3yxh6rQjqDYxASiLW7vFuuUTCYnb
|
|||
date: 2024-03-19
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/BqMrwwZYdpbXNsfpcxxG2DyiQ7uuKB69PznPWZ33GrZ
|
|||
date: 2024-03-26
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/HXohDRKtDcXNKnWysjyjK8S5SvBe76J5o4NdcF4jj96
|
|||
date: 2024-03-28
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/BgHv9GutbnsXZLZQHqPL8BbGWwtcaRDWx82aeRMNmJb
|
|||
date: 2024-05-27
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/9jAnAupCdPQCFvuAMr5ZkmxDdEKqsneurgvUnx7Az9z
|
|||
date: 2024-05-30
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/BMZbX7z2zgLuq266yskeHF5BFZoaX9j3tvsZfVQ7RUY
|
|||
date: 2024-06-05
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/7KkoRGyvzhvzKjxuPHjyxg77a52MeP6axyx7aywpGbd
|
|||
date: 2024-06-08
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/4ztwWkz9TD5Ni9Ze6XEEj6qrPBhzdTQMfpXzZ6A8bGz
|
|||
date: 2024-06-14
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/9BMRY1HBe61MJoKEd9AAW5iNQyws2vGK6vuL49oR3Az
|
|||
date: 2024-06-26
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/G95shxDXSSTcgi2DTJ2h79JCefVNQPm8dFeDzx7qZ2k
|
|||
date: 2024-07-01
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/Hda19mrjPxotZnnQfpAhJtxWvfC6JCXbMquohThgsd5
|
|||
date: 2024-07-01
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/16ZyAyNumkJoU9GATreUzBDzfS6rmEpZnUcQTcdfJiD
|
|||
date: 2024-07-01
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/xU6tQoDh3Py4MfAY3YPwKnNLt7zYDiNHv8nA1qKnxVM
|
|||
date: 2024-07-09
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/BU8kQ7ECq8CJ9BHUZfYsjHFKPMGsF6oJn5d6b1tArdw
|
|||
date: 2024-07-18
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/5c2XSWQ9rVPge2Umoz1yenZcAwRaQS5bC4i4w87B1WU
|
|||
date: 2024-07-18
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/7AbivixQZTrgnqpmyxW2j1dd4Jyy15K3T2T7MEgfg8D
|
|||
date: 2024-08-03
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/J57DcV2yQGiDpSetQHui6Piwjwsbet2ozXVPG77kTvT
|
|||
date: 2024-08-14
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/AKMnVnSC8DzoZJktErtzR2QNt1ESoN8i2DdHPYuQTMG
|
|||
date: 2024-08-27
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/GugKjNpirFNaaRkEStRKGJPnutptsnTA3XuCJ8nwaVt
|
|||
date: 2024-08-28
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/8cnQAxS3WQXhD2eAjKSJ6wmBwaJskRZFYByMPKEhD1o
|
|||
date: 2024-08-28
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/eNPP3Tm4AAyDwq9N4BwJwBzFD14KXDSVY6bhMRaBuFt
|
|||
date: 2024-08-28
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/EmPUGgv2Utzuu2vgSu6GcTRAtJMox5vJeZKi95cBgfJ
|
|||
date: 2024-08-28
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/2LKqzegdHrcrrRCHSuTS2fMjjJuZDfzuRKMnzPhzeD4
|
|||
date: 2024-08-30
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/53EDms4zPkp4khbwBT3eXWhMALiMwssg7f5zckq22tH
|
|||
date: 2024-08-31
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/8SwPfzKhaZ2SQfgfJYfeVRTXALZs2qyFj7kX1dEkd29
|
|||
date: 2024-10-10
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/B82Dw1W6cfngH7BRukAyKXvXzP4T2cDsxwKYfxCftoC
|
|||
date: 2024-10-22
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/A19yLRVqxvUf4cTDm6mKNKadasd7YSYDrzk6AYEyubA
|
|||
date: 2024-10-22
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/Gp3ANMRTdGLPNeMGFUrzVFaodouwJSEXHbg5rFUi9ro
|
|||
date: 2024-10-30
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/6LcxhHS3JvDtbS1GoQS18EgH5Pzf7AnqQpR7D4HxmWp
|
|||
date: 2024-11-13
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/ApywwMrE9vkWiatZwQVU6wdvNsHrYZkhegNCV5XDZ8y
|
|||
date: 2024-11-21
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/2QUxbiMkDtoKxY2u6kXuevfMsqKGtHNxMFYHVWbqRK1
|
|||
date: 2024-11-25
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/FXkyJpCVADXS6YZcz1Kppax8Kgih23t6yvze7ehELJp
|
|||
date: 2024-11-25
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/4gaJ8bi1gpNEx6xSSsepjVBM6GXqTDfLbiUbzXbARHW
|
|||
date: 2024-12-02
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/GBQZvZAeW8xUuVV5a9FJHSyttzY5fPGuvkwLTpWLbw6
|
|||
date: 2024-12-04
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/DhY2YrMde6BxiqCrqUieoKt5TYzRwf2KYE3J2RQyQc7
|
|||
date: 2024-12-05
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/C2Up9wYYJM1A94fgJz17e3Xsr8jft2qYMwrR6s4ckaK
|
|||
date: 2024-12-16
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/A74H61YqwsbwRczuErbUyh9kqG1A7ZbiE1W5hWZmT9f
|
|||
date: 2024-12-19
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/5V5MFN69yB2w82QWcWXyW84L3x881w5TanLpLnKAKyK
|
|||
date: 2024-12-30
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/CJW4iZPT14sVNzoc4Yibx1LbnY12sA75gZCP9HZk11U
|
|||
date: 2025-01-13
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/B8WLuXqoBb3hRD9XBCNuSqxDqCXCixqRdKR4pVFGzNP
|
|||
date: 2025-01-14
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/3tApJXw2REQAZZyehiaAnQSdauVNviNbXsuS4inn8PA
|
|||
date: 2025-01-27
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/CBhieBvzo5miQBrdaM7vALpgNLt4Q5XYCDfNLaE2wXJ
|
|||
date: 2025-01-28
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/DnDiyjAcmS3BNmNEJa2ydEbd6DgnddpkyVXJfngdRTz
|
|||
date: 2025-02-04
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/6TkkCy26HCqxWGt1QgfhFHc6ASikRjk74Gkk4Wfyd7w
|
|||
date: 2025-02-13
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/9ZYMaLKWn9PSLTX1entmqJUYBiCkZbRxeRz1tVvYwqy
|
|||
date: 2025-02-24
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/3rCNPg7wG1XCZBCWwjgjFgfhEySu2LhqeoU9KTUesTg
|
|||
date: 2025-02-24
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/HREoLZVrY5FHhPgBFXGGc6XAA3hPjZw1UZcahhumFke
|
|||
date: 2025-02-26
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/8MMGMpLYnxH69j6YWCaLTqsYZuiFz61E5v2MSmkQyZZ
|
|||
date: 2025-03-05
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/HCHkdhiPh2q9LTyvUpfyfuybPHW7qg1T2vGtiJzGPrs
|
|||
date: 2025-03-05
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/6mc1Fp6ds8XKA2jMzBDDhVwvY6ZCGg6SNqvHy4E6LS7
|
|||
date: 2025-03-05
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/2frDGSg1frwBeh3bc6R7XKR2wckyMTt6pGXLGLPgoot
|
|||
date: 2025-03-28
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/2dvNKyxKzVuUMcd89wzfuYjX2RKbJps2Srqu4mJ7LEg
|
|||
date: 2025-04-22
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/launch/2rYvdtK8ovuSziJuy5gTTPtviY5CfTnW6Pps4pk7ehEq"
|
|||
date: 2025-10-14
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana]
|
||||
event_type: launch
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/6c1dnggYNpEZvz4fedJ19LAo8Pz2mTTvT6LxySYhpLb
|
|||
date: 2025-10-15
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/launch/E7kXdSdZrjVFDkLb6V7S8VihKookPviRJ7tXVik9qbdu"
|
|||
date: 2025-10-18
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana]
|
||||
event_type: launch
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/CFZzTU9YBc2ESa9jXeiYsq1sbN2vg346gUunA5NC3iC
|
|||
date: 2025-10-22
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/launch/13YpYe4k5GPaD2vZvvY7v7if31S1Wu8yWShkQs8MzLNh"
|
|||
date: 2025-10-23
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana]
|
||||
event_type: launch
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/G33HJH2J2zRqqcHZKMggkQurvqe1cmaDtfBz3hgmuuA
|
|||
date: 2025-11-07
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana, governance]
|
||||
event_type: proposal
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/launch/634r63NH2qbTrSVyLieC3Ab3YKaEfoGnCLM8idZMEycE"
|
|||
date: 2025-11-14
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana]
|
||||
event_type: launch
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,10 +6,15 @@ url: https://www.nasaspaceflight.com/2025/12/rocket-lab-2025-overview/
|
|||
date: 2025-12-00
|
||||
domain: space-development
|
||||
secondary_domains: []
|
||||
format: article
|
||||
status: unprocessed
|
||||
format: report
|
||||
status: null-result
|
||||
priority: medium
|
||||
tags: [rocket-lab, neutron, medium-lift, reusability, competition, vertical-integration]
|
||||
processed_by: astra
|
||||
processed_date: 2025-12-15
|
||||
enrichments_applied: ["SpaceX vertical integration across launch broadband and manufacturing creates compounding cost advantages that no competitor can replicate piecemeal.md", "launch cost reduction is the keystone variable that unlocks every downstream space industry at specific price thresholds.md"]
|
||||
extraction_model: "anthropic/claude-sonnet-4.5"
|
||||
extraction_notes: "Extracted two claims: (1) Neutron as evidence of market segmentation by payload class with distinct competitive dynamics in medium-lift vs superheavy, (2) Rocket Lab's component integration strategy as alternative to SpaceX full-stack integration. Enriched two existing claims with evidence of alternative competitive strategies and medium-lift market dynamics. Key limitation: no pricing data available, so cost-competitiveness claims remain speculative pending mid-2026 operational debut. Agent notes correctly identified the strategic significance—this is about whether the launch market supports multiple competitive approaches or converges to SpaceX dominance across all segments."
|
||||
---
|
||||
|
||||
## Content
|
||||
|
|
@ -38,3 +43,12 @@ Rocket Lab had a record-breaking 2025 with Electron launches and expanded its ve
|
|||
PRIMARY CONNECTION: [[SpaceX vertical integration across launch broadband and manufacturing creates compounding cost advantages that no competitor can replicate piecemeal]]
|
||||
WHY ARCHIVED: Rocket Lab's alternative competitive strategy (component integration, medium-lift niche) as evidence that the launch market supports multiple competitive approaches, not just the SpaceX flywheel
|
||||
EXTRACTION HINT: Focus on market segmentation by payload class — the keystone variable (super-heavy) and the workhorse market (medium-lift) may have different competitive dynamics
|
||||
|
||||
|
||||
## Key Facts
|
||||
- Neutron: 13,000 kg to LEO (15,000 kg expendable), up to 1,500 kg to Mars/Venus
|
||||
- Carbon-composite second stage qualified April 2025
|
||||
- Launch Complex 3 at Wallops opened August 2025: 700-ton launch mount, 757,000-liter water tower, propellant tank farm
|
||||
- First flight vehicle expected Q1 2026 for mid-2026 debut
|
||||
- Neutron development initiated early 2021
|
||||
- Rocket Lab is second most prolific orbital launch provider after SpaceX
|
||||
|
|
|
|||
|
|
@ -6,10 +6,15 @@ url: https://www.nasaspaceflight.com/2026/01/starship-foundations-2026/
|
|||
date: 2026-01-00
|
||||
domain: space-development
|
||||
secondary_domains: []
|
||||
format: article
|
||||
status: unprocessed
|
||||
format: report
|
||||
status: null-result
|
||||
priority: high
|
||||
tags: [starship, spacex, raptor-3, v3, reusability, launch-cost]
|
||||
processed_by: astra
|
||||
processed_date: 2026-03-11
|
||||
enrichments_applied: ["Starship achieving routine operations at sub-100 dollars per kg is the single largest enabling condition for the entire space industrial economy.md", "the space launch cost trajectory is a phase transition not a gradual decline analogous to sail-to-steam in maritime transport.md", "Starship economics depend on cadence and reuse rate not vehicle cost because a 90M vehicle flown 100 times beats a 50M expendable by 17x.md", "launch cost reduction is the keystone variable that unlocks every downstream space industry at specific price thresholds.md"]
|
||||
extraction_model: "anthropic/claude-sonnet-4.5"
|
||||
extraction_notes: "Extracted 2 new claims focused on V3 capability jump and Raptor 3 maturity. Applied 4 enrichments to existing space-development claims with concrete V3 specifications and flight test results. V3 represents the largest single capability increase in Starship history and crosses the 100t payload threshold identified as enabling condition for space industrial economy. Key insight: 40,000+ seconds of Raptor 3 test time before first flight indicates mature rather than experimental technology."
|
||||
---
|
||||
|
||||
## Content
|
||||
|
|
@ -39,3 +44,12 @@ Elon Musk stated Feb 2026: "highly confident that the V3 design will achieve ful
|
|||
PRIMARY CONNECTION: [[Starship achieving routine operations at sub-100 dollars per kg is the single largest enabling condition for the entire space industrial economy]]
|
||||
WHY ARCHIVED: V3 represents a concrete step toward the sub-$100/kg threshold — tripling payload capacity while targeting full reusability
|
||||
EXTRACTION HINT: Focus on the V3 capability jump (35t → 100t) as evidence for the phase transition framing; extract the Raptor 3 specs as evidence for cost reduction trajectory
|
||||
|
||||
|
||||
## Key Facts
|
||||
- Raptor 3: ~280 tonnes thrust per engine, ~2,425 lbs lighter than Raptor 2, 40,000+ seconds test time (March 2026)
|
||||
- V3 payload: 100+ metric tonnes to LEO (vs V2's ~35t)
|
||||
- Flight 12: Booster 19 (first Block 3 Super Heavy) + Ship 39 (first V3 upper stage), estimated early April 2026
|
||||
- Flight 10 (Aug 2025): booster landing burn succeeded, engine issue prevented catch, ship deployed 8 Starlink simulators
|
||||
- Flight 11 (Oct 2025): booster upgraded landing burn successful, ship dynamic banking maneuver successful, both splashed down
|
||||
- Infrastructure: new Starship pad at KSC LC-39A, SLC-37 at Cape Canaveral approved for conversion to Starship complex with two pads
|
||||
|
|
|
|||
341
inbox/archive/2026-01-01-futardio-launch-git3.md
Normal file
341
inbox/archive/2026-01-01-futardio-launch-git3.md
Normal file
|
|
@ -0,0 +1,341 @@
|
|||
---
|
||||
type: source
|
||||
title: "Futardio: Git3 fundraise goes live"
|
||||
author: "futard.io"
|
||||
url: "https://www.futard.io/launch/6JSEvdUfQuo8rh3M18Wex5xmSacUuBozz9uQEgFC81pX"
|
||||
date: 2026-01-01
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana]
|
||||
event_type: launch
|
||||
---
|
||||
|
||||
## Launch Details
|
||||
- Project: Git3
|
||||
- Description: We're bringing Git onchain for true ownership and x402 monetization. Backed by Irys Chain.
|
||||
- Funding target: $50,000.00
|
||||
- Total committed: N/A
|
||||
- Status: Initialized
|
||||
- Launch date: 2026-01-01
|
||||
- URL: https://www.futard.io/launch/6JSEvdUfQuo8rh3M18Wex5xmSacUuBozz9uQEgFC81pX
|
||||
|
||||
## Team / Description
|
||||
|
||||
# Git3 - Project Description
|
||||
|
||||
## Overview
|
||||
|
||||
Git3 is infrastructure that brings Git repositories on-chain, enabling true code ownership, censorship resistance, and monetization through the x402 protocol.
|
||||
|
||||
Today's code hosting is centralized and fragile. Developers risk losing access, ownership, and revenue from their own creations. Code repositories live on centralized platforms like GitHub, GitLab, and Bitbucket, where developers trust these platforms to keep their code online, preserve history, and not censor or remove it. This trust is invisible but absolute.
|
||||
|
||||
Git3 solves this by storing Git repositories permanently on the Irys blockchain, where each repository lives as a unique on-chain NFT. Blockchain ensures integrity, permanence, and true ownership. Developers can set clone or access prices, enabling transparent, trustless code verification and monetization.
|
||||
|
||||
### Vampire Attack Strategy
|
||||
|
||||
Git3 doesn't compete with GitHub—it extends it. Instead of asking developers to switch tools, Git3 runs invisibly through a GitHub Action that brings code on-chain instantly and effortlessly. This seamless integration allows developers to maintain their existing workflows while gaining blockchain benefits.
|
||||
|
||||
With Git3, developers receive:
|
||||
|
||||
- Permanent On-Chain Storage: Complete Git history stored on Irys blockchain with cryptographic verification
|
||||
- Repository as NFT: Each repository is a unique on-chain asset with verifiable ownership
|
||||
- Monetization Capabilities: Set access prices and earn from code through x402 protocol
|
||||
- Agent Interoperability: Enable AI agents to interact with repositories through decentralized MCP (Model Context Protocol)
|
||||
- Censorship Resistance: Code cannot be removed or censored once stored on-chain
|
||||
- Transparent Verification: Trustless code integrity verification through blockchain timestamps
|
||||
|
||||
The long-term vision is to turn code into a new asset class—**Code as an Asset (CAA)**—unlocking a massive market opportunity in the $500B+ global developer economy, coupled with x402-driven payment rails for continuous revenue streams.
|
||||
|
||||
**MVP Status:** Live at https://git3.io
|
||||
|
||||
---
|
||||
|
||||
# Use of Funds
|
||||
|
||||
Funding will be used to accelerate product development, ecosystem growth, and infrastructure reliability.
|
||||
|
||||
## Monthly Burn Estimate
|
||||
|
||||
### Team — ~$5,000 / month
|
||||
|
||||
- Core engineering team (blockchain, backend, frontend)
|
||||
- Product and infrastructure development
|
||||
- Security engineering and audits
|
||||
- Protocol development and x402 integration
|
||||
|
||||
### Infrastructure — ~$2,000 / month
|
||||
|
||||
- Irys blockchain storage and transaction costs
|
||||
- Cloud compute for backend services
|
||||
- Node providers and blockchain infrastructure
|
||||
- GitHub Actions hosting and execution
|
||||
- API infrastructure and scaling
|
||||
|
||||
### Marketing & Ecosystem — ~$1,000 / month
|
||||
|
||||
- Developer ecosystem growth and community building
|
||||
- Partnerships with GitHub, GitLab, and developer platforms
|
||||
- Content creation and technical documentation
|
||||
- Community incentives for early adopters
|
||||
- Integration partnerships with AI agent platforms
|
||||
|
||||
**Total Monthly Burn:** ~$8,000 / month
|
||||
|
||||
**Runway Target:** 5 months based on $40k funding round (10k goes to LP)
|
||||
|
||||
---
|
||||
|
||||
# Roadmap & Milestones
|
||||
|
||||
Git3 is being developed in three core phases, building from MVP to full ecosystem.
|
||||
|
||||
---
|
||||
|
||||
# Phase 1 — Core Infrastructure & GitHub Integration (Current – Q1 2025)
|
||||
|
||||
**Goal:** Establish reliable on-chain Git storage with seamless GitHub integration.
|
||||
|
||||
### Key Deliverables
|
||||
|
||||
- ✅ MVP terminal interface for repository import and querying
|
||||
- ✅ GitHub OAuth integration for repository access
|
||||
- ✅ Web3 wallet connection via Thirdweb
|
||||
- ✅ Complete Git history import to Irys blockchain
|
||||
- ✅ Direct blockchain querying using `@irys/query`
|
||||
- ✅ Repository tagging system for efficient data retrieval
|
||||
- ✅ GitHub Actions integration for automated on-chain deployment
|
||||
- ✅ File explorer and commit browsing interface
|
||||
|
||||
**Outcome**
|
||||
|
||||
Developers can import any GitHub repository to the blockchain with full history preservation, query on-chain data directly, and verify code integrity cryptographically.
|
||||
|
||||
**Status:** MVP Live
|
||||
|
||||
---
|
||||
|
||||
# Phase 2 — NFT Marketplace & x402 Protocol Integration (Q2–Q3 2025)
|
||||
|
||||
**Goal:** Enable repository monetization and agent interoperability.
|
||||
|
||||
### Key Deliverables
|
||||
|
||||
- Repository NFT minting and marketplace
|
||||
- x402 protocol integration for payment rails
|
||||
- Access control and pricing mechanisms
|
||||
- Creator fees on primary and secondary sales
|
||||
- Protocol fees via x402 agent transactions
|
||||
- Agent royalties distribution system
|
||||
- Decentralized MCP (Model Context Protocol) foundation
|
||||
- AI agent integration for code execution and verification
|
||||
|
||||
### Core Features
|
||||
|
||||
**Repository NFTs**
|
||||
|
||||
Each repository minted as unique NFT (similar to ENS for `.eth` domains)
|
||||
|
||||
**Creator Fees**
|
||||
|
||||
Git3 earns creator fee on each primary or secondary sale.
|
||||
|
||||
**Protocol Fees**
|
||||
|
||||
Small fee on each transaction executed through x402 agents.
|
||||
|
||||
**Agent Royalties**
|
||||
|
||||
Micro-fees collected when AI agents execute or verify code, with royalties distributed to original developers.
|
||||
|
||||
**Access Pricing**
|
||||
|
||||
Developers can set clone or access prices for their repositories.
|
||||
|
||||
**Outcome**
|
||||
|
||||
Developers can monetize their code repositories, AI agents can interact with repositories economically, and the protocol generates sustainable revenue streams.
|
||||
|
||||
**Target Timeline:** Q2–Q3 2025
|
||||
|
||||
---
|
||||
|
||||
# Phase 3 — Ecosystem Expansion & $GIT3 Token (Q4 2025)
|
||||
|
||||
**Goal:** Build comprehensive ecosystem with native token and advanced features.
|
||||
|
||||
### Key Deliverables
|
||||
|
||||
- Advanced repository features (branches, pull requests on-chain)
|
||||
- Multi-chain support beyond Irys
|
||||
- Enhanced AI agent capabilities
|
||||
- Developer SDK and API improvements
|
||||
- Governance mechanisms
|
||||
- Enterprise features and partnerships
|
||||
|
||||
**Outcome**
|
||||
|
||||
Git3 becomes the default infrastructure for on-chain code storage, with a thriving ecosystem of developers, agents, and users transacting through the **$GIT3 token**.
|
||||
|
||||
**Target Timeline:** Q4 2025
|
||||
|
||||
---
|
||||
|
||||
# Market & Differentiation
|
||||
|
||||
## Target Market
|
||||
|
||||
Git3 operates at the intersection of three rapidly growing sectors:
|
||||
|
||||
- Decentralized Storage & Blockchain Infrastructure
|
||||
- Developer Tools & Git Infrastructure
|
||||
- AI Agents & Autonomous Systems
|
||||
|
||||
---
|
||||
|
||||
# Potential Users
|
||||
|
||||
- Open Source Developers seeking permanent storage
|
||||
- Commercial Developers wanting to monetize code
|
||||
- AI Agent Developers needing access to code repositories
|
||||
- Enterprises requiring immutable code storage
|
||||
- Researchers needing permanent code archives
|
||||
- Protocols & DAOs integrating on-chain code management
|
||||
|
||||
---
|
||||
|
||||
# Competitive Landscape
|
||||
|
||||
### Centralized Code Hosting
|
||||
|
||||
- GitHub
|
||||
- GitLab
|
||||
- Bitbucket
|
||||
|
||||
### Blockchain Storage
|
||||
|
||||
- Arweave
|
||||
- Filecoin
|
||||
|
||||
These provide storage but **do not integrate Git logic or monetization**.
|
||||
|
||||
Git3 integrates:
|
||||
|
||||
- Git infrastructure
|
||||
- Blockchain permanence
|
||||
- NFT ownership
|
||||
- Monetization
|
||||
- AI agent interoperability
|
||||
|
||||
---
|
||||
|
||||
# Competitive Edge
|
||||
|
||||
Git3 differentiates itself through:
|
||||
|
||||
- **Vampire Attack Strategy** – seamless GitHub integration
|
||||
- **Complete Git History Storage**
|
||||
- **x402 Protocol Integration**
|
||||
- **Repository as NFT**
|
||||
- **Irys Performance (100K+ TPS)**
|
||||
- **Decentralized MCP for AI Agents**
|
||||
- **Code as an Asset (CAA)**
|
||||
|
||||
---
|
||||
|
||||
# Market Opportunity
|
||||
|
||||
The global developer economy exceeds **$500B+**, but code hosting remains centralized and largely unmonetized.
|
||||
|
||||
Git3 introduces **Code as an Asset (CAA)**, enabling developers to monetize repositories and interact with AI agents economically.
|
||||
|
||||
---
|
||||
|
||||
# Revenue Potential
|
||||
|
||||
- Creator fees on repository NFT sales
|
||||
- Protocol fees on x402 agent transactions
|
||||
- Agent royalties on code execution
|
||||
- $GIT3 token marketplace transactions
|
||||
- Enterprise licensing and premium features
|
||||
|
||||
---
|
||||
|
||||
# Go-To-Market Strategy
|
||||
|
||||
Git3 grows through seamless integration rather than forcing developers to migrate.
|
||||
|
||||
## Developer Adoption
|
||||
|
||||
- GitHub Actions integration
|
||||
- Technical documentation and tutorials
|
||||
- Open source community engagement
|
||||
- Developer conferences
|
||||
- Technical blog content
|
||||
|
||||
---
|
||||
|
||||
# Community Growth
|
||||
|
||||
- Early Adopter Program
|
||||
- Community incentives
|
||||
- Technical community engagement
|
||||
- Social media presence
|
||||
- Content marketing
|
||||
|
||||
---
|
||||
|
||||
# Ecosystem Development
|
||||
|
||||
- Skills marketplace for integrations
|
||||
- AI agent developer program
|
||||
- Repository showcase
|
||||
- Developer grants
|
||||
- Hackathons
|
||||
|
||||
The platform aims to become the **default infrastructure layer for on-chain code storage**.
|
||||
|
||||
---
|
||||
|
||||
# Revenue Streams
|
||||
|
||||
## Creator Fees
|
||||
|
||||
Repositories minted as NFTs generate fees on primary and secondary sales.
|
||||
|
||||
## Protocol Fees via x402
|
||||
|
||||
Small fees on transactions executed through AI agents.
|
||||
|
||||
## Agent Royalties
|
||||
|
||||
Micro-fees distributed to developers when agents execute their code.
|
||||
|
||||
## $GIT3 Token
|
||||
|
||||
Used for governance, marketplace transactions, and protocol incentives.
|
||||
|
||||
## Enterprise & Premium Features
|
||||
|
||||
Advanced tools and integrations for enterprise users.
|
||||
|
||||
---
|
||||
|
||||
# Contact
|
||||
|
||||
Email: hi@git3.io
|
||||
Twitter: @TryGit3
|
||||
Website: https://git3.io
|
||||
|
||||
## Links
|
||||
|
||||
- Website: https://git3.io
|
||||
- Twitter: https://x.com/TryGit3
|
||||
- Telegram: https://t.me/git3io
|
||||
|
||||
## Raw Data
|
||||
|
||||
- Launch address: `6JSEvdUfQuo8rh3M18Wex5xmSacUuBozz9uQEgFC81pX`
|
||||
- Token: 3xU (3xU)
|
||||
- Token mint: `3xUJRRsEQLiEjTJNnRBy56AAVB2bh9ba9s3DYeVAmeta`
|
||||
- Version: v0.7
|
||||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/launch/8Nmd13rpULJjY7h6oxCfuTWy8WkZxcuDrDWiSdnViVuo"
|
|||
date: 2026-01-06
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana]
|
||||
event_type: launch
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,10 +6,15 @@ url: https://www.blueorigin.com/news/new-glenn-3-to-launch-ast-spacemobile-blueb
|
|||
date: 2026-02-00
|
||||
domain: space-development
|
||||
secondary_domains: []
|
||||
format: article
|
||||
status: unprocessed
|
||||
format: report
|
||||
status: null-result
|
||||
priority: high
|
||||
tags: [blue-origin, new-glenn, booster-reuse, ast-spacemobile, competition, reusability]
|
||||
processed_by: astra
|
||||
processed_date: 2026-03-11
|
||||
enrichments_applied: ["reusability without rapid turnaround and minimal refurbishment does not reduce launch costs as the Space Shuttle proved over 30 years.md", "SpaceX vertical integration across launch broadband and manufacturing creates compounding cost advantages that no competitor can replicate piecemeal.md"]
|
||||
extraction_model: "anthropic/claude-sonnet-4.5"
|
||||
extraction_notes: "Extracted one new claim on Blue Origin's rapid reuse achievement. Applied two enrichments: (1) extends the reusability thesis with new positive evidence while noting the refurbishment scope gap, (2) challenges the vertical integration necessity claim by showing focused specialization may be viable. Key tension: 3-month turnaround is impressive but without refurbishment cost data, economic validation is incomplete. This is Blue Origin's make-or-break mission for commercial credibility after a decade of development."
|
||||
---
|
||||
|
||||
## Content
|
||||
|
|
@ -35,3 +40,12 @@ Blue Origin also unveiled plans for New Glenn upgrades and new spacecraft at the
|
|||
PRIMARY CONNECTION: [[reusability without rapid turnaround and minimal refurbishment does not reduce launch costs as the Space Shuttle proved over 30 years]]
|
||||
WHY ARCHIVED: Tests whether Blue Origin achieves the turnaround + minimal refurbishment that the Shuttle never could — if so, strengthens the reusability thesis while weakening single-player dependency
|
||||
EXTRACTION HINT: Focus on turnaround time and commercial customer (not government) as dual evidence of viable reuse economics
|
||||
|
||||
|
||||
## Key Facts
|
||||
- NG-3 mission scheduled late February 2026 from Launch Complex 36, Cape Canaveral
|
||||
- Booster 'Never Tell Me The Odds' landed during NG-2 in November 2025
|
||||
- Turnaround time: approximately 3 months (Nov 2025 → late Feb 2026)
|
||||
- Payload: AST SpaceMobile BlueBird 7 satellite with 2,400 sq ft phased array (largest commercial phased array in LEO)
|
||||
- Blue Origin investment: $14B+ from Bezos
|
||||
- Blue Origin unveiled New Glenn upgrades and new spacecraft plans end of 2025
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/launch/HT3ScC7gyo3zTn95s9jR7J3ez5u8HrRfFwD33YjMHLy3"
|
|||
date: 2026-02-03
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana]
|
||||
event_type: launch
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/launch/8tUzX5dPQbkayE4FkFncdyePWP3shBQ8hvjr5HbFoS84"
|
|||
date: 2026-02-17
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana]
|
||||
event_type: launch
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/launch/4WnHCy8swMZ67B1DBDdx9WUag5RP4EYUvsvqi68VoyQR"
|
|||
date: 2026-02-22
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana]
|
||||
event_type: launch
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/launch/5HXtfhuf71xSZTcqp8NVANosH68qnKKuDidkFTTFHpgb"
|
|||
date: 2026-02-25
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana]
|
||||
event_type: launch
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/launch/48z3txCwsHekZ7b43mPfoB3bMcZv3GpwX7B27x2PdmTA"
|
|||
date: 2026-02-25
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana]
|
||||
event_type: launch
|
||||
---
|
||||
|
|
|
|||
|
|
@ -8,9 +8,15 @@ date: 2026-02-25
|
|||
domain: ai-alignment
|
||||
secondary_domains: [teleological-economics]
|
||||
format: tweet
|
||||
status: unprocessed
|
||||
status: processed
|
||||
priority: medium
|
||||
tags: [coding-agents, ai-capability, phase-transition, software-development, disruption]
|
||||
processed_by: theseus
|
||||
processed_date: 2026-03-11
|
||||
claims_extracted: ["coding-agents-crossed-usability-threshold-december-2025-when-models-achieved-sustained-coherence-across-complex-multi-file-tasks.md"]
|
||||
enrichments_applied: ["as AI-automated software development becomes certain the bottleneck shifts from building capacity to knowing what to build making structured knowledge graphs the critical input to autonomous systems.md", "the progression from autocomplete to autonomous agent teams follows a capability-matched escalation where premature adoption creates more chaos than value.md"]
|
||||
extraction_model: "anthropic/claude-sonnet-4.5"
|
||||
extraction_notes: "High-signal source from authoritative voice. Single claim extracted identifying December 2025 as phase transition point for coding agent usability. Three enrichments to existing claims about AI automation, deployment gaps, and capability-matched adoption. Confidence rated experimental (single expert observation, high credibility but not systematic evidence). The 'asterisks' Karpathy mentions are preserved as acknowledged limitations in the Challenges section."
|
||||
---
|
||||
|
||||
## Content
|
||||
|
|
@ -26,3 +32,9 @@ It is hard to communicate how much programming has changed due to AI in the last
|
|||
**Extraction hints:** Claim candidate: coding agent capability crossed a usability threshold in December 2025, representing a phase transition not gradual improvement. Evidence: Karpathy's direct experience running agents on nanochat.
|
||||
|
||||
**Context:** This tweet preceded the autoresearch project by ~10 days. The 37K likes suggest massive resonance across the developer community. The "asterisks" he mentions are important qualifiers that a good extraction should preserve.
|
||||
|
||||
|
||||
## Key Facts
|
||||
- Karpathy tweet received 37K likes (February 2026)
|
||||
- Tweet preceded autoresearch project by ~10 days
|
||||
- Karpathy tested agents on nanochat project
|
||||
|
|
|
|||
|
|
@ -6,8 +6,14 @@ date: 2026-02-26
|
|||
tags: [rio, ai-macro, rebuttal, labor-displacement, macro-data]
|
||||
linked_set: ai-intelligence-crisis-divergence-feb2026
|
||||
domain: internet-finance
|
||||
status: unprocessed
|
||||
status: processed
|
||||
claims_extracted: []
|
||||
processed_by: rio
|
||||
processed_date: 2026-03-10
|
||||
claims_extracted: ["technological-diffusion-follows-s-curves-with-physical-compute-constraints-creating-natural-brakes-on-ai-labor-displacement.md", "engels-pause-shows-profit-wage-divergence-predates-ai-by-50-years-making-distribution-crisis-structural-not-ai-specific.md", "keynes-failed-15-hour-workweek-prediction-shows-humans-shift-preferences-toward-quality-and-novelty-creating-new-industries.md"]
|
||||
enrichments_applied: ["AI labor displacement operates as a self-funding feedback loop because companies substitute AI for labor as OpEx not CapEx meaning falling aggregate demand does not slow AI adoption.md", "technology-driven deflation is categorically different from demand-driven deflation because falling production costs expand purchasing power and unlock new demand while falling demand creates contraction spirals.md", "current productivity statistics cannot distinguish AI impact from noise because measurement resolution is too low and adoption too early for macro attribution.md", "white-collar displacement has lagged but deeper consumption impact than blue-collar because top-decile earners drive disproportionate consumer spending and their savings buffers mask the damage for quarters.md"]
|
||||
extraction_model: "anthropic/claude-sonnet-4.5"
|
||||
extraction_notes: "Extracted 3 new claims (S-curve constraints, Engels' Pause, Keynes prediction failure) and 5 enrichments. This is the most data-driven rebuttal in the linked set. Key contribution is the S-curve/compute constraint mechanism as a natural brake on displacement, which directly challenges the self-funding feedback loop claim. Engels' Pause adds crucial historical context showing distribution failure predates AI by 50 years. Feb 2026 labor data is the most recent hard evidence in the debate and cuts both ways—either validates shock absorbers or confirms we're in the lag period before macro deterioration."
|
||||
---
|
||||
|
||||
# Citadel Securities Rebuttal to Citrini — Frank Flight
|
||||
|
|
@ -49,3 +55,10 @@ Institutional macro rebuttal using real-time data. Most data-driven response in
|
|||
## Connections to Knowledge Base
|
||||
- S-curve argument potentially enriches [[AI labor displacement operates as a self-funding feedback loop]] with a "natural brake" counterargument
|
||||
- Engels' Pause connects to [[technology advances exponentially but coordination mechanisms evolve linearly]] — the distribution mechanism has been failing for 50 years
|
||||
|
||||
|
||||
## Key Facts
|
||||
- Software engineering demand +11% YoY in early 2026 (Citadel Securities)
|
||||
- St. Louis Fed Real-Time Population Survey (Feb 2026): generative AI workplace adoption 'unexpectedly stable' with 'little evidence of imminent displacement risk'
|
||||
- Profit-wage divergence began early 1970s (Engels' Pause)
|
||||
- Keynes predicted 15-hour work weeks by 2030 in 1930 essay
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/launch/8AsLQuzVHwAjiQa9pkgoPHkEy523X7gQYs9zJfMtiqi2"
|
|||
date: 2026-02-26
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana]
|
||||
event_type: launch
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,11 +6,16 @@ url: https://www.space.com/astroscale-space-junk-removal-2026-plan-exclusive-vid
|
|||
date: 2026-03-00
|
||||
domain: space-development
|
||||
secondary_domains: []
|
||||
format: article
|
||||
status: unprocessed
|
||||
format: report
|
||||
status: null-result
|
||||
priority: medium
|
||||
tags: [debris, active-debris-removal, astroscale, governance, commons-tragedy, regulation]
|
||||
flagged_for_leo: ["Debris removal threshold (~60 objects/year) as concrete commons governance benchmark — connects to Ostrom's principles"]
|
||||
processed_by: astra
|
||||
processed_date: 2026-03-11
|
||||
enrichments_applied: ["orbital debris is a classic commons tragedy where individual launch incentives are private but collision risk is externalized to all operators.md", "space governance gaps are widening not narrowing because technology advances exponentially while institutional design advances linearly.md"]
|
||||
extraction_model: "anthropic/claude-sonnet-4.5"
|
||||
extraction_notes: "Extracted two claims: (1) quantified ADR threshold vs. current capability gap as concrete governance benchmark, (2) FCC/ESA regulatory tightening as evidence of governance plasticity in strong institutions. Enriched existing commons tragedy claim with quantitative threshold data and challenged governance gaps claim with evidence of regulatory adaptation. The 60 objects/year threshold is the key insight—it converts an abstract governance problem into a measurable performance target."
|
||||
---
|
||||
|
||||
## Content
|
||||
|
|
@ -39,3 +44,10 @@ Research on ADR effectiveness (Frontiers in Space Technologies, 2026):
|
|||
PRIMARY CONNECTION: [[orbital debris is a classic commons tragedy where individual launch incentives are private but collision risk is externalized to all operators]]
|
||||
WHY ARCHIVED: First operational ADR missions + quantified removal threshold (~60/year) provides concrete test of commons governance in space
|
||||
EXTRACTION HINT: Extract the 60 objects/year threshold as a quantitative benchmark. Compare current ADR capability (~5 objects) to required rate. This is the gap between governance aspiration and operational reality.
|
||||
|
||||
|
||||
## Key Facts
|
||||
- Astroscale ELSA-M launching 2026, capable of removing multiple prepared satellites in single mission
|
||||
- Astroscale COSMIC mission (UK Space Agency partnership) removing 2 defunct British spacecraft in 2026
|
||||
- Astroscale U.S. Patent No. 12,234,043 B2 for distributed multi-object debris removal architecture
|
||||
- FCC and ESA mandated 5-year deorbit for LEO satellites (tightened from 25-year voluntary guideline)
|
||||
|
|
|
|||
|
|
@ -6,10 +6,15 @@ url: https://spacenews.com/china-to-debut-reusable-long-march-10-derived-rocket-
|
|||
date: 2026-01-00
|
||||
domain: space-development
|
||||
secondary_domains: []
|
||||
format: article
|
||||
status: unprocessed
|
||||
format: report
|
||||
status: null-result
|
||||
priority: high
|
||||
tags: [china, long-march-10b, reusability, state-directed, competition, timeline]
|
||||
processed_by: astra
|
||||
processed_date: 2026-03-11
|
||||
enrichments_applied: ["China is the only credible peer competitor in space with comprehensive capabilities and state-directed acceleration closing the reusability gap in 5-8 years.md"]
|
||||
extraction_model: "anthropic/claude-sonnet-4.5"
|
||||
extraction_notes: "Primary extraction updates the China reusability timeline claim with concrete April 2026 debut date, challenging the '5-8 year' projection. Secondary claim captures the state+commercial parallel development structure as evidence of ecosystem depth. Combined with the February 11 sea landing source (referenced in curator notes), this provides comprehensive update on China's reusable rocket progress. No cost-per-kg data available, so economic competitiveness claims remain unsubstantiated."
|
||||
---
|
||||
|
||||
## Content
|
||||
|
|
@ -42,3 +47,12 @@ The broader Chinese reusable rocket ecosystem includes:
|
|||
PRIMARY CONNECTION: [[China is the only credible peer competitor in space with comprehensive capabilities and state-directed acceleration closing the reusability gap in 5-8 years]]
|
||||
WHY ARCHIVED: Complements the sea landing source — provides the operational vehicle timeline and specs for China's reusable rocket program
|
||||
EXTRACTION HINT: Use together with the Feb 11 sea landing source to build the case for revising the "5-8 year" timeline claim
|
||||
|
||||
|
||||
## Key Facts
|
||||
- Long March 10B first flight scheduled no earlier than April 5, 2026
|
||||
- Long March 10 first stage successful controlled sea splashdown February 11, 2026
|
||||
- LM-10B payload capacity: 11,000 kg to 900 km altitude at 50° inclination
|
||||
- Recovery method: sea-based cable/net catching system on dedicated ship
|
||||
- Long March 9 super-heavy lift first flight planned for 2033
|
||||
- Chinese commercial reusable rocket companies: iSpace, Landspace, Galactic Energy
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/launch/9MqyiXXJUAXQ1Uy5j2EV8hq21UeR3ruukWkZ1XGNhg3R"
|
|||
date: 2026-03-03
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana]
|
||||
event_type: launch
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/launch/HTyjkYarxpf115vPqGXYpPpS9jFMXzLLjGNnVjEGWuBg"
|
|||
date: 2026-03-03
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana]
|
||||
event_type: launch
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/launch/5whxoTjxW4oKeSN4C8yf5JUur7pcSChkPWgmhSZQ8oD5"
|
|||
date: 2026-03-03
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana]
|
||||
event_type: launch
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/launch/4EhLS9CWQ2dQQe1nexxvB6D3c5jGaRCirpQ5GJFS43nR"
|
|||
date: 2026-03-03
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana]
|
||||
event_type: launch
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/launch/A88sGec3GcVfyRXNXr9DyWN6wNEwSaCqeyzrmmakKFqf"
|
|||
date: 2026-03-03
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana]
|
||||
event_type: launch
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/launch/4R1peXdUehAS1aWCdnrBfLRevGktsKH2euvBLdsYXbWu"
|
|||
date: 2026-03-03
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana]
|
||||
event_type: launch
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/launch/9VHgNjV7Lg7t6o6QqSa3Jjj1TNXftxGHnLMQFtcqpK5J"
|
|||
date: 2026-03-03
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana]
|
||||
event_type: launch
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/launch/97zmRbfpCR88KkFucJnUvMKEaFg5ay6GxQSWmyEsdi67"
|
|||
date: 2026-03-03
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana]
|
||||
event_type: launch
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/launch/8UjuYsm1m8uNNVSeA1NSwvV6ch9G2QC14yKvpXjrRgw"
|
|||
date: 2026-03-04
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana]
|
||||
event_type: launch
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/launch/87ZWGbregxaa7TMD3TgYg6n2ADdTN1vqXpVCtSvKjEjw"
|
|||
date: 2026-03-04
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana]
|
||||
event_type: launch
|
||||
---
|
||||
|
|
|
|||
|
|
@ -6,7 +6,7 @@ url: "https://www.futard.io/launch/FpFytak8JZwVntqDh9G95zqXXVJNXMxRFUYY959AXeZj"
|
|||
date: 2026-03-04
|
||||
domain: internet-finance
|
||||
format: data
|
||||
status: unprocessed
|
||||
status: entity-data
|
||||
tags: [futardio, metadao, futarchy, solana]
|
||||
event_type: launch
|
||||
---
|
||||
|
|
|
|||
Some files were not shown because too many files have changed in this diff Show more
Loading…
Reference in a new issue