Skip to main content
Tachyon is built so that confidentiality and compliance don’t compete. Intents are private by default, and your users (or you, on their behalf) can grant scoped, verifiable visibility to specific counterparties, auditors, regulators, accountants, without making anything public.

​
The model in one paragraph

Every intent is encrypted end-to-end. Only the user’s viewing key can decrypt it. The user can then either reveal a single intent, a date range, or a set of intents to a designated counterparty. The counterparty receives a verifiable record. Nothing about this disclosure is published on-chain, and disclosure is scoped, granting visibility to one transaction does not grant visibility to others.
Tachyon never holds a user’s viewing key. Disclosure is always something the user (or the integrator on their behalf, with their key material) initiates.

​
What you can disclose

A single intent

Show a counterparty the exact contents of one transaction, amount, recipient, settlement hash.

A range of intents

Hand an auditor the full set of intents for a quarter, or a specific account.

A summary

Provide aggregate totals (e.g., total inflow, total outflow) without exposing individual intents.

Proof of receipt

Give a counterparty a verifiable receipt for a payment they expected to receive.

​
How it fits with KYC and sanctions screening

Tachyon does not perform KYC at the protocol level. Integrators apply their own compliance layer before signing an intent, for example:
  • Verify the user’s identity at onboarding
  • Screen the recipient address against sanctions lists
  • Apply per-transaction or daily limits
Once an intent is signed and submitted, the protocol enforces only the cryptographic and accounting rules. Compliance posture is your product’s responsibility; Tachyon ensures that confidentiality doesn’t prevent you from honoring it.
Tachyon cannot block or reverse a settled intent. KYC and sanctions checks must happen before submission.

​
Configurable disclosure by use case

Keep individual contributor amounts confidential from each other and the public. Grant viewing access to HR or external auditors so they can verify the full payroll without amounts becoming public knowledge.
Move funds across chains without exposing volumes to competitors. Grant a compliance officer scoped viewing access to verify that transfers respect reporting thresholds or sanctions policies.
Execute schedule-driven orders without leaking strategy. Risk managers retain full visibility into execution details internally while the market sees only fresh stealth-address activity.
Users can export a verifiable record of all intents in a tax year using their viewing key, without making the data public on-chain.

​
What Tachyon does not control

  • Tachyon cannot read intent contents and so cannot produce compliance reports on a user’s behalf.
  • Tachyon cannot add or remove viewers after submission. If a counterparty needs visibility into a future intent, the user must grant access at submission time or share via their viewing key afterwards.
  • Tachyon cannot freeze, block, or reverse settled intents.
This is by design: your compliance posture does not depend on Tachyon’s availability or cooperation.

Set up viewing permissions

Walk through granting auditor access at intent submission time.