Template
Template E — Sovereign
Vermont LLC; sovereign landowner; treaty-compatible governance.
Tier 1 — Vermont LLC + multi-sig treasury wallet + operating-agreement governance. No smart-contract DAO.
For properties involving sovereign entities: national parks, government-managed reserves, agency-administered lands.
When to use Template E
A property uses Template E when:
- The legal owner is a national, state, provincial, or local government
- Or: the property is co-managed under a formal sovereign framework (treaty, intergovernmental agreement)
- Sovereign agency is the principal governance partner
- Indigenous community co-management may also be present (then Template F hybrid)
Examples:
- Madagascar Andasibe-Mantadia National Park (under Madagascar National Parks)
- Ecuador Yasuni National Park (under Ministry of Environment)
- Bangladesh Sundarbans Reserve (under Forest Department)
- US National Wildlife Refuge (under USFWS, with appropriate authorities)
- Argentina Iguazú National Park (under Administración de Parques Nacionales)
Why Template E differs from Templates B and D
Sovereign entities have unique characteristics:
- Sovereign immunity considerations affect contract enforcement
- Treaty obligations may pre-exist and constrain governance
- Regulatory compliance is more complex (international + national + local)
- Public-trust doctrines often apply
- Political volatility can disrupt operations
Template E accommodates these characteristics with explicit treaty-respecting and immunity-respecting language.
Vehicle structure
Wrapper entity: Vermont LLC (standard) for US, OR Marshall Islands DAO LLC + sovereign-jurisdiction local agent for non-US sovereign deployments. The wrapper is not the sovereign entity itself; the sovereign is a member with designated agency representation.
Treasury: multi-sig wallet (Safe) with USDC. Signers: sovereign agency designee + Landseed compliance officer + designated independent. 2-of-3 standard.
Operating agreement: includes special provisions for treaty obligations, sovereign immunity, regulatory compliance, and political-disruption fallback procedures.
Beneficiaries
| Seat | Holder | Voting weight | Distribution share |
|---|---|---|---|
| Sovereign agency | The relevant government agency (designated officer) | Residual veto on national-policy decisions | 60–80% to designated environmental fund |
| Local management body (optional) | Park manager, regional authority, or analogous | Operational decisions | Small honorarium or none |
| Adjacent communities (optional, non-Template-C scope) | Community representatives | Advisory | Specific community-fund allocation |
| Landseed steward | Landseed PBC | Methodology authority + guardian veto | 2–5% protocol fee |
Distribution profile
| Recipient | Share | Purpose |
|---|---|---|
| National or regional environmental fund | 60–80% | Sovereign-defined uses; typically conservation programs, park operations |
| Local management body or stewardship reserve | 10–25% | Property-specific stewardship work |
| Adjacent communities (if seated) | 5–15% | Community fund per agreement |
| Landseed protocol fee | 2–5% | Per LLC operating agreement |
Sovereign agency receives the largest share, consistent with public-trust doctrines (the public benefits from public lands).
Governance — operating-agreement substance
Use decisions
- Sovereign agency holds residual veto on national-policy-relevant decisions (changes to park boundaries, treaty implications, etc.)
- Operational decisions delegated to local management body
- Methodology integration follows sovereign regulatory requirements
Methodology decisions
- Landseed proposes; sovereign agency ratifies through institutional governance
- 60–120-day consideration period (longer than typical to accommodate institutional review)
Treaty obligations
- Operating agreement explicitly preserves any pre-existing treaty obligations
- Treaty conflicts: treaty controls; LLC adjusts
Sovereign immunity
- The wrapper LLC is not the sovereign and does not claim immunity
- Disputes between LLC and sovereign agency: mediation-first; sovereign immunity may apply to enforcement against the agency in some jurisdictions
- Choice of law: typically the sovereign jurisdiction’s law for sovereign-relevant disputes
Regulatory compliance
- LLC complies with all applicable national and international regulations affecting the property
- Reporting per sovereign-required frameworks (CITES, Ramsar, World Heritage, etc.)
Political-disruption fallback
- If the sovereign agency becomes unable to operate (change of government, agency restructuring, conflict), the LLC has defined fallback procedures
- Treasury operations continue; methodology assessment continues; distributions may pause until sovereign reauthorization
- Local management body can assume some operational authority during disruptions
Special considerations
Sovereign-immunity asymmetry
The architecture is asymmetric: Landseed and the LLC can be sued; the sovereign typically cannot (without sovereign waiver). The operating agreement should:
- Clearly establish that the LLC’s obligations are commercial, not sovereign
- Provide that the sovereign agency’s obligations are administrative, not commercial
- Set up mediation as primary dispute resolution to avoid the asymmetry surfacing
Treaty interplay
Sovereign properties are often subject to international treaties:
- World Heritage Sites have UNESCO oversight
- Ramsar Wetlands have intergovernmental obligations
- CITES species require international permitting
- IUCN-classified protected areas have classification standards
Template E accepts that treaties control over LLC operating-agreement terms in case of conflict. The methodology provides condition assessment that supports treaty reporting.
Regulatory compliance aggregation
A sovereign property typically has many overlapping regulatory frameworks:
- National environmental laws
- Regional or provincial regulations
- International treaty obligations
- Sectoral regulations (forestry, water, mining)
The LLC’s reporting obligations aggregate these; the methodology provides the condition data each requires.
Deployment
| Phase | Duration | What happens |
|---|---|---|
| Sovereign agency engagement | 6–18 months | Inter-agency coordination, regulatory review, possibly legislative or executive approval |
| Treaty review | 3–6 months parallel | Confirm no treaty conflicts |
| Operating agreement negotiation | 3–6 months | With agency legal team; significant institutional review |
| LLC formation | 2–3 weeks | Standard formation |
| NRD-lite drafted (sovereign jurisdiction) | 8–16 weeks | Per drafting strategy; may require sovereign-specific category mapping |
| NRD-lite recorded | 4–12 weeks | Per sovereign jurisdiction’s recording mechanics; may require additional approvals |
| Operational | Ongoing | With ongoing inter-agency coordination |
Total: 18–36 months from sovereign-engagement-start to operational deployment. Slowest of the Tier 1 templates. The slowness reflects the institutional and political complexity of sovereign engagement.
Risks specific to Template E
| Risk | Mitigation |
|---|---|
| Change of government; new policy direction conflicts with deployment | Operating agreement is binding regardless of government changes; political-disruption fallback procedures preserve operations |
| Treaty obligation evolves in ways that constrain methodology | Treaty controls; LLC adjusts; methodology updates may be needed |
| Sovereign immunity invoked against LLC enforcement | Mediation-first; structural acceptance that sovereign-agency obligations are different in kind |
| Public-trust doctrine challenged in court | Sovereign agency’s authority is the foundation; if challenged, the agency manages the legal defense |
| Inter-agency conflict (multiple agencies claim authority) | Sovereign-internal dispute, not Landseed’s to resolve; operating agreement specifies which agency is the LLC’s counterparty |
| Funding disruption to sovereign agency | Operating agreement provides for revenue routing during disruptions; treasury continues to receive credit revenue |
What Template E does NOT do
- Does not give Landseed authority over sovereign decisions
- Does not claim or waive sovereign immunity
- Does not override treaty obligations
- Does not provide a vehicle for any commercial entity to acquire sovereign rights
- Does not assume political stability — fallback procedures exist for disruptions
Strategic note
Sovereign deployments are high-impact (large protected areas, significant credit volumes) but slow and politically complex. They are not appropriate for the first wave of deployments.
Recommendation: Template E is a Year 2–3 priority. The first wave should focus on US private (Templates A, B) and Madagascar community (Template C, with established partner). Sovereign engagement begins after the architecture has live deployments to demonstrate.
When Template E becomes Template F (hybrid)
Many sovereign properties are also indigenous lands. When this is the case:
- Sovereign agency is one stakeholder
- Indigenous community is another stakeholder
- Template F (hybrid) composes seats from both Template E and Template C
Template F deployment for sovereign+indigenous lands is particularly intricate; it requires both indigenous-rights-advocate review (per Template C) and sovereign-treaty review (per Template E). See Template F for details.