From 2b13ff71cdb54652c50f0e4ea0726bde15c49475 Mon Sep 17 00:00:00 2001 From: crispzlegion Date: Tue, 21 Jul 2026 14:54:53 +0530 Subject: [PATCH 1/3] Restructure docs overview, add CUSD and Fairblock Network pages Rewrites overview.mdx (opening copy, Why Fairblock, Built to Be Used, product grid), standardizes the Fairblock/FairyRing architecture description across the docs, adds the CUSD overview page and The Fairblock Network page, and reorganizes docs.json navigation so CUSD is directly visible under Confidential Transfers. Co-Authored-By: Claude Sonnet 5 --- confidential-intelligence/overview.mdx | 18 ++ ct/guides/apps/cusd-overview.mdx | 213 ++++++++++++++++++ docs.json | 111 ++++----- high-level-architecture.mdx | 2 + overview.mdx | 48 ++-- .../build/platform-setup/evm-arbitrum.mdx | 2 +- protocol/fairyring.mdx | 2 +- protocol/overview.mdx | 2 +- protocol/the-fairblock-network.mdx | 70 ++++++ resources/faq.mdx | 4 +- resources/glossary.mdx | 4 +- 11 files changed, 401 insertions(+), 75 deletions(-) create mode 100644 confidential-intelligence/overview.mdx create mode 100644 ct/guides/apps/cusd-overview.mdx create mode 100644 protocol/the-fairblock-network.mdx diff --git a/confidential-intelligence/overview.mdx b/confidential-intelligence/overview.mdx new file mode 100644 index 0000000..f77609e --- /dev/null +++ b/confidential-intelligence/overview.mdx @@ -0,0 +1,18 @@ +--- +title: "Confidential Intelligence" +sidebarTitle: "Overview" +description: "Agents and applications that work with sensitive data" +--- + +Fairblock's confidentiality infrastructure extends beyond financial transfers to confidential agents, private application workflows, and intelligent systems that interact with sensitive enterprise and financial data. + +These documentation pages primarily cover Fairblock's confidential finance products. Fairblock also supports confidential agentic and application workflows through its broader confidential intelligence platform. If you're interested in these use cases, please contact the Fairblock team. + + + + Explore encrypted balances and confidential transfer amounts. + + + Review the available RPC, REST, and gRPC endpoints. + + diff --git a/ct/guides/apps/cusd-overview.mdx b/ct/guides/apps/cusd-overview.mdx new file mode 100644 index 0000000..598a7d3 --- /dev/null +++ b/ct/guides/apps/cusd-overview.mdx @@ -0,0 +1,213 @@ +--- +title: "CUSD by Fairblock and M0" +description: "Confidential stablecoin payments with encrypted balances, configurable compliance, and selective disclosure." +--- + +## Overview + +CUSD is a confidential USD stablecoin built by Fairblock using M0 stablecoin infrastructure, with MxON supporting issuance and Predicate supporting compliance policies. + +CUSD combines transparent stablecoin functionality with an optional confidential mode. Users can protect transfer amounts and balances while preserving visible entry and exit points, address-level controls, freezing pathways, and selective disclosure. + +It is designed for payments, treasury operations, payroll, merchant settlement, trading, and other financial activity that should not be publicly exposed. + +## Why Fairblock Has a Flagship Stablecoin + +Fairblock is building a turnkey confidentiality layer for stablecoins and tokenized assets. CUSD is Fairblock's flagship confidential asset, enabling the network to deliver a fully integrated product experience, accelerate development, coordinate distribution, and align ecosystem economics. + +CUSD does not limit Fairblock to a single stablecoin. The same infrastructure can support confidential versions of existing stablecoins and tokenized assets. Issuers and partners can add confidentiality while preserving their own assets, liquidity, compliance systems, and distribution. + +## Roles in the CUSD Ecosystem + +| Partner | Role | +| --- | --- | +| **Fairblock** | Product, confidential transfers, developer integrations, selective disclosure, frontend and distribution | +| **M0** | Stablecoin infrastructure and issuance framework | +| **MxON** | Issuance, minting, backing and redemption | +| **Predicate** | Policy enforcement, address screening and compliance controls | + +## Transparent and Confidential Modes + +**Transparent CUSD**: Standard CUSD held and transferred publicly, with visible addresses and amounts. + +**Confidential CUSD**: CUSD deposited into Fairblock, where internal transfer amounts and balances are encrypted. + +```mermaid +flowchart LR + A["USDC or supported asset"] --> B["Transparent CUSD"] + B --> C["Fairblock confidential balance"] + C --> D["Confidential transfers"] + D --> E["Transparent withdrawal"] +``` + + + CUSD is the flagship implementation, not the limit of the platform. Fairblock's confidential transfer infrastructure can also be integrated with other stablecoins and tokenized assets. + + +## Why CUSD Matters + + + + Keep treasury balances, payroll, merchant revenue, supplier payments, trading flows, and institutional transfers from being publicly exposed. + + + Maintain visible entry and exit points, address screening, freezing pathways, monitoring, and selective disclosure. + + + Add confidentiality to wallets, payment applications, fintech platforms, treasury systems, and partner frontends without requiring a separate privacy chain or wallet. + + + +## How the CUSD Flow Works + +The CUSD flow has three stages: transparent entry, confidential transfer, and transparent exit. + +First, a user receives or purchases transparent CUSD. For example, the user may swap USDC into CUSD through a supported frontend. At this point, CUSD behaves like a normal transparent stablecoin. The user's address, transfer, and amount are visible and can be monitored using ordinary stablecoin compliance tools. + +Second, the user can deposit transparent CUSD into the Fairblock smart contract. This deposit is visible onchain. The deposit amount is visible. The depositing address is visible. This creates a confidential balance for the user inside the Fairblock system. + +Third, the user can make confidential transfers. Inside the Fairblock contract, transfers are represented as encrypted balance updates. The sender's encrypted balance is reduced and the receiver's encrypted balance is increased without publicly revealing the transfer amount. + +When a user wants to exit the confidential layer, the user withdraws from their confidential balance. The Fairblock smart contract sends transparent CUSD to the user's transparent address. This withdrawal is visible and can be screened. + +In practical terms, the user receives transparent CUSD, deposits it into the Fairblock contract, receives an encrypted balance, transfers confidentially, and withdraws transparent CUSD when they want to exit. + +## What Happens During a Confidential Transfer + +A confidential transfer inside Fairblock is not a normal public token transfer from one user address to another. + +Once CUSD has been deposited into the Fairblock smart contract, the transparent CUSD is held by the contract. Internal confidential transfers are handled through encrypted accounting. The sender's encrypted balance decreases and the receiver's encrypted balance increases. + +Fairblock uses homomorphic encryption to support this flow. Homomorphic encryption allows the system to perform valid operations on encrypted values. This means balances can be updated correctly without exposing the underlying transfer amounts to the public chain. + +This is the key technical distinction. Transparent CUSD movement happens at identifiable entry and exit points. Inside the confidential layer, Fairblock protects amounts and balances while preserving monitoring, selective disclosure, and partner-specific compliance workflows. + +## What Is Public and What Is Confidential + +CUSD does not make all activity invisible. It protects the financial data that should not be globally public. + +Addresses interacting with the system remain visible. Deposits into the Fairblock contract are visible. Withdrawals from the Fairblock contract are visible. Deposit and withdrawal amounts are visible. The timing of deposits and withdrawals is visible. + +What becomes confidential is the internal transfer amount, the user's confidential balance, and the encrypted accounting state inside the Fairblock layer. + +This distinction is central to CUSD. The system provides amount and balance confidentiality. It does not create an uncontrolled anonymity system. + +## Compliance and Controlled Disclosure + +### Entry and Exit Controls + +Deposits and withdrawals occur through visible transactions where addresses and amounts can be screened under applicable partner policies. + +### Freezing and Policy Enforcement + +Restricted transparent transfers, deposits, or withdrawals can be blocked or frozen through the relevant issuer, compliance-provider, or partner framework. + +### Selective Disclosure + +Authorized parties can receive scoped access to specific encrypted balances or transfers where operational, audit, compliance, or legal requirements apply. + +### Partner Oversight + +Partners can use Fairblock's dashboard or integrate approved monitoring providers for their own users and transaction flows. + + + Exact controls depend on the asset, network, issuer, jurisdiction, and partner configuration. + + +## Why CUSD Is Not a Mixer + +CUSD protects transfer amounts and balances. It is not designed to break the relationship between deposits, withdrawals, and participating addresses. Deposits and withdrawals remain visible, entry and exit points can be screened, applicable transactions can be restricted, and encrypted information can be selectively disclosed. + + + Core confidentiality does not depend on a large anonymity set. Broader network participation can nevertheless improve metadata and transaction-pattern obfuscation. + + +## The Fairblock Network Effect + +As more users, wallets, applications, and assets participate, CUSD benefits from deeper confidential liquidity, stronger economic incentives, broader utility, and improved network-level metadata obfuscation. + +The broader Fairblock network also prevents confidential assets from becoming isolated across separate chains and proprietary privacy systems. Applications can use shared infrastructure instead of maintaining multiple incompatible encryption integrations. + +## Why CUSD Is Different From Privacy Chains + +CUSD is also different from broad privacy chains, shielded pools, or private execution environments. + +Some privacy systems are designed to hide many aspects of activity at the protocol level, including transaction relationships or broader execution details. Those systems may be useful for certain applications, but they are often not the right fit for regulated stablecoin payments, enterprise use, or partner-led compliance programs. + +CUSD is more targeted. + +It focuses on confidential stablecoin transfers where amounts and balances are encrypted, while address-level compliance, entry and exit controls, freezing pathways, and selective disclosure remain available. + +This narrower design is intentional. Most businesses, payment companies, issuers, fintechs, and institutions do not need an anonymity network. They need stablecoin payments that protect sensitive amounts while satisfying compliance, monitoring, audit, and legal obligations. + +## Developer and Partner Integration Model + +CUSD is designed to integrate into existing wallets, stablecoin flows, payment applications, fintech products, and partner frontends. + +A developer or partner can support transparent CUSD by default and offer confidential CUSD as an optional privacy mode. Users do not need to move into a separate privacy chain or adopt a new wallet. They can interact with a familiar stablecoin flow that supports confidentiality when needed. + +Partners can configure compliance based on their own requirements. A partner may require screening before deposit, screening before withdrawal, dashboard access, internal review rights, third-party monitoring, or scoped disclosure access for its own transfer flow. + +This makes CUSD suitable for partners that want to offer confidentiality without taking on the risks or friction of an uncontrolled privacy system. + +## Benefits for Key Stakeholders + + + + Offer confidential payments through an existing interface without building cryptographic or disclosure infrastructure internally. + + + Protect treasury, payroll, supplier, merchant, and operational payment information. + + + Add confidential functionality to existing assets while retaining control over issuance, distribution, and compliance policies. + + + Reduce public information leakage around balances, transfers, and settlement activity. + + + Integrate confidential balances and transfers through Fairblock's SDKs and APIs. + + + +## Core Compliance Position + +CUSD's compliance position is that confidentiality and compliance are compatible. + +CUSD protects sensitive amounts and balances from public exposure, but it does not remove the ability to screen addresses, monitor entry and exit points, freeze restricted transfers, support audits, or disclose specific information to authorized parties. + +Users first interact with transparent CUSD. They may optionally deposit into Fairblock to create a confidential balance. Internal transfers update encrypted balances. Withdrawals return transparent CUSD to a transparent address. + +This creates a practical compliance framework. Users enter through visible, screenable transactions. Users exit through visible, screenable transactions. Addresses remain part of the compliance perimeter. Amounts and balances are protected from public exposure. Authorized parties can receive targeted disclosure where required. Partners can configure additional monitoring for their own flows. + +M0 provides the stablecoin infrastructure. MxON supports issuance and minting. Predicate supports compliance across integrated chains. Fairblock provides the confidentiality, application layer, selective disclosure infrastructure, developer experience, partner onboarding, and go-to-market. + +This is the foundation of compliant confidential stablecoin infrastructure. + +## Public Positioning + +CUSD makes stablecoin payments private enough for real-world use and compliant enough for serious partners. + +It is not a mixer. It is not an anonymity protocol. It is not designed to remove oversight from stablecoin systems. + +CUSD gives issuers, wallets, fintechs, developers, institutions, merchants, market makers, neobanks, and payment companies a way to protect sensitive financial information while preserving the controls required for regulated financial activity. + +It offers common-sense confidentiality for balances, treasury activity, large trades, merchant payments, market-making flows, and institutional payments without requiring users to bridge to a privacy chain, adopt a new wallet, tolerate delays, or accept a weaker compliance posture. + +## Summary + +CUSD combines a transparent stablecoin with optional confidential balances and transfers. Fairblock protects sensitive amounts from public exposure while preserving visible entry and exit points, configurable compliance controls, and selective disclosure. + +CUSD is Fairblock's flagship confidential asset. The broader Fairblock platform can extend the same confidentiality infrastructure to additional stablecoins and tokenized assets. + + + + Start using CUSD today. + + + Build with the Stabletrust SDK. + + + Talk to the team about partnering. + + diff --git a/docs.json b/docs.json index 1252143..e66d21f 100644 --- a/docs.json +++ b/docs.json @@ -39,7 +39,9 @@ "group": "Get Started", "pages": [ "overview", - "high-level-architecture" + "high-level-architecture", + "protocol/the-fairblock-network", + "ct/sdk-reference/supported-networks" ] }, { @@ -47,96 +49,89 @@ "pages": [ "ct/overview", { - "group": "Get Started", + "group": "How It Works", "pages": [ - "ct/get-started/architecture", - "ct/get-started/quick-start" + "ct/how-it-works/confidential-transfers", + "ct/how-it-works/unlinkable-transfers" ] }, { - "group": "Apps", - "expanded": true, + "group": "Confidential CUSD", "pages": [ - "ct/guides/apps/stabletrust-app", - "ct/guides/apps/cusd-app", - "ct/guides/apps/yieldshield-app", - "ct/guides/apps/compliance-dashboard-app" + "ct/guides/apps/cusd-overview", + "ct/guides/apps/cusd-app" ] }, { - "group": "Build", - "expanded": true, + "group": "Stabletrust", "pages": [ - "ct/guides/build/building-with-sdk", - "ct/guides/build/unlinkable-transfers", - "ct/guides/build/agentic-api" + "ct/guides/apps/stabletrust-app", + "ct/guides/apps/yieldshield-app" ] }, { - "group": "How It Works", + "group": "Compliance and Disclosure", "pages": [ - "ct/how-it-works/confidential-transfers", - "ct/how-it-works/unlinkable-transfers", - "ct/how-it-works/compliance" + "ct/how-it-works/compliance", + "ct/guides/apps/compliance-dashboard-app" ] }, { - "group": "SDK Reference", + "group": "SDK", "pages": [ + "ct/get-started/architecture", + "ct/get-started/quick-start", + "ct/guides/build/building-with-sdk", + "ct/guides/build/unlinkable-transfers", + "ct/guides/build/agentic-api", "ct/sdk-reference/methods", - "ct/sdk-reference/supported-networks", "ct/sdk-reference/common-errors" ] + }, + { + "group": "API Reference", + "pages": [ + "api-reference/overview", + "api-reference/rpc-endpoints", + "api-reference/rest-api" + ] } ] }, { - "group": "Pre-Execution Privacy", + "group": "Protected Execution", "pages": [ "pep/overview", { - "group": "Get Started", + "group": "Auctions and Intents", "pages": [ - "pep/get-started/architecture", - "pep/get-started/quick-start" - ] - }, - { - "group": "Apps", - "expanded": true, - "pages": [ - "pep/guides/apps/fairrates" + "pep/guides/apps/fairrates", + "pep/guides/build/sealed-bid-auctions", + "pep/guides/build/private-governance" ] }, { - "group": "Build", - "expanded": true, + "group": "Encrypted Transactions", "pages": [ - "pep/guides/build/sealed-bid-auctions", - "pep/guides/build/private-governance", "pep/guides/build/encrypted-transactions", "pep/guides/build/private-decryption", "pep/guides/build/verifiable-randomness", - { - "group": "Platform Setup", - "expanded": true, - "pages": [ - "pep/guides/build/platform-setup/cosmos-chains", - "pep/guides/build/platform-setup/evm-arbitrum", - "pep/guides/build/platform-setup/fairyring-native" - ] - } - ] - }, - { - "group": "How It Works", - "pages": [ "pep/how-it-works/conditional-encryption", "pep/how-it-works/mpc-ibe", "pep/how-it-works/decryption-modes", "pep/how-it-works/network-flow" ] }, + { + "group": "Integration Guide", + "pages": [ + "pep/get-started/architecture", + "pep/get-started/quick-start", + "pep/guides/build/platform-setup/cosmos-chains", + "pep/guides/build/platform-setup/evm-arbitrum", + "pep/guides/build/platform-setup/fairyring-native" + ] + }, { "group": "Module Reference", "pages": [ @@ -146,10 +141,24 @@ } ] }, + { + "group": "Confidential Intelligence", + "pages": [ + "confidential-intelligence/overview" + ] + }, { "group": "Resources", "pages": [ - "resources/community", + { + "group": "Ecosystem", + "pages": [ + "ecosystem/community", + "ecosystem/partners", + "ecosystem/supported-chains" + ] + }, + "resources/faq", "resources/glossary" ] } diff --git a/high-level-architecture.mdx b/high-level-architecture.mdx index 7635dfb..d491a66 100644 --- a/high-level-architecture.mdx +++ b/high-level-architecture.mdx @@ -3,6 +3,8 @@ title: "High-Level Architecture" description: "The shared architecture every Fairblock integration passes through" --- +Fairblock is a decentralized confidentiality network that provides cryptographic services and confidential application infrastructure across multiple chains and execution environments. FairyRing coordinates Fairblock's decentralized cryptographic services; users and partners access Fairblock through supported chains, applications, SDKs, and APIs without needing to interact directly with the underlying network. + Fairblock lets any application add confidentiality without exposing private data onchain. The optimized cryptograhic scheme an app relies on can differ based on the application, for example MPC, identity-based encryption, or homomorphic encryption, but the top-level architecture is the same. This page describes that shared architecture: the four components every integration passes through, and the end-to-end flow of an encrypted message from the user to Fairblock's cryptographic network and back to the integrated blockchain. diff --git a/overview.mdx b/overview.mdx index ffffe27..99d3369 100644 --- a/overview.mdx +++ b/overview.mdx @@ -1,46 +1,60 @@ --- title: "Overview of Fairblock" -description: "A privacy layer designed for enterprise adoption" +description: "The turnkey confidentiality layer for digital assets and intelligent systems" --- -Fairblock is the turnkey confidentiality layer for enterprise finance and AI. As stablecoins, tokenized assets scale onchain, institutions need privacy solutions that are compliant, performant, and embedded in the infrastructure they already run. Fairblock delivers. Confidential assets and transactions, live on the chains where users and liquidity already are. +Fairblock provides programmable confidentiality for stablecoins, tokenized assets, transactions, and intelligent applications. It allows developers and partners to protect sensitive values and data while preserving performance, interoperability, compliance controls, and familiar user experiences. -## Why Fairblock +Fairblock's current product focus is confidential finance. Stablecoins and tokenized assets increasingly support payments, treasury operations, trading, and financial applications, but their balances and transaction amounts remain publicly exposed. Fairblock enables these assets to operate confidentially across existing chains, wallets, and applications. -As stablecoins and tokenized assets move into the mainstream, enterprises and financial institutions need privacy to protect payroll, treasury operations, revenue flows, trading activity, and customer data. Public transactions create unnecessary compliance risks and expose sensitive business information to competitors. +The same infrastructure can support confidential agents, private application workflows, and intelligent systems that interact with sensitive enterprise and financial data. -At the same time, AI adoption is accelerating, but businesses cannot always share their confidential data and IP with Anthropic and OpenAI. They need AI inference and agents that can access, process, and act on sensitive information without compromising privacy, security, or regulatory requirements. +## Why Fairblock -Privacy is no longer optional, it is a prerequisite for enterprise adoption. The challenge has been delivering it without sacrificing performance, usability, or interoperability. +Public infrastructure exposes information that businesses normally protect: balances, payment amounts, payroll, treasury activity, trading flows, customer activity, and proprietary application data. This limits the use of public networks and intelligent systems for serious commercial activity. -Fairblock is building the infrastructure for confidential finance and intelligence: performant and compliant privacy for stablecoins, RWAs, inference, agents, and enterprise applications. +Fairblock provides a practical alternative to both full public exposure and isolated anonymity systems. Sensitive values remain confidential, while applications can retain address-level controls, interoperability, monitoring, selective disclosure, and partner-specific compliance policies. ## Built to Be Used - High throughput for institutional volume. + Fairblock selects cryptographic approaches based on each application's requirements, avoiding unnecessary computational overhead. - Full compliance through sanction/AML monitoring, selective disclosure, and traceability + Applications can support sanctions screening, entry and exit controls, freezing pathways, monitoring, traceability, and selective disclosure. - Privacy without bridging assets or changing wallets. + Users can access confidentiality through existing wallets, applications, assets, and chains without entering a separate privacy ecosystem. - Plug into any frontend, neobank, wallet, or agentic platform. + Developers can integrate confidential balances, transactions, and application workflows through Fairblock applications, SDKs, and APIs. -Note: For simplicity and clarity, this documentation focuses on confidentiality and privacy for onchain financial applications. Fairblock is also building confidential AI inference, AI agents, robotics, and other confidential compute capabilities. If you're interested in these use cases, please contact the Fairblock team. +Note: These documentation pages primarily cover Fairblock's confidential finance products. Fairblock also supports confidential agentic and application workflows through its broader confidential intelligence platform. -## Get Started +## Products - - Confidential assets and payments using HE and ZK. + + Add encrypted balances and confidential transfer amounts to stablecoins and tokenized assets. + + [Explore Confidential Transfers](/ct/overview) · [Integrate the SDK](/ct/guides/build/building-with-sdk) + + + Use Fairblock's flagship confidential stablecoin, built with M0. + + [Understand CUSD](/ct/guides/apps/cusd-overview) · [Launch CUSD](https://fairblock-cusd-app.vercel.app/) + + + Protect orders, bids, intents, governance activity, and other sensitive inputs before execution. + + [Explore Protected Execution](/pep/overview) · [Build a Protected Application](/pep/get-started/quick-start) - - Sealed-bid auctions, private governance, and encrypted transactions using MPC-IBE. + + Build agents and applications that interact with sensitive data and private workflows. + + [Explore Confidential Intelligence](/confidential-intelligence/overview) · [View API Documentation](/api-reference/overview) diff --git a/pep/guides/build/platform-setup/evm-arbitrum.mdx b/pep/guides/build/platform-setup/evm-arbitrum.mdx index f315879..b9d220a 100644 --- a/pep/guides/build/platform-setup/evm-arbitrum.mdx +++ b/pep/guides/build/platform-setup/evm-arbitrum.mdx @@ -230,7 +230,7 @@ Welcome to the Fairblock and RustVM Integration Tutorial, showcased with an Arbi > -Fairblock is a dynamic confidentiality network that delivers high performance, low overhead, and custom confidential execution to blockchain applications. Dynamic confidentiality unlocks the encrypted economy onchain applications designed for real-world use cases, like optimizable financial markets, competitive PVP markets like auctions, predictions, and gaming, and privacy-preserving inference. +Fairblock is a decentralized confidentiality network that provides cryptographic services and confidential application infrastructure across multiple chains and execution environments. This unlocks the encrypted economy for onchain applications designed for real-world use cases, like optimizable financial markets, competitive PVP markets like auctions, predictions, and gaming, and privacy-preserving inference. V1 is live on testnet with bespoke MPC-IBE which offer conditional confidentiality (for pre-execution confidentiality, sealed-bid auctions, selective disclosure, encrypted limit orders etc) and HE for confidential stablecoin transfers. diff --git a/protocol/fairyring.mdx b/protocol/fairyring.mdx index 1666eb3..c22df34 100644 --- a/protocol/fairyring.mdx +++ b/protocol/fairyring.mdx @@ -3,7 +3,7 @@ title: "FairyRing" description: "Fairblock's native chain for confidential computing" --- -FairyRing is a Cosmos SDK-based blockchain purpose-built for confidential computing. It serves as the cryptographic engine for the entire Fairblock ecosystem. +FairyRing coordinates Fairblock's decentralized cryptographic services. Users and partners access Fairblock through supported chains, applications, SDKs, and APIs without needing to interact directly with the underlying network. It is a Cosmos SDK-based blockchain purpose-built for confidential computing. ## Key Features diff --git a/protocol/overview.mdx b/protocol/overview.mdx index d1032b9..3bc9690 100644 --- a/protocol/overview.mdx +++ b/protocol/overview.mdx @@ -5,7 +5,7 @@ description: "FairyRing protocol architecture and design" --- -FairyRing is a dynamic, decentralized network that hosts app-specific secure confidential computing. Built with the Cosmos SDK, it provides cryptographic primitives as native chain functions. +FairyRing coordinates Fairblock's decentralized cryptographic services. Users and partners access Fairblock through supported chains, applications, SDKs, and APIs without needing to interact directly with the underlying network. Built with the Cosmos SDK, it provides cryptographic primitives as native chain functions. ## Core Design Principles diff --git a/protocol/the-fairblock-network.mdx b/protocol/the-fairblock-network.mdx new file mode 100644 index 0000000..b3b2358 --- /dev/null +++ b/protocol/the-fairblock-network.mdx @@ -0,0 +1,70 @@ +--- +title: "The Fairblock Network" +description: "Why Fairblock is a shared confidentiality network, not an isolated privacy system" +--- + +## A Shared Confidentiality Network + +Fairblock becomes more valuable as more users, assets, applications, chains, wallets, neobanks, and AI agents use the same confidentiality network. + +Encrypted balances and transaction amounts remain confidential by design, even when only a small number of users are active. Fairblock does not depend on a mixer or a large anonymity set to provide core confidentiality. However, broader participation increases activity diversity and can strengthen network-level metadata and transaction-pattern obfuscation. + +More participation can also create stronger financial incentives. As confidential balances and activity grow, Fairblock can generate additional float economics, transaction fees, ecosystem incentives, and partner-funded rewards. These economics can be redirected toward users, applications, liquidity providers, and integrations that expand the network. + +## Why Shared Infrastructure Matters + +A shared, neutral confidentiality layer prevents every chain, issuer, wallet, application, neobank, and agent platform from building an isolated system. + +Fragmentation creates real problems: + +- Liquidity becomes divided across incompatible confidential environments. +- Applications must integrate and maintain multiple encryption or privacy SDKs. +- Cross-chain wallets and neobanks cannot practically maintain a separate confidentiality stack for every network. +- Smaller systems may use weaker cryptography, receive fewer security reviews, or provide no meaningful confidentiality. +- Centralized privacy services require businesses to trust individual operators with sensitive information. +- Applications and agents using incompatible confidentiality systems cannot easily interact. + +Fairblock provides shared infrastructure through which assets, applications, chains, wallets, and intelligent systems can interact using common confidentiality and disclosure mechanisms. + +## The Network Flywheel + +```mermaid +flowchart TD + A["More supported assets and chains"] --> B["More wallets, applications, neobanks, and agents"] + B --> C["More users and confidential activity"] + C --> D["Stronger financial incentives and metadata obfuscation"] + D --> E["Deeper confidential liquidity and broader interoperability"] + E --> F["Lower integration costs for additional partners"] + F --> A +``` + +## What the Network Provides + + + + Encrypted values remain protected by design, while increased activity improves metadata and transaction-pattern obfuscation. + + + Float economics, transaction fees, and ecosystem incentives can reward productive confidential balances, activity, integrations, and liquidity. + + + A shared confidentiality layer reduces the fragmentation created when each chain or issuer launches an isolated confidential environment. + + + Wallets, neobanks, applications, and agent platforms can integrate a common confidentiality layer instead of maintaining separate systems for every chain and asset. + + + Applications and assets can interact through shared cryptographic infrastructure without trusting a single centralized privacy provider. + + + Common confidentiality and disclosure mechanisms make it easier for assets, applications, chains, and agents to interact securely. + + + +## Differences from Mixers and Anonymity-Set Systems + +Fairblock does not depend on a mixer or a large anonymity set to provide core confidentiality. It is not a mixer and not an anonymity pool: it is programmable confidentiality built for legitimate businesses and finance, where addresses stay traceable and encrypted amounts remain compatible with compliance, monitoring, and selective disclosure. + + + Fairblock does not rely on network size to provide core confidentiality. Encrypted balances and transfer amounts remain confidential even with limited participation. Broader usage strengthens metadata obfuscation, activity diversity, liquidity, incentives, interoperability, and integration value. + diff --git a/resources/faq.mdx b/resources/faq.mdx index b2ffdfe..5673259 100644 --- a/resources/faq.mdx +++ b/resources/faq.mdx @@ -5,11 +5,11 @@ description: "Frequently asked questions about Fairblock" - Fairblock is a decentralized confidential computing network that provides end-to-end applications for eliminating information leakage in open finance. It uses multimodal cryptography (HE, IBE, MPC, ZK) to enable confidential transactions, sealed-bid auctions, and protected trading across multiple blockchain ecosystems. + Fairblock is a decentralized confidentiality network that provides cryptographic services and confidential application infrastructure across multiple chains and execution environments. It uses multimodal cryptography (HE, IBE, MPC, ZK) to enable confidential transactions, sealed-bid auctions, and protected trading across multiple blockchain ecosystems. - FairyRing is Fairblock's native blockchain, built with the Cosmos SDK. It serves as the cryptographic execution layer: handling distributed key generation, threshold encryption, and confidential computation for applications across all integrated chains. + FairyRing coordinates Fairblock's decentralized cryptographic services. Users and partners access Fairblock through supported chains, applications, SDKs, and APIs without needing to interact directly with the underlying network. It is built with the Cosmos SDK and handles distributed key generation, threshold encryption, and confidential computation for applications across all integrated chains. diff --git a/resources/glossary.mdx b/resources/glossary.mdx index 87b3630..53f1410 100644 --- a/resources/glossary.mdx +++ b/resources/glossary.mdx @@ -49,7 +49,7 @@ Transparent, manipulation-resistant pricing mechanisms enabled by sealed-bid auc ### Fairblock -Network leveraging dynamic confidential computing to mitigate centralized risks in open finance. +A decentralized confidentiality network that provides cryptographic services and confidential application infrastructure across multiple chains and execution environments. ### Gateway Contracts @@ -61,7 +61,7 @@ Offchain messaging bridge for key distribution and cross-chain communication. ### FairyRing -A dynamic and decentralized network that hosts app-specific secure confidential computing. Built with Cosmos SDK. +Coordinates Fairblock's decentralized cryptographic services. Users and partners access Fairblock through supported chains, applications, SDKs, and APIs without needing to interact directly with the underlying network. Built with Cosmos SDK. ### fairyringclient From 56f8a97a326801cd22fdd57c7c70fa381367e7f2 Mon Sep 17 00:00:00 2001 From: crispzlegion Date: Wed, 22 Jul 2026 14:50:32 +0530 Subject: [PATCH 2/3] Replace mermaid diagrams with static SVGs, remove duplicate CUSD page - Swap network flywheel and CUSD mode diagrams from mermaid to matching SVG assets - Remove duplicate "CUSD by Fairblock and M0" page (cusd-app.mdx), keep cusd-overview Co-Authored-By: Claude Sonnet 5 --- .../cusd-transparent-confidential-modes.svg | 34 ++ assets/network-flywheel.svg | 51 +++ ct/guides/apps/cusd-app.mdx | 340 ------------------ ct/guides/apps/cusd-overview.mdx | 8 +- docs.json | 3 +- protocol/the-fairblock-network.mdx | 10 +- 6 files changed, 88 insertions(+), 358 deletions(-) create mode 100644 assets/cusd-transparent-confidential-modes.svg create mode 100644 assets/network-flywheel.svg delete mode 100644 ct/guides/apps/cusd-app.mdx diff --git a/assets/cusd-transparent-confidential-modes.svg b/assets/cusd-transparent-confidential-modes.svg new file mode 100644 index 0000000..9133b20 --- /dev/null +++ b/assets/cusd-transparent-confidential-modes.svg @@ -0,0 +1,34 @@ + + + + Transparent and Confidential Modes + + + + + + + + + + + USDC or supported asset + Transparent CUSD + Confidential balance + Confidential transfer + Transparent withdrawal + + + + + + + + + + + + + + + diff --git a/assets/network-flywheel.svg b/assets/network-flywheel.svg new file mode 100644 index 0000000..8c6d5ed --- /dev/null +++ b/assets/network-flywheel.svg @@ -0,0 +1,51 @@ + + + + The Network Flywheel + + + + + + + + + + + + + More supported assets and chains + + More wallets, applications, + neobanks, and agents + + More users and confidential + activity + + Stronger financial incentives and + metadata obfuscation + + Deeper confidential liquidity and + broader interoperability + + Lower integration costs for + additional partners + + + + + + + + + + + + + + + + + + + diff --git a/ct/guides/apps/cusd-app.mdx b/ct/guides/apps/cusd-app.mdx deleted file mode 100644 index 064fe49..0000000 --- a/ct/guides/apps/cusd-app.mdx +++ /dev/null @@ -1,340 +0,0 @@ ---- -title: "CUSD by Fairblock and M0" -description: "Confidential Stablecoin Infrastructure for Compliant Onchain Finance" ---- - -CUSD is a confidential USD stablecoin product built by Fairblock with M0 stablecoin infrastructure, MxON as the issuer and minter partner on the M0 network, and Predicate as the compliance partner. - -CUSD is designed for businesses, institutions, wallets, payment companies, fintechs, developers, market makers, neobanks, merchants, and end users that want the benefits of stablecoin payments without exposing sensitive financial information to the entire public internet. - -Public blockchains are transparent by default. That transparency is useful for verification, but it creates a practical barrier for real-world financial activity. Treasury balances, payroll amounts, supplier payments, merchant revenue, large trades, and institutional flows should not be permanently visible to competitors, counterparties, employees, customers, analysts, bots, or attackers. - -CUSD solves this by adding confidential transfers to stablecoin payments. Transfer amounts and balances can be encrypted, while address-level traceability, compliance controls, entry and exit screening, freezing pathways, and selective disclosure remain available. - - - **The goal is not anonymity. The goal is compliant confidentiality.** - - -## Roles in the CUSD Ecosystem - -CUSD is built through a partnership between Fairblock, M0, MxON, and Predicate. Each party plays a distinct role. - - - - Fairblock is the CUSD product and application layer. Fairblock provides the CUSD frontend, partner onboarding, user and enterprise distribution, confidential transfer technology, selective disclosure infrastructure, compliance UX, developer integrations, and go-to-market support. Fairblock makes CUSD usable by wallets, businesses, payment partners, developers, and end users. - - - M0 is the modular stablecoin infrastructure layer. M0 provides the underlying stablecoin architecture, contracts and rails, issuer framework, and base infrastructure that CUSD uses. - - - MxON is the issuer and minter partner on the M0 network. MxON supports the stablecoin issuance function, including minting, the backing and collateral framework, redemption mechanics, and issuer-side responsibilities. - - - Predicate is the compliance partner. Predicate supports policy enforcement, address screening, transaction checks, and compliance controls across the integrated chains where M0 and CUSD are supported. - - - -Together, these roles separate product, infrastructure, issuance, and compliance. Fairblock delivers the confidential stablecoin application and user experience. M0 provides the stablecoin infrastructure. MxON supports issuance and minting. Predicate provides compliance enforcement and monitoring. - -## What CUSD Is - -CUSD is a USD stablecoin experience that combines normal transparent stablecoin functionality with an optional confidential transfer layer. - -At the base level, CUSD behaves like a normal transparent stablecoin. Users can receive it, hold it, transfer it, or swap into it through supported applications. These transparent flows can be monitored and controlled using standard stablecoin compliance systems. - -Fairblock adds an optional confidential mode. A user can deposit transparent CUSD into the Fairblock smart contract and receive a confidential balance. From that point, transfers can happen through encrypted balance updates rather than public amount transfers. - -This gives CUSD two modes. - - - - Transparent CUSD is standard stablecoin activity. Transfers, amounts, and addresses are public and compatible with ordinary stablecoin monitoring, sanctions screening, and freezing controls. - - - Confidential CUSD is CUSD deposited into the Fairblock confidentiality layer. Internal transfer amounts and balances are encrypted, while deposits, withdrawals, address interactions, compliance controls, and selective disclosure remain available. - - - - - This document focuses specifically on CUSD. Fairblock's confidentiality technology can support other stablecoins, assets, and applications, but CUSD is the focus here because it combines Fairblock's confidentiality layer, M0's stablecoin infrastructure, yield, MxON's issuance role, and Predicate's compliance framework. - - -## Why CUSD Matters - -Stablecoins are becoming an important settlement layer for global payments. However, fully public payment amounts and balances limit their usefulness for serious business activity. - -A company may not want competitors to see its treasury balances. A payroll platform cannot expose employee compensation onchain. A merchant may not want revenue and supplier payments visible in real time. A market maker or trading firm may not want its flows and balances publicly tracked. A neobank or payment company may need stablecoin settlement without leaking customer activity. - -CUSD is designed for these use cases. It provides common-sense confidentiality for balances and transfer amounts while preserving the compliance controls that issuers, enterprises, fintechs, wallets, and regulated partners need. - -CUSD is particularly suited for businesses and enterprises because it is neutral, compliance-oriented, and designed to integrate into existing payment workflows. It can also support commercial arrangements such as rewards, revenue sharing, or float/yield-based economics where applicable. - -Most importantly, CUSD provides confidentiality without requiring users or partners to adopt the usual compromises of privacy systems: - -- Users do not need to bridge to a privacy chain -- They do not need a new wallet -- They do not need to accept long delays -- They do not need to use a mixer -- Partners do not need to weaken their compliance posture - -## How the CUSD Flow Works - -The CUSD flow has three stages: transparent entry, confidential transfer, and transparent exit. - - - - First, a user receives or purchases transparent CUSD. For example, the user may swap USDC into CUSD through a supported frontend. At this point, CUSD behaves like a normal transparent stablecoin. The user's address, transfer, and amount are visible and can be monitored using ordinary stablecoin compliance tools. - - - Second, the user can deposit transparent CUSD into the Fairblock smart contract. This deposit is visible onchain. The deposit amount is visible. The depositing address is visible. This creates a confidential balance for the user inside the Fairblock system. - - - Third, the user can make confidential transfers. Inside the Fairblock contract, transfers are represented as encrypted balance updates. The sender's encrypted balance is reduced and the receiver's encrypted balance is increased without publicly revealing the transfer amount. - - - When a user wants to exit the confidential layer, the user withdraws from their confidential balance. The Fairblock smart contract sends transparent CUSD to the user's transparent address. This withdrawal is visible and can be screened. - - - -In practical terms, the user receives transparent CUSD, deposits it into the Fairblock contract, receives an encrypted balance, transfers confidentially, and withdraws transparent CUSD when they want to exit. - -## What Happens During a Confidential Transfer - -A confidential transfer inside Fairblock is not a normal public token transfer from one user address to another. - -Once CUSD has been deposited into the Fairblock smart contract, the transparent CUSD is held by the contract. Internal confidential transfers are handled through encrypted accounting. The sender's encrypted balance decreases and the receiver's encrypted balance increases. - -Fairblock uses homomorphic encryption to support this flow. Homomorphic encryption allows the system to perform valid operations on encrypted values. This means balances can be updated correctly without exposing the underlying transfer amounts to the public chain. - - - This is the key technical distinction. Transparent CUSD movement happens at identifiable entry and exit points. Inside the confidential layer, Fairblock protects amounts and balances while preserving monitoring, selective disclosure, and partner-specific compliance workflows. - - -## What Is Public and What Is Confidential - -CUSD does not make all activity invisible. It protects the financial data that should not be globally public. - - - - - Addresses interacting with the system remain visible - - Deposits into the Fairblock contract are visible - - Withdrawals from the Fairblock contract are visible - - Deposit and withdrawal amounts are visible - - The timing of deposits and withdrawals is visible - - - - The internal transfer amount - - The user's confidential balance - - The encrypted accounting state inside the Fairblock layer - - - -This distinction is central to CUSD. The system provides amount and balance confidentiality. It does not create an uncontrolled anonymity system. - -## Compliance Architecture - -CUSD is designed for partners that need privacy and compliance at the same time. - -The compliance architecture combines M0's stablecoin framework, MxON's issuer and minter role, Predicate's compliance layer, and Fairblock's confidentiality and selective disclosure infrastructure. - -Predicate supports compliance screening and policy enforcement across integrated chains where M0 and CUSD are supported. This allows CUSD to maintain a consistent compliance posture across supported deployments. - -The compliance model is based on three core controls. - - - - The first is entry control. When a user receives, purchases, swaps into, or deposits CUSD, the relevant address and transaction can be screened. - - - The second is exit control. When a user withdraws CUSD from the confidential layer, the destination address can be screened. - - - The third is selective disclosure. When authorized parties need access to specific encrypted information, Fairblock's encryption architecture can support controlled disclosure under defined circumstances. - - - -This structure allows partners to support confidential stablecoin payments without losing the operational controls they require. - -## Compliance Controls - - - - CUSD begins as a transparent stablecoin. When a user first receives, purchases, or swaps into CUSD, standard compliance tools can apply. - - The user's address can be screened against sanctions lists, wallet risk systems, transaction monitoring tools, and other compliance systems used by M0, Predicate, Fairblock, MxON, or relevant partners. - - The same applies when a user deposits CUSD into the Fairblock contract. The deposit is visible, the address is visible, and the amount is visible. This creates a clear checkpoint before funds enter the confidential layer. - - If an address is sanctioned, blocked, or restricted under the applicable compliance policy, the relevant CUSD transfer can be prevented or frozen through the applicable M0, Predicate, issuer, or partner control framework. - - - - Withdrawals are also controlled points. - - When a user withdraws from the Fairblock confidentiality layer, transparent CUSD is sent from the Fairblock contract to a transparent address. That destination address can be screened before or during execution. - - If the destination address is sanctioned, blocked, or restricted under the applicable compliance policy, the withdrawal can be prevented or frozen through the relevant stablecoin controls. - - This means the confidential layer is not an uncontrolled exit path. Users still enter and exit through visible, screenable transactions. - - - - Fairblock's design is compatible with freezing and blocking controls at the transparent CUSD layer. - - The most relevant control points are the initial receipt or swap into CUSD, the deposit of CUSD into the Fairblock contract, the withdrawal of CUSD from the Fairblock contract, and transparent CUSD transfers outside the confidential layer. - - The exact implementation may vary by deployment, chain, and partner requirements. In the CUSD flow, freezing or blocking can be handled through the relevant M0, Predicate, issuer, or partner compliance framework. - - The key point is that CUSD confidentiality does not remove the ability to enforce compliance controls at transparent transfer points. - - - - Fairblock supports selective disclosure for authorized parties. - - The purpose of selective disclosure is to avoid a false choice between public exposure and complete opacity. Public blockchains should not expose every sensitive commercial payment amount to everyone, but compliance teams, auditors, security partners, and authorities may need access to specific information under defined circumstances. - - Fairblock uses encryption architecture, including identity-based encryption, to support controlled disclosure of relevant encrypted information. - - Depending on the deployment and partner requirements, selective disclosure can support transfer amount review, user balance review, audit workflows, security investigations, partner compliance monitoring, and authority-facing disclosure under valid legal process. - - Disclosure can be scoped to the relevant user, transfer, time period, partner flow, or compliance need. It does not require making all confidential activity public. - - - - Different partners have different compliance requirements. CUSD is designed to support that reality. - - Some partners may prefer Fairblock to manage the transparency dashboard and disclosure workflow. Other partners may require direct visibility into their own transfer flows or may want their approved compliance provider to monitor activity. - - Fairblock can support controlled access for a partner's own activity. For example, a partner may work with Fairblock to provide its internal compliance team or approved monitoring provider with access to relevant disclosure capabilities for that partner's own transfers. - - This can support proactive compliance workflows such as taint analysis, transaction risk monitoring, counterparty screening, suspicious activity review, internal audit, incident investigation, and regulatory reporting support. - - This access is scoped to the partner's relevant activity and is intended to support the partner's own compliance obligations. It is not a general public exposure of all confidential data. - - - - Fairblock provides a transparency dashboard to support operational oversight and compliance workflows. - - The dashboard can be managed by Fairblock, or access can be provided to partners where required. Partner access can be scoped to the partner's own transfers, users, or compliance perimeter. - - The dashboard is designed to help partners understand and monitor confidential stablecoin activity without forcing all sensitive payment information to be publicly visible onchain. - - For enterprises, issuers, fintechs, wallets, and payment companies, this creates the practical middle ground: privacy from the public internet, with controlled visibility for authorized compliance and operational stakeholders. - - - -## Why CUSD Is Not a Mixer - - - **CUSD is not a mixer.** - - -A mixer is generally designed to break the link between depositors and withdrawers. Its core purpose is address unlinkability. Users deposit assets into a pool and withdraw in a way that makes it difficult to determine which deposit funded which withdrawal. - -CUSD is different. - -CUSD is designed for amount and balance confidentiality, not address unlinkability. Addresses remain visible. Deposits and withdrawals remain visible. Entry and exit points can be screened. Applicable transfers can be blocked or frozen. Encrypted information can be selectively disclosed to authorized parties where required. - -CUSD does not aim to erase the transaction graph. It aims to prevent sensitive payment amounts and balances from being exposed to the entire public internet. - - - The correct framing is simple: CUSD provides confidential stablecoin infrastructure. It does not provide an uncontrolled anonymity system. - - -## Why CUSD Is Different From Privacy Chains - -CUSD is also different from broad privacy chains, shielded pools, or private execution environments. - -Some privacy systems are designed to hide many aspects of activity at the protocol level, including transaction relationships or broader execution details. Those systems may be useful for certain applications, but they are often not the right fit for regulated stablecoin payments, enterprise use, or partner-led compliance programs. - -CUSD is more targeted. - -It focuses on confidential stablecoin transfers where amounts and balances are encrypted, while address-level compliance, entry and exit controls, freezing pathways, and selective disclosure remain available. - -This narrower design is intentional. Most businesses, payment companies, issuers, fintechs, and institutions do not need an anonymity network. They need stablecoin payments that protect sensitive amounts while satisfying compliance, monitoring, audit, and legal obligations. - -## Developer and Partner Integration Model - -CUSD is designed to integrate into existing wallets, stablecoin flows, payment applications, fintech products, and partner frontends. - -A developer or partner can support transparent CUSD by default and offer confidential CUSD as an optional privacy mode. Users do not need to move into a separate privacy chain or adopt a new wallet. They can interact with a familiar stablecoin flow that supports confidentiality when needed. - -Partners can configure compliance based on their own requirements. A partner may require screening before deposit, screening before withdrawal, dashboard access, internal review rights, third-party monitoring, or scoped disclosure access for its own transfer flow. - -This makes CUSD suitable for partners that want to offer confidentiality without taking on the risks or friction of an uncontrolled privacy system. - -## Benefits for Key Stakeholders - - - - For stablecoin issuers, CUSD can make stablecoins more usable for real commercial payments while preserving compliance controls. - - - For enterprises, CUSD can support treasury, payroll, supplier payments, large transfers, and operational payments without exposing sensitive financial data publicly. - - - For payment companies and fintechs, CUSD can support merchant settlement, neobank payments, B2B transfers, and customer-facing payment products with stronger privacy. - - - For wallets and applications, CUSD can provide a better user experience for payments where financial privacy matters. - - - For developers, Fairblock provides infrastructure for encrypted balances and confidential transfers without requiring each application to build cryptography and compliance workflows from scratch. - - - For market makers and trading firms, CUSD can reduce information leakage around balances, flows, and large trades. - - - For compliance teams, CUSD provides control points, monitoring options, selective disclosure, and partner-specific configurations. - - - For end users, CUSD protects financial privacy without requiring a mixer, new wallet, privacy chain, or complex UX. - - - -## Core Compliance Position - -CUSD's compliance position is that confidentiality and compliance are compatible. - -CUSD protects sensitive amounts and balances from public exposure, but it does not remove the ability to screen addresses, monitor entry and exit points, freeze restricted transfers, support audits, or disclose specific information to authorized parties. - -Users first interact with transparent CUSD. They may optionally deposit into Fairblock to create a confidential balance. Internal transfers update encrypted balances. Withdrawals return transparent CUSD to a transparent address. - -This creates a practical compliance framework: - -- Users enter through visible, screenable transactions -- Users exit through visible, screenable transactions -- Addresses remain part of the compliance perimeter -- Amounts and balances are protected from public exposure -- Authorized parties can receive targeted disclosure where required -- Partners can configure additional monitoring for their own flows - -M0 provides the stablecoin infrastructure. MxON supports issuance and minting. Predicate supports compliance across integrated chains. Fairblock provides the confidentiality, application layer, selective disclosure infrastructure, developer experience, partner onboarding, and go-to-market. - -This is the foundation of compliant confidential stablecoin infrastructure. - -## Public Positioning - -CUSD makes stablecoin payments private enough for real-world use and compliant enough for serious partners. - -It is not a mixer. It is not an anonymity protocol. It is not designed to remove oversight from stablecoin systems. - -CUSD gives issuers, wallets, fintechs, developers, institutions, merchants, market makers, neobanks, and payment companies a way to protect sensitive financial information while preserving the controls required for regulated financial activity. - -It offers common-sense confidentiality for balances, treasury activity, large trades, merchant payments, market-making flows, and institutional payments without requiring users to bridge to a privacy chain, adopt a new wallet, tolerate delays, or accept a weaker compliance posture. - -## Summary - -CUSD is a confidential USD stablecoin product built by Fairblock with M0 stablecoin infrastructure, MxON as the issuer and minter partner, and Predicate as the compliance partner. - -CUSD starts as a normal transparent stablecoin. Users can optionally deposit CUSD into the Fairblock contract to create a confidential balance. Internal transfers update encrypted balances using homomorphic encryption. Withdrawals return transparent CUSD to a transparent address. - -The system protects transfer amounts and balances from public exposure, but it does not remove address traceability or compliance controls. - -Entry and exit transactions can be screened. Restricted transfers can be blocked or frozen through the applicable stablecoin controls. Encrypted information can be selectively disclosed to authorized parties where required. Partners can access dashboards or configure monitoring for their own flows. - - - **CUSD's core promise is compliant confidentiality for stablecoin payments.** - - - diff --git a/ct/guides/apps/cusd-overview.mdx b/ct/guides/apps/cusd-overview.mdx index 598a7d3..d31b5fb 100644 --- a/ct/guides/apps/cusd-overview.mdx +++ b/ct/guides/apps/cusd-overview.mdx @@ -32,13 +32,7 @@ CUSD does not limit Fairblock to a single stablecoin. The same infrastructure ca **Confidential CUSD**: CUSD deposited into Fairblock, where internal transfer amounts and balances are encrypted. -```mermaid -flowchart LR - A["USDC or supported asset"] --> B["Transparent CUSD"] - B --> C["Fairblock confidential balance"] - C --> D["Confidential transfers"] - D --> E["Transparent withdrawal"] -``` +![Transparent and Confidential Modes](/assets/cusd-transparent-confidential-modes.svg) CUSD is the flagship implementation, not the limit of the platform. Fairblock's confidential transfer infrastructure can also be integrated with other stablecoins and tokenized assets. diff --git a/docs.json b/docs.json index e66d21f..db86f0c 100644 --- a/docs.json +++ b/docs.json @@ -58,8 +58,7 @@ { "group": "Confidential CUSD", "pages": [ - "ct/guides/apps/cusd-overview", - "ct/guides/apps/cusd-app" + "ct/guides/apps/cusd-overview" ] }, { diff --git a/protocol/the-fairblock-network.mdx b/protocol/the-fairblock-network.mdx index b3b2358..075d738 100644 --- a/protocol/the-fairblock-network.mdx +++ b/protocol/the-fairblock-network.mdx @@ -28,15 +28,7 @@ Fairblock provides shared infrastructure through which assets, applications, cha ## The Network Flywheel -```mermaid -flowchart TD - A["More supported assets and chains"] --> B["More wallets, applications, neobanks, and agents"] - B --> C["More users and confidential activity"] - C --> D["Stronger financial incentives and metadata obfuscation"] - D --> E["Deeper confidential liquidity and broader interoperability"] - E --> F["Lower integration costs for additional partners"] - F --> A -``` +![The Network Flywheel](/assets/network-flywheel.svg) ## What the Network Provides From ad415901ca6fb0ed24747b0f6c963f4eec4a5029 Mon Sep 17 00:00:00 2001 From: crispzlegion Date: Thu, 30 Jul 2026 13:21:25 +0530 Subject: [PATCH 3/3] Fix broken Launch CUSD link on CUSD overview page Co-Authored-By: Claude Sonnet 5 --- ct/guides/apps/cusd-overview.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ct/guides/apps/cusd-overview.mdx b/ct/guides/apps/cusd-overview.mdx index d31b5fb..70c443f 100644 --- a/ct/guides/apps/cusd-overview.mdx +++ b/ct/guides/apps/cusd-overview.mdx @@ -195,7 +195,7 @@ CUSD combines a transparent stablecoin with optional confidential balances and t CUSD is Fairblock's flagship confidential asset. The broader Fairblock platform can extend the same confidentiality infrastructure to additional stablecoins and tokenized assets. - + Start using CUSD today.