Compare commits

..

1 commit

Author SHA1 Message Date
Teleo Agents
982049a88c rio: extract from 2026-03-05-futardio-launch-you-get-nothing.md
- Source: inbox/archive/2026-03-05-futardio-launch-you-get-nothing.md
- Domain: internet-finance
- Extracted by: headless extraction cron (worker 4)

Pentagon-Agent: Rio <HEADLESS>
2026-03-11 14:06:46 +00:00
7 changed files with 47 additions and 104 deletions

View file

@ -1,50 +0,0 @@
---
type: claim
claim_id: seyf_intent_wallet_architecture
domain: internet-finance
confidence: speculative
tags:
- intent-based-ux
- wallet-architecture
- defi-abstraction
- natural-language-interface
created: 2026-03-05
processed_date: 2026-03-05
source:
- inbox/archive/2026-03-05-futardio-launch-seyf.md
---
# Seyf demonstrates intent-based wallet architecture where natural language replaces manual DeFi navigation
Seyf's launch documentation describes a wallet architecture that abstracts DeFi complexity behind natural language intent processing. This architecture is from launch documentation for a fundraise that failed to reach its target, so represents planned capabilities rather than demonstrated product-market fit.
## Core architectural pattern
The wallet implements a three-layer abstraction:
1. **Intent layer**: Users express goals in natural language ("I want to earn yield on my USDC")
2. **Solver layer**: Backend translates intents into optimal DeFi operations across protocols
3. **Execution layer**: Atomic transaction bundles execute the strategy
This inverts the traditional wallet model where users manually navigate protocol UIs and construct transactions.
## Key architectural decisions
**Natural language as primary interface**: The wallet treats conversational input as the main UX, not a supplementary feature. Users describe financial goals rather than selecting from protocol menus.
**Protocol-agnostic solver**: The backend maintains a registry of DeFi primitives (lending, swapping, staking) and composes them based on intent optimization, not hardcoded protocol integrations.
**Atomic execution bundles**: Multi-step strategies (e.g., swap → deposit → stake) execute as single atomic transactions, preventing partial failures.
## Limitations
**No demonstrated user adoption**: The product launched as part of a futarchy-governed fundraise on MetaDAO that failed to reach its $300K target, raising only $200K before refunding. We have no evidence of production usage or user validation of the intent-based model.
**Solver complexity not detailed**: The documentation describes the solver layer conceptually but doesn't specify how it handles intent ambiguity, optimization trade-offs, or protocol risk assessment.
**Limited to Solana**: The architecture assumes Solana's transaction model. Cross-chain intent execution would require different primitives.
## Related claims
- [[futarchy-governed-fundraising-on-metadao-shows-early-stage-liquidity-constraints-in-seyf-launch]] - The fundraising outcome for this product
- [[defi-complexity-creates-user-experience-friction-that-limits-mainstream-adoption]] - The broader UX problem this architecture attempts to solve

View file

