Blockdaemon provides node and validator infrastructure. We participate selectively in governance only where needed to support protocol security, safety, liveness, and reliable validator operation.
Blockdaemon will not (except for certain limited proposals described below) propose, sponsor, endorse, solicit support for, campaign on, delegate voting power for, or vote on (collectively, “Actively Support”) any proposal whose purpose or effect, in whole or part, is to authorize, direct, allocate, distribute, invest, or otherwise determine use of protocol-, DAO-, foundation-, community-pool-, or project-level funds or assets.
This includes proposals representing the following (although not exhaustive):
This rule applies regardless of proposal label, forum, or voting mechanism, including on-chain votes, off-chain signaling, temperature checks, and delegated voting.
Blockdaemon may submit or make proposals requesting a grant from a protocol's, DAO's, foundation's, or community pool's treasury or grant program (collectively, the “Grantor”), for Blockdaemon's own initiatives as may be required by the Grantor. This limited exception permits only the act of submitting or making such a grant proposal. Blockdaemon will not Actively Support any such grant proposal, and will otherwise remain subject to this Section 1.
Blockdaemon may participate in governance only where a proposal is limited to technical and operational matters necessary for protocol safety or validator continuity, including security incident response, consensus safety, network liveness, validator operations, and non-financial technical upgrades.
Blockdaemon will not participate where an operational or technical proposal is bundled with, or materially affects, funding, treasury use, compensation, asset allocation, or another matter listed in Section 1. This includes a proposal that would alter, directly or incidentally, token supply, fee structures, reward or emissions rates, slashing parameters with material economic effect, or any other matter listed in Section 1.
Blockdaemon has no obligation to vote on any proposal. Blockdaemon’s default position will be to abstain. Blockdaemon will participate only where a proposal clearly falls within Section 2.
This policy governs Blockdaemon's discretionary governance activity. Where customers delegate voting power to Blockdaemon as part of staking or infrastructure arrangements, Blockdaemon will exercise such delegated voting rights consistent with this policy. This policy does not amend applicable customer agreements or protocol mechanics governing delegation, withdrawal, or customer voting rights.
Blockdaemon may update this policy as legal, regulatory, protocol, or operational conditions change.