Chainlink Developer Documentation

This project demonstrates how to use the Chainlink Runtime Environment (CRE) to bridge AWS serverless APIs with Ethereum smart contracts. It combines AWS reliability with decentralized trust to enable:

• Price feeds for DeFi protocols: Low-latency, tamper-resistant pricing data for lending, derivatives, and AMMs.
• Proof-of-reserves monitoring: Continuous verification that stablecoins and wrapped assets are fully backed by underlying reserves.
• Custom data feeds: Configurable, multi-source data feeds for tokenized assets.

The Giveaway Manager is an intermediate-level proof of concept designed to demonstrate provably-fair giveaways using Chainlink Automation and VRF (Verifiable Random Function).

It supports two primary giveaway modes:

1. Static Giveaways: Transparently picks winners from a participant list provided in a CSV format. Participant IDs (such as emails or addresses) are hashed before being stored onchain to ensure privacy.
2. Dynamic Giveaways: Allows participants to register themselves onchain via transactions over a set period. Winners are then selected using VRF Direct Funding.

Note: This application demonstrates the selection process only; fulfillment of prizes is not included. The provided code is an un-audited template intended for educational purposes and should not be used in production without independent audits.

Chainlink provides data feeds on the Solana network using Offchain Reporting (OCR) to aggregate data from multiple providers.

Key Architectural Differences: Unlike EVM-based chains, Solana separates storage (Accounts) from logic (Programs). A Solana 'Program' is stateless and contains the logic, while 'Accounts' store the state. To use Chainlink products, your program must be deployed on a supported Solana cluster.

Performance Note: Price Feed performance is dependent on the underlying blockchain. High network congestion may impact the frequency of updates. Monitor Solana status for system performance updates.

The VRF Subscription Balance Monitor is a quickstart tutorial designed to show how to automate the process of funding Chainlink VRF subscription balances. By using Chainlink Automation, you can deploy a manager contract that monitors multiple VRF subscriptions and automatically tops them up with LINK when they fall below a certain threshold, ensuring continuous availability for randomness requests.

Key Details:

• Products used: Chainlink Automation, Chainlink VRF
• Difficulty: Intermediate
• Estimated time: 30 minutes
• Prerequisites: A wallet with gas tokens (ETH) and ERC-677 LINK.
• Core Functionality: Monitors existing VRF subscriptions and performs top-ups only when necessary (e.g., when a subscription is underfunded).

Before implementing the VRF direct funding method, ensure you have the following tools and credentials ready:

• Foundry: Installed via foundryup.
• make: Installed on your OS.
• git: Verified via git --version.
• Etherscan API Key: Required for contract verification. Create an account and key at Etherscan.
• RPC Endpoint: An account with Infura or Alchemy, or your own testnet client.
• Wallet: Must contain gas tokens and ERC-677 LINK.

To ensure data integrity, you must confirm that a Data Streams report is signed by the Decentralized Oracle Network (DON). On Solana, there are two primary integration patterns:

1. Onchain integration: Verify reports directly within your Solana program by using Cross-Program Invocation (CPI) to call the Chainlink Verifier program. This is the method covered in this tutorial.
2. Offchain integration: Verify reports client-side using an SDK. This is suitable for applications where verification does not need to happen within a smart contract execution.

Both methods provide the same security guarantees and use the same underlying verification logic; the only difference is the execution environment (onchain vs. offchain).

The API documentation for each version of Chainlink Local is organized into several key functional areas. When navigating the documentation, you can find detailed information regarding:

• CCIP Components: Documentation for the Router and Simulator.
• Data Feed Contracts: Details on available data feed implementations.
• Token Implementations: Information on how tokens are handled within the framework.
• JavaScript Utilities: Helper functions and tools for JS-based testing.
• Testing Helpers: Specialized utilities to assist in writing tests.

The production implementation consists of the following components across two different blockchain environments:

• Ethereum Sepolia: Deploys an ERC20 token paired with a CCIP BurnMint pool. In this tutorial, the authority is EOA-controlled.
• Solana Devnet: Deploys an SPL token utilizing dual-layer governance via Squads and SPL multisig.
• Cross-Chain Transfer: Enables bidirectional token transfers through autonomous operations managed by the Pool Signer PDA.

Chainlink Cross-Chain Interoperability Protocol (CCIP) is a secure protocol that enables developers to build applications capable of transferring tokens, arbitrary data (messages), or both across different blockchains.

CCIP is designed with a defense-in-depth security model including:

• Decentralized Architecture: Uses multiple Decentralized Oracle Networks (DONs).
• Rate Limiting: Allows owners to configure and enforce policies for Cross-Chain Tokens on both source and destination chains to mitigate risk.
• Timelocked Upgrades: Security-critical changes must pass through a Role-based Access Control Timelock contract, allowing a review/veto period.
• Sybil-Resistant Node Operators: Secured by globally distributed, independent organizations.