Shieldednot connected
Mainnet

What leaks

Overclaiming is the most damaging thing a privacy product can do, because someone acts on the claim. This page is the complete list, and it includes the parts that are not flattering. 5 of 9 facts below are public.

Public

The address that shielded into the pool, and how much

Shielding is an ordinary public deposit and the pool screens the depositor. Nothing Convoy does changes this, and no product built on STRK20 can.

Hidden

Which address placed an order

The join arrives as a call from the pool, submitted by a rotating shared relayer. Your address appears nowhere in the calldata or the signature.

Public

How many lots each order is

Lot counts travel in the invoke calldata and are echoed in the OrderJoined event. This is why sizes are quantised and capped: the number is public, so the design makes it uninformative rather than pretending it is hidden.

Hidden

Whether two orders belong to the same person

Nothing on chain associates one commitment with another. A wallet holding several orders in a batch produces legs that are indistinguishable from several different people.

Public

The aggregate swap: total size, rate and timing

One transaction for the whole batch. It is public, and that is the point: it reveals the sum, not any component. The larger the batch, the less any single order can be inferred from it.

Hidden

Each order's individual execution price

There is no per-order price. Every lot in a batch clears at the same rate, computed pro rata from what the single swap actually returned.

Public

That a redemption happened, and for how much

The redemption is a call from the pool to this contract, and the amount it credits is visible.

Hidden

Who redeemed, and to which wallet

Output is credited to an open note inside the pool. The note is not a public address and the redeeming wallet is not in the transaction.

Public

That a redemption came from a specific join

Redeeming reveals the key whose hash is the commitment recorded at join, so an observer can pair the two events. This does not identify a person: orders are bearer instruments, the key can be handed to anyone, and neither event carries an address.

The honest limits

A batch of one hides nothing

Cover comes from company. A batch that draws a single order gives that order no more privacy than executing alone, which is why a batch below its minimum order count voids and refunds instead of crossing. The board states the current set size rather than implying safety.

A distinctive shield still stands out

If you shield an unusual amount and immediately commit all of it, the deposit and the batch are still circumstantially linked by timing. Shield a round amount, ahead of time, and in a size that is not unusual. Lot quantisation fixes the order leg; it cannot fix a deposit you made ten seconds earlier.

Timing correlation across batches

Joining every batch at the same size at the same time of day is a pattern, and patterns survive quantisation. Convoy makes any single order unremarkable; it does not make a habit unremarkable.

Not audited

The venue contract is covered by a unit and fuzz suite and is deliberately non-upgradeable, with no administrative path to deposited value. It has not had a third-party audit. Treat the amounts you commit accordingly.

Verify any of this yourself