Validators are often described in purely operational terms — uptime, signing, missed-block rate. Those numbers matter, but they are only half of what a validator actually does for a chain. The other half is governance. Every proposal that touches consensus, economics, treasury or upgrades passes through validator votes, and the quality of those votes shapes the chain as much as any patch release.
NodeStake is an institutional-grade validator. We are also a community-trusted validator on every chain we secure. We take that responsibility seriously — and the most visible expression of it is how we treat every on-chain proposal.
Governance is part of the job
When delegators choose a validator, they are not just outsourcing a signing key. They are delegating governance voice. A delegator who cares about a chain's direction needs a validator who actually reads proposals, weighs trade-offs, and votes — not one that abstains by default or rubber-stamps whatever the foundation puts forward.
We treat every proposal on every chain we validate as something that deserves real attention. That means reading the proposal text in full, reviewing forum and Discord discussion, checking the technical changelog where one exists, and forming an explicit position before the vote closes. "We didn't get to it in time" is not an acceptable answer for an operator at our scale.
Listening to the community
Good governance does not happen in private. We make a deliberate effort to listen before we vote — across forum threads, governance calls, validator working groups, and direct conversations with delegators and protocol teams. Our delegators have meaningful skin in the game, and their views inform how we think about each vote.
When a proposal is genuinely contested, we say so. When we disagree with the foundation or the proposer, we say so — publicly, with reasoning. When we are persuaded by community feedback to change a position, we say that too. Governance only works if validators behave as accountable participants, not as silent rubber stamps.
Promoting ecosystem development
Validator influence does not stop at the vote. We use our position to actively promote the health of the ecosystems we are part of:
- Engaging with proposers early — flagging issues at the draft stage rather than at the vote, when the cost of a fix is much lower.
- Funding and contributing to public goods — public RPC endpoints, snapshots, IBC relayers, explorers and tooling that the chain depends on but no single party owns.
- Supporting builders — making time for new teams shipping on the chains we secure, helping with infrastructure questions, and amplifying credible launches.
- Sharing operational knowledge — publishing post-mortems, network statistics and operator guides so the broader validator set learns alongside us.
These activities don't show up in commission, but they are how we think a serious validator earns its place in the ecosystems it participates in.
How we vote, in practice
Our internal practice on every governance vote, on every chain we secure:
- Read the proposal in full — including any linked specifications, code diffs or budget breakdowns.
- Review community discussion across forum, Discord and validator channels.
- Form an explicit position — Yes, No, NoWithVeto or Abstain — with a written reason.
- Where the proposal has economic or security consequences, require sign-off from a named engineer or operator on our team.
- Cast the vote with enough headroom before the deadline that we can change it if material new information appears.
Abstain is a legitimate vote, but it is not a hiding place. We commit to a position on any proposal that meaningfully affects the chain.
What we ask of the chains we secure
Validators are only one side of the governance contract. Chains and proposers also have responsibilities — reasonable voting windows, clear proposal structure, separable decisions instead of bundled mega-proposals, and forum discussion before on-chain submission. Where chains run governance well, we engage harder. Where they don't, we say so — both in votes and in conversation with the teams.
Our goal is straightforward: leave every chain we secure with healthier governance than we found it. That is part of what an institutional, community-trusted validator owes the networks that delegate to it.
About NodeStake
NodeStake is an institutional-grade validator and infrastructure operator running 50+ networks with $420M+ in delegated stake. Founded in 2019 with a perfect no-slashing record, we operate the full stack — validators, IBC relayers, public RPC endpoints, snapshots, and custom chain infrastructure — for protocols, foundations and institutional delegators across the Cosmos, EVM and emerging L1 ecosystems.
Website: https://nodestake.org
X / Twitter: https://x.com/NodeStake_top