Sabitlenmiş Tweet
Veilnet
129 posts
Veilnet
@Veilnet_
FHE-powered encrypted state transitions settled on-chain through commitments, nullifiers, Merkle tree, and ZK proof 0xd13ba0d625c04b8364de5e15e58bf2ebdda8dba3
Base Katılım Mart 2026
26 Takip Edilen524 Takipçiler
@snipe1prins Our roadmap is fluid, we can adjust based on community feedback and what we see developing.
Our focus at the moment is VeilAI.
English
@Veilnet_ Impressive how quickly you adjust and optimize things. How do you currently determine what gets priority within VeilNet? Which milestones do you want to deliver in the coming period?
English
In the AI era, your prompts become part of your data footprint.
Welcome to VeilAI, part of the $VEILNET ecosystem.
Every question, strategy, research query, wallet context, trading idea, medical note, business plan, or agent instruction can reveal something about you.
That data is valuable.
It can be logged, analysed, used to improve systems, tied to accounts, linked to metadata, or become part of a wider behavioural profile.
This is why data ownership matters.
AI is moving from simple chat into execution:
agents
wallet actions
DeFi strategy
research workflows
payments
automation
identity-linked tasks
The more useful AI becomes, the more sensitive the prompts become.
Veil AI is our next step toward solving this.
The goal is to let users interact with AI without exposing every prompt, intent, wallet context, or instruction path as readable data.
We are building toward encrypted prompt usage where sensitive requests can move through a privacy layer before reaching the execution environment.
This means:
prompts encrypted before processing
private routing for sensitive requests
less exposed wallet/context leakage
privacy-aware AI interactions
future support for agentic workflows
AI should not require users to surrender their intent.
Your prompts are your data.
Veil AI is being built to help keep them private.
English
We have just rolled out an upgrade to Veil DEX.
You can now trade privately across a wider set of Base assets using Veilnet’s encrypted swap flow.
Supported assets now include:
ETH
USDC
cbBTC
POD
PITCH
VVV
KTA
OTHQ
BEAN
CGN
GITLAWB
VEILNET
WETH
Under the hood, Veil DEX uses FHE-based encrypted state handling and Merkle tree commitments to keep the swap lifecycle privacy-aware from input to settlement.
Users can also route received tokens back to the same wallet or to a separate destination wallet, adding another layer of unlinkability between the swap initiator and the final receiver.
This upgrade makes Veil DEX more than a private swap screen.
It turns it into an expanding private trading layer for Base assets:
encrypted swap intent
FHE-side private accounting
Merkle-committed balances
destination wallet routing
onchain settlement
All powered by $VEILNET
English
@skullzxmeta @bellinixo this is clearly a problem with your UI on uniswap.
Please make sure you are using the correct trading pool and uniswap v4 as we launched via @bankrbot
English
Encrypted AI prompts are now being tested inside Veilnet.
This is one of the next extensions of our privacy stack: bringing encrypted execution beyond transfers and swaps, and into AI interactions.
The idea is simple:
users should not have to expose sensitive prompts, wallet context, strategy requests, research queries, or agent instructions in plaintext.
Your AI data is your own.
A normal AI workflow leaks too much:
prompt content
IP / network metadata
wallet context
model request history
strategy intent
follow-on actions
Veilnet is testing a different flow:
user enters prompt
→ prompt is encrypted before execution
→ request is routed through a privacy layer
→ sensitive context is protected
→ AI response is returned through the app
→ optional onchain actions can later be verified and settled privately
For maximum privacy, this can be combined with Tor routing, so the request is not only protected at the content layer but also at the network layer.
The long-term direction is clear:
private transfers
private swaps
encrypted prompts
private agents
confidential AI workflows
$VEILNET is becoming more than a shielded transfer app.
It is becoming an encrypted application layer for DeFi, AI, and privacy-native onchain activity.
English
Veilnet retweetledi
Base has been pretty much interesting in the last 3 days and I’ve been actively researching for solid project with good product and thesis; found @Veilnet_ and my thesis below⬇️
Veilnet is an innovative privacy protocol designed to shield your assets and transactions on public blockchains.
It functions as a secure vault where deposits are pooled on‑chain, while individual balances and activities live in a private state accumulator managed by an off‑chain sequencer and represented as encrypted commitments in a Merkle tree.
In other words, these means that @Veilnet_ is privacy protocol that is made to protect your transaction from the public ledger which is the blockchain; once deposit is been made into the pool onchain the activity lives in a accumulator and it’s encrypted in a merkle tree.
Their architecture is literally interesting, was was inspired by a Fully hormomophic Encryption (FHE) which settles onchain through commitment, ZK proof, nullifier and merkle tree which provide encrypted computations and activities directly onchain without revealing transactions and data.
Core Features
- Shielded Balances: Your net worth within Veilnet is invisible to the public
- Shielded Addresses: Interactions do not publicly link your wallet to counterparties
- Private Transfers: Send tokens securely without leaving an on-chain trail
- Multi-Chain Support: Currently on Base and Ethereum, expanding to more EVM chains
Market thesis
$VEILNET has a native FHE DEX which one of the product in the ecosystem.
Full privacy with Merkle and Zk tech
They are the first FHE and zK proof privacy protocol on Base ecosystem.
Currently seating sub 300k mcap, feels like it’s a magic for this price currently an I believe it’s going to be trading for higher price soon.
Seating at 270k mcap;
0xd13BA0d625c04b8364De5e15E58Bf2eBDDA8DbA3
English
Veilnet is an Ecosystem.
It is a shared private execution environment.
The important part is the continuity between products:
A user can deposit into a vault, generate a private balance, move that balance through a shielded transfer, swap through Veil DEX, route output to a different wallet, and later interact with encrypted AI prompts — all without each action needing to expose the same public identity graph.
That is the technical shift.
Instead of every product creating a new isolated privacy flow, Veilnet is building around reusable private state.
Balances can be represented as commitments.
State transitions can be compressed into roots.
Nullifiers can enforce one-time use.
FHE-side computation can handle sensitive logic before public settlement.
Contracts can verify outcomes without needing the full plaintext context.
So the ecosystem is not just:
vault
DEX
transfers
AI
DeSci
It is a network of applications sharing the same privacy rail.
The vault is where private state begins.
Veil DEX is where private state becomes active liquidity.
Encrypted prompts are where private intent meets AI execution.
Future modules extend the same model into more onchain workflows.
The product layer is what users see.
The deeper system is a private state machine for onchain activity.
That is what $VEILNET is building.
English
@DevoutSol Yes once we hit certain goals in our roadmap we will be looking to collaborate and partner with relevant partners
English
Love it, you guys are shipping so fast I’d think you already have the entire stack built out and you’re just feeding us breadcrumbs ;)
Once this launches, do you plan to seek partnerships with some agent infra projects? I feel like that would be a great direction to bring initial AI users onto the platform.
English
Veilnet retweetledi
"Hades, I'm sorry for previously fading you. What are you buying now?"
Gems I've been accumulating 👇
➜ $VEILNET / @Veilnet_
Delivers contract-level privacy using FHE + ZK proofs + Merkle commitments + nullifiers to provide encrypted computations and actions directly onchain without revealing sensitive data.
Private vaults are already live, and their FHE-powered DEX (first ever on Base) is coming this week allowing true privacy onchain.
🔸 Key Selling Points:
- FHE-powered smart contracts for private onchain logic and computations
- Private vaults with encrypted token movements already shipping
- Upcoming native FHE DEX very soon
- Full privacy stack (FHE + ZK + Merkle + nullifiers)
- Critical infrastructure for private AI agents and confidential DeFi on Base + multi-chain
- Competitors like $OCT are sitting at $30M
---
➜ $ECHO / @BuiltByEcho
An autonomous agent that observes builders' pain points and ships tools to solve these problems.
Already shipped one of its major products, Vaultline, which is a storage and access layer wired directly to the x402 payment protocol.
This lets agents autonomously store, access, and pay for resources using seamless micropayments on Base.
🔸 Key Selling Points:
- Vaultline: Storage/access layer integrated with x402 for autonomous agent payments
- Reduces agent friction by enabling the right tool in the right workflow
- Practical infra play in Base’s exploding agent economy (Bankr-deployed, shipping real products)
- One of the only 5 accounts followed by @Darks0l_
----
➜ $COP / @clashofperps
A platform that gamifies perps trading turning UX into competitive, fun gameplay to onboard retail.
Already integrated with multiple perps platforms (Pacifica, Phoenix Trade, Decibel, GMX, etc), driving volume in millions to their DEXes through quests, campaigns, and cross-chain tournaments.
🔸 Key Selling Points:
- Proven volume driver for perps DEXes
- Trading + gameplay hybrid; volume on integrated perps DEXes earns points
- Regular tournaments with $COP prize pools across multiple chains and platforms (Pacifica, Decibel, Phoenix, GMX, etc.)
- Quests and campaigns that reward active participation
- Early buyers out and distribution is happening now.
I expect all of these to break $1M very soon.
You've been warned.
$VEILNET: 0xd13BA0d625c04b8364De5e15E58Bf2eBDDA8DbA3
$ECHO: 0xa7f63eb41779925803a3eec30890742571e63ba3
$COP: 0xd8db4c337d09da8d7ceb7d87adfe224d17785ba3
English
@VirtualMorales We have posted a video with live transactions below
x.com/Veilnet_/statu…
Veilnet@Veilnet_
Veil DEX testing is now underway on Base. This is a live test of our private DEX flow using real transactions on Base Mainnet. Public Release of Veil DEX will be soon. Route tested: USDC → ETH Input: 0.02 USDC This is not a normal public DEX swap. A normal swap exposes the entire execution path: wallet address token pair amount in expected output route timing router interaction execution behaviour follow-on wallet activity Veil DEX is designed to change the swap lifecycle by moving sensitive intent and state handling into Veilnet’s encrypted execution model before settlement becomes public. The tested flow: 1. User approves Veil DEX The user approves the Veil DEX contract to spend 0.02 USDC. approve(Veil DEX, 20000) Tx: basescan.org/tx/0xef32b92c1… 2. User deposits USDC into Veil DEX The user deposits 0.02 USDC into the Veil DEX contract. deposit(USDC, 20000) Tx: basescan.org/tx/0xb89a3521f… This creates the input-side private state for the swap. Instead of the user directly broadcasting a standard wallet → router → DEX path, the value first enters Veil DEX’s encrypted execution flow. 3. Off-chain FHE state preparation After the deposit, the sensitive swap parameters are prepared off-chain. The private state can be represented as encrypted values rather than public plaintext values. Conceptually, the system is dealing with encrypted arithmetic over swap state: encrypted input amount encrypted balance update encrypted asset transition encrypted output accounting encrypted state delta The chain does not need to inspect the full plaintext swap context. It only needs the resulting commitment, nullifier data, proof material, and settlement instructions. 4. Merkle root #1 is committed Root #1 represents the committed input state: user USDC amountIn Root: 0xdc3d4c5862abe5bc247baf0b1ac92d4a27043a63ec815d8f471a5afbbb32c659 updateMerkleRoot(root1) Tx: basescan.org/tx/0x0daaa48e5… Instead of publishing the full private state transition, Veilnet compresses the state into a Merkle root. The root becomes the public reference. The underlying private path does not. 5. Shielded swap execution The swap is then executed through the Veil DEX flow. Quote: 0.02 USDC → 0.000009473027280205 ETH Slippage: 500 bps Minimum output: 0.000008999375916194 ETH SwapAuth nullifier: 0x3558d765ce5db37209d2259384de196e433a8e8ff93aa1cb6325c5cbd3bcbe0d adminExecuteSwap Tx: basescan.org/tx/0xfdf4123fd… This is the core test transaction. Behind the scenes, the FHE-side flow is used to handle the sensitive swap logic before settlement. The encrypted computation layer can process private state transitions using ciphertext-side arithmetic, where the system updates balances, transition values, and state deltas without turning the full intent path into public transaction data. The output ETH is credited into Veil DEX reserves first. That matters because the execution is not simply presented as a direct public user swap path. The swap is mediated through: encrypted state preparation FHE-based private computation Merkle commitment tracking nullifier protection contract verification onchain settlement 6. Merkle root #2 is committed After the swap, a second root is committed. Root #2 represents the updated output-side private state: user ETH amountOut Root: 0x4217510bbf0b825e71629a6862d14a5c1cb146893262f492ad6b378afdf25633 updateMerkleRoot(root2) Tx: basescan.org/tx/0x392c9cb9d… This records the post-swap state transition. The chain can verify that state changed. But it does not need the full plaintext computation path behind the swap. 7. ETH payout is withdrawn to the user The final step withdraws the ETH output to the user. Withdraw leaf: token = ETH Balance: 9473027280205 wei Nullifier: 0xf17677cf48d750e47972cab371b3e921d2507911dea5f08f8a0130eb7b4231b6 adminWithdraw(leaf 1) Tx: basescan.org/tx/0x5de298343… This completes the tested swap lifecycle: USDC deposited input state encrypted and prepared FHE-side arithmetic handles private state logic Merkle root commits input state swap executes output state is committed nullifier prevents reuse ETH is withdrawn settlement completes onchain The public chain can still see contract calls, root updates, and settlement. But the full swap lifecycle is no longer expressed as a simple public wallet → router → pair route. That is the point of Veil DEX. A normal DEX makes the trade path public by default. Veil DEX is being built to move sensitive swap intent into encrypted execution, use FHE-style computation for private state handling, compress state transitions into Merkle commitments, and settle through verifiable contracts onchain. The chain remains verifiable. The user path becomes more private. This is the first live testing phase toward the first FHE-powered DEX experience. Shielded transfers proved the privacy rail. Veil DEX brings that rail into active DeFi execution, powered through $VEILNET
English
Veil DEX is live, but this is only the first version.
Next, we’re looking to build out the utility layer around it:
limit orders
expanded liquidity pools
more token pairs
improved routing
deeper execution options
additional privacy-focused swap features
The goal is to make Veil DEX more than a simple swap interface.
We want it to become a full private trading environment powered by Veilnet’s encrypted execution architecture.
A normal DEX exposes almost every part of a trade:
wallet
pair
amount
timing
route
follow-on activity
Veil DEX is designed to reduce that leakage by moving sensitive swap intent into a private execution path, using encrypted state handling, Merkle commitments, nullifier protection, and onchain settlement.
The current release proves the core flow.
The next phase is about depth, utility, and better execution.
Private swaps are live.
Now we expand what private trading can do with $VEILNET.
English
@SamariSaddler It will be directly integrated into the Veilnet ecosystem.
English
@Veilnet_ Are you planning to eventually integrate private AI interactions directly into the Veil ecosystem/wallet experience, or keep the AI tooling separate from the DEX side?
Really interesting direction for AI privacy + encrypted execution. Been a great ride so far.
English
This is just the beginning of the $VEILNET journey.
We are passionate about tackling privacy in AI.
Your data is your property and your AI prompts should not be compiled as part of a database.
Currently under development and testing is encrypting your prompts sent to AI LLM's.
Testing underway and more info coming soon.
Veilnet@Veilnet_
Veil DEX is now live. app.veilnet.to/veil-dex The first release is live with 5 active pairs: ETH / USDC ETH / VIRTUAL ETH / KEYCAT ETH / MFER ETH / SPACEX More pairs will be added over the next few days as we continue expanding liquidity routes and testing live execution across the Veilnet ecosystem. Veil DEX is built around one core idea: swaps should not expose the full user path by default. A normal DEX trade can reveal: wallet address token pair input amount output amount route timing trading behaviour follow-on wallet activity Veil DEX introduces a different execution flow. User selects swap → swap intent is encrypted → private swap state is prepared → off-chain FHE computation handles sensitive arithmetic → Merkle commitments record private state transitions → nullifiers prevent reuse → contracts verify and settle onchain The public chain still gets the important parts: valid execution state commitment settlement asset movement But the user does not have to expose the full plaintext swap path in the same way as a normal public trade. To increase privacy even further, users can choose where they receive the output tokens: back into their own wallet or into a separate destination wallet That means the swap result does not always need to return to the same visible address that initiated the interaction. Private transfers proved the rail. Veil DEX brings that rail into live DeFi execution. The first FHE-powered DEX experience is live. All under the $VEILNET umbrella.
English
@DevoutSol Much more to come!
Check our roadmap to see what we have planned.
x.com/Veilnet_/statu…
Veilnet@Veilnet_
English
@Veilnet_ Thank you for the clarification and transparency. It seems like you have a lot in your pipeline, I’m very excited to see this project grow over the coming months.
English
Thank you for your support.
Yeah, the best way to frame it would be like this:
Octra and Veilnet are both working toward the same broad idea: encrypted computation becoming a core part of crypto.
The difference is in the approach.
Octra is building encrypted compute infrastructure.
Veilnet is building a private application ecosystem powered by encrypted execution.
We’re not trying to be a new L1. We’re focused on bringing privacy directly into existing onchain user flows, starting on Base.
English
@Veilnet_ Love how quickly you’re delivering, extremely bullish on this team.
Can you compare/contrast this project from Octra? What are some differentiating initiatives in your roadmap?
English
Good question. The way to think about it is: prompt privacy is not just “encrypt the message and hope for the best.”
It is a stack.
The prompt is encrypted in the browser before it touches our backend (using Arcium's RescueCipher flow) to AWS Nitros Enclave that handles the model path.
So when the prompt leaves the users device it is already ciphertext not plaintext.
And to protect user's anonymity we route every outbound call through Tor Sock55. Each Veilnet user can be isolated through a separate Tor circuit, so the inference provider sees a Tor exit path instead of the user’s IP or our server IP.
There is more to it, but we will be revealing all in the next few days, stay tuned.
English
Veil DEX is now live.
app.veilnet.to/veil-dex
The first release is live with 5 active pairs:
ETH / USDC
ETH / VIRTUAL
ETH / KEYCAT
ETH / MFER
ETH / SPACEX
More pairs will be added over the next few days as we continue expanding liquidity routes and testing live execution across the Veilnet ecosystem.
Veil DEX is built around one core idea:
swaps should not expose the full user path by default.
A normal DEX trade can reveal:
wallet address
token pair
input amount
output amount
route
timing
trading behaviour
follow-on wallet activity
Veil DEX introduces a different execution flow.
User selects swap
→ swap intent is encrypted
→ private swap state is prepared
→ off-chain FHE computation handles sensitive arithmetic
→ Merkle commitments record private state transitions
→ nullifiers prevent reuse
→ contracts verify and settle onchain
The public chain still gets the important parts:
valid execution
state commitment
settlement
asset movement
But the user does not have to expose the full plaintext swap path in the same way as a normal public trade.
To increase privacy even further, users can choose where they receive the output tokens:
back into their own wallet
or into a separate destination wallet
That means the swap result does not always need to return to the same visible address that initiated the interaction.
Private transfers proved the rail.
Veil DEX brings that rail into live DeFi execution.
The first FHE-powered DEX experience is live.
All under the $VEILNET umbrella.
English
Veilnet retweetledi
$VEILNET on @base looks like a solid early privacy infrastructure play.
I shared it in my privates around 100k mc and guess where it's at now... 350k MC
For me personally, it's easily one of the best privacy projects live on Base right now.
The @veilnet_ team is building a full encrypted execution layer for EVM chains (Base + ETH already live, more coming).
The core tech is FHE + ZK proofs so smart contracts can run on encrypted data without exposing any onchain data until you choose to selectively disclose.
Pretty clean infrastructure so far and I'm also in this time.
@OnlyHades_ @Crypto_Jopp @HanzoYasunaga
English