COZ distributed 303 NEO across two developer contributions in Proof of Working 2.11, recognizing improvements to Python wallet tooling and a contract deployment workspace. Both contributors, CLAUS and Vault Keeper, are returning participants whose work has been recognized across multiple rounds of the program.

The two projects share a common thread: strengthening operational evidence in the developer workflow. Where CLAUS extends the tooling developers use to interact with wallets and transactions, Vault Keeper tightens the process of deploying and managing smart contracts on-chain.

neo-n3-wallet v0.2.0

CLAUS was recognized for v0.2.0 of the neo-n3-wallet Python library, which was first introduced in round 2.10 as a standalone account infrastructure library for Neo N3 applications.

The update adds off-chain message signing and verification through initial local helpers, mnemonic-first wallet creation via a new Wallet.from_mnemonic() method, DeferredRelay attribute construction for upcoming protocol work, and a simplified transaction fee estimator. Automated test coverage expanded from 142 to 149 tests.

CLAUS has been a consistent Python tooling contributor since round 2.3, when work on the NeoFS Python SDK was first recognized. Subsequent rounds have seen contributions to the NeoFS SDK, Nanvil development environment integrations, and now the neo-n3-wallet library, collectively broadening the Python toolchain available to Neo N3 developers.

Pusharoo deployment workspace

Vault Keeper contributed wallet-secured deployment workspace improvements to Pusharoo, the contract management platform first recognized in round 2.9. Where previous work added an event relay service for forwarding contract activity to external systems via webhooks, this round’s contribution focuses on trust and verification in the deployment workflow itself.

The update introduces wallet-signed project management with creator-bound controls for project and artifact handling. Backend signature validation ensures that management actions are cryptographically tied to the project owner. Neo RPC deployment checks now verify on-chain status before creating deployment records, and an interactive console with decoded VM output gives developers clearer visibility into contract behavior during and after deployment.

The practical effect is that release workflows gain stronger operational evidence, checking project ownership and deployment records against wallet and on-chain activity rather than relying on manual assumptions.

Cumulative totals

Since its January 2026 relaunch, the Proof of Working program has distributed 6,311 NEO to community contributors across 11 rounds. COZ staff members are excluded from weekly rewards, but consistent open-source code contributors are eligible to join COZ.

The full announcement can be found at the link below:
https://coz.io/blog/proof-of-working-2-11/

Tags: ,