Founder & CEO @arxoninfra (First EVM-compatible Selective privacy Layer-1 with four privacy flag mask)
Joined October 2025
- Tweets2.2K
- Following23
- Followers445
- Likes3.3K
Pinned Tweet
We did it! @arxoninfra
Congratulations to all the Arxon development team and partners.
The first L1 Blockchain with independent four flag for Selective privacy Txn is officially possible with Arxon Blockchain.
In a single Txn you can now officially
- Hide sender's wallet address
- Hide receiver's address
- Hide Txn amount
- Hide your wallet balance from being able to see by the public at any point.
And you can make any public in a same txn whatever you chose to hide.
This is just the beginning of a revolution.
Expect our Arxon official whitepaper soon
It's called centralised Exchange for a reason, don't be silly about it that your funds got frozen.
Even when we want decentralisation, there are users who still want a controlled system too
Privacy will be one of those. Quite underestimated because the chain delivering the variety of privacy technology is in development.
But 2027 will yield a high demand for Privacy differently.
We chose Halo2 over the pasta curves to eliminate the trusted setup entirely.
Arxon privacy and integrity rely strictly on pure maths. Our privacy model means mathematical certainty. Users do not have to trust that a group of developers destroyed their setup keys.
Many production zero knowledge systems, including the Groth16 proofs of Zcash’s Sapling pool and of most mixers, need a trusted setup: a ceremony that produces parameters and must destroy a secret along the way. If the secret survives, whoever holds it can forge proofs and mint value that nobody can detect. Ceremonies have been run carefully, with many participants, but the assumption never goes away.
Arxon uses Halo2 with the inner product argument (IPA) as its polynomial commitment. There is no ceremony and no secret to destroy.
Read more here>> arxon.io/blog/why-arxon-chos…
I love how this article breaks down our IPA method in proofing our selective privacy using Halo2.
It's a good read.
Many production zero knowledge systems, including the Groth16 proofs of Zcash’s Sapling pool and of most mixers, need a trusted setup: a ceremony that produces parameters and must destroy a secret along the way. If the secret survives, whoever holds it can forge proofs and mint value that nobody can detect. Ceremonies have been run carefully, with many participants, but the assumption never goes away.
Arxon uses Halo2 with the inner product argument (IPA) as its polynomial commitment. There is no ceremony and no secret to destroy.
Read more here>> arxon.io/blog/why-arxon-chos…
Gabe retweeted
Our weekly blog explaining Arxon Technology and more updates and announcements is now live on our site
arxon.io/blog/
Check the section out
Being calculatively impulsive is a huge advantage in any field of life.
Be calculative and impulsive then you're unstoppable.
Glad to have you onboard @ZyraV21
What's about to happen next will be too loud 🔥
Gabe retweeted
Cooking something really interesting for @arxoninfra , keep tuned :D
A successful life is a very boring one.
Same routine everyday for a long period of time till it makes sense.
It's learn, work, evolve and repeated over and over again
One full year building every single day.
I'm glad for how the building process is turning out with the amazing Arxon team.
We keep scaling because everything else coming next is big.
Today made it, One year of building Arxon.
A year ago, we set out to build something that didn't exist yet: a sovereign Layer-1 with real, base-layer privacy, not bolted on, not app-specific, but native to the chain itself.
No hype cycles. No shortcuts. Just steady building.
Here's where we are:
• A Live Chain: The Arxon Chain was Built from scratch with integration of Frontier for full EVM compatibility with ongoing within the development team, running on BABE/GRANDPA consensus.
• Arxon Privacy Model: Four independent toggles (sender, receiver, amount, balance) architecture no other sovereign L1 has implemented at the base layer. ZK circuit development and formal audit underway with zk audits companies.
• Growing Community: 25000+ confirmed, authenticated users. With growing Ambassadors who are representing Arxon to their regional communities driving real community growth, not paid engagement.
• Our App Product: Arxon mobile app live on the Play Store, and coming soon on app store with in-app mining and games built to onboard users into the ecosystem.
This is not a rushed development. It's steady, ongoing work because privacy people can actually trust takes time to build right.
Year two starts now. 🚀
Gabe retweeted
Today made it, One year of building Arxon.
A year ago, we set out to build something that didn't exist yet: a sovereign Layer-1 with real, base-layer privacy, not bolted on, not app-specific, but native to the chain itself.
No hype cycles. No shortcuts. Just steady building.
Here's where we are:
• A Live Chain: The Arxon Chain was Built from scratch with integration of Frontier for full EVM compatibility with ongoing within the development team, running on BABE/GRANDPA consensus.
• Arxon Privacy Model: Four independent toggles (sender, receiver, amount, balance) architecture no other sovereign L1 has implemented at the base layer. ZK circuit development and formal audit underway with zk audits companies.
• Growing Community: 25000+ confirmed, authenticated users. With growing Ambassadors who are representing Arxon to their regional communities driving real community growth, not paid engagement.
• Our App Product: Arxon mobile app live on the Play Store, and coming soon on app store with in-app mining and games built to onboard users into the ecosystem.
This is not a rushed development. It's steady, ongoing work because privacy people can actually trust takes time to build right.
Year two starts now. 🚀
