| type |
entity_type |
name |
domain |
status |
parent_entity |
platform |
proposal_url |
proposal_date |
resolution_date |
category |
summary |
key_metrics |
token |
launch_address |
tracked_by |
created |
| decision |
decision_market |
Salmon Wallet: Futardio Fundraise |
internet-finance |
failed |
salmon-wallet |
futardio |
https://www.futard.io/launch/Aakx1gdDoNQYqiv5uoqdXx56mGr6AbZh73SWpxHrk2qF |
2026-03-03 |
2026-03-04 |
fundraise |
Open-source wallet infrastructure project seeking $375K for 12-month runway through futarchy-governed ICO |
| raise_target |
total_committed |
oversubscription_ratio |
monthly_burn_rate |
planned_runway |
| $375,000 |
$97,535 |
0.26 |
$25,000 |
12 months |
|
| name |
ticker |
mint |
| Salmon Token |
SAL |
DDPW4sZT9GsSb2mSfY9Yi9EBZGnBQ2LvvJTXCpnLmeta |
|
Aakx1gdDoNQYqiv5uoqdXx56mGr6AbZh73SWpxHrk2qF |
rio |
2026-03-11 |
Salmon Wallet: Futardio Fundraise
Summary
Salmon Wallet attempted to raise $375,000 through MetaDAO's futarchy platform for 12-month operational runway covering wallet development, security, infrastructure, and mobile app releases. Despite being an established project (active since 2022, listed on Solana wallet adapter, $122.5K prior funding), the raise attracted only $97,535 (26% of target) before refunding. First observed futarchy-governed wallet infrastructure project on the platform.
Market Data
- Outcome: Failed (refunding)
- Raise Target: $375,000
- Total Committed: $97,535
- Oversubscription: 0.26x
- Duration: 1 day (2026-03-03 to 2026-03-04)
- Token: SAL (Salmon Token)
Use of Funds (Proposed)
- Team: $18,300/month (73%)
- Infrastructure: $4,200/month (17%)
- Growth & Ecosystem: $2,000/month (8%)
- Governance, Legal & Contingency: $500/month (2%)
- Total Monthly Burn: $25,000
- Target Runway: 12 months
Roadmap (Proposed)
- Q2-2026: Android release, WebApp relaunch, signing flow optimization
- Q3-2026: iOS TestFlight, staking integration, AI transaction security
- Q4-2026: Custom notifications, portfolio view, Wallet-as-a-Service
- Q1-2027: Cross-platform optimization, ecosystem integrations
Significance
First empirical data point on futarchy adoption friction for operational software infrastructure versus pure capital allocation vehicles. The failed raise suggests futarchy mechanisms face challenges when applied to projects with ongoing operational complexity, team budgets, and multi-quarter development roadmaps. Despite technical credibility and operational history, the project could not achieve minimum viable liquidity in the futarchy market.
Relationship to KB