VeilOn Announcement
54 subscribers
75 photos
1 video
45 links
A zk-native cross-chain wallet and protocol for private, untraceable transfers, swaps, and bridging powered by stealth addresses & encrypted transaction layers.

https://linktr.ee/VEILONWALLET
Download Telegram
What does the network pay for?

Relayers earn when they deliver. The core payout is tied to the successful inclusion of a user’s transaction within a target window.

The fee is transparent to the user (quoted up front) and is settled on-chain or in-protocol. On top of the base fee, two elements adjust the economics:

▫️Congestion factor: compensates for volatile gas and bursty demand.

▫️Quality multiplier: rewards sustained uptime, low failure rates, and tight inclusion times.

A Relayer that habitually lands transactions quickly and without error earns slightly more per job than one that cuts corners.

This is not goodwill; it’s arithmetic. The protocol wants to direct sensitive traffic to proven operators without locking out new entrants.
1
Private Airdrops | Eligibility Proofs | Private Claims

Public airdrops leak intent and wallets. Veilon keeps the distribution verifiable while recipients stay unseen.

What you will read in the article:

▫️Core idea
▫️How it works
▫️Why this helps
▫️Set-up patterns for issuers
▫️Recipient playbook
▫️Trade-offs to acknowledge
▫️Others

Read it now: https://x.com/Veilonwallet/status/1967241936005468390
1
MEV-Safe Swaps | Shielded intents via relayers ✔️

Veilon routes swap intents through relayers and settles from shielded notes. Mempools see a proof and a Merkle root update; not your address or fee pattern. The DEX executes against validated notes; nullifiers stop double spend.

What changes for you:

▫️ No public fee trail.
▫️ Less sniping and sandwich risk.
▫️ Funds stay non-custodial until fill.
▫️ Finality is verifiable via proofs.

Checklist:

▫️ Keep funds shielded between steps.
▫️ Use sane slippage and timeouts.
▫️ Avoid distinctive amounts.
▫️ Configure multiple relayers; rotate if congested.
▫️ Teams: publish aggregates only; use scoped viewing keys for audits.

» Result: intent stays private; settlement stays verifiable; Veilon gives MEV less to work with.
Please open Telegram to view this post
VIEW IN TELEGRAM
1
Validator & Staking Payouts | Quiet Mode

Validator income is predictable; that also makes it easy to profile. Veilon routes rewards to stealth wallets so operators settle earnings without exposing strategy or treasury maps.

Point payouts to a shielded address; distributions land as private notes. When broadcasts are needed, relayers submit and get reimbursed inside the shielded system; chains verify proofs and root updates; not who earned what.

Finance teams read totals with scoped viewing keys; no spend rights; expiry set.

Why it helps?

▫️Breaks the link between validator identity and payout timing.

▫️Removes fee and amount fingerprints from dashboards.

▫️Keeps custody non-custodial; funds remain in your notes.

▫️Audits work through time-boxed viewing keys.

Proofs add compute; deeper pools improve crowding; reliable relayers matter.

The outcome is clean separation of identity and income; rewards arrive quietly; reporting stays verifiable on your terms with Veilon.
1
PoL-Gated Deposits | Disclose only what is needed

Some venues want provenance checks without harvesting your history. Veilon supports Proof of Innocence (PoL): you prove your funds are not linked to a restricted set; the venue learns the outcome, not your wallet graph.

A deposit flow looks like this: the exchange publishes a policy set; your wallet builds a PoL against shielded notes; a relayer submits the proof; the venue verifies and accepts the deposit or enables features. On chain, observers see a proof verified and root updates; not your address or route.

What is revealed: proof validity, policy identifier, and time window. What stays private: counterparties, exact amounts, intermediate hops.

For venues

▫️ Request a specific policy; verify locally; store the decision, not the user’s path.
▫️ Offer expiry on approvals; re-check only when policy changes.
▫️ Use viewing keys for aggregate reporting; never for spend.

For users

▫️ Keep funds shielded between steps; generate PoL just-in-time.
▫️ Prefer fresh stealth addresses for deposit credit.
▫️ Share viewing keys only when scoped and time-boxed.