@ -1,47 +0,0 @@
---
type: claim
domain: internet-finance
description: "MetaDAO's conditional token architecture fragments liquidity across pass/fail pools; a shared-base-pair AMM would let a single META/USDC deposit serve both pMETA/pUSDC and fMETA/fUSDC markets, reducing the capital required to keep conditional markets liquid."
confidence: speculative
source: "rio, based on MetaDAO Proposal 12 (futard.io, Feb 2025) — Proph3t's concept developed in collaboration with Robin Hanson"
created: 2026-03-11
depends_on:
- "MetaDAO Proposal 12 (AnCu4QFDmoGpebfAM8Aa7kViouAk1JW6LJCJJer6ELBF) — Proph3t's description of shared liquidity AMM design"
challenged_by:
- "Shared liquidity between conditional token pairs could introduce cross-pool price manipulation vectors not present in isolated AMMs"
- "Redemption mechanics may be incompatible with shared liquidity — winning conditional tokens must redeem 1:1 against underlying, which requires ring-fenced reserves"
---
# Shared-liquidity AMMs could solve futarchy capital inefficiency by routing base-pair deposits into all derived conditional token markets without requiring separate capital for each pass and fail pool
[[MetaDAOs Autocrat program implements futarchy through conditional token markets where proposals create parallel pass and fail universes settled by time-weighted average price over a three-day window]] creates a structural capital problem: every active proposal fragments the token liquidity base. A DAO with 10 concurrent proposals needs liquidity in 20 separate AMMs (one pass, one fail per proposal). Each pool competes for the same depositor base. Thin markets in individual conditional pools mean noisy TWAP signals and higher manipulation risk.
MetaDAO's Proph3t, in collaboration with Robin Hanson, has proposed a shared-liquidity AMM design to address this. The concept: people provide META/USDC liquidity once into a base pool, and that liquidity is accessible to both the pMETA/pUSDC market and the fMETA/fUSDC market simultaneously. Rather than siloing capital into separate pools per proposal universe, the underlying deposit serves as a shared reserve that conditional token markets draw against.
The mechanism would work directionally: when a trader buys pass tokens (pMETA), the trade routes through the shared META/USDC reserve, and the AMM logic credits the appropriate conditional token while debiting the underlying. The pool doesn't need to hold conditional tokens as inventory — it holds the base asset and mints conditionals on demand against it.
If viable, this would make futarchy markets cheaper to bootstrap: a project launching with 10 concurrent governance proposals currently needs 10x the liquidity capital. Shared-base-pair liquidity could collapse that multiplier, making [[futarchy adoption faces friction from token price psychology proposal complexity and liquidity requirements]] easier to address at the liquidity dimension specifically.
The design is at concept stage — Proph3t noted it in Proposal 12 as something they want to write about with Hanson, not a completed mechanism. The technical challenge is maintaining correct conditional redemption guarantees (winning tokens must redeem 1:1 for underlying base tokens) while sharing the reserve. Cross-pool contamination — where fail token market losses could drain the reserve for pass token settlement — would need to be solved at the architecture level.
## Evidence
- MetaDAO Proposal 12 (Feb 2025, passed): "we've been thinking about a new 'shared liquidity AMM' design where people provide META/USDC liquidity and it can be used in pMETA/pUSDC and fMETA/fUSDC markets" — Proph3t, confirmed by proposal passing
- [[MetaDAOs Autocrat program implements futarchy through conditional token markets where proposals create parallel pass and fail universes settled by time-weighted average price over a three-day window]] — source of the liquidity fragmentation problem (each proposal spawns two isolated AMMs)
## Challenges
- Shared reserves may be incompatible with the conditional redemption guarantee — winners must receive underlying tokens 1:1, which requires ring-fenced reserves per universe, not shared pools
- Cross-pool risk: a large loss in fail token markets could deplete the shared reserve and impair pass token settlement, creating contagion
- The concept is undeveloped — Proph3t flagged it as something to write about with Hanson, not a designed mechanism; this claim may be superseded by more detailed analysis
---
Relevant Notes:
- [[MetaDAOs Autocrat program implements futarchy through conditional token markets where proposals create parallel pass and fail universes settled by time-weighted average price over a three-day window]] — the architecture this would modify
- [[futarchy adoption faces friction from token price psychology proposal complexity and liquidity requirements]] — liquidity fragmentation is one of those friction points
- [[futarchy implementations must simplify theoretical mechanisms for production adoption because original designs include impractical elements that academics tolerate but users reject]] — shared-liquidity AMM is another round of simplification, this time for capital efficiency
- [[MetaDAO is the futarchy launchpad on Solana where projects raise capital through unruggable ICOs governed by conditional markets creating the first platform for ownership coins at scale]] — platform this would improve
Topics:
- [[internet finance and decision markets]]

View file

@ -0,0 +1,29 @@
---
type: entity
entity_type: project
name: You Get Nothing
domain: internet-finance
status: failed
tracked_by: rio
created: 2026-03-11
key_metrics:
funding_target: 69069.00
total_committed: 0
launch_date: 2026-03-05
close_date: 2026-03-06
platform: Futardio
platform_version: v0.7
token_symbol: 86P
outcome: refunding
---
# You Get Nothing
Parody/joke project launched on Futardio with no substantive content. The entire project description consisted of repetitive variations of "you get nothing." Launched 2026-03-05 with a $69,069 funding target and immediately went to refunding status, closing the next day with zero commitments. Represents a data point about Futardio's permissionless launch model allowing non-serious projects.
## Timeline
- **2026-03-05** — Launched on Futardio with $69,069 funding target, token 86P, entirely joke/parody content
- **2026-03-06** — Closed with refunding status, zero commitments raised
## Relationship to KB
Example of permissionless launch platform activity patterns. Demonstrates that [[futarchy-governed permissionless launches require brand separation to manage reputational liability because failed projects on a curated platform damage the platforms credibility]].

View file

@ -6,7 +6,7 @@ url: "https://www.futard.io/proposal/evGundfgMRZWCYsGF7GMKcgh6LjxDTFrvWRAhxiQS8h
date: 2024-09-05
domain: internet-finance
format: data
status: null-result
status: unprocessed
tags: [futardio, metadao, futarchy, solana, governance]
event_type: proposal
processed_by: rio

