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 429 NEO distributed across the following ecosystem contributions:

Award Proof: Transaction

Proof of Working 2.13 highlights progress across three distinct operational layers of ecosystem health: community discovery and education, smart contract release workflows, and decentralized storage client infrastructure.

The common thread across these contributions is lowering friction. Whether that means making news approachable through short-form video, preventing errors when deploying and recovering smart contracts, or ensuring storage client libraries stay compatible with evolving node protocols, each effort helps maintain a dependable foundation for builders and users alike.

• REDDON NEO NEWS (REDDON):
  
  REDDON NEO NEWS is a short-form video series delivering ecosystem updates through fast, one-minute YouTube Shorts led by an original animated frog anchor. The project covers current Neo ecosystem developments, project milestones, and network updates in an engaging, approachable format, publishing new episodes roughly every three days with additional distribution across Reddit, X, and Telegram. To date, the contributor has produced 67 videos.
  
  This matters because short-form, accessible educational content broadens ecosystem discovery and helps non-technical audiences stay informed about products, platform improvements, and community developments without getting lost in technical jargon.
• Pusharoo — Wallet-Secured Contract Release Workspace (Vault Keeper):
  
  Pusharoo continues to mature as a dedicated smart contract release workspace for managing artifacts, deployments, contract interactions, and operational tracking through a connected wallet. This round introduces recovery tools for contracts deployed outside Pusharoo, persistent deployment lifecycle tracking with resumable confirmation states, pre-wallet review steps prior to contract release, and wallet-confirmed project deletion. It also improves decoded contract-console output, enforces management access restrictions for non-owners, and standardizes loading, error, empty, and retry states across the interface.
  
  This matters because contract release workflows become more dependable when developers can recover existing deployments, track in-flight transactions, review operational parameters before signing, and manage contracts within a consistent, defensive interface.
• NeoFS Python SDK v0.5.0 (CLAUS):
  
  NeoFS Python SDK v0.5.0 updates the Python decentralized storage library to align with newer NeoFS API standards and REST Gateway capabilities. Following the deprecation of the legacy Search RPC on current nodes, this release restores object listing by migrating list_objects() to SearchV2 with built-in pagination. It also introduces HTTP-style byte-range downloads and supports optional comments on Extended Access Control List (EACL) records.
  
  This matters because storage-backed applications require reliable SDK maintenance as node protocols evolve. Restoring core object listing and adding range downloads ensures Python applications continue operating seamlessly against modern decentralized storage infrastructure.

These improvements help reduce operational friction across the ecosystem. When educational channels reach new audiences, developer workspaces prevent deployment misconfigurations, and core SDKs stay compatible with node upgrades, the entire network becomes easier to navigate and build upon.

At a higher level, this round reflects the variety of work needed to sustain an active decentralized ecosystem. A healthy platform requires both accessible entry points for newcomers and robust, reliable tools for technical teams operating in production.

Together, these contributions support community engagement and developer productivity in equal measure. They demonstrate that ongoing maintenance, interface polish, and creative communication are just as essential to long-term ecosystem viability as new protocol features.

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, Proof of Working 2.10, Proof of Working 2.11, and Proof of Working 2.12.

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.