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

Award Proof: Transaction

Proof of Working 2.7 highlights progress across two practical but important ecosystem layers at once: easier token experimentation and broader storage tooling access.

On one side, HushForge is pushing toward a more accessible token-launch workflow with stronger transparency signals and standards exploration. On the other, NeoFS SDK for Zig expands infrastructure access for a new class of developers who want storage tooling in a modern systems language.

• HushForge — Direct Speculative Token Launchpad (AboimPinto):
  
  HushForge continued evolving from a community-token launcher into a platform for creating speculative tokens directly on Neo. This round adds native speculative token creation directly into the Forge workflow, opens a Neo standards proposal for a multi-fungible token interface that allows a single contract to represent multiple fungible tokens, and introduces automated trust and quality indicators such as Forge Audit Index and ForgeScore. The direct token creation flow has already been validated on a local private Neo3 chain, with TestNet deployment positioned as the next milestone. You can review the video walkthrough here and the related specification notes here.
  
  This matters because it reduces the friction of launching new token experiments while adding clearer transparency signals that can help users evaluate what they are interacting with. The accompanying standards work also points toward more scalable token deployment patterns across the ecosystem.
• NeoFS SDK for Zig (Merl):
  
  NeoFS SDK for Zig brings decentralized storage tooling into another modern systems language by providing a native Zig implementation aligned closely with the official Go SDK. The project includes gRPC client support, multi-node connection pooling, container and object operations, streaming uploads and downloads, search functionality, session management, ACL helpers, and NeoFS placement logic including QL policy parsing, HRW, and tzhash. It also ships with pinned protobuf definitions, cross-language test vectors, Docker-based integration testing, runnable examples, and extensive documentation, and is currently released as version 0.1.0 targeting Zig 0.15.x.
  
  This matters because broader SDK language coverage lowers integration barriers for new builders. Giving Zig developers a credible path into NeoFS expands the storage ecosystem’s reach and makes NeoFS more accessible for performance-oriented and systems-level applications.

That combination matters because ecosystem growth depends on both experimentation surfaces and durable infrastructure. It is not enough to make systems more powerful in theory. They also need to become easier to build with, easier to evaluate, and easier to extend from different technical starting points.

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

At a higher level, this week’s work makes Neo easier to experiment on and easier to integrate with.

Together, these contributions point in a practical direction: lower-friction token tooling, broader infrastructure language support, and a healthier path for builders who want to extend the ecosystem in public.

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.