Mainnet Tokenomics and Update
Connect your Solana and Base wallets and deposit NULLA by 12/06/2026.
Claim bridged WNULLA on Base starting 13/06/2026 with a 1:1.25 ratio.
Relaunch Pool
We will mint 1.25 billion tokens.
This supply will ensure that we have sufficient tokens to:
- Cover the incremental ratio allocation for early buyers.
- Provide the initial validator stake operated by the core team.
- Supply liquidity for the bridged token in the Uniswap pool.
The pool will be funded using the dollar-denominated liquidity generated after early buyers deposit their NULLA tokens into the designated collection address.
An appropriate amount of WNULLA tokens will be paired with this liquidity to maintain the same token price that existed prior to the aforementioned sale.
Mainnet Economics
The network will launch with an annual inflation rate of 8%, distributed across each era (every 24 hours).
The newly minted tokens will be allocated as follows:
80% to stakers, subject to a 2-day bonding period.
20% to the Treasury.
This inflation rate may be adjusted through governance over the lifetime of the chain.
The purpose of inflation is to incentivize validators and stakers until transaction fee revenue becomes sufficient to secure the network without the need to mint additional tokens.
Network Fees
Network transaction fees will be distributed as follows:
20% to the block author.
80% to the Treasury.
Treasury Funds
In the long term, treasury reserves may also be used to support token-burning mechanisms, reducing the circulating supply and helping offset the inflation introduced during the network’s early stages.
CALL DETAILS
DATE: 11TH JUNE (THURSDAY)
TIME - 7:00PM UTC
Chain - SOLANA
TARGET - 10Million MC ABOVE
How to be ready?
Put notifications on.
Free airdrop for holders
Like and retweet drop your SOL for airdrop
Join TG 👇
T.me/fluffyalpha
I bought a bag of $PRI around a $40k market cap.
Not because I think it’s the next meme coin, but because it’s one of the more interesting experiments I’ve seen on Solana in a while.
The idea is simple: instead of asking people to learn privacy tools, use mixers, bridge funds, or adopt a separate privacy coin, PRI tries to make privacy something you opt into once and then forget about.
Holders can delegate their tokens into a growing anonymity set managed by The Custodian, an autonomous agent that progressively adds privacy layers over time. The roadmap moves from pooled ownership and gas abstraction to active defense, stealth addresses, and eventually shielded balances.
What caught my attention is that it’s already live on mainnet. Every opt-in updates a cryptographic commitment that’s published on-chain, creating a public audit trail of the experiment as it grows.
The bigger idea isn’t even PRI itself. It’s the Private Meme Coin Standard (PMCS): a framework where any meme coin could eventually inherit the same privacy infrastructure without needing its own privacy chain.
Could it fail? Absolutely. The hardest parts of the roadmap are still ahead.
But at a ~$40k market cap, I’m willing to take a bet on a team thinking about privacy, incentives, and adoption in a very different way than most crypto projects.
Worth a look.
@NullaNetwork Look at what you guys are doing? The project progress is still so slow when AI could be used. You keep changing your own plans all the time.Everyone who's been supporting you has lost faith. The mainnet launch is still a long way off.
The Deposit app is now live on the official website: nulla.network/deposit
You can also access it directly from the nulla.network homepage, as demonstrated in the video.
The tokenomics will be shared in some hours, stay tuned!
The new runtime for the relay has been upgraded. We decided to start the testnet with a clean slate.
This upgrade is central to what we are building next.
- A custom pallet for the Ethereum bridge implementation.
- A bridge between the parachain and the relay chain.
@NullaNetwork So how is the progress of the project now? Many people are waiting for the results. Can you update the progress of the project in a timely manner?
We have been working on one of the most important long-term upgrades to the $Nulla protocol: making the ProofHub parachain quantum-resistant.
Today we want to share what we have accomplished so far.
What we changed:
The core of ProofHub is the verifier, the piece of code that runs inside the blockchain and checks that every private transaction is mathematically valid. We have replaced the original cryptographic primitives with quantum-safe alternatives:
ML-DSA-44 (NIST FIPS 204 standard) replaces the classical signature scheme for balance proofs
BLAKE3 replaces the elliptic-curve-based commitment scheme
STARK proofs (Winterfell) replace the classical range proof system
All three run entirely inside the on-chain WASM runtime, no off-chain trust assumptions.
What we tested:
We ran a full end-to-end test on our dev chain: a real transaction that generates a quantum-safe keypair, creates a BLAKE3 commitment, produces a STARK range proof, and submits everything as an unsigned extrinsic. The chain verified all three layers and emitted ProofAccepted on-chain. We are sharing a short video of this test running live.
PoS development is moving forward! The first BABE consensus implementation is on GitHub, with a few issues left to fix before the network switch.
We’re sharing daily updates on GitHub, don’t miss out!
github.com/NullaZK/NULLA/…
this video shows the node we just turned on in rpc-external mode that will be used as a sentry node for the explorer, this node has no authority capabilities and will be used only as an archive node.
We plan to finish the explorer setup tomorrow.
Hey community, what you’re seeing here it's a single-node dev chain feeding a public, non-authority sentry endpoint.
Our indexer connects to that endpoint, stores blocks, extrinsics, and events in Postgres, and serves a fast API and this minimal web UI, this is a demo environment, not our production chain. The goal here is only to validate the indexing stack and explorer.
The explorer shows new blocks as they arrive, with transaction status based on on-chain events: included, success/failure, and finalized. Some fields like section, method, signer, and hash may appear empty in this demo because we’re using a safe event-only fallback; in production we’ll wire runtime types so they’re fully decoded.
This setup keeps validators protected,the explorer talks only to the sentry node. The data you see is ephemeral and specific to this test; it’s not the actual chain.
Next steps for production: add runtime types, search, and deploy the stack behind HTTPS on a dedicated host, UI branding.