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

Award Proof: Transaction

Proof of Working 2.6 highlights progress across three practical surfaces of the Neo ecosystem at once: multi-chain user tooling, trustless financial infrastructure, and wallet interoperability for real-world application access.

That spread matters because ecosystem progress is stronger when it compounds across usage layers. Better assistants make systems easier to operate, better token primitives make projects easier to structure credibly, and better wallet support makes applications easier to reach from the devices and flows people already use.

• Neo AI Agent — Neo X Expansion (thermx5):
  
  Neo AI Agent continued evolving into a more capable ecosystem interface by expanding from Neo N3 into Neo X. This round adds full Neo X EVM support through viem, including balances, block inspection, ERC-20 and ERC-721 asset handling, transaction receipts, contract calls, and safer previews before transfers or contract writes. The assistant also improves its prompt routing between Neo N3 and Neo X and adds interactive chain selection during CLI sessions, backed by stronger CI and testing coverage. Explore the repository and the related pull request.
  
  This matters because better tooling does not only mean more features. It means reducing the cognitive overhead of moving across network models while giving builders and operators a safer, more accessible way to interact with both Neo N3 and Neo X from one interface.
• NeoVest (fireche):
  
  NeoVest introduces a trustless token vesting platform for Neo N3 focused on making vesting schedules transparent, enforceable, and directly verifiable on-chain. The platform supports cliff, linear, and stepped vesting models, works with any NEP-17 asset, verifies deployed contract integrity through a public dashboard, and lets beneficiaries claim directly from the contract instead of relying on custodial or off-chain processes. The browser-based deployment flow also keeps the operator experience practical by pairing contract creation with wallet signing.
  
  This matters because vesting is a core primitive for teams, communities, and treasury design. Bringing that primitive on-chain in an inspectable way strengthens trust, reduces operational ambiguity, and gives Neo builders a more credible foundation for long-term token distribution.
• FORGE — WalletConnect + Mobile Expansion (AboimPinto):
  
  FORGE continued improving usability by expanding wallet compatibility and mobile support. This round adds WalletConnect and AppKit support alongside NeoLine, improves Neon Desktop and Neon Mobile wallet flows, introduces a shared wallet harness for CI and testing, and pushes toward a mobile-friendly operator experience through an Android WalletConnect proof of concept. Automated emulator coverage in GitHub Actions further strengthens confidence that the wallet surface behaves consistently as support broadens.
  
  This matters because token and app ecosystems grow faster when users are not trapped behind one wallet path or one device class. Better wallet interoperability and mobile readiness lower onboarding friction and make Neo applications easier to reach in real-world contexts.

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

At a higher level, this week’s work makes Neo easier to use across chains, easier to structure around trustless token operations, and easier to access from more wallet and device contexts.

Together, these contributions point in a practical direction: stronger operator tooling, more credible infrastructure primitives, and lower-friction entry points for the next wave of Neo applications and communities.

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.