>> Result: compliance without oversharing; your deposit is accepted on facts, not on a dossier.
3
Recurring On-Chain Subscriptions | Private by default

Recurring payments are useful; they also leak patterns. Public ledgers expose who paid whom and when.

Veilon keeps the schedule while hiding the trail; each cycle proves under shield; relayers cover gas; chains verify structure, not people. Timing windows break profiling signatures.

📰 Learn more: https://x.com/Veilonwallet/status/1969743317538840583
3
Anonymous DAO Voting | zk ballots with public tallies

DAO votes often leak more than outcomes. Wallet addresses tied to ballots create maps of governance alignments and treasury influence.

Veilon applies zero-knowledge proofs so members can cast ballots without exposing their identity. The chain verifies that each vote is valid, tallies results openly, and prevents double voting through nullifiers.

What remains visible is the outcome; what stays hidden is who voted and how they aligned. Each ballot is a private note committed under shield; when it is used, only a nullifier signals that the right was exercised. Observers cannot reconstruct voter graphs or trace alliances across proposals.

Audits are still possible. DAO treasurers can issue time-boxed viewing keys to external reviewers, scoped only to specific proposals or periods. These keys allow observers to confirm turnout or quorum without learning the voter list.

Results >> remain trustworthy, yet the community avoids the surveillance footprint that public ballots often create.
1
🛡 Shielded Liquidity Provision | AMM without LP doxxing

Providing liquidity usually doxxes strategy. Each add or remove action on public chains ties back to a wallet.

Veilon hides that trail by converting deposits into shielded notes; relayers submit proofs; pools update totals privately.

On chain, only this is visible:

▫️ Proof verified
▫️ Nullifier consumed
▫️ New Merkle root

What stays hidden:

▫️ Wallet identity behind liquidity
▫️ Exact deposit or withdrawal size
▫️ Timing habits of LP strategies

How rewards flow:

▫️ Fees settle into stealth wallets
▫️ Rewards unlinkable to deposits
▫️ No route leakage to LP identity

For protocols:

▫️ Pool health metrics stay public
▫️ Proof pass rates confirm validity
▫️ Scoped viewing keys allow aggregate audits

Result: liquidity is visible; strategies are not. LPs keep privacy while AMMs remain verifiable.
Please open Telegram to view this post
VIEW IN TELEGRAM
1
Private Perp Positions | shielded leverage

Perpetual futures are a favorite target for analysis. Every wallet that opens or closes a position on a public chain leaves a pattern: size, leverage, timing, and eventual liquidation history. Veilon removes those traces.

>> Positions are funded from shielded notes; proofs confirm validity; and relayers cover gas so no fee trail links back to the trader.

When a position is opened, the contract sees only that a valid proof is presented and funds are locked. The details of which wallet provided them remain hidden. As trades close, settlement is verified through nullifiers, ensuring positions cannot be double-used, but without mapping profits or losses to identities.

The chain still shows what matters, total open interest, collateralization levels, and settlement health, while individual strategies stay private. Traders avoid being profiled; protocols maintain transparency over risk.

>> The result is leverage with accountability, but without exposing wallets to copy-trading or predatory analysis.
1
Gasless Relays | Decoupling Fees from Identity

Paying gas from your wallet ties address to action. Veilon uses relayers to cover gas; reimbursements happen privately inside the shielded system. You sign an encrypted intent; a relayer broadcasts; the chain sees a zk proof and a Merkle root update; not your address. The relayer observes transport metadata for reliability; not who you are or what you paid.

Benefits: fee behavior no longer fingerprints you; onboarding is smoother; control remains non-custodial. Trade-offs: relayer availability and reimbursement lag; network fees still apply; mitigate with multiple relayers and a fallback.

Setup hygiene:

• Enable gasless in wallet settings.
• Keep funds shielded between steps.
• Avoid tiny repetitive reimburse amounts.
• Rotate relayers; keep logs minimal.
• Teams: pre-fund a project vault; reimburse on schedule; publish aggregates only.

