@NullaNetwork

AuthGate Launch Week — Private Access Keys Are Here We're shipping something we've been building toward since day one: the first real-world use case for Nulla private notes. Until now, private notes let you move value anonymously. Starting this week, they let you buy access to real services, without an account, without a login, without anyone knowing who you are. Here’s how the week looks: Day 1 — AuthGate Parachain Goes Live The AuthGate parachain (para 2003) launches on the Nulla Testnet with the first registered service slots. This is the on-chain layer that makes anonymous access keys possible: a provider registers a service, sets a price, and from that moment anyone with a private note can pay for access — cryptographically, with zero identity exposure. Day 2 — Desktop Wallet Update The nulla-wallet desktop binary ships with full AuthGate support. Two new commands: access buy (spend a private note to get an access key) and access use (redeem the key). This is the first wallet release where your private balance can do something beyond moving funds. Day 3 — Android Wallet The Android build follows. Same commands, same privacy guarantees, now on mobile. Private payments for real services, from your pocket. Day 4 — First Live Application The first Web2 application integrated with AuthGate goes live. You can visit it, pay with a private note, and gain access — with no account, no email, no trace. The provider receives payment. The chain verifies the proof. Nobody learns who you are. This is what private notes were built for.

Testing on the new Parachain AuthGate, which will bring the first utility to NULLA, is progressing well. This marks the beginning of the next phase. Tomorrow, we will share the roadmap with the community, outlining how this major update will be rolled out. https://t.co/6v8i1izaRC

We are finalizing testing for the new AuthGate parachain. As you can see, after connecting to the test AuthGate chain and listing the previously registered app authentication access offers, it is possible to submit a request to register a new app service with a specified cost. After this testing phase is complete, we will move on to the SDK, allowing app owners to implement this functionality in virtually any existing web application.

The network continues to grow rapidly, and we've now reached 15 connected peers. This call was made directly from the team's node, demonstrating the network in action. You can monitor the node and network activity in real time using the explorer: https://t.co/GV6RaIjPr8 https://t.co/Uw9blEmLaa

We now have our first external validator node actively participating in the validator set. While this is an important milestone for network decentralization, we are keeping the active validator count at 5 for now. As more external candidates become ready, we will gradually expand the validator set to ensure growth remains stable, secure, and well-observed. Validator Growth Plan • 1–2 candidates → 5 validators (continue observing) • 3–4 candidates → 7 validators (fault tolerance increases to 2) • 6–8 candidates → 9 validators • 10–14 candidates → 11 validators (fault tolerance = 3) • 15–20 candidates → 15 validators (fault tolerance = 4) Key principles • Never increase the validator count by more than 2 at a time • Wait at least 2–3 eras after each expansion before increasing again • Maintain a meaningful minValidatorBond to ensure strong validator commitment and network quality This measured approach allows us to steadily increase decentralization while maintaining the security, reliability, and performance of the network.