Skip to content

Commit f8c6a15

Browse files
committed
add ctas
1 parent dd3f374 commit f8c6a15

File tree

3 files changed

+3
-2
lines changed

3 files changed

+3
-2
lines changed

src/content/oracle-platform/compliance-standard.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,6 @@ import { ClickToZoom } from "@components"
88

99
The global financial system requires adherence to various forms of compliance within different geographic regions in order to conduct transactions, such as KYC/AML or transaction rate limits. These compliance requirements are implemented to protect against fraud or illicit activity and ensure specific jurisdictional or internal business requirements are satisfied. As a result, token issuers, financial institutions, and DeFi protocols need a way to embed compliance into their tokenized assets and blockchain applications in a manner that’s efficient, reliable, and specific to their unique needs.
1010

11-
The Chainlink compliance standard, powered by the Onchain Compliance Protocol (OCP) an open, protocol-level specification defining how to utilize DONs to define and store compliance data onchain and utilize identity data and policies in smart contracts. OCP allows existing identity systems (e.g., GLEIF’s vLEI, ERC-3643) to be integrated with onchain infrastructure via the Cross-Chain Identity (CCID) framework, with policies enforced onchain and offchain using the Policy Manager. Compliance policies can be embedded directly within smart contracts and any token type, credentials can be verified without exposing personal data, and identity attestations can be coordinated across blockchains and jurisdictions. This is enabled by CCT and its compliance extension, which functions as a connector between smart contracts and CCID and the Policy Manager.
11+
The Chainlink compliance standard, powered by the Onchain Compliance Protocol (OCP) an open, protocol-level specification defining how to utilize DONs to define and store compliance data onchain and utilize identity data and policies in smart contracts. OCP allows existing identity systems (e.g., GLEIF’s vLEI, ERC-3643) to be integrated with onchain infrastructure via the [Cross-Chain Identity (CCID) framework](https://blog.chain.link/automated-compliance-engine-technical-overview/), with policies enforced onchain and offchain using the Policy Manager. Compliance policies can be embedded directly within smart contracts and any token type, credentials can be verified without exposing personal data, and identity attestations can be coordinated across blockchains and jurisdictions. This is enabled by CCT and its compliance extension, which functions as a connector between smart contracts and CCID and the Policy Manager.
1212

1313
<ClickToZoom src="/images/oracle-platform/compliance-standard.png" />

src/content/oracle-platform/data-standard.mdx

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -16,4 +16,5 @@ Chainlink ODP supports data oracle services that enable developers to bring any
1616

1717
- [Price Feeds](/data-feeds/price-feeds) for accurately pricing digital assets in real time, such as cryptocurrency, stablecoins, equities, commodities, ETFs, fixed income, and more.
1818
- [SmartData](/data-feeds/smartdata) for servicing tokenized assets. For example, Proof of Reserve can verify the current collateralization of onchain assets backed by offchain or cross-chain reserves, while Net Asset Value (NAV) can price tokenized funds to support onchain subscriptions and redemptions.
19+
- [Data Streams](/data-streams) to access high-frequency market data for cryptocurrency, Real Word Assets, Net Asset Value (NAV), and more.
1920
- Any other data type needed to facilitate an onchain transaction, such as lending rates, assets under management (AUM), sports scores, weather information, and more.

src/content/oracle-platform/privacy-standard.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ import { ClickToZoom } from "@components"
88

99
Blockchain transactions, particularly those involving regulated institutions and assets or requiring the use of sensitive data, need a way to maintain privacy over different aspects of the transaction. Without privacy, many forms of blockchain transactions simply cannot take place, whether due to regulatory or consumer constraints.
1010

11-
The Chainlink privacy standard utilizes privacy oracles to conceal sensitive data and provide confidential computing via CRE. It also includes multiple other Chainlink services, including DECO, Blockchain Privacy Manager, and CCIP Private Transactions. Through the Chainlink privacy standard and services, institutions can integrate public and private chains with legacy systems without exposing sensitive data onchain and incorporate privacy into key parts of a transaction, such as:
11+
The Chainlink privacy standard utilizes privacy oracles to conceal sensitive data and provide confidential computing via CRE. It also includes multiple other Chainlink services, including DECO, Blockchain Privacy Manager, and CCIP Private Transactions. Through the [Chainlink privacy standard and services](https://blog.chain.link/ccip-private-transactions-blockchain-privacy-manager/), institutions can integrate public and private chains with legacy systems without exposing sensitive data onchain and incorporate privacy into key parts of a transaction, such as:
1212

1313
- **Privacy of data entering and leaving blockchains**: The Blockchain Privacy Manager enables institutions to integrate the public Chainlink Platform and their existing systems with private blockchain networks while limiting onchain data exposure.
1414
- **Privacy of cross-chain transactions**: CCIP Private Transactions leverages the Blockchain Privacy Manager and a novel onchain encryption/decryption protocol to enable institutions to transact across multiple private blockchains using the public CCIP network while keeping the transaction details confidential.

0 commit comments

Comments
 (0)