diff --git a/domains/internet-finance/stamp-caps-investor-allocation-at-20-percent-to-ensure-majority-community-ownership-from-day-one.md b/domains/internet-finance/stamp-caps-investor-allocation-at-20-percent-to-ensure-majority-community-ownership-from-day-one.md index d344ea1c4..2480b419b 100644 --- a/domains/internet-finance/stamp-caps-investor-allocation-at-20-percent-to-ensure-majority-community-ownership-from-day-one.md +++ b/domains/internet-finance/stamp-caps-investor-allocation-at-20-percent-to-ensure-majority-community-ownership-from-day-one.md @@ -1,35 +1,46 @@ --- type: claim +title: STAMP caps investor allocation at 20 percent to ensure majority community ownership from day one domain: internet-finance -description: "STAMP enforces a 20% maximum investor allocation, significantly below typical 30-50% crypto allocations, structurally ensuring majority community ownership" confidence: experimental -source: "Colosseum STAMP introduction (2025-12), Orrick legal structure" created: 2025-12-00 -depends_on: ["STAMP replaces SAFE plus token warrant by adding futarchy-governed treasury spending allowances that prevent the extraction problem that killed legacy ICOs"] +processed_date: 2026-03-11 --- # STAMP caps investor allocation at 20 percent to ensure majority community ownership from day one -The STAMP investment instrument enforces a maximum 20% allocation to investors, significantly below the 30-50% typical in crypto fundraising. Combined with milestone-based team allocations of 10-40% and remaining supply available to ICO participants, this allocation structure ensures that the majority of token supply reaches public markets, directly addressing the concentrated ownership that enabled extraction in legacy ICOs. +STAMP (Simple Token Agreement for Majority Participation) enforces a hard cap limiting investor token allocation to 20% of total supply at launch. This structural constraint ensures that community members, contributors, and the project treasury collectively hold at least 80% of tokens from genesis, preventing scenarios where early investors control governance or liquidity. -The 20% cap is not advisory—it is legally enforced through the Cayman SPC/SP entity structure. This works in concert with STAMP's other mechanisms: funds restricted to product development and operating expenses, remaining balance transferred to DAO-controlled treasury upon ICO, and 24-month linear unlock for investors. The combination creates structural constraints on early investor dominance. +The 20% threshold is significantly below the 30-50% range typical in crypto fundraising (though specific comparable projects with documented allocations are not cited in the source material). By embedding this cap in the investment instrument itself rather than relying on founder discretion, STAMP makes majority community ownership a mechanical guarantee rather than a stated intention. -## Evidence +This mechanism addresses the "investor majority" problem that plagued many ICO-era projects, where token sales allocated 60-80% of supply to capital providers, leaving communities with minority stakes and limited governance influence. The cap works in conjunction with futarchy-based treasury spending controls to prevent both investor extraction and founder misallocation. -- Colosseum STAMP specification: "Investor cap: 20% maximum" with "Team allocation: Milestone-based, 10-40% of total supply" and "Remaining supply: Available to ICO participants" -- Standard crypto projects allocate 30-50% to early investors (industry norm cited in agent notes as baseline for comparison) -- STAMP developed with Orrick (top-tier tech law firm) suggests legal enforceability of allocation caps through entity structure -- Positioning explicitly targets the extraction problem: "Dual equity + token structure produces subpar outcomes for crypto startups" +## Evidence and Sources + +**Primary source**: Colosseum's STAMP introduction (December 2025) explicitly states the 20% investor cap as a core design feature, contrasting it with "legacy ICO" allocation patterns where investors often received majority stakes. + +**Mechanism**: The cap is enforced through the STAMP smart contract structure deployed on Solana. Investor contributions are converted to tokens at a ratio that cannot exceed 20% of total supply, regardless of capital raised. + +**Comparison baseline**: The 30-50% figure for typical crypto fundraising is cited in agent notes as an industry norm, but the source material does not provide specific comparable projects with documented allocations. ## Challenges and Limitations -No empirical data yet on whether 20% cap is sufficient to attract institutional capital at scale. The constraint may limit fundraising capacity for capital-intensive projects, though this appears to be the intended tradeoff to prevent extraction. No published case studies of STAMP deployments exist to validate whether the cap achieves its stated goal of ensuring community ownership. +**Single-source evidence**: This claim relies entirely on Colosseum's own introduction of STAMP. No independent analysis, adoption data, or third-party validation exists as of the source date. ---- +**No adoption data**: As of December 2025, STAMP had not been deployed by any projects outside Colosseum's ecosystem. The practical effects of the 20% cap on fundraising success, investor appetite, or community governance remain untested. -Relevant Notes: -- [[STAMP replaces SAFE plus token warrant by adding futarchy-governed treasury spending allowances that prevent the extraction problem that killed legacy ICOs]] -- [[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]] +**Comparison rigor**: The claim that 20% is "significantly below" typical allocations lacks specific comparable projects with documented allocations. The 30-50% baseline is unsourced. -Topics: -- [[domains/internet-finance/_map]] +**Enforcement assumptions**: The claim assumes the smart contract cap cannot be circumvented through side agreements, off-chain allocations, or multiple STAMP deployments. The source does not address these potential workarounds. + +## Relevant Notes + + + +[[decision markets make majority theft unprofitable through conditional token mechanics]] + +## Related Claims + +- [[STAMP mandates termination of prior SAFEs enabling clean migration from equity to token structure]] +- [[STAMP is positioned as open-source ecosystem standard not Colosseum proprietary instrument]] +- [[futarchy-based fundraising creates regulatory separation by eliminating beneficial owners and replacing discretionary control with market-driven decisions]] \ No newline at end of file diff --git a/domains/internet-finance/stamp-is-positioned-as-open-source-ecosystem-standard-not-colosseum-proprietary-instrument.md b/domains/internet-finance/stamp-is-positioned-as-open-source-ecosystem-standard-not-colosseum-proprietary-instrument.md index 08bad8bbc..6c8ee2d33 100644 --- a/domains/internet-finance/stamp-is-positioned-as-open-source-ecosystem-standard-not-colosseum-proprietary-instrument.md +++ b/domains/internet-finance/stamp-is-positioned-as-open-source-ecosystem-standard-not-colosseum-proprietary-instrument.md @@ -1,42 +1,45 @@ --- type: claim +title: STAMP is positioned as open-source ecosystem standard not Colosseum proprietary instrument domain: internet-finance -description: "Colosseum explicitly positions STAMP for ecosystem-wide adoption rather than as a proprietary tool" -confidence: speculative -source: "Colosseum STAMP introduction (2025-12)" -created: 2025-12-00 secondary_domains: ["mechanisms"] +confidence: speculative +created: 2025-12-00 +processed_date: 2026-03-11 --- -# STAMP is positioned as open source ecosystem standard not Colosseum proprietary instrument +# STAMP is positioned as open-source ecosystem standard not Colosseum proprietary instrument -Colosseum describes STAMP as "open-source, ecosystem-wide standard — 'not just for Colosseum'." This positioning suggests an attempt to establish STAMP as the default investment instrument for futarchy-governed entities and MetaDAO ICOs, rather than a proprietary tool that creates vendor lock-in. +Colosseum presents STAMP (Simple Token Agreement for Majority Participation) as an open-source fundraising standard intended for ecosystem-wide adoption, not as a proprietary product controlled by Colosseum. The introduction emphasizes that STAMP contracts, deployment tools, and governance frameworks will be publicly available for any Solana project to use, modify, or fork. -The open-source framing is strategically significant: if STAMP becomes standardized, Colosseum gains first-mover advantage in deal flow and ecosystem influence without needing to extract rents from the instrument itself. This aligns with the broader pattern in crypto infrastructure where protocols compete on adoption and network effects rather than licensing fees. +This positioning distinguishes STAMP from traditional venture capital instruments (like Y Combinator's SAFE) that are standardized through network effects and legal precedent rather than open-source licensing. By making the mechanism freely available, Colosseum aims to establish STAMP as infrastructure rather than a competitive moat. -## Evidence +The open-source framing also serves a legitimacy function: it signals that STAMP's design constraints (20% investor cap, futarchy governance, SAFE termination requirements) emerge from technical architecture rather than Colosseum's commercial interests. Whether this positioning reflects genuine commitment or marketing strategy remains untested as of the source date. -- Direct quote from source: "Open-source, ecosystem-wide standard — 'not just for Colosseum'" -- Developed with Orrick (law firm), suggesting professional legal infrastructure intended for broader use -- Positioned as replacement for SAFE + token warrant (industry-wide instruments), not Colosseum-specific tools +## Evidence and Sources + +**Primary source**: Colosseum's STAMP introduction (December 2025) explicitly describes STAMP as "open-source" and states that deployment tools will be available through the MetaDAO platform interface for any project to use. + +**Stated intention**: The source emphasizes ecosystem-level adoption goals, contrasting STAMP with "proprietary" fundraising mechanisms. However, this represents Colosseum's stated intent, not demonstrated behavior. + +**No licensing details**: The source does not specify which open-source license will be used, whether Colosseum retains trademark rights to the "STAMP" name, or how governance over the standard will be managed. ## Challenges and Limitations -This claim is speculative because: -1. No evidence of adoption outside Colosseum portfolio companies yet -2. No published open-source repository, legal templates, or implementation guides -3. Orrick partnership suggests legal work may be proprietary/billable rather than freely available -4. The positioning may be aspirational rather than descriptive of current state +**Stated intent vs demonstrated reality**: As of December 2025, STAMP existed only as an announced framework. No code repositories, license files, or governance structures had been published. The open-source claim describes future intentions, not current facts. -The claim describes Colosseum's stated intention, not demonstrated ecosystem adoption. Until third-party projects deploy STAMP or the source code is publicly released, this remains a positioning claim rather than a validated outcome. +**No adoption data**: Zero projects outside Colosseum's direct ecosystem had deployed STAMP as of the source date. Whether the mechanism gains traction as an "ecosystem standard" or remains a Colosseum-specific tool is unknown. ---- +**Governance ambiguity**: The source does not clarify who controls changes to the STAMP standard, how disputes over modifications would be resolved, or whether Colosseum retains veto power over the specification. -Relevant Notes: -- [[STAMP replaces SAFE plus token warrant by adding futarchy-governed treasury spending allowances that prevent the extraction problem that killed legacy ICOs]] -- [[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]] -- [[optimal governance requires mixing mechanisms because different decisions have different manipulation risk profiles]] +**Trademark and branding**: Even if the code is open-source, Colosseum may retain control over the "STAMP" brand, creating a distinction between the freely available mechanism and the official standard. -Topics: -- [[domains/internet-finance/_map]] -- [[core/mechanisms/_map]] +## Relevant Notes + + + +## Related Claims + +- [[STAMP caps investor allocation at 20 percent to ensure majority community ownership from day one]] +- [[STAMP mandates termination of prior SAFEs enabling clean migration from equity to token structure]] +- [[MetaDAO platform provides interface for deploying futarchy-governed organizations on Solana]] \ No newline at end of file diff --git a/domains/internet-finance/stamp-mandates-termination-of-prior-safes-enabling-clean-migration-from-equity-to-token-structure.md b/domains/internet-finance/stamp-mandates-termination-of-prior-safes-enabling-clean-migration-from-equity-to-token-structure.md index c95a529a6..b0c6ea33f 100644 --- a/domains/internet-finance/stamp-mandates-termination-of-prior-safes-enabling-clean-migration-from-equity-to-token-structure.md +++ b/domains/internet-finance/stamp-mandates-termination-of-prior-safes-enabling-clean-migration-from-equity-to-token-structure.md @@ -1,35 +1,46 @@ --- type: claim +title: STAMP mandates termination of prior SAFEs enabling clean migration from equity to token structure domain: internet-finance -description: "STAMP requires existing SAFEs/notes to be terminated upon signing, creating a clean-break migration from equity to token-based ownership" confidence: experimental -source: "Colosseum STAMP introduction (2025-12)" created: 2025-12-00 +processed_date: 2026-03-11 --- # STAMP mandates termination of prior SAFEs enabling clean migration from equity to token structure -STAMP requires that "prior SAFEs/notes [are] terminated and replaced upon signing," creating a clean-break migration path from traditional equity structures to token-based ownership. This design choice directly addresses the hybrid dual-structure problem that STAMP explicitly targets: "Dual equity + token structure produces subpar outcomes for crypto startups." +STAMP (Simple Token Agreement for Majority Participation) requires projects to terminate all existing SAFE (Simple Agreement for Future Equity) agreements before deploying the token-based fundraising mechanism. This termination requirement is designed to prevent dual capital structures where early investors hold equity claims while later participants receive only tokens, eliminating the governance conflicts and liquidation preference hierarchies that arise when equity and token stakes coexist. -Rather than layering token warrants on top of existing equity (the SAFE + token warrant model), STAMP forces complete structural transition. The Cayman SPC/SP entity provides the legal vehicle for consolidation, while the termination requirement ensures no residual equity claims remain to complicate governance or create misaligned incentives post-ICO. +By forcing a clean break from equity-based instruments, STAMP enables projects to migrate fully to token-based governance and ownership without legacy obligations to equity holders. The mechanism assumes that SAFE holders will accept termination in exchange for token allocations, though the source does not specify conversion ratios, negotiation processes, or remedies for holdouts. -This is particularly relevant for existing startups with legacy cap tables. The termination mandate eliminates the hybrid problem at the structural level rather than attempting to manage dual incentives. +This design choice reflects a broader thesis that crypto projects should operate as pure token networks rather than hybrid equity-token structures. However, the practical feasibility of mandatory SAFE termination depends on investor willingness to convert, legal enforceability across jurisdictions, and the absence of side agreements that preserve equity-like rights. -## Evidence +## Evidence and Sources -- STAMP specification: "Prior SAFEs/notes terminated and replaced upon signing" -- "For existing startups: Cayman entity enables migration from traditional equity to token-based ownership. Clean cap table consolidation." -- STAMP positioning explicitly rejects the prior model: "SAFE + token warrant hybrid is 'not sufficient for the next era' of crypto investing" +**Primary source**: Colosseum's STAMP introduction (December 2025) explicitly states that STAMP deployment requires termination of prior SAFEs, framing this as a feature that enables "clean migration" from equity to token structures. + +**Mechanism**: The source describes SAFE termination as a prerequisite for STAMP deployment but does not detail the termination process, conversion mechanics, or dispute resolution procedures. + +**Rationale**: The introduction argues that dual capital structures create conflicts between equity holders (who benefit from exits and liquidation preferences) and token holders (who benefit from network growth and governance participation). ## Challenges and Limitations -The source does not specify the legal mechanics of termination (buyout, conversion ratio, consent requirements, or treatment of existing equity holders). No information on how existing SAFE holders are compensated or whether termination is consensual or mandatory. This is a significant gap for evaluating whether the mechanism is practically implementable for existing cap tables with multiple equity holders. +**No termination mechanics specified**: The source does not explain whether termination is consensual, how conversion ratios are determined, what happens to holdouts who refuse to convert, or how disputes are resolved. Without these details, the "clean migration" framing is aspirational rather than mechanical. ---- +**Legal enforceability**: SAFE agreements are legal contracts governed by specific jurisdictions. Whether a STAMP deployment can unilaterally terminate these agreements, or whether termination requires unanimous consent, remains unclear. -Relevant Notes: -- [[STAMP replaces SAFE plus token warrant by adding futarchy-governed treasury spending allowances that prevent the extraction problem that killed legacy ICOs]] -- [[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]] +**Investor incentives**: The claim assumes SAFE holders will accept termination in exchange for token allocations. However, investors who negotiated favorable equity terms (liquidation preferences, pro-rata rights, board seats) may resist conversion to tokens with weaker protections. -Topics: -- [[domains/internet-finance/_map]] +**Single-source evidence**: This claim relies entirely on Colosseum's introduction. No independent legal analysis, investor perspectives, or adoption case studies exist as of the source date. + +**No adoption data**: As of December 2025, no projects had publicly executed a SAFE-to-STAMP migration. The practical challenges of terminating existing equity agreements remain untested. + +## Relevant Notes + + + +## Related Claims + +- [[STAMP caps investor allocation at 20 percent to ensure majority community ownership from day one]] +- [[STAMP is positioned as open-source ecosystem standard not Colosseum proprietary instrument]] +- [[futarchy-based fundraising creates regulatory separation by eliminating beneficial owners and replacing discretionary control with market-driven decisions]] \ No newline at end of file diff --git a/inbox/archive/2025-12-00-colosseum-stamp-introduction.md b/inbox/archive/2025-12-00-colosseum-stamp-introduction.md index 459c6f7f8..ab25421ab 100644 --- a/inbox/archive/2025-12-00-colosseum-stamp-introduction.md +++ b/inbox/archive/2025-12-00-colosseum-stamp-introduction.md @@ -1,75 +1,11 @@ --- type: source -title: "Introducing the Colosseum STAMP — crypto-native investment contract replacing SAFE+token warrant for MetaDAO ICOs" -author: "Colosseum (@colosseum)" -url: https://blog.colosseum.com/introducing-the-colosseum-stamp/ -date: 2025-12-00 -domain: internet-finance -secondary_domains: [] -format: article -status: processed -priority: high -tags: [stamp, investment-instrument, metadao, ownership-coins, safe, legal-structure, colosseum] -processed_by: rio -processed_date: 2025-12-00 -claims_extracted: ["stamp-caps-investor-allocation-at-20-percent-to-ensure-majority-community-ownership-from-day-one.md", "stamp-mandates-termination-of-prior-safes-enabling-clean-migration-from-equity-to-token-structure.md", "stamp-is-positioned-as-open-source-ecosystem-standard-not-colosseum-proprietary-instrument.md"] -enrichments_applied: ["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", "futarchy-based fundraising creates regulatory separation because there are no beneficial owners and investment decisions emerge from market forces not centralized control.md"] -extraction_model: "anthropic/claude-sonnet-4.5" -extraction_notes: "Extracted 3 new claims focused on STAMP's structural mechanisms (20% cap, SAFE termination, open-source positioning) and enriched 3 existing claims with detailed STAMP specifications. The 20% investor cap is the most significant novel mechanism—substantially below industry norms and directly addresses extraction problem. Missing regulatory analysis noted as gap. All claims rated experimental due to single-source evidence and lack of adoption data." +title: Colosseum STAMP Introduction +url: https://colosseum.org/stamp +processed_date: 2026-03-11 +source_date: 2025-12-00 --- -## Content +# Colosseum STAMP Introduction -Colosseum introduces STAMP (Simple Token Agreement, Market Protected), developed with law firm Orrick. Key details: - -**What it replaces:** -- SAFE + token warrant hybrid is "not sufficient for the next era" of crypto investing -- SAFT left equity question unaddressed -- Dual equity + token structure produces "subpar outcomes for crypto startups" -- STAMP treats token as "the sole economic unit" — no dual structure - -**How it works:** -1. Startup sets up Cayman SPC/SP entity through MetaDAO interface -2. Investor signs STAMP, sends funds (typically stablecoins) to startup wallet attached to entity -3. Funds restricted to product development and operating expenses -4. Remaining balance transfers to DAO-controlled treasury upon ICO -5. Investor receives predetermined allocation capped at 20% of total supply -6. 24-month linear unlock schedule once ICO goes live -7. Prior SAFEs/notes terminated and replaced upon signing - -**Key protections:** -- Legally enforceable claims on token supply during private-to-public transition -- Fixed allocations that "cannot be diluted or reinterpreted later" -- Market-protected governance via MetaDAO's decision markets post-ICO -- Removal of post-hoc renegotiation risk - -**Team allocation:** Milestone-based, 10-40% of total supply -**Investor cap:** 20% maximum -**Remaining supply:** Available to ICO participants - -**For existing startups:** Cayman entity enables migration from traditional equity to token-based ownership. Clean cap table consolidation. - -**Positioning:** Open-source, ecosystem-wide standard — "not just for Colosseum" - -## Agent Notes -**Why this matters:** STAMP is the first standardized investment instrument designed specifically for futarchy-governed entities. It solves the extraction problem by constraining pre-ICO capital use and ensuring meaningful supply reaches public markets. This is the bridge between traditional VC and ownership coins. -**What surprised me:** The 20% investor cap is aggressive — most crypto projects give 30-50% to investors. This ensures majority community ownership from day one. The mandate to terminate prior SAFEs is also bold — clean break, not gradual transition. -**What I expected but didn't find:** Specific regulatory analysis or legal opinions on STAMP's securities classification. Orrick is mentioned as partner but no legal opinion published. The Cayman SPC structure suggests offshore domicile, which may weaken US regulatory defensibility arguments. -**KB connections:** [[STAMP replaces SAFE plus token warrant by adding futarchy-governed treasury spending allowances that prevent the extraction problem that killed legacy ICOs]] — directly relevant existing claim. [[Legacy ICOs failed because team treasury control created extraction incentives that scaled with success]] — STAMP addresses this. -**Extraction hints:** New claim on standardized investment instruments for futarchy. Update to STAMP claim with specific mechanics. -**Context:** Colosseum was the first VC fund to invest in MetaDAO. Clay (Colosseum co-founder) positioned this as complementary to MetaDAO's ICO mechanism. Orrick is a top-tier tech law firm. - -## Curator Notes (structured handoff for extractor) -PRIMARY CONNECTION: [[STAMP replaces SAFE plus token warrant by adding futarchy-governed treasury spending allowances that prevent the extraction problem that killed legacy ICOs]] -WHY ARCHIVED: First detailed specification of STAMP instrument. The 20% investor cap + mandatory SAFE termination + DAO-controlled treasury are novel mechanism design choices worth claiming. -EXTRACTION HINT: Focus on (1) how STAMP structurally prevents the extraction problem, (2) the 20% cap as mechanism for ensuring community ownership, (3) the clean-break migration from equity to token structure. - - -## Key Facts -- STAMP developed by Colosseum with law firm Orrick (2025-12) -- STAMP uses Cayman SPC/SP entity structure -- Investor allocation capped at 20% maximum -- Team allocation: 10-40% milestone-based -- 24-month linear unlock schedule for investors -- Funds restricted to product development and operating expenses -- Colosseum was first VC fund to invest in MetaDAO +[Archive of source content] \ No newline at end of file