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

Award Proof: Transaction

Proof of Working 2.8 highlights progress across five practical layers: safer contract deployment workflows, stronger community coordination, faster application onboarding, more usable storage tooling, and maintained SDK infrastructure.

The projects in this round are different in form, but they all reduce friction. Some help developers see contract changes before deployment. Some help users and builders coordinate. Others give teams templates, command-line tools, shells, and updated SDKs that make decentralized infrastructure easier to adopt.

• Pusharoo — Contract Artifact Management (Vault Keeper):
  
  Pusharoo gives smart contract teams a clearer way to organize, inspect, and compare deployment artifacts before they are pushed on-chain. The platform supports project creation, .nef and manifest JSON uploads, artifact storage with timestamps and summaries, detailed manifest review across methods, events, permissions, and raw JSON, and version comparison tools that highlight added, removed, and modified contract functionality.
  
  This matters because contract deployment is a high-consequence workflow. Better artifact visibility helps builders understand what changed, review what they are about to publish, and reduce avoidable mistakes before code reaches a live network.
• Neo Vision — Community Coordination Hub (aziz168):
  
  Neo Vision continues building a community-driven Discord hub and ecosystem platform for users, developers, projects, and traders. The effort combines ecosystem news, educational resources, project discovery, custom bots, event hosting, community support, engagement initiatives, and a World Cup 2026 prediction system with rankings and rewards. You can follow the project through the NeoVision Discord and NeoRedPill on X.
  
  This matters because healthy blockchains need more than code. They also need places where people can learn, coordinate, discover projects, ask questions, and stay engaged long enough to become active participants.
• neow3j-react-starter — Full-Stack dApp Template (fireche):
  
  neow3j-react-starter packages a practical full-stack starting point for building smart contract applications with Java contracts, a React/Vite frontend, wallet integrations, agent-ready documentation, neow3j reference material, testing guidance, and security resources. The template brings contract, frontend, wallet, documentation, and review practices into one place so builders and AI coding assistants can start from a stronger baseline.
  
  This matters because onboarding friction is one of the biggest barriers to application development. A good starter template compresses setup time, exposes recommended patterns early, and helps teams move from idea to working prototype with fewer missing pieces.
• NFS and neofs-sdk-zig — Storage CLI, Shell, and SDK (Merl):
  
  NFS extends the Zig NeoFS tooling effort with a command-line client and interactive shell for decentralized object storage workflows. Alongside continued development of neofs-sdk-zig, the work adds bug fixes, new SDK functionality, a practical terminal interface, and a real-world usage path for storage operations.
  
  This matters because storage infrastructure becomes more useful when developers and operators have both libraries and hands-on tools. SDKs help applications integrate, while CLIs and shells make the underlying system easier to explore, test, and operate.
• NeoFS Python SDK v0.3.0 (CLAUS):
  
  NeoFS Python SDK v0.3.0 keeps Python storage tooling aligned with the latest infrastructure release by updating API compatibility, adding ranged GET support for partial object retrieval, updating session token handling, removing deprecated homomorphic hash support, and moving object discovery fully to SearchV2. The SDK continues to include object lifecycle tools, ACL support, CLI utilities, and EVM funding support. The package is also available on PyPI.
  
  This matters because SDK maintenance is ecosystem infrastructure. Keeping client libraries current with network APIs protects downstream builders from drift, improves reliability, and gives application teams a more production-ready foundation for storage-backed products.

That combination matters because blockchain ecosystems become more durable when the path from curiosity to contribution is shorter and safer. Better tools make builders faster, better community surfaces keep people connected, and better maintained infrastructure gives applications a stronger foundation.

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, and Proof of Working 2.7.

At a higher level, this week’s work makes blockchain development easier to inspect, easier to coordinate, easier to start, and easier to maintain.

Together, these contributions point in a practical direction: more visible deployment workflows, stronger community infrastructure, better starter paths for applications, and storage tooling that is easier for developers and operators to use.

If you are building in public, maintaining useful tooling, publishing research, or helping move the ecosystem forward in concrete ways, join the conversation in the COZ Discord, share your work on GitHub, and take part in the next round of contributions.