View file

@ -6,16 +6,14 @@ url: "https://www.futard.io/proposal/AnCu4QFDmoGpebfAM8Aa7kViouAk1JW6LJCJJer6ELB
date: 2025-02-10
domain: internet-finance
format: data
status: processed
status: unprocessed
tags: [futardio, metadao, futarchy, solana, governance]
event_type: proposal
processed_by: rio
processed_date: 2025-02-10
enrichments_applied: ["futarchy-governed-DAOs-converge-on-traditional-corporate-governance-scaffolding-for-treasury-operations-because-market-mechanisms-alone-cannot-provide-operational-security-and-legal-compliance.md", "futarchy-implementations-must-simplify-theoretical-mechanisms-for-production-adoption-because-original-designs-include-impractical-elements-that-academics-tolerate-but-users-reject.md", "MetaDAO-is-the-futarchy-launchpad-on-Solana-where-projects-raise-capital-through-unruggable-ICOs-governed-by-conditional-markets-creating-the-first-platform-for-ownership-coins-at-scale.md"]
extraction_model: "anthropic/claude-sonnet-4.5"
claims_extracted:
- "shared-liquidity-amms-could-solve-futarchy-capital-inefficiency-by-routing-base-pair-deposits-into-all-derived-conditional-token-markets.md"
extraction_notes: "Governance proposal data showing MetaDAO's operational evolution. One novel claim extracted: the shared-liquidity AMM concept for conditional markets (Proph3t + Hanson concept, not yet implemented). Remaining insights enrich existing claims about futarchy implementation, mechanism simplification, and MetaDAO's platform development. The proposal also demonstrates convergence on traditional advisory structures (Robin Hanson advisor hire via futarchy vote)."
extraction_notes: "Governance proposal data showing MetaDAO's operational evolution. No novel claims—all insights enrich existing claims about futarchy implementation, mechanism simplification, and MetaDAO's platform development. The proposal demonstrates convergence on traditional advisory structures while iterating on futarchy mechanism design for capital efficiency."
---
## Proposal Details

View file

@ -6,7 +6,7 @@ url: "https://www.futard.io/launch/6hjjscmjd2iEiycvcjymMqiRqXgzmi74hzMk4y7t267S"
date: 2026-02-25
domain: internet-finance
format: data
status: null-result
status: unprocessed
tags: [futardio, metadao, futarchy, solana]
event_type: launch
processed_by: rio

View file

@ -6,13 +6,17 @@ url: "https://www.futard.io/launch/4xAEV1JHuNSLLdMCa8tiC6CdVYpEXttuZ8U9izv9ALjp"
date: 2026-03-05
domain: internet-finance
format: data
status: unprocessed
status: processed
tags: [futardio, metadao, futarchy, solana]
event_type: launch
processed_by: rio
processed_date: 2026-03-10
extraction_model: "anthropic/claude-sonnet-4.5"
extraction_notes: "This source is a joke/parody project on Futardio with no substantive content. The entire description is repetitive variations of 'you get nothing.' No evidence, no claims, no insights to extract. The project immediately went to refunding status. This is a data point about platform activity (permissionless launches include non-serious projects) but does not warrant a standalone claim. Preserved as factual record of platform usage patterns."
processed_by: rio
processed_date: 2026-03-11
extraction_model: "anthropic/claude-sonnet-4.5"
extraction_notes: "Parody project with no substantive content. Created entity record as factual documentation of platform usage pattern (permissionless launches include non-serious projects). No claims extracted - this is purely factual data about a failed joke launch. Entity created despite trivial outcome because it illustrates the permissionless nature of Futardio launches and provides concrete example for existing claim about brand separation needs."
---
## Launch Details
@ -118,3 +122,12 @@ Nothing. No way.
- Launch address: 4xAEV1JHuNSLLdMCa8tiC6CdVYpEXttuZ8U9izv9ALjp
- Token: 86P
- Platform version: v0.7
## Key Facts
- You Get Nothing launched on Futardio 2026-03-05 with $69,069 target
- Project description was entirely repetitive 'you get nothing' text
- Closed 2026-03-06 in refunding status with zero commitments
- Launch address: 4xAEV1JHuNSLLdMCa8tiC6CdVYpEXttuZ8U9izv9ALjp
- Token: 86P (mint: 86PsjsKJpFKZS8fZLuZxhep6MxhV3Gz2EcmEYPkpmeta)
- Platform version: v0.7