Rounds are Veilify’s scheduled payout batches. The current UI previews them through Advanced transfers. They let scheduled withdrawals share a departure time instead of leaving the moment each user clicks. Timing can link a deposit to a withdrawal. Waiting for a round can reduce the immediate timing clue, but it does not establish anonymity. The Robinhood scheduler and live Veilify RPC are still pending; the countdown in the current app is a preview.

​
How a round works

  1. Choose a round, prepare the withdrawal and sign it.
  2. Before the round, the scheduler proves your withdrawal and preflights it.
  3. At the round, every queued withdrawal for that slot is dispatched.
  4. Each one confirms independently. Your activity shows delivered with a transaction hash.

​
Reference policy

Round timing, amount grids, fee rates and gas reserves are dynamic policy. Read them from veilify_getWithdrawalPolicy at runtime. Do not hardcode them.

​
Lifecycle

​
Moved rounds

The service can move a withdrawal to a later round. The app shows the original round (movedFrom) and the reason:

​
What a round is not

A round is a service scheduling policy, not an on-chain guarantee. shieldedWithdrawal does not check timestamps. The selected round is not part of the signed transaction. You trust Veilify Network to send at the round you chose.
A round is not an anonymity measurement. The countdown and crowd animation are illustrative. They do not show how many withdrawals are in a real round.
The planned round flow lets you choose a shared departure time and spread one exit over several slots, instead of leaving the moment you click.