ZWeave — see how your Solana wallets link together

What it is

A privacy check-up for people with more than one wallet.

Most people keep a few wallets apart on purpose: one for savings, one for trading, one for the NFT you minted at 2 a.m. On a public chain, those walls are thinner than they look. ZWeave reads the public history of wallets you own and shows exactly which threads connect them — and how strong each one is.

For anyone who wants to know what an onlooker can infer before someone else does it for them.
Answers “can these wallets be tied together, and by what?” — with the transactions as evidence.
Gives concrete, lawful hygiene tips for each thread it finds.
Keeps nothing: no accounts, no database of audits, no analytics.

What you’re looking at

Reading the loom.

Before you paste anything, the hero shows an idle loom — decoration only, no data. After an audit, every shape and thread maps to something real on-chain.

Your wallets

Bright cores with spinning rings, lettered A, B, C… in the order you pasted them.

First funders

Saffron diamonds: the address that sent each wallet its first SOL, when the scan reaches back that far.

Counterparties

Wire spheres are busy hubs (exchanges, bots, services). Warm solid beads are quiet addresses — often personal, or a deposit address unique to one customer.

Thread thickness

More strands = stronger evidence. Three twisted strands mean an outright tie; a single fine thread is a weak hint.

Dashed threads

Behavioural links: acting within the same minute again and again, or keeping the same hours.

Travelling light

Pulses that run along a thread only show direction of reading — they’re motion, not money.

Crimson direct transfers between your wallets
Saffron who funded whom first
Magenta one wallet paid fees for, or co-signed with, another
Teal the same counterparty in plain transfers
Violet lockstep timing
Blue the same less-common tokens, same hours of the day

How it works

Four steps, one bounded scan.

You paste wallets. Up to 3 (8 with Pro), each with an optional nickname. They go to our server over HTTPS — and only there.
One bounded read. The server asks Solana RPC for each wallet’s most recent 1,000 signatures (getSignaturesForAddress), samples 16 transactions (getTransaction, v0 and v1 formats), lists token holdings (getTokenAccountsByOwner) and classifies up to 6 shared counterparties (getMultipleAccounts + a 25-signature activity probe).
Weaving, in memory. It intersects the histories: transactions you share, who funded each wallet first, the same deposit addresses, activity inside the same minute compared with what chance would produce, and uncommon tokens you hold in common.
Your browser draws it. The result comes back as a graph that three.js renders as twisted threads. The job stays in memory for 10 minutes so the page can fetch it, then it’s gone.

What it can’t see

A free audit reads at most ~73 RPC calls’ worth of data and stops after 55 seconds. Wallets with long histories are sampled, so a link that happened in an unread transaction can be missed — a “clear” result is not proof that wallets are unlinkable. Off-chain data (exchange accounts, IP addresses, RPC logs, analytics firms) is invisible to ZWeave and can link wallets that look clean here.

Built with

Small, sharp, no trackers.

three.js r169 served from this site — tube-geometry threads with a custom GLSL pulse shader, additive blending and Unreal bloom.
3D force layout computed in your browser; adaptive quality drops bloom and resolution on slow frames, pauses when the tab is hidden.
Zero-dependency Node server: hand-rolled base58, ed25519 verification, ATA derivation and v0 transaction encoding.
Frugal RPC: one throttled queue with hard timeouts and a watchdog; 2 audits at a time; v1 transactions supported.
Self-hosted fonts (Fraunces, Manrope, JetBrains Mono) and a strict Content-Security-Policy: no third-party requests at all.

Features

Free for the basics. Deeper with Pro.

Free

Audit up to 3 wallets at once
1,000 most recent signatures per wallet
16 sampled transactions per wallet + up to 6 shared transactions read in full
First-funder detection, shared counterparties, timing and token overlap
3D thread map, evidence links, hygiene tips

Unlock with the coin

Audit up to 8 wallets at once (28 pairs)
Deeper history: 3,000 signatures and 36 samples per wallet, 18 shared reads, 20 counterparty probes
PNG and PDF report with the full evidence appendix
50,000 tokens burned → 30 days, stacking

The coin

Burn to unlock. That’s the whole job.

ZWeave’s coin has one purpose here: you burn some in your own wallet transaction to unlock Pro. The server builds the transaction, your wallet signs it, and the server checks on-chain that the tokens were destroyed before it unlocks anything.

Burning destroys tokens permanently. It gives no return, revenue share or financial right. The free version stays free.

Burn ledger

The ledger opens when the coin is live.

Privacy & safety

The trust model, in plain words.

What our server can see

The wallet addresses you paste (and their nicknames) — needed to read their history. They live in memory for the audit and up to 10 minutes after, then they’re dropped.
Your IP address, like every web server. It is used only for in-memory rate-limit counters that reset within the hour, never written to disk or logged with an audit.
If you sign in for Pro: your wallet address, the fact that it ran an audit, and your Pro expiry date (stored so Pro survives restarts).

What we never do

Write audits to disk, keep a history, or log the addresses you check.
Run analytics, load third-party scripts, fonts or pixels.
Ask for a seed phrase or private key, hold funds, or move funds. Signing in is a free message signature.
Show you a burn without the exact amount first.

Who else sees something

Our Solana RPC provider sees the lookups for your addresses — coming from our server’s IP, not yours. The RPC key never reaches your browser.
Solscan, if you click an evidence link.
The blockchain itself: everything ZWeave shows is already public to anyone who looks.

ZWeave is a personal-privacy tool for wallets you own. It does not mix, tumble or hide funds, and its tips are about not leaking more than you mean to — not about evading exchanges, sanctions or law enforcement.

FAQ

Questions, answered.

Is the data live?

Yes. Every audit reads Solana mainnet at the moment you press Weave. The same set of wallets is answered from a 10-minute in-memory cache to save RPC calls.

Why does it say “faint” or “clear” when I know they’re linked?

ZWeave reads a bounded sample. A busy wallet’s link may sit in a transaction outside the 1,000 most recent signatures or between samples. Pro reads three times deeper. And off-chain links (exchange accounts, IPs) are invisible to it by design.

Can I audit someone else’s wallets?

ZWeave is meant for your own wallets. It shows nothing a block explorer wouldn’t, but please use it for what it’s for: checking your own exposure.

Does it cost anything?

No. Free audits cover up to 3 wallets. Pro is unlocked by burning the coin — never by paying us.

What happens when I burn?

The server builds a transaction that burns the exact unlock amount from your own token account plus a short memo. Your wallet shows it, you sign it, and the tokens are destroyed. The server confirms the burn on-chain and unlocks Pro for 30 days, stacking. Nothing is sent to us.

Which wallets work?

Any Solana wallet that supports the Wallet Standard and message signing — Phantom, Solflare, Backpack and others. You only need one to sign in for Pro.

Will the tips make me anonymous?

No, and nothing honest can promise that. They reduce what casual onlookers can infer from public data. Exchanges and other services can still know which wallets are yours, and that’s expected.

Which of your wallets give each other away?

Every thread, with receipts.

Threads found

Hygiene — what you can do

Report