Compliance:

• Finance: use scoped viewing keys for reimburse totals.
• Partners: request Proof of Innocence when a source-of-funds check is needed.

Gasless relays separate cost from identity; proofs keep settlement verifiable while your wallet avoids public fee trails.
1
Cross-Chain Quiet Claims | Bridge with shield

Bridges usually spill routes; source wallet to target wallet becomes a public thread. Veilon treats a claim like a private note. You shield on the source chain; the wallet creates a commitment; a relayer carries the encrypted proof; and gas is handled off-path. On the target chain the verifier checks the proof against published roots and credits a fresh stealth address. The relayer later gets reimbursed inside the shielded system; not from your public account.

From the outside the ledger shows structure; not people. Observers see Merkle root updates; proof verification events; and a nullifier that marks the claim as used. They do not see the route that moved value from chain A to chain B; nor the wallets on either end.

Veilon keeps auditability without exposing the path. Programs can publish per-epoch totals with a receipt hash that proves inclusion; no recipient list attached. If partners need a closer look; time-boxed viewing keys can reveal only the narrow slice they are entitled to see.

There are trade-offs. Proofs add compute; deeper pools give better crowding; coordination with reliable relayers matters.

>> The result is simple; assets arrive where you want them while the route never becomes someone else’s roadmap.
3
Shielded Yield Harvesting | Auto-compound in private

Yield farming often leaks strategy. Every claim or compound is a signal—wallet balance, reward timing, gas habits. Veilon shields these moves. Rewards flow into notes; compounding runs under proof; and relayers cover gas so no address is tied to the action.

Nullifiers guarantee rewards are claimed once without showing who claimed them. On chain, observers see proof verification and root updates; not which wallet harvested or how much. Strategies remain private, while the system prevents double claims.

Protocols still track health: total rewards distributed, proof success rates, and pool growth. If audits are needed, scoped viewing keys reveal aggregates for a program or epoch, never individual farmer details.

For users, this means rewards compound quietly, balances stay shielded, and harvesting no longer gives away timing or scale.

>> The result: yield optimization with verifiable integrity, but no strategy doxxing.
1
Auditable Yet Private | Scoping Viewing Keys 👁‍🗨

Viewing keys are read-only; they let others verify activity on your terms without spend rights. Scope them narrowly so audits work without exposing strategy.

Scope dimensions:

▫️ What: balances only; or specific notes; hide memos and counterparties.
▫️ When: start and end dates; auto-expiry after review.
▫️Where: a single vault or project wallet; not the entire account.
▫️ Amount: ceilings or rounded values to avoid exact pricing.
▫️ Event type: incoming only; settlement proofs only; exclude internal moves.

Controls:

✔️ Rotate keys on staff changes; revoke immediately after use.
✔️ Log access at the system level; never per-user telemetry.
✔️ Pair with Proof of Innocence if a source-of-funds check is required.

Keep scopes minimal; test wit
Please open Telegram to view this post
VIEW IN TELEGRAM
1
Recurring On-Chain Subscriptions | Private by default

Recurring payments are useful; they also leak patterns. Public ledgers expose who paid whom and when.

Veilon keeps the schedule while hiding the trail; each cycle proves under shield; relayers cover gas; chains verify structure, not people. Timing windows break profiling signatures.

📰 Learn more: https://x.com/Veilonwallet/status/1975232153341637069
4
How Veilon Schedules Private Charges

You enroll by selecting a plan, cadence, and a spend cap. The wallet prepares commitments that authorize one cycle at a time; funds remain shielded between cycles.

When a due window opens, the wallet assembles a proof, encrypts the intent, and sends it to a relayer. The relayer broadcasts, covers gas, and is reimbursed privately inside Veilon. Settlement credits a fresh stealth address controlled by the merchant. From start to finish, there is no public fee trail tied to you.

For resilience, the wallet can retry within a small randomized window if the first attempt fails. If a cycle cannot be completed, the wallet can issue a zero-knowledge non-payment notice tied to the same program identifier; the merchant learns that access should pause, not who you are.

