Skip to main content

Privacy Roadmap

Aruvi's first version was a confidential payment protocol - amounts encrypted on-chain with fully homomorphic encryption. When the project moved to Arc, that raised an obvious question: what happens to privacy?

Where things stand​

On Arc today, payment amounts are public, like on any standard EVM chain. Arc's privacy features are on Circle's roadmap but not yet live.

The Arc Privacy Sector (APS)​

Circle has designed an opt-in confidential execution environment for Arc:

  • Two execution environments - public Arc and the confidential APS - advance in lockstep within the same consensus rounds
  • Transactions are encrypted to the APS network key and executed by validators inside hardware enclaves
  • No execution results, return values, or event logs from private contracts reach the public ledger
  • Private and public contracts compose atomically - no bridges, no async messaging
  • The key exchange is already quantum-resistant (X-Wing KEM / ML-KEM-768)

Because APS reuses standard EVM bytecode, contracts like Aruvi's gateway are expected to run there with minimal modification.

Aruvi's plan​

  1. Today - instant public USDC payments with the full feature set (requests, subscriptions, refunds, batch payouts)
  2. When APS ships - deploy a confidential instance of the gateway inside APS, letting users opt into private payments while keeping public payments cheap and simple
  3. The goal - the original Aruvi promise (amounts visible only to sender and recipient) with Arc's sub-second finality and USDC-native gas

What you can do today​

  • Amounts in the Aruvi UI can be hidden at a glance (they're still public on-chain)
  • Use fresh addresses per counterparty to limit linkability
  • Follow Arc's documentation for APS availability announcements
Honest by design

We won't call a payment "private" until the chain makes it private. Anything else is marketing.