+   Compliance and security

Compliance is
built in, not bolted on.

A privacy product only works long term if a bank, an auditor and a card issuer can all live with it. Today that means read-only viewing keys you issue yourself and statements built on your own machine. Screening at the edge and association-set proofs are the plan, and this page says plainly which is which.

Compliance · preview

Disclosure

0

Master keys. Every viewing key is issued by you, and only by you

Signetpay / ComplianceScreening · Viewing keys · Attestations · Security ↓

At the edge01

(At the edge)

01

Edge compliance screening

Planned: sanctions screening on every shield and unshield, plus association-set proofs that demonstrate pool hygiene. Not implemented yet.

02

Fiat ramps with identity separation

Planned: licensed on- and off-ramps, with KYC records that never link to on-chain activity. No ramp is connected yet — money comes in by bridge or transfer.

03

Time-decorrelated withdrawals

Planned: exits scheduled and split, so an unshield can't be matched to a shield by timing. Not implemented yet.

Disclosure02

(Disclosure)

01

Read-only viewing keys

A key that recognises the payments you receive and cannot move them, for an accountant, auditor or lender.

02

Scoping and expiry

Planned: keys limited to a date range, with an expiry that revokes them on their own. Today a key is unscoped and permanent.

03

Encrypted transaction memos

Private bookkeeping labels, readable only by you or a viewing-key holder.

04

Private tax and accounting export

CSV or PDF, generated locally from a viewing key. Nothing leaves your machine.

Attestations03

(Attestations)

01

Zero-knowledge proof of funds

Prove a balance above X, or that you held a position for N months, without revealing the account.

02

Collateral attestation

A lender accepts a proof of shielded holdings instead of watching a public wallet.

03

Corporate actions for tokenized stocks

Dividends and splits are credited to shielded holders without revealing who holds what.

Who you can prove things to04

(Who you can prove things to)

PartyPublic walletSignetpay
AccountantScreenshots and a shared spreadsheetA read-only viewing key, or a statement you export yourself
AuditorFull wallet history, foreverA read-only key that can never spend (scoping to the audit window is planned)
LenderA public balance they can watch every dayA proof of balance above X, or a collateral attestation
Bank or card issuerNothing to show but a mixer addressPlanned: an association-set proof plus screening on every shield and unshield
CounterpartyYour whole balance, from one paymentA one-time stealth address and nothing else

Security05

(Security)

01

Social recovery

Guardians, passkeys and hardware wallets. A lost device isn't a lost account.

02

Client-side portfolio dashboard

Your portfolio decrypts locally in the browser. The server never sees your positions.

03

Card and device controls

Per-card and per-device spending limits, freeze, and an instant kill switch.

04

Shielded treasury multi-sig

Co-signers on the treasury, for companies that can't put funds behind a single key.

05

Automatic note consolidation

Your encrypted notes are defragmented in the background, so proofs stay fast and fees stay low.

06

Gas sponsorship

A paymaster pays the gas. You never hold the chain's gas token.

What Signetpay never sees06

(What Signetpay never sees)

01

Your positions

Notes decrypt in your browser. The dashboard, the statements and the tax export are all generated locally.

02

Your KYC record next to your chain activity

Signetpay runs no identity checks at all. When licensed ramps arrive they will hold that record, and we will still never hold both halves of the link.

03

A permanent back door

There is no master viewing key. Every disclosure is scoped, time-boxed and issued by you.

Privacy everyone can live withCompliance

Privacy your accountant, your lender
and your card issuer can all live with.

  1. 01Screened at the edge
  2. 02Scoped viewing keys
  3. 03ZK attestations
SignetpayLoading (0%)