▫️ Keep a buffer in your shielded vault.
▫️ Prefer rounded tier prices to avoid unique amount fingerprints.
▫️ If you must unshield for off-chain rails, do it once after funds arrive to a personal stealth address.
🔥6
Back to The Basic | How Does VEILON Generate Revenue?

VEILON ensures sustainability through clearly defined revenue streams that feed into its decentralized treasury:

> Shielding and Unshielding Fees: Each transaction into or out of the privacy layer carries a small fee. Users pay modest amounts, fueling treasury growth without high barriers.

> Private DEX Trading Fees: VEILON hosts its own private decentralized exchange, where token swaps incur fees. This revenue stream grows with trading volume, creating a steady income source for the DAO treasury.

> Premium Features: Features like VEILON’s built-in sniper service, enabling anonymous early trading at token launches, carry premium fees. Traders pay for privacy and a competitive edge.

> Enterprise Compliance Integrations: Enterprises requiring Proof of Innocence or selective audits pay fees for optional compliance services, further diversifying revenue.

All fees collected go directly into VEILON’s DAO-controlled treasury, funding continued development, liquidity incentives, and ecosystem growth. It’s a balanced, transparent financial structure, aligning user privacy with platform sustainability.
🔥8
Few days to the end of our thread contest

You still have a chance to get in and stand a chance to win from our $500 prize pool

Don't forget to follow all instructions to be eligible to participate

See quoted tweet for more information

https://x.com/Veilonwallet/status/1978018848281440613
🔥25🥰6
Build With Veilon: SDK Overview

Ship privacy without heavy backend work. Veilon’s tools add zero-knowledge privacy to wallets and dApps; non-custodial; on-chain; developer-friendly.

Integrate encrypted balances, private swaps, and confidential transactions with minimal code.

The stack is on-chain by design across Ethereum, Polygon, Arbitrum, BSC, and more; no off-chain dependencies.

https://x.com/Veilonwallet/status/1978510581108789741

Website
Whitepaper
GitHub
👍11🔥4
Merkle Roots | Sync and Validation

In Veilon, shielded transfers are represented as commitments inserted as Merkle tree leaves. As leaves accumulate, the tree’s Merkle root changes; this root is the public commitment to the current note set.

Proofs reference a root; validators check that the proof is valid for a recognized, recent root; then record the transition. The ledger shows structure; not people

https://x.com/Veilonwallet/status/1979226328722448407

Website
Whitepaper
GitHub
23🔥5👨‍💻1
𝙃𝙉𝙄 𝘼𝙨𝙨𝙚𝙩 𝙋𝙧𝙞𝙫𝙖𝙘𝙮 & 𝙋𝙧𝙤𝙩𝙚𝙘𝙩𝙞𝙤𝙣 | 𝙗𝙚 𝙮𝙤𝙪𝙧 𝙤𝙬𝙣 𝙥𝙧𝙞𝙫𝙖𝙩𝙚 𝙗𝙖𝙣𝙠 𝙬𝙞𝙩𝙝𝙤𝙪𝙩 𝙩𝙝𝙚 𝙚𝙭𝙥𝙤𝙨𝙪𝙧𝙚

Large wallets attract attention; both on-chain and off.

Veilon equips high networth users with tools to keep holdings and movements discreet while preserving verifiability.

You can hide balance visibility from public explorers; run stealth payments or internal transfers; and hold assets across chains in shielded states so routes and counterparties stay out of view.

When required, you can also prove clean origin of funds using an opt-in check without exposing your broader history.

• Obscure balances from public explorers

• Conduct stealth payments or internal transfers

• Secure assets across chains in shielded states

• Prove clean origin of funds (optional)

The goal is simple, operate like your own private bank without the usual exposure.

Veilon’s model focuses on minimizing what observers can learn while allowing you to move value and demonstrate compliance on your terms.

Whitepaper
Website
GitHub
❤‍🔥18🔥32
Our thread contest has officially come to an end

Team is currently reviewing all entries and winners will be announced soon

Goodluck to all participants

https://x.com/Veilonwallet/status/1980594706070585554
🔥176