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

Award Proof: Transaction

This round stands out because the work does not sit in just one layer of the ecosystem.

From making NeoFS easier to use in Python and on the desktop to improving public visibility into Neo X activity, this round shows the kind of open work that strengthens the ecosystem by making it easier to build, easier to inspect, and easier to join.

• NeoFS Python SDK (CLAUS):
  
  One of the most important infrastructure contributions in this round is a production-ready Python SDK for NeoFS. The project gives Python developers a more direct and practical way to work with decentralized storage by supporting the full storage lifecycle, including container creation, upload, listing, download, and deletion. It also handles cryptography, signing, and notarization automatically, which removes a large amount of implementation friction for developers who want to start building rather than spend their time stitching together low-level storage logic. The package is published on PyPI, making installation straightforward, and it now includes Neo X EVM funding support so users can bridge GAS and fund storage from familiar wallet flows such as MetaMask. CLI tooling and ACL management further strengthen the package as real working infrastructure rather than a narrow prototype.
  
  This matters because it lowers the barrier for backend, data, and DevOps-oriented developers to start using NeoFS in real applications.
• Forge (AboimPinto):
  
  Forge continued moving toward a faster and more approachable token-launch experience. The tool is built around one-click token creation and immediate trading through bonding-curve mechanics, with built-in tax logic applied on every trade. The contribution is notable not because token tooling is new in the abstract, but because it pushes toward a more usable operator experience for communities, experiments, and crowdfunding-style initiatives that need a faster path from idea to live token behavior.
  
  That kind of simplification matters because easier launch tooling can reduce the friction of experimentation and help more community-driven projects test mechanisms in public.
• Neo Analytics (thermx5):
  
  Neo Analytics continued expanding its role as a public visibility layer for the ecosystem. This round adds stronger Neo X coverage, including transactions, ERC-20 tracking, and richer charting, alongside new asset-level pages that make token-specific activity easier to inspect. The backend also saw reliability and scalability improvements, including ingestion locking, admin controls, and shared-infrastructure refactoring. Explore the dashboard, the dedicated Neo X page, and example asset-level analysis such as the FUSD asset page.
  
  This kind of work matters because better analytics improve transparency for builders, users, and researchers trying to understand what is actually happening across the ecosystem.
• Neo N3 Assistant (fireche):
  
  The Neo N3 Assistant continued evolving as an AI-powered interface for navigating the Neo ecosystem. This round adds support for local AI model operation and integrates the latest Neo news through Neo News Today, while remaining open-source and customizable. That combination is important because it keeps the assistant flexible for different users and environments while improving access to timely ecosystem information.
  
  Projects like this matter because they can make Neo knowledge easier to reach, especially for users and developers who prefer conversational interfaces over searching across many separate sources.
• NeoFS Mount (Merl):
  
  NeoFS Mount pushes decentralized storage in another important direction: familiar everyday usability. The project makes it possible to mount NeoFS storage like a local drive across Linux, macOS, and Windows, with support for native file explorer patterns such as Finder, Explorer, FUSE, Apple File Provider, and Windows CfAPI. It also includes a system tray app for monitoring and configuration, alongside a CLI option for users who prefer a more direct workflow.
  
  This matters because infrastructure becomes much more usable when people can interact with it through patterns they already understand. Work like this helps NeoFS feel less like specialized blockchain tooling and more like a practical storage surface people can actually adopt.

Some contributions make NeoFS easier to use directly in code. Others make it easier to work with storage through familiar desktop patterns. Others improve visibility into ecosystem activity, or reduce the friction of launching and experimenting with new applications and tokens.

Taken together, that is exactly the kind of compounding public work Proof of Working is meant to support: infrastructure that becomes usable, tooling that becomes approachable, and ecosystem activity that becomes easier for others to understand and build on.

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

At a higher level, this week’s work shows meaningful progress across three connected layers of the ecosystem.

The infrastructure layer is getting stronger through tools like the NeoFS Python SDK and NeoFS Mount. The tooling layer is getting easier to use through projects like Forge and Neo N3 Assistant. The visibility layer is getting better through Neo Analytics and its continued expansion across Neo N3 and Neo X.

That combination matters because real ecosystem growth depends on more than one-off launches. It depends on making core capabilities usable, making public activity legible, and giving contributors more surfaces they can build on next.

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.