One Interface to Rule Them All: Neo's NEP-21 Finally Puts Wallet Chaos Out of Its Misery

Neo N3 just leveled up its developer experience. Erik Zhang, Neo co-founder and core developer, has finalized NEP-21, a standard that gives decentralized applications a common language for talking to wallet providers. After a review process stretching back to November 2021 with renewed activity concluding in March, the proposal has officially reached "Accepted" status. Because apparently, getting crypto developers to agree on something took a bit longer than most DAO governance cycles.

The Problem NEP-21 Solves

Without a shared interface, Neo dApp developers have been forced to write separate integration code for every wallet out there. Each wallet defined its own methods and data formats, meaning users got different experiences depending on which wallet they connected. It's the classic Web3 UX nightmare: your transaction works in Wallet A but Wallet B thinks you're speaking Mandarin. NEP-21 changes that by giving both sides a unified playbook.

What This Enables

Developers can now build a single wallet integration that works across any compliant wallet, rather than maintaining a separate codebase for each provider. Wallet creators get a clear implementation target, making it easier for new entrants to join the ecosystem. Users benefit from consistent behavior when connecting wallets, signing transactions, and interacting with dApps—no more wallet-specific surprises. Imagine a world where clicking "Connect Wallet" actually means the same thing everywhere. Revolutionary, I know.

The Standard's Family Tree

NEP-21 slots into a broader standardization effort. NEP-20 handles wallet-based authentication, letting applications verify a user's control of a Neo address. NEP-21 provides the unified interface through which dApps call wallets to complete that authentication and other operations. NEP-33 aims to standardize the login entry point into a "Sign in with Neo" flow. It's a whole interoperability dynasty, and everyone's getting a numbered door in the mansion.

Under the Hood

NEP-21 defines the IDapiProvider interface that wallet providers implement. It covers several capability categories:

Identity and Connection: dApps can call authentication() to verify addresses (using the NEP-20 scheme), retrieve connected accounts, or prompt users to select a different address.

On-Chain Data Reading: Methods exist for invoking contracts off-chain, querying blocks, transactions, application logs, contract storage, and token information—all without requiring a user signature. Because sometimes you just want to peek at the blockchain without asking permission, like reading someone's publicly visible transaction history at a party.

Contract Invocation and Transaction Handling: dApps can invoke contracts on-chain, construct unsigned transactions (useful for multi-signature workflows), and relay signed transactions to the network. The abortOnFail parameter lets dApps specify that an entire transaction should revert if any single invocation returns false—critical for operations where partial execution would be problematic. Yes, atomic transactions are as satisfying in DeFi as they sound.

Message Signing: The standard includes methods for signing arbitrary messages using ECDSA with SHA256, supporting off-chain authorization and protocol declarations. Because when you need to prove you control an address without actually moving assets, there's a method for that.

Event Notifications: Wallets emit standardized events when users switch accounts or change networks, keeping dApp frontends synchronized. Think of it as the blockchain's version of "DING! You have mail"—except the mail is your portfolio updates.

Finding Each Other

The standard defines how wallets and