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

Award Proof: Transaction

Proof of Working 2.10 highlights practical improvements across several parts of the builder workflow: local contract debugging, wallet infrastructure, storage SDKs, event delivery, and analytics.

The common thread is operational clarity. These contributions make it easier for developers to observe contracts, manage accounts, search and protect stored data, relay on-chain events, and understand wallet activity.

• ncast watch for Nanvil (CLAUS):
  
  CLAUS contributed live smart contract event monitoring directly to Nanvil through the new ncast watch workflow. The work ports event-watching functionality from neo-n3-watch into Nanvil so developers can monitor contract events from the same local command-line environment they already use for building and testing. The contribution was reviewed and merged through the Nanvil pull request.
  
  This matters because smart contract debugging becomes easier when event monitoring is part of the core local workflow. Developers can spend less time wiring together separate tools and more time observing how contracts behave while they test.
• neo-n3-python-wallet (CLAUS):
  
  CLAUS also released a standalone Python wallet library for Neo N3 applications. The library supports BIP-39 mnemonic generation and recovery across eight languages, BIP-32 and BIP-44 hierarchical deterministic wallet derivation, NEP-2 encrypted private keys, NEP-6 wallet files, address generation, WIF utilities, key management, and signing. It also includes 142 automated tests and resolves a Python 3.13 Windows SHA-256 compatibility issue.
  
  This matters because Python developers need reliable account infrastructure before they can build higher-level applications. A focused wallet library gives teams a clearer foundation for generating accounts, managing keys, and integrating secure wallet behavior into Neo N3 tools and services.
• NeoFS Python SDK v0.4.0 (CLAUS):
  
  NeoFS Python SDK v0.4.0 expands Python storage tooling with support for container attribute management, container locking, attribute-based object search, paginated results, and additional CLI commands for container and search workflows. The update closes feature gaps between the Python SDK and supported NeoFS node capabilities, giving application developers more control over stored data and better discovery tools.
  
  This matters because decentralized storage integrations depend on SDKs staying aligned with the network features they expose. Better container controls and object search support make it easier for Python applications to manage data safely and operate against NeoFS with less custom infrastructure.
• Pusharoo Event Relay (Vault Keeper):
  
  Vault Keeper added an event relay service to Pusharoo that monitors smart contract application logs and forwards matching events to external systems through webhooks. The work supports subscriptions for specific contract events, real-time notifications to user-defined endpoints, and a dedicated Event Webhooks interface inside Pusharoo.
  
  This matters because many applications need to connect on-chain activity with off-chain systems. Webhook-based event delivery can support notifications, backend automation, analytics, bots, and operational workflows without every team having to build its own event infrastructure from scratch.
• Wallet Tracker (fireche):
  
  fireche built a blockchain analytics tool for visualizing token transfers, wallet relationships, and fund flows through an interactive graph interface. The tool traces token movement across multiple wallet hops, displays wallet balances and holdings, labels known wallets such as exchanges and bridges, supports live wallet monitoring and alerts, and gives users a graph-based way to explore transaction history.
  
  This matters because transparency tools make blockchain activity easier to understand. Clearer wallet and transfer visualization helps users investigate transactions, monitor large movements, and reason about fund flows without manually piecing together every step.

That kind of work is not always flashy, but it compounds. Better developer and operator tooling lowers friction for every application that comes after it.

At a higher level, this round strengthens the practical operating layer around Neo development: watching contracts while they run, managing wallets from Python, working with NeoFS data, relaying events into external systems, and tracing wallet activity after the fact.

Together, these contributions point toward a builder experience that is easier to observe, easier to connect, and easier to reason about. They do not all live in the same part of the stack, but they all make the ecosystem more usable for people turning on-chain activity into working applications.

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.