COZ has shipped dAPI support for neon-js, its JavaScript/TypeScript SDK for Neo N3, introducing a standardized provider layer that lets wallets and dApps connect, sign, and transact through a single shared interface rather than rebuilding bespoke integration code for every pairing.
The release implements NEP-21, the unified dAPI standard for Neo N3 finalized by Neo co-founder Erik Zhang in April 2026. neon-js is COZ’s long-standing JavaScript/TypeScript SDK for Neo.
What the provider layer does
Before a shared provider layer exists in an ecosystem, each dApp must write its own logic to connect to each wallet it wants to support, and each wallet must write its own logic to respond to each dApp. Multiply that across a developer ecosystem and the result is significant duplicated work and potential inconsistent behavior, particularly in edge cases.
The neon-js provider layer standardizes four categories of wallet–dApp interaction: connecting, requesting signatures, preparing transactions, and handling errors. A dApp developer integrating against the NEP-21 provider layer gains compatibility with any NEP-21-compliant wallet without writing wallet-specific code for each one. A wallet implementing NEP-21 becomes automatically compatible with any dApp built on neon-js, without additional per-dApp integration work.
Standardizing error handling and transaction preparation across integrations also reduces the class of edge-case bugs that arise when wallets and dApps handle these operations differently.
How it works
NEP-21 defines the IDapiProvider interface, a specification covering authentication, account management, contract invocation, transaction handling, message signing, and event notifications. The standard is transport-layer agnostic, meaning it specifies what capabilities a wallet must expose to dApps without prescribing how the underlying connection is made. Provider discovery occurs through Neo.DapiProvider.ready and Neo.DapiProvider.request window events, which wallets and dApps scan for to establish the connection.
NEP-21 depends on NEP-20, the wallet-based authentication standard for Neo N3, which was also finalized in April 2026.
Where this fits in the NEP-21 adoption story
The wallet-side of the NEP-21 ecosystem arrived earlier this year when NeoLine shipped v5.8.0 as the first wallet to implement the standard. That release and the neon-js update together form the two halves of a working NEP-21 ecosystem: a wallet that can respond to standardized requests and an SDK that can make them.
With this release, neon-js becomes the reference JavaScript/TypeScript implementation of NEP-21 in the Neo N3 developer toolchain. When a standard has a well-maintained SDK implementation that developers already use, it lowers the barrier for building against it. The practical effect is that NEP-21 adoption now has a clear on-ramp for developers working in JavaScript and TypeScript.
The full announcement can be found at the link below:
https://coz.io/blog/neon-js-dapi-support-neo-n3/
About The Author: Dylan Grabowski
Dylan is a reformed urban planner with a passion for covering the Neo ecosystem. His objective as a writer for Neo News Today is to report news in an objective, fact-based, non-sensational manner. When not behind a computer screen, he can be found in the mountains rock climbing. Find Dylan on Twitter (@GrabowskiDylan).
More posts by Dylan Grabowski