NEAR’s 15 October announcement says House of Stake has approved HSP-007, replacing discretionary grants for its multi-party computation signing infrastructure with funding from protocol emissions. The project reports 17 mainnet operators as of that announcement, with capacity to fund up to 21. These are attributed project figures, not an independently measured operator census.

Chain Signatures distributes signing responsibilities across operators rather than placing the complete key with one participant. For applications relying on that service, how operators are paid is an operational issue alongside the cryptography: infrastructure needs continuing maintenance, monitoring and staffing.

Payment follows service, not merely membership

The final HSP-007 text specifies retrospective monthly compensation, offchain service-level validation and explicitly authorized onchain transfers. Payments are not an autonomous stream. The document provides for partial or complete forfeiture when uptime falls below its thresholds, plus a challenge process and public reporting.

It sets maximum allocations rather than guaranteed spending and uses a trailing price reference with compensation caps. Its older context refers to nine nodes; that should not replace the later announcement’s dated 17-operator figure. The proposal explicitly says the funding arrangement does not alter emissions rates or protocol rules.

NetNapz assessment: the reporting is the accountability test

Assessment: a standing funding framework can make infrastructure planning less dependent on repeated grant decisions. That benefit should be evaluated through delivered service, not inferred solely from governance approval. Monthly records should reconcile the eligible operator list, measured performance, reward calculations and actual transfers.

The split between offchain verification and onchain payment creates a specific review task. A visible transfer can establish that money moved, but it cannot by itself establish that the underlying uptime calculation was correct. Reviewers need enough methodological detail to reproduce the calculation and understand any dispute. This is an accountability requirement, not evidence that an operator or administrator has acted improperly.

More funded operators may broaden participation, but the count alone does not settle independence. Geographic, hosting, organizational and software dependencies also matter. Likewise, paying for availability cannot guarantee that every signature request succeeds or remove the possibility of implementation defects.

Separate this from the issuance-cut debate

Assessment: allocating existing protocol resources and changing the rate at which tokens are issued are different decisions. The separate NEAR issuance-cut draft covered by NetNapz should not be presented as implemented by this funding announcement. Neither a budget authorization nor an operator payment demonstrates incremental token demand or a price benefit.

Sources and verification limits

NEAR announcement, 15 October 2026; HSP-007 final text. Checked 17 October. Approval and operator status are attributed to NEAR; NetNapz has not independently verified the vote tally, queried the signer contract, audited the implementation or reconciled monthly payments. This report does not establish completion of every administrative milestone.