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

Award Proof: Transaction

Proof of Working 2.9 highlights progress across six practical layers: making governance and development activity easier to follow, improving vesting usability, simplifying wallet integration, strengthening deployment workflows, accelerating local smart contract development, and making contract events easier to monitor.

The projects in this round are different in shape, but they all reduce friction around real work. Some help people understand what is happening across GitHub. Some make token vesting clearer and safer to test. Others improve wallet integration, deployment review, local development, and live debugging.

• Gasetta — AI-Summarized Neo Development Dashboard (fireche):
  
  Gasetta gives the Neo community an AI-assisted way to follow development activity across the Neo project organization. The dashboard summarizes issues, pull requests, discussions, and releases, highlights consensus and key decisions from long GitHub threads, surfaces Founder Spotlight comments, separates N3 and N4 activity, and supports cross-repository filtering with Hot, New, and Most Discussed views.
  
  This matters because open-source development is easier to trust when the conversation is easier to follow. By making technical discussions more readable, Gasetta helps developers, contributors, and community members stay informed without having to manually read every thread across the organization.
• NeoVest Updates + TestNet — Vesting UX and Public Testing (fireche):
  
  NeoVest continued improving its token vesting experience with more accurate balances, claim amounts retrieved from on-chain data, a better wallet account selector, richer vesting displays with progress bars and timestamps, revoke-status visibility, and a public TestNet deployment for end-to-end validation.
  
  This matters because vesting tools ask users to trust timelines, balances, and unlock states. More accurate data presentation improves confidence, while a public TestNet gives projects and users a safer place to validate behavior before relying on a production deployment.
• Neo N3 WalletKit — Framework-Independent Wallet Integration (Vault Keeper):
  
  Neo N3 WalletKit packages wallet connectivity and smart contract interaction into a framework-independent TypeScript toolkit for frontend applications. It supports WalletConnect, NeoLine, and OneGate, provides shared APIs for wallet connections and contract calls, handles both read-only interactions and signed transactions, includes React and Angular example projects, and is published as an npm package for easier adoption.
  
  This matters because wallet integration is one of the first real hurdles for dApp teams. A consistent toolkit lets developers support multiple wallet providers through a shared interface and build application flows faster without rewriting the same connection logic for each frontend stack.
• Pusharoo — Browser-Based Smart Contract Artifact Management (Vault Keeper):
  
  Pusharoo expands the smart contract deployment workflow into a browser-based artifact management platform. It supports uploading compiled contract artifacts and manifest files, integrates WalletKit for wallet connectivity, enables browser-based contract deployment and updates, tracks deployment history and confirmation status, and includes artifact comparison, manifest analysis, and version management tools.
  
  This matters because deployment is not just a command; it is a review process. Better artifact comparison, manifest visibility, and deployment history help developers understand what they are publishing, reduce avoidable mistakes, and maintain contracts with more confidence.
• Nanvil — Local Neo Development Environment (Merl):
  
  Nanvil provides a local blockchain development environment for building and testing smart contracts. It launches a local single-validator blockchain with prefunded test accounts, supports optional MainNet and TestNet forking, includes developer-focused RPC commands for mining blocks, advancing time, and impersonating accounts, offers a built-in block explorer, and bundles command-line tools for contract interaction and compilation across multiple programming languages.
  
  This matters because local development should be fast, repeatable, and self-contained. By reducing setup work and giving developers a controlled environment for testing contract behavior, Nanvil helps teams iterate faster before moving to shared networks.
• neo-n3-watch — Real-Time Contract Event Monitoring (CLAUS):
  
  neo-n3-watch is a zero-configuration command-line utility for streaming smart contract events directly to a terminal in real time. It can watch live contract events with a single command, filter by contract, event name, network, RPC endpoint, and polling interval, and run without node setup or indexing infrastructure. The tool is distributed as an npm package for quick installation.
  
  This matters because debugging and monitoring decentralized applications often begins with simply seeing what happened on-chain. A lightweight event stream gives developers a direct way to observe contract behavior, diagnose issues, and monitor application activity without standing up extra infrastructure.

That combination matters because healthy ecosystems need more than individual applications. They need visibility, developer tooling, test environments, deployment discipline, and monitoring paths that make it easier for contributors to build, inspect, and maintain useful software.

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

At a higher level, this week’s work makes the Neo ecosystem easier to understand, easier to test, easier to connect to, and easier to debug.

Together, these contributions point toward a practical builder experience: clearer development signals, more trustworthy user interfaces, shared wallet tooling, safer deployment review, local testing environments, and simple event monitoring when applications are running.

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.