Contents
Abstract
Cosmos formalizes chain-level sovereignty and interoperable communication without formalizing many of the retention and coordination mechanisms that other blockchain architectures place inside a shared settlement layer or common security regime. Inter-Blockchain Communication enables sovereign chains to exchange packets. The Cosmos SDK enables application-specific chains. Relayer continuity, route maintenance, monitoring quality, treasury stewardship, crisis management, and ecosystem legitimacy remain only partially formalized. Sovereignty-first ecosystems therefore impose an institutional-completion requirement: residual institutions must perform the coordination, monitoring, and conflict-containment work that the strongest protocol layer leaves outside itself.
The claim is developed through Hirschman’s (1970) exit-voice-loyalty framework, Ostrom’s (1990) design principles, and Helmke and Levitsky’s (2004) typology of formal-informal institutional relations. It engages the closest adjacent scholarship on blockchain exit and forking, blockchain commons, DAO governance, and Cosmos Interchain Security. The empirical reconstruction focuses on three clusters: residual interdependence around relayers and route continuity, the 2023 liquid-staking-module governance crisis and subsequent Interchain Foundation accountability dispute, and AtomOne as a design-level counter-design with completed falsification still unavailable.
Several points require precision. Proposal 952 is an ICF no-confidence vote; it is separate from late-stage liquid-staking proposals. AtomOne is treated as a design-level comparator whose constitutional structure can be analyzed now, while long-run stress-pattern evaluation remains a follow-up question. Interchain Security is analyzed as a limited and retreating counter-design whose public difficulties make the residual-formalization thesis visible without proving it as a general law. The institutional claim is specific: sovereignty-first architectures redistribute governance burden into residual institutions, and when those institutions weaken, exit becomes more attractive relative to voice.
Keywords: Cosmos, institutional completion, Hirschman, Ostrom, Helmke-Levitsky, Interchain Security, AtomOne, IBC, relayers, blockchain governance, residual institutions.
1. Introduction
Cosmos is often described as a sovereignty-first blockchain ecosystem. The description is accurate and incomplete. The SDK lets teams build application-specific chains, and IBC lets those chains communicate without collapsing into a common settlement layer or single validator set (Kwon and Buchman 2016). Sovereignty at the chain layer relocates ecosystem dependence into relayers, channels, governance procedures, foundations, public coordination, and shared legitimacy.
Cosmos is a residual-formalization case because sovereignty is strongly specified at the chain layer while maintenance, monitoring, stewardship, conflict management, and legitimacy production remain institutional burdens outside the coded layer. The central claim is that sovereignty-first ecosystems impose an institutional-completion requirement. Formal architecture that reduces protocol-enforced commitments necessarily shifts coordinating and monitoring work onto residual institutions. When those institutions come under stress, exit becomes more attractive relative to voice, and branching becomes a recurrent governance response.
Institutional completion names a specific architectural sequence. A sovereignty-first design formalizes autonomy and interoperability strongly while leaving retention, monitoring, repair, and legitimacy-production less fully specified. Those omitted functions do not disappear. They reappear as burdens on relayer operators, foundations, governance forums, and other ecosystem bodies. The concept therefore does different work from a general public-goods story or a generic account of informal coordination. It identifies the mismatch between what the architecture formalizes most strongly and what the ecosystem still has to supply in order to remain governable.
The claim is Cosmos-specific and bounded. The architecture leaves key retention and repair functions outside its strongest formal commitments, and later political stress reveals how consequential those residual institutions were. Loyalty is inferred from observable alignment, public trust, continued participation, and exit or branch behavior. AtomOne functions as a design-level comparator, with long-run stress-pattern evaluation left to follow-up work.
Three episodes make the case visible. First, relayer and route maintenance show that interoperability without shared settlement remains operationally dependent on under-formalized ecosystem work. Second, the liquid-staking-module crisis and the Interchain Foundation reporting dispute reveal monitoring, disclosure, and stewardship as core institutional supports. Third, AtomOne shows how actors inside the ecosystem attempted to constitutionalize functions they believed Cosmos Hub governance had left too informal.
Williamson (1985) is relevant but secondary. Transaction-cost economics can describe parts of the case, especially validator investment, relayer persistence, and incomplete contracting around interchain arrangements. The application of transaction-cost economics to blockchain institutions is itself established (Davidson, De Filippi, and Potts 2018), and Allen, Berg, and Davidson’s (2023) analysis of Interchain Security makes that explicit for shared security. The central object is the institutional burden that remains after a sovereignty-first architectural commitment has already been made. Hirschman, Ostrom, and Helmke-Levitsky remain primary, while Williamson and Vatiero are engaged as adjacent resources.
1.1. Institutional Completion as a Test
Institutional completion operates as a four-part test. A residual function enters the concept only when four conditions are visible.
First, there is formal asymmetry: the architecture formalizes autonomy, interoperation, or settlement more strongly than it formalizes a related maintenance, monitoring, repair, or legitimacy function. Second, the omitted function is operationally necessary for the formalized architecture to work at ecosystem scale. Third, the function is carried by identifiable actors outside the strongest formal layer, such as relayers, foundations, governance forums, treasury stewards, validators, or constitutional projects. Fourth, the function becomes visible under stress as a subsidy need, disclosure demand, legitimacy dispute, repair process, or redesign proposal.
The collapse rule is simple. If the function is optional, purely expressive, or adequately supplied by the strongest formal layer, the evidence remains ordinary politics, public goods, or maintenance. Institutional completion begins where an architecture-shaped burden can be traced from formal design choice to residual carrier to stress-visible repair.
2. Prior Art and Analytical Position
2.1. Exit, forking, and blockchain governance
Atik and Gerro’s (2018) Hirschman-based analysis of Bitcoin hard forks remains the closest direct precedent for an exit-voice reading of blockchain branching. Their concept of reversible exit is especially useful in Cosmos, where token-holders, validators, applications, and teams can often reduce or restore alignment with relatively low friction. Berg and Berg (2020) extend this discussion by treating forking as a specific governance response, which connects to the open-source-software literature on code forking, governance, and sustainability (Nyman and Lindman 2013). Morrison, Mazey, and Wingreen’s (2020) treatment of the DAO controversy further establishes that branching episodes are central empirical sites for analyzing institutional conflict in blockchain systems.
Cosmos differs from those earlier cases because branching does not arise in a monolithic protocol alone. It occurs within a wider ecosystem of sovereign units linked by shared legitimacy, route dependence, and institutionally mediated coordination. That difference is exactly why Hirschman needs to be used carefully here. Exit is plural across chains, validators, teams, applications, and token positions. Voice is both on-chain and off-chain. Loyalty is institutionally produced, but only indirectly observable.
2.2. Commons and DAO literatures
Rozas et al. (2021) argue that blockchain systems may furnish affordances for commons governance, but they do not eliminate the need for institutional design. Murtazashvili et al. (2022) extend that line by treating blockchain networks as knowledge commons with technical, institutional, and maintenance layers. Hassan and De Filippi (2021) supply the bridge between DAO definition and commons governance. These literatures matter because Cosmos often appears to be a pure constitutional-technical ecosystem when in fact it depends heavily on shared governance and maintenance practices that remain partially outside the protocol core.
Ostrom’s design principles require explicit caution in Cosmos, which is far from a small, face-to-face commons. The useful comparison asks which design principles the architecture strongly supports, which it only partially supports, and which it leaves to residual institutions. That selective mapping turns out to be analytically productive.
The boundary with these literatures should also be explicit. Commons and self-infrastructuring accounts identify shared maintenance burdens and ongoing rebuilding work. Institutional completion adds a more specific claim about burden allocation. It explains why those burdens become structurally load-bearing in Cosmos: the architecture formalizes sovereignty and interoperation more strongly than the institutions that secure retention, monitoring, and crisis repair. The concept therefore links constitutional design choice to predictable downstream governance dependence.
2.3. Cosmos-specific prior art
Allen, Berg, and Davidson’s study of Interchain Security is the most directly adjacent institutional-economics analysis of a core Cosmos governance object. It treats ICS as a governance and contracting problem shaped by incomplete contracts, opportunism, vertical integration risk, and asset-specific investments. That analysis clarifies the boundary. Allen-Berg-Davidson ask how a shared-security arrangement should be governed so that it remains robust and value-adding. The residual-formalization question asks what institutional work remains outside the strongest formal layer when sovereignty is preserved and why that work becomes politically consequential when stress arrives.
That distinction becomes sharper once the empirical record is updated. Allen-Berg-Davidson focus on the design and governance of a formal attachment mechanism meant to stabilize interchain relations. The residual question concerns what happens when that mechanism does not become the dominant solution and the burden returns to forums, foundations, relayer operators, and ad hoc subsidy politics: the institutional consequences of preserving sovereignty when shared security does not absorb the ecosystem’s coordination burden.
The difference matters because ICS itself now looks less like a settled solution and more like a limited or retreating counter-design. Neutron exited the arrangement in March 2025. Stride moved off replicated security as the Hub adopted opt-in partial set security. Gaia v27 disabled creation of new consumer chains as part of a staged ICS removal plan. The evidence supports a narrower conclusion: shared security remains conceptually possible, while the strongest intra-ecosystem attempt to formalize retention through shared security did not become the dominant organizational solution. That strengthens the residual-formalization argument rather than displacing it.
2.4. Williamson and adjacent TCE literature
Williamson’s (1985) framework illuminates part of the case, especially the asset-specificity of validator and relayer investments, the temporal specificity of client and route maintenance, and the incomplete-contract character of interchain security arrangements. Vatiero’s (2022) transaction-cost critique of smart contracts reinforces that point by showing why blockchain enforcement does not eliminate adaptation problems. Williamson remains secondary because the central object is residual institutional burden generated by a sovereignty-first architecture, not contract-structure minimization or governance-form selection. For that question, Hirschman, Ostrom, and Helmke-Levitsky supply the better vocabulary.
3. Method and Scope
The analysis is a public-architecture and public-governance study, structured as a theory-developing single-case design (George and Bennett 2005; Gerring 2007). It relies on four source classes.
First, protocol and documentation sources establish the baseline architecture: Cosmos SDK materials, IBC materials, Interchain Security materials, and AtomOne constitutional and launch materials. Second, governance sources establish formal voice and public institutional conflict: governance proposals, forum discussions, and associated public records. Third, operational materials establish residual maintenance burden: relayer documentation, subsidy requests, and public service commitments. Fourth, public disclosures and reporting reconstruct the LSM and Interchain Foundation controversies.
Source asymmetry matters. Repository and governance artifacts are stronger than press coverage. Interested-party disclosures can still be important, especially where they reveal what public participants were told and when. The analysis therefore distinguishes between strong architectural claims, which rest on public formal artifacts, and interpretive crisis claims, which rest on mixed evidentiary surfaces.
Forensic discipline therefore matters more than decimal precision. The governance surfaces that do most of the work here are public and nameable: Cosmos forum materials around Proposal 787 and Grace Yu’s Proposal 952 no-confidence thread, governance records such as Observatory and Polkachu, the AtomOne constitution and launch materials, Polkachu’s gm-ibc documentation, Cosmos Hub governance and liquid-staking documentation, and the Interchain Foundation Treasury Snapshot series. The source spine was refreshed on May 4, 2026; a May 17 local packet then pinned exact proposal fields, vote windows, final tallies, AtomOne Proposal 2 API custody, and corrected relayer proposal identifiers. The institutional argument does not rely on exact vote percentages where the stronger point is proposal identity, source class, and sequence.
Evidence base for the process trace
2017 white paper; current docs
Cosmos sovereignty and IBC baseline
Source classWhite paper and protocol documentation.
Public sourceCosmos white paper; IBC documentation.
BoundaryEstablishes formal autonomy and interoperation, not later governance stress.
Current operator docs; recurring subsidy requests
Relayer continuity burden
Source classOperator documentation and governance records.
Public sourcePolkachu gm-ibc; Polkachu relayer inventory; Cosmos Hub Proposal 862; Persistence Proposal 97.
BoundaryShows continuity work outside the strongest formal layer, not a complete subsidy model.
Proposal 790; Gaia v12 / Proposal 821
LSM formal governance path
Source classGovernance record and module documentation.
Public sourceProposal 790; Cosmos Hub liquid staking module.
BoundaryShows that LSM moved through formal governance, not the whole later disclosure controversy.
Proposal 787, 2023 governance cycle
ICF transparency demand
Source classGovernance record and forum record.
Public sourceProposal 787; Cosmos forum thread.
BoundaryShows a public transparency demand, not an adjudicated finding of liability or misconduct.
Proposal 952, 2024 governance cycle
ICF no-confidence and reporting demand
Source classGovernance record and forum record.
Public sourceProposal 952 forum record; Polkachu vote record.
BoundaryShows a no-confidence and reporting-demand episode, not a late-stage LSM proposal.
2024 annual report; January 2026 snapshot
ICF reporting response
Source classFoundation disclosure.
Public sourceICF annual report; ICF treasury snapshot.
BoundaryShows a reporting reset and continuing snapshot practice, not a full independent audit.
November 2023; February 2024; 2025
AtomOne / GovGen counter-design
Source classProject materials and governance record.
Public sourceGovGen launch material; AtomOne constitution; constitution ratification record.
BoundaryShows constitutional counter-design, not long-run comparative success.
The sequence would weaken if the public record showed that route continuity, reporting, monitoring, and constitutional redesign were isolated adjacent episodes, with no recurrence as architecture-produced burdens. It would also weaken if later evidence showed that comparable sovereignty-first ecosystems absorbed the same stresses through protocol-level mechanisms without relying on residual institutions.
The behavioral boundary is observable exit and voice. Loyalty is treated more cautiously as an institutional achievement inferred from patterns of alignment, public trust, and continued participation; no psychological measurement is attempted.
4. Sovereignty and Residual Interdependence
Cosmos formalizes sovereignty at the chain layer. That is the beginning of the story, not the end. Interoperability depends on relayers, route continuity, governance-mediated upgrades, and counterpart coordination. These are not small details. They are the operational conditions under which sovereign interoperability works at all.
The evidence is concrete. Public relayer operators document extensive unpaid or under-subsidized maintenance burdens. Polkachu reports operating dozens of relayer hubs and hundreds of IBC relay channels. Its gm-ibc documentation states plainly that every relayer ends up maintaining its own infrastructure and that channels can remain broken before anyone notices. Governance subsidy requests reinforce the same point. Cosmos Hub Proposal 862 (Cosmos Hub Governance 2023) sought an 8,000 ATOM fee-grant subsidy for relayer gas after fee increases. Persistence Proposal 97 (Persistence Governance 2024) sought roughly 40,113 XPRT for a two-month relayer service commitment across ten chains with a 99 percent service target. Interoperability depends on material ecosystem labor.
The economic structure of that labor is constitutive of the argument and bears its own analytical weight. Route continuity creates ecosystem-wide value, but the costs appear in operator-specific form: infrastructure upkeep, gas expenditure, monitoring time, upgrade coordination, and response capacity when channels fail. Benefits are diffuse across chains and users; costs are concentrated in the organizations that keep routes live. That is why subsidy politics recur. The architecture creates a maintenance function with public-good characteristics but does not embed a strong automatic financing mechanism for it. Institutional completion therefore has a fiscal dimension as well as a governance one.
Nabben’s language of self-infrastructuring (Nabben 2023) is useful here. Cosmos continuously rebuilds the maintenance conditions that make its interchain protocol meaningful in practice. Route continuity, client upgrades, fee markets, and relayer persistence are part of the governance problem even when they are not coded as governance modules.
Interchain Security was the most explicit attempt to formalize some of this dependence more strongly. Cosmos therefore recognized that sovereignty without stronger attachment mechanisms carried limits. By 2026, ICS reads less as stable institutional completion than as a limited counter-design whose replicated-security path had lost momentum. The exit of early consumer arrangements, the migration of others, and Gaia’s disabling of new consumer-chain creation all suggest that the attempt did not become the durable solution its advocates hoped for. The residual burden returned elsewhere.
5. Governance Stress and Institutional Failure
5.1. ICF stewardship and reporting
The first stress cluster concerns foundation stewardship and reporting. The record is stronger than a minimal stewardship reading would suggest. Cosmos Hub Proposal 787 demanded fuller financial transparency from the Interchain Foundation. Leadership turnover then unfolded across Ethan Buchman, Brian Fabian Crain, and Josh Cincinnati. Public statements from the new leadership described the period as a leadership crisis and treated the disclosure conflict as symptomatic of deeper institutional disorder. The later Treasury Snapshot series beginning in August 2024 did not erase the episode. It marked an attempt to rebuild reporting credibility after trust had already been damaged.
Treasury stewardship is one of the residual functions a sovereignty-first architecture leaves outside its strongest formal commitments. When reporting becomes irregular, the architecture does not supply an automatic repair path. The repair must be institutional and political.
5.2. The LSM crisis
The liquid-staking-module crisis made the monitoring problem visible in sharper form. The issue extended beyond module design. It included provenance, audit sequence, disclosure timing, engineering-process trust, and the governance implications of learning later that governance participants had worked with an incomplete record. Public disclosure in October 2024 reopened questions about what was known, when it was known, and how those facts should have entered the 2023 proposal process: All in Bits disclosed that developers later linked to North Korea had contributed much of the module’s code and that associated security and provenance concerns had not been surfaced before the Gaia v12 governance process (All in Bits 2024; Decrypt 2024). The episode therefore converted monitoring itself into a contested governance object.
That distinction matters. The claim does not require every factual dispute to be conclusively resolved. It requires evidence that Cosmos relied on residual institutions to perform disclosure, monitoring, and trust-production work, and that those institutions came under visible stress. On that point, the public record is strong.
5.3. Proposal sequence and voice under stress
The proposal sequence still matters, but it has to be described correctly. Proposal 790 and Proposal 821 reflect the formal governance pathway through which the LSM and associated upgrade work moved. Proposal 952 is different. It is Yu’s (2024) declaration of no confidence in Interchain Foundation leadership and a call to action. Proposal 952 belongs to the broader institutional-confidence sequence, not the LSM proposal sequence. The correct analytical move is narrower and stronger: the LSM scandal and broader stewardship failures entered the same legitimacy field as the ICF no-confidence vote, showing that the stress had migrated from a technical module dispute into a wider institutional confidence problem.
This is the Hirschman point. Formal voice remained active. Participants still voted, still organized, still argued. Voice had become a site for conflict over whether the institutions carrying residual governance work still deserved confidence. That is different from saying the chain stopped governing. It means governance was active under damaged institutional conditions.
6. Helmke-Levitsky and Ostrom in the Cosmos Case
Helmke-Levitsky supplies the coding discipline for residual institutions, and Ostrom supplies the diagnostic for governance functions the architecture weakly supports.
The Helmke-Levitsky assignments depend on two questions: whether the informal or off-chain practice converges with the formal institution’s purpose, and whether the formal institution is effective enough to do the work on its own. Complementary relations support effective formal rules. Accommodating relations work around formal rules while continuing to use them. Competing relations pull against formal outcomes and weaken the formal process’s capacity to generate trusted decisions. Substitutive relations supply a function that the formal architecture needs but has left institutionally incomplete.
Complementary informal institutions appear where validator coordination, relayer operation, and conference-centered discussion reinforce formal governance. Accommodating institutions appear where lobbying, coalition-building, and off-chain pressure shape formal outcomes without openly contesting formal rules. Competing institutions are most visible in the LSM crisis, where informational and trust conflicts cut against the effectiveness of the formal process itself. Substitutive institutions appear where the Interchain Foundation, relayer operators, and other ecosystem bodies perform tasks the architecture cannot complete by itself.
These categories are adversarially reassignable if left undefended, so their value depends on assignment discipline. The ecosystem simultaneously exhibits multiple formal-informal relations, and that coexistence is analytically consequential.
The assignments are strongest when tied to specific formal rules. Validator and relayer coordination are complementary because they help the existing governance and interoperability rules work as intended. Coalition-building around proposals is accommodating because it operates through the formal process while reshaping its practical use. The LSM controversy is competing because the informational conflict damaged the capacity of the formal process to generate trusted outcomes. Interchain Foundation stewardship and relayer subsidy arrangements are substitutive because they perform monitoring, treasury communication, and continuity functions the architecture does not itself specify in enforceable protocol form.
The process tracing is strongest when each assignment is tied to a visible formal surface. Complementary relations attach to IBC continuity and governance execution rules that still require operators to keep channels live in practice. Accommodating relations attach to proposal-centered voice, where coalition building and conference politics influence outcomes without replacing voting itself. Competing relations attach to the 790-821-952 sequence, where the formal governance path remained available but confidence in the information entering that path became a contested object. Substitutive relations attach to stewardship and continuity functions visible in the Treasury Snapshot repair effort and relayer-subsidy proposals such as Cosmos Hub Proposal 862 and Persistence Proposal 97, where actors supplied monitoring and maintenance work that the architecture did not fully constitutionalize.
Ostrom sharpens the same diagnosis from another angle. Cosmos strongly supports rights to organize and nested enterprises. It only partially supports boundaries, congruence, and collective choice in the Ostromian sense. Monitoring, graduated sanctions, and conflict resolution remain the weakest points. This distribution is exactly what the institutional-completion argument predicts: the architecture formalizes sovereignty-supporting principles more strongly than crisis-management and stewardship principles.
7. AtomOne as Design-Level Counter-Design
AtomOne should not be treated as an already completed falsification test. It is too young for that. The right use is design-level comparison.
On that level, AtomOne is extremely informative. The relevant dates and terms matter. The airdrop snapshot belongs to November 25, 2023, not January 2024. GovGen’s governance-chain launch is a separate February 27, 2024 event. The mainnet token is ATONE, not the earlier provisional ATOM1 label. Its constitutional design is central to the comparison. Ordinary supermajority and constitutional-majority thresholds are not the same thing, and the latter sits above 90 percent, beyond two-thirds or three-quarters.
Those specifics matter because AtomOne’s design constitutes a systematic formalization of the monitoring, agenda control, constitutional amendment, and oversight functions that Cosmos Hub governance was perceived to leave too informal. That makes AtomOne a design-level counter-design to the institutional-completion problem. The available time horizon is too short to claim long-run comparative success or failure. The design still shows what some actors inside the ecosystem thought had to be constitutionalized if the same pattern was to be avoided.
The causal linkage also has to be stated carefully. The October 2024 disclosure controversy post-dates AtomOne mainnet, so the claim cannot be a direct scandal-to-design sequence. The tighter claim is that visible governance stress around monitoring, stewardship, agenda discipline, and legitimacy helped shape the counter-design, while later disclosures amplified an existing sense that institutional safeguards had been inadequate.
AtomOne is too young to function as a completed stress-pattern falsification test at a 24-to-36-month horizon. It can function as a design document written in institutional form. As such, it reveals which missing functions participants believed needed stronger constitutional treatment.
8. Falsification, Alternatives, and Scope
The central claim would weaken under three conditions.
First, it would weaken if comparable sovereignty-first ecosystems repeatedly sustained contested governance without relying on significant residual maintenance, monitoring, or legitimacy work outside the coded layer. Second, it would weaken if IBC continuity and route maintenance turned out to be operationally trivial and institutionally light. Third, it would weaken if later evidence showed that formal constitutional redesign in AtomOne produces no meaningful difference at all in how governance stress is metabolized over time.
Alternative explanations still deserve engagement. Founder politics plainly matter. Market conditions matter. External regulation matters at the margin. Those explanations do not replace the institutional-completion argument because they do not explain why these particular sites of weakness, monitoring, stewardship, relayer continuity, and governance legitimacy, became so load-bearing in a sovereignty-first architecture.
The scope is deliberately narrow: a Cosmos-specific paper with bounded implications for other sovereignty-oriented systems. The mechanism addresses cases where a blockchain ecosystem formalizes sovereignty and interoperability more strongly than monitoring and retention. In that setting, omitted work returns as residual institutional burden.
9. Conclusion
Cosmos shows that sovereignty and interdependence are not opposites. A sovereignty-first architecture can formalize autonomy while still depending heavily on residual institutions for maintenance, monitoring, legitimacy, and crisis repair.
That is the force of the institutional-completion claim. The architecture redistributes governance burden into relayers, route coordinators, foundations, public governance processes, and legitimacy-producing institutions, which become the places where the system’s stability is carried.
Put more mechanically, the sequence runs as follows. Sovereignty-first design weakens shared enforcement and shared retention at the protocol layer. That design choice pushes continuity, monitoring, and repair into actors that sit outside the strongest formal commitments. Those actors then require subsidies, legitimacy, and discretionary coordination to keep the ecosystem coherent. When any of those supports weaken, the architecture has fewer internal shock absorbers than a more vertically integrated system. Institutional completion is the name for that sequence.
The LSM crisis, the ICF no-confidence episode, and AtomOne’s constitutional redesign attempt all make the same point from different angles. Residual institutions were core supports of Cosmos governance. When those supports weakened, exit became more attractive relative to voice, and the ecosystem’s sovereignty-first character expressed itself as institutional strain.
Cosmos shows a version of residual consequence that is neither settlement concentration nor claim partitioning nor commensuration failure. It is the persistence of ecosystem maintenance and legitimacy work after sovereignty has been formalized at the chain layer. The code narrowed some commitments while leaving ecosystem maintenance and legitimacy work to residual institutions.
References
All in Bits. 2024. "On the LSM Module." October 15, 2024. https://github.com/allinbits/announcements/blob/main/2024_10_15_lsmnk.md.
Allen, Darcy W. E., Chris Berg, and Sinclair Davidson. 2023. "The Governance of Cosmos Interchain Security." RMIT Blockchain Innovation Hub working paper. SSRN. https://papers.ssrn.com/sol3/papers.cfm?abstract_id=4638119.
Atik, Jeffery, and George Gerro. 2018. "Hard Forks on the Bitcoin Blockchain: Reversible Exit, Continuing Voice." Stanford Journal of Blockchain Law and Policy 1(1).
AtomOne. n.d. "Constitution." Accessed May 4, 2026. https://github.com/atomone-hub/genesis/blob/main/CONSTITUTION.md.
AtomOne Valopers. 2025. "Constitution Proposal Ratification." Proposal 2. Accessed May 4, 2026. https://atomone.valopers.com/proposals/2.
Berg, Alastair, and Chris Berg. 2020. "Exit, Voice, and Forking." Cosmos + Taxis 8(8-9): 76-89.
Davidson, Sinclair, Primavera De Filippi, and Jason Potts. 2018. "Blockchains and the Economic Institutions of Capitalism." Journal of Institutional Economics 14(4): 639-658.
De Filippi, Primavera, and Benjamin Loveluck. 2016. "The Invisible Politics of Bitcoin: Governance Crisis of a Decentralised Infrastructure." Internet Policy Review 5(3).
Decrypt. 2024. "Developers Linked to North Korea Helped Develop Cosmos Staking Module, Says Co-Founder." October 16, 2024. https://decrypt.co/286539/developers-linked-to-north-korea-helped-develop-cosmos-staking-module-says-co-founder.
George, Alexander L., and Andrew Bennett. 2005. Case Studies and Theory Development in the Social Sciences. Cambridge: MIT Press.
Gerring, John. 2007. Case Study Research: Principles and Practices. Cambridge: Cambridge University Press.
Hassan, Samer, and Primavera De Filippi. 2021. "Decentralized Autonomous Organization." Internet Policy Review 10(2).
Helmke, Gretchen, and Steven Levitsky. 2004. "Informal Institutions and Comparative Politics: A Research Agenda." Perspectives on Politics 2(4): 725-740.
Hirschman, Albert O. 1970. Exit, Voice, and Loyalty: Responses to Decline in Firms, Organizations, and States. Cambridge: Harvard University Press.
Cosmos Hub Forum. 2023. "Formally Request Full Financial Transparency from the Interchain Foundation." Posted March 1, 2023. https://forum.cosmos.network/t/formally-request-full-financial-transparency-from-the-interchain-foundation/10002.
Cosmos Hub Governance. 2023. "Proposal 787: Formally Request Full Financial Transparency from the Interchain Foundation." Mintscan. Accessed May 14, 2026. https://www.mintscan.io/cosmos/proposals/787.
Cosmos Hub Governance. 2023. "Proposal 790: Liquid Staking Module." Mintscan. Accessed May 14, 2026. https://www.mintscan.io/cosmos/proposals/790.
Cosmos Hub Governance. 2023. "Proposal 821: Gaia v12 Upgrade (Software Upgrade)." Submitted August 25, 2023. https://forum.cosmos.network/t/proposal-821-passed-gaia-v12-upgrade/11366.
Cosmos Hub Governance. 2023. "Proposal 862: Cosmos Hub IBC Relayer Gas Cost Restitution Using FeeGrants." Accessed May 17, 2026. https://www.mintscan.io/cosmos/proposals/862.
Cosmos Hub Documentation. n.d. "On-Chain Proposal Process." Accessed May 4, 2026. https://docs.cosmos.network/hub/latest/governance/process.
Cosmos Hub Documentation. n.d. "x/liquid." Accessed May 4, 2026. https://docs.cosmos.network/hub/latest/modules/liquid.
Cosmos Hub Documentation. n.d. "Cosmos SDK LSM." Accessed May 4, 2026. https://docs.cosmos.network/hub/v25/modules/lsm-migration.
Yu, Grace. 2024. "Declaration of No Confidence in ICF Leadership & Call to Action." Cosmos Hub governance discussion thread. https://forum.cosmos.network/t/proposal-952-passed-declaration-of-no-confidence-in-icf-leadership-call-to-action/14233.
Kwon, Jae, and Ethan Buchman. 2016. Cosmos Whitepaper: A Network of Distributed Ledgers.
Interchain Standards. n.d. "ICS 18: Relayer Algorithms." Accessed May 17, 2026. https://github.com/cosmos/ibc/blob/main/spec/relayer/ics-018-relayer-algorithms/README.md.
Morrison, R. M., N. C. H. Mazey, and G. M. Wingreen. 2020. "The DAO Controversy: The Case for a New Species of Corporate Governance?" Frontiers in Blockchain 3:25.
Murtazashvili, Ilia, Jennifer Brick Murtazashvili, Martin Weiss, and Michael Madison. 2022. "Blockchain Networks as Knowledge Commons." International Journal of the Commons 16(1): 108-119.
Nabben, Kelsie. 2023. "Web3 as 'self-infrastructuring': The Challenge Is How." Big Data & Society 10(1).
Interchain Foundation. 2024. "Annual Report 2023, and Beyond." Medium. Accessed May 4, 2026. https://medium.com/the-interchain-foundation/annual-report-2023-and-beyond-616d22dce090.
Interchain Foundation. 2026. "ICF Treasury Snapshot: January 2026." Medium. Accessed May 4, 2026. https://medium.com/the-interchain-foundation/icf-treasury-snapshot-january-2026-70a0925ef7ea.
Polkachu. 2024. "Prop 952: Declaration of No Confidence in the Interchain Foundation (ICF) Leadership: A Call to Action." Accessed May 4, 2026. https://www.polkachu.com/gov_proposals/4215.
Polkachu. n.d. "IBC Relaying." Accessed May 17, 2026. https://www.polkachu.com/relayers.
Polkachu. n.d. "gm-ibc README." Accessed May 4, 2026. https://github.com/polkachu/gm-ibc.
Persistence Governance. 2024. "Proposal 97: Extension of CryptoCrew’s IBC Relayer Service Mandate for 2 Months." Accessed May 17, 2026. https://persistence.valopers.com/proposals/97.
Nyman, Linus, and Juho Lindman. 2013. "Code Forking, Governance, and Sustainability in Open Source Software." Technology Innovation Management Review 3(1): 7-12.
Ostrom, Elinor. 1990. Governing the Commons: The Evolution of Institutions for Collective Action. Cambridge: Cambridge University Press.
Rozas, David, Antonio Tenorio-Fornes, Silvia Diaz-Molina, and Samer Hassan. 2021. "When Ostrom Meets Blockchain: Exploring the Potentials of Blockchain for Commons Governance." SAGE Open 11(1).
RoboMcGobo. 2026. "Remove ICS from the Cosmos Hub (Software Upgrades to Follow)." Cosmos Hub Forum. Accessed May 4, 2026. https://forum.cosmos.network/t/remove-ics-from-the-cosmos-hub-software-upgrades-to-follow/16682.
Williamson, Oliver E. 1985. The Economic Institutions of Capitalism: Firms, Markets, Relational Contracting. New York: Free Press.
Vatiero, Massimiliano. 2022. "Smart Contracts vs Incomplete Contracts: A Transaction Cost Economics Viewpoint." Computer Law & Security Review 46: 105710.