Add CCIP docs

docs/apps/ccip-bridge/guides/smart-contract-requirements.md

@@ -0,0 +1,36 @@
+---
+description: Learn the token requirements to integrate with CCIP
+slug: /apps/ccip-bridge/smart-contract-requirements
+title: ERC-20 Smart Contract Requirements
+toc_max_heading_level: 2
+---
+
+## Overview
+
+Before enabling an ERC20-compatible token in CCIP, it's important to understand the requirements it must fulfill to integrate with CCIP.
+
+## Token Administrator address requirement
+
+The token contract must provide an easy way to obtain the token administrator address. This can be achieved if the token contract includes **one of the following functions**:
+
+* **owner()**: This function returns the token contract owner's address. **We recommend using this function.**
+* **getCCIPAdmin()**: This function returns the token administrator's address if it differs from the contract owner's.
+
+## Requirements for CCIP token transfers
+
+The token's smart contract must meet minimum requirements to integrate with CCIP.
+
+### Burn & Mint Requirements
+* The token smart contract must have the following functions:
+  * **mint(address account, uint256 amount)**: This function is used to mint the amount of tokens to a given **account** on the destination blockchain.
+  * **burn(uint256 amount)** / **burn(address account, uint256 amount)**: This function is used to burn the amount of tokens on the source blockchain.
+  * **decimals()**: Returns the token's number of decimals.
+* On the source and destination blockchains, the token contract must support granting **mint and burn** permissions. The token issuers or another role (such as the token administrator) will grant these permissions to the token pool.
+### Lock & Mint Requirements
+* The token smart contract must have the following function:
+  * **decimals()**: Returns the token's number of decimals.
+* On the destination blockchain, The token contract must support granting mint and burn permissions described above. The token issuers or another role (such as the token administrator) will grant these permissions to the token pool.
+
+:::info
+**If you don't have an existing token**: For all blockchains where tokens need to be burned and minted (for example, the source or destination chain in the case of Burn and Mint, or the destination blockchain in the case of Lock and Mint), Chainlink provides a [BurnMintERC677](https://github.com/smartcontractkit/ccip/blob/ccip-develop/contracts/src/v0.8/shared/token/ERC677/BurnMintERC677.sol) contract that you can use to deploy your token in minutes. This token follows the [ERC677](https://github.com/ethereum/EIPs/issues/677) or [ERC777](https://ethereum.org/en/developers/docs/standards/tokens/erc-777/), allowing you to use it as-is or extend it to meet your specific requirements. You can also use a standard **ERC-20** as long as it meets the above specifications.
+:::

docs/apps/ccip-bridge/overview.md

@@ -0,0 +1,53 @@
+---
+description: A protocol to enable secure token transfers between blockchain networks
+slug: /apps/ccip-bridge
+title: Chainlink CCIP Bridge
+---
+
+## Overview
+
+The **Cross-Chain Interoperability Protocol (CCIP)** is a protocol developed by Chainlink to enable secure and reliable communication and token transfers between different blockchain networks. It provides the technical infrastructure for cross-chain interactions, enabling developers to build decentralized applications (dApps) that operate across multiple blockchains.
+
+---
+
+## Features
+
+1. **Cross-Chain Connectivity**  
+   Enables communication and token transfers between blockchain networks, including both public and private chains.
+
+2. **Decentralized Infrastructure**  
+   Utilizes Chainlink's Decentralized Oracle Network to process and validate cross-chain messages, ensuring system reliability.
+
+3. **Token Transfers**  
+   Supports secure movement of tokens between chains, allowing for interoperability between blockchain ecosystems.
+
+4. **Built-in Safeguards**  
+   Includes security features such as rate limiting to mitigate risks associated with cross-chain interactions.
+
+---
+
+## Components
+
+- **CCIP Nodes**  
+  Nodes in the Chainlink network that manage cross-chain communication and ensure secure message delivery.
+
+- **Message Routers**  
+  Smart contracts that process and relay messages on each connected blockchain.
+
+- **Token Bridge**  
+  A mechanism for transferring tokens across blockchains, designed to maintain security and decentralization.
+
+---
+
+## Use Cases
+
+- Cross-chain asset transfers.
+- Multi-chain decentralized finance (DeFi) operations.
+- Interoperable tokenized assets (e.g., NFTs).
+- Cross-network governance solutions.
+
+---
+
+:::info
+Developers can access CCIP through [Chainlink's documentation and SDKs](https://docs.chain.link/ccip). The protocol provides tools and resources for integrating cross-chain functionality into dApps, with an emphasis on security and straightforward implementation.
+:::

sidebars.js

@@ -140,6 +140,17 @@ const sidebars = {
             'apps/ronin-bridge/reference/withdrawal-limits',
           ]
         },
+        {
+          type: 'category',
+          label: 'Chainlink CCIP Bridge',
+          link: {
+            type: 'doc',
+            id: 'apps/ccip-bridge/overview', 
+          },
+          items: [
+            'apps/ccip-bridge/guides/smart-contract-requirements',
+          ]
+        },
         // Katana
         {
           type: 'category',