diff --git a/reports/llms-report.json b/reports/llms-report.json index 6a281009ee9..43a47dd587b 100644 --- a/reports/llms-report.json +++ b/reports/llms-report.json @@ -1,5 +1,5 @@ { - "startedAt": "2025-12-12T21:54:23.121Z", + "startedAt": "2025-12-15T18:30:25.869Z", "siteBase": "https://docs.chain.link", "sections": [ { @@ -14,17 +14,17 @@ "section": "cre-ts", "pagesProcessed": 79, "outputPath": "src/content/cre/llms-full-ts.txt", - "bytes": 629623, - "prevBytes": 629623, + "bytes": 629202, + "prevBytes": 629202, "deltaBytes": 0 }, { "section": "vrf", "pagesProcessed": 35, "outputPath": "src/content/vrf/llms-full.txt", - "bytes": 301012, + "bytes": 301005, "prevBytes": 301012, - "deltaBytes": 0 + "deltaBytes": -7 }, { "section": "ccip", @@ -38,9 +38,9 @@ "section": "data-feeds", "pagesProcessed": 37, "outputPath": "src/content/data-feeds/llms-full.txt", - "bytes": 302816, + "bytes": 302811, "prevBytes": 302816, - "deltaBytes": 0 + "deltaBytes": -5 }, { "section": "data-streams", @@ -79,16 +79,16 @@ "pagesProcessed": 25, "outputPath": "src/content/chainlink-automation/llms-full.txt", "bytes": 197667, - "prevBytes": 196013, - "deltaBytes": 1654 + "prevBytes": 197667, + "deltaBytes": 0 }, { "section": "resources", "pagesProcessed": 12, "outputPath": "src/content/resources/llms-full.txt", - "bytes": 341272, - "prevBytes": 341272, - "deltaBytes": 0 + "bytes": 340405, + "prevBytes": 340412, + "deltaBytes": -7 }, { "section": "architecture-overview", @@ -123,5 +123,5 @@ "deltaBytes": 0 } ], - "finishedAt": "2025-12-12T21:54:26.892Z" + "finishedAt": "2025-12-15T18:30:30.307Z" } diff --git a/src/components/Footer/Footer.astro b/src/components/Footer/Footer.astro index 7f8a2078d1a..e78527acbe0 100644 --- a/src/components/Footer/Footer.astro +++ b/src/components/Footer/Footer.astro @@ -59,9 +59,6 @@
  • Community overview
    • -
  • - Grant program -
  • Events
    • diff --git a/src/content/cre/llms-full-ts.txt b/src/content/cre/llms-full-ts.txt index eb14e7b6ca8..17a26472a84 100644 --- a/src/content/cre/llms-full-ts.txt +++ b/src/content/cre/llms-full-ts.txt @@ -14491,13 +14491,6 @@ const onLogTrigger = (runtime: Runtime, log: EVMLog): string => { } ``` - - --- # SDK Reference: HTTP Trigger diff --git a/src/content/cre/reference/sdk/triggers/evm-log-trigger-ts.mdx b/src/content/cre/reference/sdk/triggers/evm-log-trigger-ts.mdx index 6464c1fba1f..65475254a44 100644 --- a/src/content/cre/reference/sdk/triggers/evm-log-trigger-ts.mdx +++ b/src/content/cre/reference/sdk/triggers/evm-log-trigger-ts.mdx @@ -274,10 +274,3 @@ const onLogTrigger = (runtime: Runtime, log: EVMLog): string => { return "Log decoded" } ``` - - diff --git a/src/content/data-feeds/l2-sequencer-feeds.mdx b/src/content/data-feeds/l2-sequencer-feeds.mdx index b3d623b4c5a..623dfcaaea5 100644 --- a/src/content/data-feeds/l2-sequencer-feeds.mdx +++ b/src/content/data-feeds/l2-sequencer-feeds.mdx @@ -92,7 +92,7 @@ The diagram below shows how these feeds update and how a consumer retrieves the 1. Chainlink nodes trigger an OCR round every 30s and update the sequencer status by calling the `validate` function in the [`ArbitrumValidator` contract](https://github.com/smartcontractkit/chainlink/blob/contracts-v1.3.0/contracts/src/v0.8/l2ep/dev/arbitrum/ArbitrumValidator.sol) by calling it through the [`ValidatorProxy` contract](https://github.com/smartcontractkit/chainlink/blob/contracts-v1.0.0/contracts/src/v0.8/ValidatorProxy.sol). -1. The `ArbitrumValidator` checks to see if the latest update is different from the previous update. If it detects a difference, it places a message in the [Arbitrum inbox contract](https://developer.offchainlabs.com/docs/inside_arbitrum#the-big-picture). +1. The `ArbitrumValidator` checks to see if the latest update is different from the previous update. If it detects a difference, it places a message in the [Arbitrum inbox contract](https://docs.arbitrum.io/how-arbitrum-works/inside-arbitrum-nitro). 1. The inbox contract sends the message to the [`ArbitrumSequencerUptimeFeed` contract](https://github.com/smartcontractkit/chainlink/blob/contracts-v1.3.0/contracts/src/v0.8/l2ep/dev/arbitrum/ArbitrumSequencerUptimeFeed.sol). The message calls the `updateStatus` function in the `ArbitrumSequencerUptimeFeed` contract and updates the latest sequencer status to 0 if the sequencer is up and 1 if it is down. It also records the block timestamp to indicate when the message was sent from the L1 network. 1. A consumer contract on the L2 network can read these values from the [`ArbitrumUptimeFeedProxy` contract](https://github.com/smartcontractkit/chainlink/blob/contracts-v1.0.0/contracts/src/v0.6/EACAggregatorProxy.sol), which reads values from the `ArbitrumSequencerUptimeFeed` contract. diff --git a/src/content/data-feeds/llms-full.txt b/src/content/data-feeds/llms-full.txt index 6955dc98310..9dc79ca85f0 100644 --- a/src/content/data-feeds/llms-full.txt +++ b/src/content/data-feeds/llms-full.txt @@ -1408,7 +1408,7 @@ zkSync Mainnet: [0x0E6AC8B967393dcD3D36677c126976157F993940](https://explorer.zk The diagram below shows how these feeds update and how a consumer retrieves the status of the Arbitrum sequencer. 1. Chainlink nodes trigger an OCR round every 30s and update the sequencer status by calling the `validate` function in the [`ArbitrumValidator` contract](https://github.com/smartcontractkit/chainlink/blob/contracts-v1.3.0/contracts/src/v0.8/l2ep/dev/arbitrum/ArbitrumValidator.sol) by calling it through the [`ValidatorProxy` contract](https://github.com/smartcontractkit/chainlink/blob/contracts-v1.0.0/contracts/src/v0.8/ValidatorProxy.sol). -2. The `ArbitrumValidator` checks to see if the latest update is different from the previous update. If it detects a difference, it places a message in the [Arbitrum inbox contract](https://developer.offchainlabs.com/docs/inside_arbitrum#the-big-picture). +2. The `ArbitrumValidator` checks to see if the latest update is different from the previous update. If it detects a difference, it places a message in the [Arbitrum inbox contract](https://docs.arbitrum.io/how-arbitrum-works/inside-arbitrum-nitro). 3. The inbox contract sends the message to the [`ArbitrumSequencerUptimeFeed` contract](https://github.com/smartcontractkit/chainlink/blob/contracts-v1.3.0/contracts/src/v0.8/l2ep/dev/arbitrum/ArbitrumSequencerUptimeFeed.sol). The message calls the `updateStatus` function in the `ArbitrumSequencerUptimeFeed` contract and updates the latest sequencer status to 0 if the sequencer is up and 1 if it is down. It also records the block timestamp to indicate when the message was sent from the L1 network. 4. A consumer contract on the L2 network can read these values from the [`ArbitrumUptimeFeedProxy` contract](https://github.com/smartcontractkit/chainlink/blob/contracts-v1.0.0/contracts/src/v0.6/EACAggregatorProxy.sol), which reads values from the `ArbitrumSequencerUptimeFeed` contract. @@ -4823,7 +4823,7 @@ Traditional MEV searching depends on spotting oracle price updates in the public ### Example Application: Aave Liquidations -Aave is a lending protocol where collateralized positions must remain above a [threshold](https://aave.com/docs/concepts/liquidations) called their health factor. When an oracle price update reveals a borrower is undercollateralized, the position becomes eligible for liquidation. The searcher liquidates the position in exchange for a liquidation bonus reward. With Chainlink SVR, a searcher's liquidation transaction can be bundled with the new SVR price update through Flashbots. +Aave is a lending protocol where collateralized positions must remain above a [threshold](https://aave.com/help/borrowing/liquidations) called their health factor. When an oracle price update reveals a borrower is undercollateralized, the position becomes eligible for liquidation. The searcher liquidates the position in exchange for a liquidation bonus reward. With Chainlink SVR, a searcher's liquidation transaction can be bundled with the new SVR price update through Flashbots. For more background on how Aave liquidations work, see [Aave Documentation](https://docs.aave.com/). To understand how Chainlink SVR adds a structured auction for these Aave liquidation opportunities, read the following sections. diff --git a/src/content/data-feeds/svr-feeds/index.mdx b/src/content/data-feeds/svr-feeds/index.mdx index 59014405596..12c7b48f7ee 100644 --- a/src/content/data-feeds/svr-feeds/index.mdx +++ b/src/content/data-feeds/svr-feeds/index.mdx @@ -205,7 +205,7 @@ Traditional MEV searching depends on spotting oracle price updates in the public ### Example Application: Aave Liquidations -Aave is a lending protocol where collateralized positions must remain above a [threshold](https://aave.com/docs/concepts/liquidations) called their health factor. When an oracle price update reveals a borrower is undercollateralized, the position becomes eligible for liquidation. The searcher liquidates the position in exchange for a liquidation bonus reward. With Chainlink SVR, a searcher's liquidation transaction can be bundled with the new SVR price update through Flashbots. +Aave is a lending protocol where collateralized positions must remain above a [threshold](https://aave.com/help/borrowing/liquidations) called their health factor. When an oracle price update reveals a borrower is undercollateralized, the position becomes eligible for liquidation. The searcher liquidates the position in exchange for a liquidation bonus reward. With Chainlink SVR, a searcher's liquidation transaction can be bundled with the new SVR price update through Flashbots. For more background on how Aave liquidations work, see [Aave Documentation](https://docs.aave.com/). To understand how Chainlink SVR adds a structured auction for these Aave liquidation opportunities, read the following sections. diff --git a/src/content/resources/contributing-to-chainlink.mdx b/src/content/resources/contributing-to-chainlink.mdx index 952c5214272..b7537ca3581 100644 --- a/src/content/resources/contributing-to-chainlink.mdx +++ b/src/content/resources/contributing-to-chainlink.mdx @@ -123,9 +123,3 @@ If you're interested in running an in-person meetup or watch party, [reach out t Chainlink runs hackathons multiple times per year and often sponsors other hackathons across the blockchain ecosystem. Participating in a hackathon that Chainlink is a part of is a great way to learn how to use Chainlink. It is also a great way to showcase your skills to the Chainlink team and the wider community. Hackathons are a popular place for recruiting talent into the blockchain ecosystem. To stay up to date on the hackathons that Chainlink is running or sponsoring, keep an eye out on the official Chainlink social media channels, and sign up for our [developer newsletter](/resources/developer-communications). - -## Applying for a grant - -The [Chainlink grant program](https://chain.link/community/grants) encourages development of critical developer tooling, add high-quality data, and the launch key services around the Chainlink Network. Grant categories include community, integration, bug bounty, research, and social impact grants. If you have a great idea that fits into one of these categories, you can apply for a grant. If successful, you will receive the funding and support needed to successfully build and implement your idea. - -For more information about the grant program, go to the [Chainlink Grants web page](https://chain.link/community/grants). diff --git a/src/content/resources/hackathon-resources.mdx b/src/content/resources/hackathon-resources.mdx index ee7b09830df..15db5dd352e 100644 --- a/src/content/resources/hackathon-resources.mdx +++ b/src/content/resources/hackathon-resources.mdx @@ -57,7 +57,7 @@ If you are new to Smart Contracts, read the [Getting Started Guide](/getting-sta ### BUILD projects - [Source Network](https://source.network/) -- [Thirdfi](https://www.thirdfi.org/) +- [Thirdfi](https://data.thirdfi.org/) ## Join the community diff --git a/src/content/resources/link-token-contracts.mdx b/src/content/resources/link-token-contracts.mdx index 7e8f6574c94..0acdcd9c46d 100644 --- a/src/content/resources/link-token-contracts.mdx +++ b/src/content/resources/link-token-contracts.mdx @@ -270,13 +270,13 @@ Testnet LINK are available at [faucets.chain.link/bitlayer-testnet](https://fauc ### Bittensor EVM Mainnet -| Parameter | Value | -| :-------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -| Chain ID | `964` | -| Address |
    | -| Name | Chainlink Token on Bittensor EVM Mainnet | -| Symbol | LINK | -| Decimals | 18 | +| Parameter | Value | +| :-------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Chain ID | `964` | +| Address |
    | +| Name | Chainlink Token on Bittensor EVM Mainnet | +| Symbol | LINK | +| Decimals | 18 | ## Blast @@ -900,8 +900,6 @@ ETH is used to pay for transactions on the Kroma mainnet. Testnet ETH is used to pay for transactions on the Kroma testnet. -Testnet Native and LINK are available at [faucets.chain.link/kroma-testnet](https://faucets.chain.link/kroma-testnet). - | Parameter | Value | | :------------- | :--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `ETH_CHAIN_ID` | `2358` | @@ -1970,8 +1968,6 @@ ETH is used to pay for transactions on the Zircuit mainnet. Testnet ETH is used to pay for transactions on the Zircuit testnet. -Testnet Native and LINK are available at [faucets.chain.link/zircuit-sepolia](https://faucets.chain.link/zircuit-sepolia). - | Parameter | Value | | :------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `ETH_CHAIN_ID` | `48899` | @@ -1984,7 +1980,7 @@ Testnet Native and LINK are available at [faucets.chain.link/zircuit-sepolia](ht ### ZKsync Era Mainnet -ETH is used to pay for transactions on ZKsync Era Mainnet. Use the recommended [ZKsync Bridges](https://zksync.io/explore#bridges) to transfer ETH from Ethereum to ZKsync. +ETH is used to pay for transactions on ZKsync Era Mainnet. Use the recommended [ZKsync Bridges](https://docs.zksync.io/zksync-network/zksync-era/ecosystem/bridges) to transfer ETH from Ethereum to ZKsync. | Parameter | Value | | :------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | diff --git a/src/content/resources/llms-full.txt b/src/content/resources/llms-full.txt index af965a41342..042aab4c712 100644 --- a/src/content/resources/llms-full.txt +++ b/src/content/resources/llms-full.txt @@ -285,12 +285,6 @@ Chainlink runs hackathons multiple times per year and often sponsors other hacka To stay up to date on the hackathons that Chainlink is running or sponsoring, keep an eye out on the official Chainlink social media channels, and sign up for our [developer newsletter](/resources/developer-communications). -## Applying for a grant - -The [Chainlink grant program](https://chain.link/community/grants) encourages development of critical developer tooling, add high-quality data, and the launch key services around the Chainlink Network. Grant categories include community, integration, bug bounty, research, and social impact grants. If you have a great idea that fits into one of these categories, you can apply for a grant. If successful, you will receive the funding and support needed to successfully build and implement your idea. - -For more information about the grant program, go to the [Chainlink Grants web page](https://chain.link/community/grants). - --- # Install Frameworks @@ -697,7 +691,7 @@ If you are new to Smart Contracts, read the [Getting Started Guide](/getting-sta ### BUILD projects - [Source Network](https://source.network/) -- [Thirdfi](https://www.thirdfi.org/) +- [Thirdfi](https://data.thirdfi.org/) ## Join the community @@ -1034,13 +1028,13 @@ Testnet LINK are available at [faucets.chain.link/bitlayer-testnet](https://fauc ### Bittensor EVM Mainnet -| Parameter | Value | -| :-------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | -| Chain ID | `964` | -| Address |
    | -| Name | Chainlink Token on Bittensor EVM Mainnet | -| Symbol | LINK | -| Decimals | 18 | +| Parameter | Value | +| :-------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | +| Chain ID | `964` | +| Address |
    | +| Name | Chainlink Token on Bittensor EVM Mainnet | +| Symbol | LINK | +| Decimals | 18 | ## Blast @@ -1664,8 +1658,6 @@ ETH is used to pay for transactions on the Kroma mainnet. Testnet ETH is used to pay for transactions on the Kroma testnet. -Testnet Native and LINK are available at [faucets.chain.link/kroma-testnet](https://faucets.chain.link/kroma-testnet). - | Parameter | Value | | :------------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `ETH_CHAIN_ID` | `2358` | @@ -2735,8 +2727,6 @@ ETH is used to pay for transactions on the Zircuit mainnet. Testnet ETH is used to pay for transactions on the Zircuit testnet. -Testnet Native and LINK are available at [faucets.chain.link/zircuit-sepolia](https://faucets.chain.link/zircuit-sepolia). - | Parameter | Value | | :------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | `ETH_CHAIN_ID` | `48899` | @@ -2749,7 +2739,7 @@ Testnet Native and LINK are available at [faucets.chain.link/zircuit-sepolia](ht ### ZKsync Era Mainnet -ETH is used to pay for transactions on ZKsync Era Mainnet. Use the recommended [ZKsync Bridges](https://zksync.io/explore#bridges) to transfer ETH from Ethereum to ZKsync. +ETH is used to pay for transactions on ZKsync Era Mainnet. Use the recommended [ZKsync Bridges](https://docs.zksync.io/zksync-network/zksync-era/ecosystem/bridges) to transfer ETH from Ethereum to ZKsync. | Parameter | Value | | :------------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | diff --git a/src/content/vrf/llms-full.txt b/src/content/vrf/llms-full.txt index 4b026ed98b3..ffabc17a636 100644 --- a/src/content/vrf/llms-full.txt +++ b/src/content/vrf/llms-full.txt @@ -2513,7 +2513,7 @@ This guide explains how to test Chainlink VRF v2 on a [Remix IDE](https://remix- Complete the following tasks to test your VRF v2 consumer locally: 1. Deploy the [VRFCoordinatorV2Mock](https://github.com/smartcontractkit/chainlink/blob/contracts-v1.3.0/contracts/src/v0.8/vrf/mocks/VRFCoordinatorV2Mock.sol). This contract is a mock of the [VRFCoordinatorV2](https://github.com/smartcontractkit/chainlink/blob/contracts-v1.3.0/contracts/src/v0.8/vrf/VRFCoordinatorV2.sol) contract. -2. Deploy the [MockV3Aggregator](https://github.com/smartcontractkit/chainlink/blob/contracts-v1.3.0/contracts/src/v0.8/shared/mocks/MockV3Aggregator.sol) contract. +2. Deploy the [MockV3Aggregator](https://github.com/smartcontractkit/chainlink/blob/contracts-v1.3.0/contracts/src/v0.8/tests/MockV3Aggregator.sol) contract. 3. Deploy the [LinkToken](https://github.com/smartcontractkit/chainlink/blob/contracts-v1.3.0/contracts/src/v0.8/shared/token/ERC677/LinkToken.sol) contract. 4. Deploy the [VRFV2Wrapper](https://github.com/smartcontractkit/chainlink/blob/contracts-v1.3.0/contracts/src/v0.8/vrf/VRFV2Wrapper.sol) contract. 5. Call the VRFV2Wrapper [setConfig function](https://github.com/smartcontractkit/chainlink/blob/contracts-v1.3.0/contracts/src/v0.8/vrf/VRFV2Wrapper.sol#L119) to set wrapper specific parameters. diff --git a/src/content/vrf/v2/direct-funding/examples/test-locally.mdx b/src/content/vrf/v2/direct-funding/examples/test-locally.mdx index ee1aff0fdce..58db326b44f 100644 --- a/src/content/vrf/v2/direct-funding/examples/test-locally.mdx +++ b/src/content/vrf/v2/direct-funding/examples/test-locally.mdx @@ -27,7 +27,7 @@ This guide explains how to test Chainlink VRF v2 on a [Remix IDE](https://remix- Complete the following tasks to test your VRF v2 consumer locally: 1. Deploy the [VRFCoordinatorV2Mock](https://github.com/smartcontractkit/chainlink/blob/contracts-v1.3.0/contracts/src/v0.8/vrf/mocks/VRFCoordinatorV2Mock.sol). This contract is a mock of the [VRFCoordinatorV2](https://github.com/smartcontractkit/chainlink/blob/contracts-v1.3.0/contracts/src/v0.8/vrf/VRFCoordinatorV2.sol) contract. -1. Deploy the [MockV3Aggregator](https://github.com/smartcontractkit/chainlink/blob/contracts-v1.3.0/contracts/src/v0.8/shared/mocks/MockV3Aggregator.sol) contract. +1. Deploy the [MockV3Aggregator](https://github.com/smartcontractkit/chainlink/blob/contracts-v1.3.0/contracts/src/v0.8/tests/MockV3Aggregator.sol) contract. 1. Deploy the [LinkToken](https://github.com/smartcontractkit/chainlink/blob/contracts-v1.3.0/contracts/src/v0.8/shared/token/ERC677/LinkToken.sol) contract. 1. Deploy the [VRFV2Wrapper](https://github.com/smartcontractkit/chainlink/blob/contracts-v1.3.0/contracts/src/v0.8/vrf/VRFV2Wrapper.sol) contract. 1. Call the VRFV2Wrapper [setConfig function](https://github.com/smartcontractkit/chainlink/blob/contracts-v1.3.0/contracts/src/v0.8/vrf/VRFV2Wrapper.sol#L119) to set wrapper specific parameters. diff --git a/src/features/feeds/data/StreamsNetworksData.ts b/src/features/feeds/data/StreamsNetworksData.ts index 37ed9544dfe..9c5e68ee768 100644 --- a/src/features/feeds/data/StreamsNetworksData.ts +++ b/src/features/feeds/data/StreamsNetworksData.ts @@ -283,12 +283,12 @@ export const StreamsNetworksData: NetworkData[] = [ mainnet: { label: "HyperEVM Mainnet", verifierProxy: "0x60fAa7faC949aF392DFc858F5d97E3EEfa07E9EB", - explorerUrl: "https://hyperliquid.cloud.blockscout.com/address/%s", + explorerUrl: "https://hyperevmscan.io/address/address/%s", }, testnet: { label: "HyperEVM Testnet", verifierProxy: "0x60fAa7faC949aF392DFc858F5d97E3EEfa07E9EB", - explorerUrl: "https://evm.hyperstats.xyz/address/%s", + explorerUrl: "https://testnet.purrsec.com/address/%s", }, }, {