Neo Completes the Auth Trifecta: NEP-33 Drops the 'neoauth://' Mic

Neo co-founder Erik Zhang has published NEP-33, the third Neo Enhancement Proposal in two weeks. Yes, you read that correctly—three NEPs in fourteen days. Either Erik has discovered the secret to temporal manipulation, or Neo's developers are just built different. Either way, the standard defines a URI-based transport mechanism that allows native applications to invoke wallet applications for authentication, completing a three-layer stack that standardizes how users sign in with their Neo wallet. It's like watching someone finally organize a junk drawer that's been chaos for years.

NEP-33 follows NEP-20, which established cryptographic authentication rules, and NEP-21, which defined a unified interface for dApps to communicate with wallet providers. Where those two standards handle authentication logic and wallet capabilities, NEP-33 addresses the entry point: how one application hands off an authentication request to a wallet and receives the result. Think of it as the bouncer at the club—making sure the right people get in, but not actually checking IDs itself.

What this enables

Before NEP-33, there was no standardized way for a mobile or desktop application to invoke a Neo wallet for authentication. Each wallet and application implemented its own invocation and callback format, creating fragmentation. Picture if every website had its own unique "log in" button that looked different, required different passwords, and sometimes just didn't work—that was Neo authentication circa last week. Developers were essentially building custom bridges to every single wallet, which is a lot of bridge-building for a ecosystem that wants to scale.

NEP-33 introduces neoauth://, a custom URI scheme that gives native applications a universal "Sign in with Neo" entry point. Yes, finally, the Neo ecosystem has its own answer to "Sign in with Google" and "Sign in with Apple"—though admittedly with slightly fewer data-harvesting implications. The operating system routes the request to a compatible wallet, which returns the result via a callback URI. Developers building on Neo can now integrate wallet authentication without writing wallet-specific code for each provider. It's the difference between learning fifteen different languages to order coffee versus just pointing at the menu.

Additionally, NEP-33 has been designed with forward compatibility in mind. Zhang addressed a question about whether separate URI schemes should exist for different Neo network versions: Since the address formats of N3 and