NeoLine has released v5.8.1 of its Chrome extension wallet with full support for NEP-21, the unified dAPI standard that Neo co-founder Erik Zhang finalized last week. The update makes NeoLine the first wallet in the Neo ecosystem to implement the standard IDapiProvider interface, a common set of methods that allows decentralized applications to communicate with wallet providers through a single, consistent integration.
NEP-21 addresses a long-standing fragmentation problem on Neo N3. Without a shared interface, dApp developers had to write separate integration logic for each wallet, and users experienced inconsistent behavior depending on which wallet they connected. The standard defines a transport-independent interface that works with browser extensions, desktop clients, and mobile wallets.
NeoLine implementation
Now that the NeoLine implementation is live, dApp developers building on Neo N3 can now write a single wallet integration using the NEP-21 interface and have it work out-of-the-box. As other wallets adopt the standard, the same integration will extend to those providers without additional development work.
The update also introduces a standardized provider discovery mechanism. Wallets and dApps can now automatically locate each other in the browser via predefined window events, replacing the ad hoc detection methods dApp developers previously relied on. Standardized error codes provide developers with consistent, predictable error handling, regardless of which compatible wallet a user connects to.
How it works
NeoLine’s v5.8.1 implementation includes the full NEP-21 specification. The wallet exposes methods related to authentication, account management, contract invocation, transaction construction and signing, on-chain data queries, and event notifications.
Authentication follows the NEP-20 Challenge/Response protocol, the associated standard that Zhang finalized earlier this month. NEP-20 defines an off-chain, address-based authentication scheme where users prove ownership of their Neo address through a cryptographic signature. from NeoLine authenticate() method implements this flow natively.
The wallet reports the dAPI version as “1.0” and lists compatibility with standards including NEP-11, NEP-17, and NEP-21.
The full developer documentation can be found via the link below:
https://tutorial.neoline.io/reference/neo3-provider-api