​

Compliance and Regulation

​

Confidential amounts, transparent addresses

Fairblock’s compliance model is simple: encrypt commercially sensitive amounts, keep transaction counterparties auditable, and enable scoped disclosure when an authorized party has a legitimate need. Fairblock encrypts transaction amounts and balances by default while keeping sender and receiver addresses transparent. This provides financial confidentiality without sacrificing auditability.

• Fairblock is not a mixer. Compliance controls can screen, block, and monitor illicit activity while also preserving transaction traceability and auditability.
• Regulators, auditors, banks, and compliance teams can still see which addresses interacted.
• Businesses gain confidentiality over commercially sensitive payment amounts and balances.
• Encrypted amounts can be selectively disclosed when required for legitimate compliance, legal, or audit purposes.
• This model is consistent with how regulated financial institutions handle sensitive financial data: public transparency is limited, while authorized parties can obtain access when appropriate.

This is also how traditional financial systems operate. Banks do not publicly expose account balances or transaction amounts, and Apple Pay does not broadcast payments to the world. However, both can provide records to auditors, regulators, or law enforcement when legally required. Fairblock applies the same principle to onchain finance.

​

Selective disclosure

Transparent addresses are only one part of Fairblock’s compliance model. Fairblock also supports granular selective disclosure of encrypted amounts using Identity-Based Encryption (IBE) and Multiparty Computation (MPC). Rather than giving a centralized auditor permanent visibility into every encrypted transaction, Fairblock follows a least-privilege model where disclosures are scoped to the minimum data required. Authorized disclosures can be limited to:

• A specific transaction
• A specific user
• A specific application
• A defined time period

This allows institutions to satisfy legitimate regulatory, compliance, legal, and audit requirements without introducing a permanent surveillance backdoor.

​

Compliance dashboard and API

Fairblock provides a compliance dashboard for compliance officers, auditors, regulated institutions, and ecosystem partners to request access to encrypted transaction data when appropriate. Partners can also integrate the same functionality through an API, allowing disclosure requests and approval workflows to remain entirely within their own internal compliance systems. This enables organizations to:

• Issue a scoped view key for a specific transaction, user, or application.
• Maintain internal approval and compliance workflows.
• Avoid granting permanent visibility to any centralized third party.
• Preserve user confidentiality while remaining compliant with regulatory obligations.

​

AML, sanctions screening, and transaction monitoring

Fairblock integrates with compliance and blockchain intelligence providers such as Predicate and Range Security to identify sanctioned or high-risk addresses. Compliance checks can be performed before assets enter confidential balances and before assets leave the confidential system. Depending on the asset issuer and deployment, deposits or withdrawals involving sanctioned, hacked, or otherwise high-risk addresses can be blocked or frozen according to the issuer’s compliance policies. Because addresses remain transparent in Fairblock’s default transfer model, existing AML infrastructure continues to work without modification. Institutions can continue using:

• OFAC and sanctions screening
• AML transaction monitoring
• Address risk scoring
• Transaction graph analysis
• Blockchain forensic tools

Confidentiality is added without removing the compliance surface institutions already depend on.

​

Taint analysis

Fairblock remains fully compatible with taint analysis and other blockchain forensic techniques. Since transaction counterparties remain visible, compliance teams can continue tracing the lineage of assets, identifying exposure to illicit funds, and performing forensic investigations while transaction amounts remain confidential. This enables businesses to protect commercially sensitive financial information without sacrificing auditability.

​

Compliance-controlled unlinkability

Fairblock’s default model is confidential transfers with encrypted amounts and transparent addresses. For specific institutional deployments that require stronger privacy, Fairblock can also support unlinkable address flows where counterparties need protection from public relationship mapping. Examples include merchant payments, treasury management, VC fund operations, trading desks, and banking applications. These deployments are intended for controlled environments and can include:

• Opt-in KYB/KYC-scoped deployments.
• Deposit and withdrawal screening.
• Issuer or application-level blocking and freezing controls where supported.
• Selective disclosure for authorized compliance, audit, or legal requests.
• Reconstruction of transaction lineage when required by authorized parties.

Even in these deployments, confidentiality does not eliminate compliance. It simply limits unnecessary public disclosure while preserving the ability for authorized parties to investigate and audit activity when appropriate.

​

Built for regulated confidentiality

Fairblock is designed for regulated confidentiality, not regulatory evasion. The goal is not to hide financial activity from institutions. The goal is to eliminate unnecessary public leakage of commercially sensitive information while preserving the compliance capabilities that regulated businesses, stablecoin issuers, payment providers, and financial institutions require.