DAY 2 update:
We've published updates for both the Android and Desktop wallet, now pointing to the new mainnet endpoints.
Android: https://t.co/q0617uPAdX
Download and install the new APK over your existing installation (same package, should update in place and preserve your wallet). As always with any update, back up your recovery phrase first just in case — if Android ever asks you to uninstall before installing, that would wipe local data.
Desktop: https://t.co/OSkei08yqR
extract the new zip anywhere you like, your wallet data lives in your user profile folder, not inside the app folder, so it's preserved regardless of extraction path. If you have a desktop shortcut pointing to the old folder, just recreate it after extracting. As always, back up your recovery phrase before updating.
We registered the Nulla demo app on the AuthGate AppSlot.
We set the price at 1 plank (the smallest unit, so basically zero).
This is the slot that will allow people to purchase private access to the demo app.
Stay tuned!
AuthGate Is Ready: Real Privacy for Web2 Login:
Today we want to explain, in a precise and verifiable way, how AuthGate works, the new module from Nulla Network that allows users to access Web2 applications completely anonymously, paying with shielded NULLA.
What is AuthGate?
AuthGate is a dedicated parachain (para 2003) that acts as a bridge between Nulla's on-chain privacy and the login systems of traditional Web2 applications. It requires no wallet connection, no email, and no KYC.
How it actually works, step by step
A service provider registers their application on AuthGate, specifying an access price in NULLA.
The user already owns shielded NULLA (private notes on ProofHub or Pedersen coins on ScanProof) in their wallet.
The user purchases an access key by spending the private note. This operation generates a local secret (blinding) and a public cryptographic commitment, calculated as follows:
commitment
=
BLAKE3
(
"nulla_access_key_v1"
∥
app_id
∥
blinding
)
The privacy parachain sends a cross-chain XCM message to AuthGate, which records this commitment in its storage — without ever learning the identity of the person who made the payment.
The user presents the secret (tx-id + blinding) to the application's website. The application's backend verifies that the hash matches, then marks the key as "used" on-chain.
The application grants access. No wallet address, no IP address, and no identity is ever linked to the account that made the original payment.
Each key is single-use: once consumed, it cannot be reused by anyone else, not even by the person who originally purchased it.
The first real-world use case
We have already prepared the first demonstration website using AuthGate in production: a real Web2 application with a login page integrated directly with our official SDK ("nulla-authgate-sdk"), not a simulation.
Over the next few days:
- we will officially register this application on AuthGate;
- we will launch the dApp together with the SDK, so that anyone can see the complete flow working in real time on our network.
Try it without spending anything
To allow the entire community to test how it works without any financial risk, this first demonstration application will have an access key with a zero cost (0 NULLA).
This means you will be able to:
- generate a private note and complete the entire real cryptographic flow;
- gain access to the demonstration application;
- verify for yourself that the system works exactly as described;
- without spending a single real NULLA.
Why it matters
This is not simply a discount or coupon system: it is the first public demonstration that a traditional Web2 application can authenticate its users without ever knowing who they are, leveraging Nulla Network's cryptographic privacy end-to-end, from payment all the way to login.
We will keep you updated as soon as the demonstration application is registered and live.
Stay tuned.
We just updated the GitHub repository with the Authgate Parachain:
https://t.co/PcIvifXUXU
This GitHub update covers only the runtime and pallet of the parachain.
Tomorrow, we will update the SDK that providers can use to add privacy-preserving authentication to their websites, leveraging NULLA.
Alongside the SDK, we’ll also release the first website created by the NULLA team to properly showcase the functionality.
Parachain AuthGate is being registered right now.
This step requires waiting for at least one session and assigning validator cores to the parachain ID.
Once we ensure the chain is healthy and remains stable for at least one day, we will publish the code on GitHub along with a detailed explanation of the workflow that powers this parachain and enables user privacy.
NULLA Bridge
The NULLA Bridge allows users to transfer value between NULLA Mainnet and Base by connecting and verifying both wallets.
NULLA to Base: NULLA tokens are locked on-chain through the official nullaBridge pallet. Once the transaction is finalized, the system verifies the wallet, recipient, and amount. The team then mints the equivalent amount of wNULLA on Base.
Base to NULLA: the user submits a request signed by both wallets. The team reviews the request, completes the wNULLA burn on Base, and then unlocks the corresponding NULLA tokens to the specified wallet.
Every request:
requires valid signatures from both wallets;
verifies the available balance on the source chain;
cannot exceed the available balance;
prevents either wallet from submitting another request while one is pending;
can be tracked directly through the dapp.
The bridge is manually operated by the team to provide an additional verification layer for every transfer. Wallet signatures bind the addresses, direction, and amount, but cannot move funds on their own. Minting and unlocking are performed only after the corresponding on-chain transaction has been verified.
On the L1 Mainnet, we have a total supply of 1.25 billion tokens, therefore on Base, we minted the equivalent amount required to distribute the tokens to all users and provide liquidity for the liquidity pool.
At the moment, the bridge holds exactly the same amount of tokens that was minted on Base.
The remaining supply is allocated as follows: 5 million tokens to each validator required to run the chain, with the remainder held in the sudo address.
Regarding staking and rewards, these parameters remain the same as in the first launch:
20% of each era’s emissions go to the treasury.
The remaining 80% is distributed among validators and potential nominators of each node based on their actual era points.
80% of transaction fees go to the treasury, while the remaining 20% goes to the block author.
Inflation is set at 8%.
These values can be queried directly from the chain storage using the Nullascan explorer by navigating to Chain State → nullaParams.
New chain L1 is now live again, with validators run by the team.
Chain blocks can be observed here:
https://t.co/KocLN0lApI
We have already locked the bridge pallet and the equivalent amount minted on Base.
We will now perform the calls to register the parachains and set the validator cores for them.
Nulla is live again !
NULLA SHIPPING SCHEDULE
1 Week Update Plan
Seven days across the network — chain live, wallets upgraded, and the Authgate parachain deployed. Here's exactly what's landing.
DAY 1 — Ignition
Turn on Chain + Parachains
DAY 2 — Wallets & Code
Desktop Wallet upgrade
Mobile Wallet upgrade
GitHub updates
DAY 3 — Content Drop
Video content
Tokenomics info message
DAY 4 — Bridge Focus
Bridge info message
Video content
DAY 5 — Authgate Live
Deploy Authgate Parachain
Turn on Authgate
DAY 6 — Authgate
Authgate GitHub update
2 video contents
DAY 7 — The Full Picture
BUILT IN PUBLIC — NULLA NETWORK
We were here:
TL;DR — Nulla Network · June–August 2026
Chain Delivery
Nulla relay chain launched on mainnet.
Apps
Desktop and mobile wallets shipped at mainnet genesis.
Both support the quantum lane (STARK + ML-DSA-44) and homomorphic lane (Pedersen + Bulletproofs).
Local proof generation, note management, and XCM relay↔parachain transfers are supported.
Parachains
Two privacy parachains are live:
ProofHub (para 2000, spec v123) — quantum lane, BLAKE3 commitments, Winterfell STARK verifier, ML-DSA-44 spend tags.
ScanProof (para 2002, spec v9) — homomorphic lane, Pedersen on Ristretto255, Bulletproofs, Schnorr.
AuthGate
The first real-world use case built on Nulla. It enables application authentication via private proofs—users can prove their identity or access rights on-chain without revealing who they are to the application. It was developed and tested end-to-end as the first consumer of the ProofHub privacy workflow.
Where We Are Now
We have relaunched the Base token and are ready to restart the L1. This time, the launch will include the privacy parachains right from the beginning.
As soon as we push the chain live, we will update the mobile and desktop apps to work with the new blockchain's official endpoint.
We will then start delivering, one by one, the use-case applications we have developed over the past few months. The first of these will be the AuthGate parachain, which will allow users to authenticate with Web2 applications without having to register with an email address.
Workflow:
Registration — the user deposits a private note into ProofHub (quantum lane). The note encodes a credential (e.g. "this person paid for a subscription" or "this person is in the allowlist"). The note commitment goes on-chain, the identity stays off-chain.
On-chain verification — the app backend calls ProofHub to verify the proof. ProofHub confirms the spend tag is valid and unspent. It emits an event: access granted.
Nullification — The same credential cannot be replayed. If the user needs a new session, they either use a change note (if value remains) or deposit a new note.
What the app sees: a verified boolean. No wallet address, no identity, no history.
Okay everyone, we have relaunched and this is the new official Nulla token:
https://t.co/bL6v0xfvE1
Total supply is 1,250,000,000 tokens, but the remaining supply has not been minted yet.
For now, the circulating supply is only 33,000,000 tokens, which is the entire amount currently deposited in the LP.
Total supply: 1,250,000,000
Starting LP / circulating supply: 33,000,000
Initial price: $0.0003636
Current circulating market cap: $12,000
FDV (based on total supply): ~$454,545
Total LP value: $24,000
CA:
0x0a3d02b6f24b8bade4ea5328d2f29de2b0b4d6c2
Hello everyone, so in order to allow to everybody to perform the claim in the same moment we will keep open this register form on the nulla website for other 24 hours.
This is meant to allow users how had bridged the tokens on the previous nulla chain to connect a base wallet where they will recive the same amount of tokens that they are allowed from the previous chain. after this step we will immediately open the claim on the same website -> Monday
There has been an exploit.
Please do not trade the coin until further notice.
We will share updates shortly with explanation and solution.
Thank you for your patience and cooperation.
Bridge: Relay → Parachain
This clip shows a cross-chain bridge transfer from the Nulla Relay Chain to a parachain .
The wallet handles the XCM reserve transfer automatically: you select the destination parachain, enter the amount, and the funds move on-chain in a single click.
No manual extrinsic construction, no third-party bridge required, everything runs locally inside Nulla Wallet.