Oracle platform

src/config/sidebar.ts

@@ -281,6 +281,28 @@ export const SIDEBAR: Partial<Record<Sections, SectionEntry[]>> = {
           title: "Bridges and Associated Risks",
           url: "resources/bridge-risks?parent=dataFeeds",
         },
+        {
+          title: "Chainlink Oracle Platform",
+          url: "oracle-platform/overview?parent=dataFeeds",
+          children: [
+            {
+              title: "Data Standard",
+              url: "oracle-platform/data-standard?parent=dataFeeds",
+            },
+            {
+              title: "Interoperability Standard",
+              url: "oracle-platform/interoperability-standard?parent=dataFeeds",
+            },
+            {
+              title: "Compliance Standard",
+              url: "oracle-platform/compliance-standard?parent=dataFeeds",
+            },
+            {
+              title: "Privacy Standard",
+              url: "oracle-platform/privacy-standard?parent=dataFeeds",
+            },
+          ],
+        },
         {
           title: "Chainlink Architecture",
           url: "architecture-overview/architecture-overview?parent=dataFeeds",
@@ -569,6 +591,28 @@ export const SIDEBAR: Partial<Record<Sections, SectionEntry[]>> = {
           title: "Bridges and Associated Risks",
           url: "resources/bridge-risks?parent=dataStreams",
         },
+        {
+          title: "Chainlink Oracle Platform",
+          url: "oracle-platform/overview?parent=dataStreams",
+          children: [
+            {
+              title: "Data Standard",
+              url: "oracle-platform/data-standard?parent=dataStreams",
+            },
+            {
+              title: "Interoperability Standard",
+              url: "oracle-platform/interoperability-standard?parent=dataStreams",
+            },
+            {
+              title: "Compliance Standard",
+              url: "oracle-platform/compliance-standard?parent=dataStreams",
+            },
+            {
+              title: "Privacy Standard",
+              url: "oracle-platform/privacy-standard?parent=dataStreams",
+            },
+          ],
+        },
         {
           title: "Chainlink Architecture",
           url: "architecture-overview/architecture-overview?parent=dataStreams",
@@ -752,6 +796,28 @@ export const SIDEBAR: Partial<Record<Sections, SectionEntry[]>> = {
           title: "Bridges and Associated Risks",
           url: "resources/bridge-risks?parent=automation",
         },
+        {
+          title: "Chainlink Oracle Platform",
+          url: "oracle-platform/overview?parent=automation",
+          children: [
+            {
+              title: "Data Standard",
+              url: "oracle-platform/data-standard?parent=automation",
+            },
+            {
+              title: "Interoperability Standard",
+              url: "oracle-platform/interoperability-standard?parent=automation",
+            },
+            {
+              title: "Compliance Standard",
+              url: "oracle-platform/compliance-standard?parent=automation",
+            },
+            {
+              title: "Privacy Standard",
+              url: "oracle-platform/privacy-standard?parent=automation",
+            },
+          ],
+        },
         {
           title: "Chainlink Architecture",
           url: "architecture-overview/architecture-overview?parent=automation",
@@ -943,6 +1009,28 @@ export const SIDEBAR: Partial<Record<Sections, SectionEntry[]>> = {
           title: "Bridges and Associated Risks",
           url: "resources/bridge-risks?parent=chainlinkFunctions",
         },
+        {
+          title: "Chainlink Oracle Platform",
+          url: "oracle-platform/overview?parent=chainlinkFunctions",
+          children: [
+            {
+              title: "Data Standard",
+              url: "oracle-platform/data-standard?parent=chainlinkFunctions",
+            },
+            {
+              title: "Interoperability Standard",
+              url: "oracle-platform/interoperability-standard?parent=chainlinkFunctions",
+            },
+            {
+              title: "Compliance Standard",
+              url: "oracle-platform/compliance-standard?parent=chainlinkFunctions",
+            },
+            {
+              title: "Privacy Standard",
+              url: "oracle-platform/privacy-standard?parent=chainlinkFunctions",
+            },
+          ],
+        },
         {
           title: "Chainlink Architecture",
           url: "architecture-overview/architecture-overview?parent=chainlinkFunctions",
@@ -1102,6 +1190,28 @@ export const SIDEBAR: Partial<Record<Sections, SectionEntry[]>> = {
           title: "Bridges and Associated Risks",
           url: "resources/bridge-risks?parent=vrf",
         },
+        {
+          title: "Chainlink Oracle Platform",
+          url: "oracle-platform/overview?parent=vrf",
+          children: [
+            {
+              title: "Data Standard",
+              url: "oracle-platform/data-standard?parent=vrf",
+            },
+            {
+              title: "Interoperability Standard",
+              url: "oracle-platform/interoperability-standard?parent=vrf",
+            },
+            {
+              title: "Compliance Standard",
+              url: "oracle-platform/compliance-standard?parent=vrf",
+            },
+            {
+              title: "Privacy Standard",
+              url: "oracle-platform/privacy-standard?parent=vrf",
+            },
+          ],
+        },
         {
           title: "Chainlink Architecture",
           url: "architecture-overview/architecture-overview?parent=vrf",
@@ -1946,6 +2056,28 @@ export const SIDEBAR: Partial<Record<Sections, SectionEntry[]>> = {
           title: "Bridges and Associated Risks",
           url: "resources/bridge-risks",
         },
+        {
+          title: "Chainlink Oracle Platform",
+          url: "oracle-platform/overview",
+          children: [
+            {
+              title: "Data Standard",
+              url: "oracle-platform/data-standard",
+            },
+            {
+              title: "Interoperability Standard",
+              url: "oracle-platform/interoperability-standard",
+            },
+            {
+              title: "Compliance Standard",
+              url: "oracle-platform/compliance-standard",
+            },
+            {
+              title: "Privacy Standard",
+              url: "oracle-platform/privacy-standard",
+            },
+          ],
+        },
         {
           title: "Chainlink Architecture",
           url: "architecture-overview/architecture-overview",

src/config/sidebarSections.ts

@@ -15,6 +15,7 @@ export const SIDEBAR_SECTIONS = {
   VRF: "vrf",
   AUTOMATION: "automation",
   ARCHITECTURE: "architecture",
+  ORACLE: "oracle",
   RESOURCES: "resources",
   LEGACY: "legacy",
   GLOBAL: "global",

src/content.config.ts

@@ -176,6 +176,14 @@ const architectureOverviewCollection = defineCollection({
   schema: baseFrontmatter,
 })
 
+const oraclePlatformCollection = defineCollection({
+  loader: glob({
+    base: "./src/content/oracle-platform",
+    pattern: "**/*.md?(x)",
+  }),
+  schema: baseFrontmatter,
+})
+
 const gettingStartedCollection = defineCollection({
   loader: glob({
     base: "./src/content/getting-started",
@@ -210,6 +218,7 @@ export const collections = {
   "architecture-overview": architectureOverviewCollection,
   "getting-started": gettingStartedCollection,
   "any-api": anyApiCollection,
+  "oracle-platform": oraclePlatformCollection,
 }
 
 export type Collection = keyof typeof collections

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

@@ -0,0 +1,13 @@
+---
+section: global
+date: Last Modified
+title: "Chainlink Compliance Standard"
+---
+
+import { ClickToZoom } from "@components"
+
+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.
+
+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.
+
+<ClickToZoom src="/images/oracle-platform/compliance-standard.png" />

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

@@ -0,0 +1,20 @@
+---
+section: global
+date: Last Modified
+title: "Chainlink Data Standard"
+---
+
+import { ClickToZoom } from "@components"
+
+Most blockchain transactions require some form of external data to determine if specific conditions were met prior to triggering the execution of smart contract code. High-quality data is paramount to maintaining blockchain application security and ensuring accurate outcomes, as manipulated data can result in unexpected outcomes and the loss of user funds. Due to their inherent security model, blockchains do not have direct access to external data in the real world and thereby require oracle infrastructure to deliver the data, often referred to as the blockchain oracle problem.
+
+The Onchain Data Protocol (ODP) is an open, protocol-level specification for how a DON aggregates and verifies external data and publishes it onchain. It also encapsulates how applications securely access the data via a consistent set of interfaces across any blockchain—regardless of source, format, aggregation, delivery models, chains used, or use case. All of Chainlink’s data oracle solutions are unified under the ODP standard, giving institutions the foundation they need to seamlessly and securely bring core financial data onchain and power the next generation of global markets.
+
+<ClickToZoom src="/images/oracle-platform/odp.png" />
+
+Chainlink ODP supports data oracle services that enable developers to bring any external data onchain and use it as part of their blockchain transactions. Some examples include:
+
+- [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.
+- [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.
+- [Data Streams](/data-streams) to access high-frequency market data for cryptocurrency, Real Word Assets, Net Asset Value (NAV), and more.
+- 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/interoperability-standard.mdx

@@ -0,0 +1,17 @@
+---
+section: global
+date: Last Modified
+title: "Chainlink Interoperability Standard"
+---
+
+import { ClickToZoom } from "@components"
+
+There are currently hundreds of public and private blockchains and potentially thousands more to come in the future, each with its own distinct assets, applications, and users. To maximize liquidity and support cross-chain applications, a unified interoperability standard for sending data and value across blockchains must be established, akin to how TCP/IP unifies the Internet we know today.
+
+The Chainlink interoperability standard, powered by the [Cross-Chain Interoperability Protocol (CCIP)](/ccip) is an open, protocol-level specification for how a DON reads data on a source blockchain, verifies it, and writes it on a destination blockchain. The ISMS of CCIP has been certified under ISO 27001 and CCIP has completed a SOC 2 Type 1 attestation covering the Trust Services Criteria for security, availability, and confidentiality—demonstrating its commitment to secure and resilient infrastructure and operations.
+
+<ClickToZoom src="/images/oracle-platform/inop-standard.jpg" />
+
+Utilizing interoperability oracles, CCIP enables data and tokens to be seamlessly and securely transferred across blockchains. CCIP also supports Programmable Token Transfers, where data (messages) and value (tokens) can move together across chains, particularly to instruct the receiving smart contract what to do with the tokens once they arrive, such as deploying them in a lending market or using them to purchase an asset. The result is CCIP connecting all public and private blockchains into a single Internet of Contracts, driving unified liquidity and efficient cross-chain applications.
+
+CCIP supports the [Cross-Chain Token (CCT) standard](/ccip/concepts/cross-chain-token) for making any new or existing token cross-chain-enabled via CCIP. CCT allows self-serve deployments, full control and ownership for developers, enhanced programmability, and zero-slippage transfers—all backed by CCIP’s industry-standard defense-in-depth security. Notably, CCTs are token logic agnostic, meaning token developers can deploy pre-audited token pool contracts to turn any ERC20-compatible token into a CCT or deploy their own custom token pool contracts for bespoke token use cases. CCTs do not require token developers to inherit any CCIP-specific code within their token’s smart contract. Furthermore, token developers can participate in the security of their tokens through the Token Developer Attestation feature by attesting to token burn or lock events on source chains before CCIP can mint or unlock tokens on destination chains.

src/content/oracle-platform/overview.mdx

@@ -0,0 +1,35 @@
+---
+section: global
+date: Last Modified
+title: "Chainlink Oracle Platform Overview"
+---
+
+import { ClickToZoom } from "@components"
+
+The Chainlink stack consists of four open standards for designing and operating oracle services, covering data oracles, interoperability oracles, compliance oracles, and privacy oracles. Developers and institutions leverage these oracle services to address specific use case requirements of advanced blockchain applications or to support end-to-end solutions.
+
+<ClickToZoom src="/images/oracle-platform/cll-stack.png" />
+
+## Data Standard
+
+The Chainlink data standard, powered by the Onchain Data Protocol (ODP); an open, protocol-level specification for how a DON aggregates and verifies external data and publishes it onchain.
+
+Learn more about the [Chainlink Data Standard](/oracle-platform/data-standard).
+
+## Interoperability Standard
+
+The Chainlink interoperability standard, powered by the Cross-Chain Interoperability Protocol (CCIP); an open, protocol-level specification for how a DON reads data on a source blockchain, verifies it, and writes it on a destination blockchain.
+
+Learn more about the [Chainlink Interoperability Standard](/oracle-platform/interoperability-standard).
+
+## Compliance Standard
+
+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.
+
+Learn more about the [Chainlink Compliance Standard](/oracle-platform/compliance-standard).
+
+## Privacy Standard
+
+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.
+
+Learn more about the [Chainlink Privacy Standard](/oracle-platform/privacy-standard).

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

@@ -0,0 +1,18 @@
+---
+section: global
+date: Last Modified
+title: "Chainlink Privacy Standard"
+---
+
+import { ClickToZoom } from "@components"
+
+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.
+
+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:
+
+- **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.
+- **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.
+- **Privacy of offchain data shared onchain**: DECO enables statements about offchain data to be shared onchain without revealing the underlying data.
+- **Privacy of transaction computations**: Chainlink can provide private and confidential computing for transactions while also ensuring cryptographic verifiability of how it was done, making use of threshold encryption and trusted execution environments (TEEs).
+
+<ClickToZoom src="/images/oracle-platform/privacy-standard.png" />

src/pages/oracle-platform/[...id].astro

@@ -0,0 +1,29 @@
+---
+import DocsLayout from "~/layouts/DocsLayout.astro"
+import { getCollection, render } from "astro:content"
+
+export async function getStaticPaths() {
+  const oraclePlatformEntries = await getCollection("oracle-platform")
+
+  return oraclePlatformEntries.map((entry) => {
+    const routeId = entry.id.replace(/\.(md|mdx)$/, "")
+
+    return {
+      params: { id: routeId },
+      props: { entry },
+    }
+  })
+}
+
+interface Props {
+  entry: Awaited<ReturnType<typeof getCollection<"oracle-platform">>>[number]
+}
+
+const { entry } = Astro.props
+
+const { Content, headings } = await render(entry)
+---
+
+<DocsLayout frontmatter={entry.data} {headings}>
+  <Content />
+</DocsLayout>