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.

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.

COZ staff members are excluded from weekly rewards.

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

Award Proof: Transaction

Proof of Working 2.11 recognizes work at two practical points in the builder workflow: the wallet tooling developers use to create and prepare accounts, and the deployment workspace teams use to manage contract releases.

The common thread is stronger operational evidence. One contribution improves the Python-side wallet path around message handling, mnemonic creation, attributes, fees, and testing. The other makes project management and deployment records more accountable to wallet identity and on-chain results.

• neo-n3-wallet Python Library v0.2.0 (CLAUS):
  
  neo-n3-wallet v0.2.0 extends the Python wallet library around current node compatibility and upcoming protocol work. The update adds initial local helpers for off-chain message signing and verification, DeferredRelay attribute construction, Wallet.from_mnemonic() for mnemonic-first wallet creation, and a simplified transaction-fee estimator. It also expands automated coverage from 142 to 149 tests.
  
  This matters because Python developers need wallet tooling that stays practical as the surrounding infrastructure changes. More complete wallet creation, transaction-preparation, and test coverage help teams integrate account workflows with less custom plumbing.
• Pusharoo — Wallet-Secured Contract Deployment Workspace (Vault Keeper):
  
  Pusharoo is an open-source contract-management workspace for artifact handling, deployment, contract interaction, and deployment tracking. This round adds wallet-signed project-management checks, creator-bound controls for project and artifact management, backend signature validation, and Neo RPC deployment checks before a deployment record is created. It also adds an interactive console with decoded VM output and refines the frontend and backend workflows around contract management.
  
  This matters because release workflows become easier to trust when project ownership and deployment records are checked against the wallet and on-chain activity they are meant to represent. The result is a clearer path for teams managing contract artifacts and releases without relying only on manual tracking.

That kind of work helps reduce uncertainty around the steps that sit between writing code and operating it. Better tooling does not remove every responsibility from a team, but it gives developers clearer information to work from.

At a higher level, this round strengthens the operational layer around Neo development: preparing wallet workflows in Python, managing contract artifacts, and checking that recorded deployments match the chain activity behind them.

Together, these contributions make two common workflows easier to reason about: moving from a mnemonic to a usable wallet, and moving from a contract artifact to a deployment record that can be checked. They address different parts of the stack, but both help teams replace manual assumptions with clearer tooling.

If you want to understand the broader purpose of the initiative, read Proof of Working Is Back. You can also review previous rounds in Proof of Working 2.0, Proof of Working 2.1, Proof of Working 2.2, Proof of Working 2.3, Proof of Working 2.4, Proof of Working 2.5, Proof of Working 2.6, Proof of Working 2.7, Proof of Working 2.8, Proof of Working 2.9, and Proof of Working 2.10.

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.