At Govmos, we appreciate the thoughtful proposal around Replicated Blockspace (PB) and commend your effort to frame it as a modular and accessible offering for future network participants. We recognize the importance of developing systems that offer plug-and-play infrastructure, and your contribution to this dialogue is both valuable and timely.
As part of our mandate from the AADAO, we conducted an in-depth analysis of ICS 2.0 and its Partial Set Security (PSS) model. This has led us to believe that much of what PB seeks to achieve is already embedded—and arguably improved—within the architecture of PSS. For more context, we encourage readers to explore our comprehensive breakdown available here:
ICS 2.0 Economics – Partial Set Security (PSS) Financial Model
1. PSS Top-N – Cost-Efficient and Accountable Execution Replication
The Top-N mechanism in PSS mirrors the intent behind your replicated execution model but does so with added elegance and efficiency. Rather than relying on full validator set replication—which brings heavy infrastructure costs—PSS allows governance to define a targeted subset of top validators responsible for chain operation.
This model reduces cost, enforces accountability via slashing, and addresses key challenges seen in real deployments like Neutron, where centralized validators often failed to meet upgrade standards. With PSS, those same validators would be economically incentivized to improve—or risk being replaced through natural stake migration.
2. PSS Opt-In – Fully Customizable Blockspace-as-a-Service
We are fully aligned with your vision of offering blockspace-as-a-service to both public and private clients. The Opt-in model in PSS allows applications to handpick their preferred validator sets and fine-tune their own parameters for execution, slashing, rewards, and more.
“PB must be accessible, simple, and plug-and-play—any organization should be able to launch its own chain in just a few clicks.”
You’re absolutely right to highlight usability as a barrier. That’s precisely the role of Forge, the PSS companion platform currently under development. While still in its early stages, Forge has been designed to deliver on your vision of a seamless, low-friction deployment experience. It’s fair to say that a true “Forge Endgame” will take time—but it’s well underway.
“In short, PB aims to be an all-in-one solution, a ‘Forge Endgame.’”
We commend the ambition and clarity in your articulation of PB’s goals. We simply want to emphasize that PSS was built to address these same issues with more composability, deeper customization, and a modular architecture that futureproofs shared security across many chain types and use cases.
Final Thoughts
Your proposal reflects a strong understanding of the needs ahead, and your conclusions are sound. The good news is that PSS already integrates many of your core ideas, and it does so in a way that’s fundamentally more flexible and aligned with Cosmos’ modular ethos.
The slow initial adoption of both RS and PSS should not be mistaken for lack of product-market fit. We believe it’s a matter of timing, tooling, and education. With continued development and the maturing of Forge and other deployment tools, the true value of PSS will soon become more evident.
Thank you again for sparking this conversation.
Govmos
