Proof of Working 2.15

by

COZ Council

14 October 2026

Proof of Working 2.15 recognizes ecosystem contributions to Neo Quorum Watch for governance transparency and Pusharoo for multi-wallet contract release management.

COZ primarily operates through the community Discord and COZ GitHub, central places where contributors share progress, collaborate in public, and turn ideas into working ecosystem tools.

Governance

There is no formal process for joining COZ. Interested contributors have to do the work first, and submitted code must be licensed under the Apache 2.x License. Consistent contributors can become eligible to join the COZ organization and collaborate more directly across projects.

Organizational decision making is made collaboratively by the COZ Council, a multi-disciplinary body of platform and functional leads, and communicated by an appointed member holding the Speaker role.

COZ is not a regulatory body and takes no responsibility for the quality of third-party smart contracts deployed on affiliate platforms.

Funding Pool

COZ staff members are excluded from weekly rewards.

This week, we are awarding 277 NEO distributed across the following ecosystem contributions:

Award Proof: Transaction

Why this round matters

Proof of Working 2.15 focuses on two pillars of decentralized ecosystem maturity: transparent on-chain governance analytics and team-safe smart contract deployment workflows.

Both contributions solve real operational friction. Neo Quorum Watch establishes an independent, verifiable record of Council governance decisions, while Pusharoo provides structured, multi-wallet release controls so development teams can deploy safely across test and production networks.

  • Neo Quorum Watch (Fritzorama):

    Neo Quorum Watch is an open-source, independent dashboard designed to make Neo Council governance participation transparent, traceable, and straightforward to verify.

    The dashboard tracks the active 21-member Council roster by Neo N3 public key, aggregates governance voting records linked directly to individual proposals, and reconstructs historical Council eligibility to evaluate participation accurately against who was eligible when proposals opened. The pipeline enforces fail-closed validation when identities, vote tallies, or historical attributions cannot be verified, operating across distinct development and production environments.

    This matters because decentralized governance requires transparent, verifiable participation records. By providing verifiable, proposal-linked voting metrics, Neo Quorum Watch helps the community evaluate Council activity and identify participation gaps with confidence.
  • Pusharoo — Wallet-Secured Contract Release Workspace (Vault Keeper):

    Pusharoo continues to evolve as a dedicated smart contract release and operations workspace for managing artifacts, deployments, upgrades, recovery, and contract interactions. This round introduces collaborative deployment permissions for teams operating across multiple networks.

    Project owners can authorize specific deployment wallets with granular permissions restricted to TestNet, MainNet, or both. Permissions are verified server-side based on the connected wallet and active network, allowing teams to use separate testing and production keys without duplicating projects or fracturing release histories. Sensitive project settings remain owner-restricted.

    This matters because team-based smart contract operations require safe multi-wallet workflows. Enforcing network-specific deployment authorization prevents accidental production releases while maintaining strict key custody.

By removing friction from governance auditing and contract release pipelines, these tools help make building and participating in the Neo ecosystem more reliable.

What this round adds up to

At a higher level, sustainable blockchain ecosystems depend on tooling that increases visibility and strengthens operational safety. Clear governance records hold leadership accountable, while scoped deployment authorization protects live protocols from operational mistakes.

Independent analytics and developer release management reinforce each other to build long-term confidence across the network.

If you want to understand the broader purpose of the initiative, read Proof of Working Is Back or explore recent updates in Proof of Working 2.14.

Get involved

If you are building useful Neo ecosystem tooling, improving documentation, maintaining SDKs, or helping make applications easier to use, bring the work into the open and share it with the community. Proof of Working exists to recognize public contributions that make the ecosystem stronger.