Skip to content

Commit 0db9ffb

Browse files
khadnikhadni
committed
fix links
1 parent f737dc0 commit 0db9ffb

File tree

9 files changed

+33
-33
lines changed

9 files changed

+33
-33
lines changed

‎reports/llms-report.json‎

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
{
2-
"startedAt": "2025-12-15T17:15:14.069Z",
2+
"startedAt": "2025-12-15T18:30:25.869Z",
33
"siteBase": "https://docs.chain.link",
44
"sections": [
55
{
@@ -15,16 +15,16 @@
1515
"pagesProcessed": 79,
1616
"outputPath": "src/content/cre/llms-full-ts.txt",
1717
"bytes": 629202,
18-
"prevBytes": 629623,
19-
"deltaBytes": -421
18+
"prevBytes": 629202,
19+
"deltaBytes": 0
2020
},
2121
{
2222
"section": "vrf",
2323
"pagesProcessed": 35,
2424
"outputPath": "src/content/vrf/llms-full.txt",
25-
"bytes": 301012,
25+
"bytes": 301005,
2626
"prevBytes": 301012,
27-
"deltaBytes": 0
27+
"deltaBytes": -7
2828
},
2929
{
3030
"section": "ccip",
@@ -38,9 +38,9 @@
3838
"section": "data-feeds",
3939
"pagesProcessed": 37,
4040
"outputPath": "src/content/data-feeds/llms-full.txt",
41-
"bytes": 302816,
41+
"bytes": 302811,
4242
"prevBytes": 302816,
43-
"deltaBytes": 0
43+
"deltaBytes": -5
4444
},
4545
{
4646
"section": "data-streams",
@@ -86,9 +86,9 @@
8686
"section": "resources",
8787
"pagesProcessed": 12,
8888
"outputPath": "src/content/resources/llms-full.txt",
89-
"bytes": 340412,
90-
"prevBytes": 340411,
91-
"deltaBytes": 1
89+
"bytes": 340405,
90+
"prevBytes": 340412,
91+
"deltaBytes": -7
9292
},
9393
{
9494
"section": "architecture-overview",
@@ -123,5 +123,5 @@
123123
"deltaBytes": 0
124124
}
125125
],
126-
"finishedAt": "2025-12-15T17:15:18.320Z"
126+
"finishedAt": "2025-12-15T18:30:30.307Z"
127127
}

‎src/content/data-feeds/l2-sequencer-feeds.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -92,7 +92,7 @@ The diagram below shows how these feeds update and how a consumer retrieves the
9292
<ClickToZoom src="/images/data-feed/l2-diagram-arbitrum.webp" />
9393

9494
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).
95-
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).
95+
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).
9696
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.
9797
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.
9898

‎src/content/data-feeds/llms-full.txt‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1408,7 +1408,7 @@ zkSync Mainnet: [0x0E6AC8B967393dcD3D36677c126976157F993940](https://explorer.zk
14081408
The diagram below shows how these feeds update and how a consumer retrieves the status of the Arbitrum sequencer.
14091409

14101410
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).
1411-
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).
1411+
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).
14121412
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.
14131413
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.
14141414

@@ -4823,7 +4823,7 @@ Traditional MEV searching depends on spotting oracle price updates in the public
48234823

48244824
### Example Application: Aave Liquidations
48254825

4826-
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.
4826+
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.
48274827

48284828
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.
48294829

‎src/content/data-feeds/svr-feeds/index.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -205,7 +205,7 @@ Traditional MEV searching depends on spotting oracle price updates in the public
205205

206206
### Example Application: Aave Liquidations
207207

208-
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.
208+
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.
209209

210210
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.
211211

‎src/content/resources/link-token-contracts.mdx‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -270,13 +270,13 @@ Testnet LINK are available at [faucets.chain.link/bitlayer-testnet](https://fauc
270270

271271
### Bittensor EVM Mainnet
272272

273-
| Parameter | Value |
274-
| :-------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
275-
| Chain ID | `964` |
276-
| Address | <Address contractUrl="https://taostats.io//address/0xf09AFe78d3c7d359b334d7cB88995751F7eC5E13" urlId="964_0xf09AFe78d3c7d359b334d7cB88995751F7eC5E13" urlClass="erc-token-address"/> |
277-
| Name | Chainlink Token on Bittensor EVM Mainnet |
278-
| Symbol | LINK |
279-
| Decimals | 18 |
273+
| Parameter | Value |
274+
| :-------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
275+
| Chain ID | `964` |
276+
| Address | <Address contractUrl="https://taostats.io/address/0xf09AFe78d3c7d359b334d7cB88995751F7eC5E13" urlId="964_0xf09AFe78d3c7d359b334d7cB88995751F7eC5E13" urlClass="erc-token-address"/> |
277+
| Name | Chainlink Token on Bittensor EVM Mainnet |
278+
| Symbol | LINK |
279+
| Decimals | 18 |
280280

281281
## <img src="/assets/chains/blast.svg" style="height: 24px; width: auto; margin-right: 8px;" />Blast
282282

‎src/content/resources/llms-full.txt‎

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1028,13 +1028,13 @@ Testnet LINK are available at [faucets.chain.link/bitlayer-testnet](https://fauc
10281028

10291029
### Bittensor EVM Mainnet
10301030

1031-
| Parameter | Value |
1032-
| :-------- | :------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
1033-
| Chain ID | `964` |
1034-
| Address | <Address contractUrl="https://taostats.io//address/0xf09AFe78d3c7d359b334d7cB88995751F7eC5E13" urlId="964_0xf09AFe78d3c7d359b334d7cB88995751F7eC5E13" urlClass="erc-token-address" /> |
1035-
| Name | Chainlink Token on Bittensor EVM Mainnet |
1036-
| Symbol | LINK |
1037-
| Decimals | 18 |
1031+
| Parameter | Value |
1032+
| :-------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
1033+
| Chain ID | `964` |
1034+
| Address | <Address contractUrl="https://taostats.io/address/0xf09AFe78d3c7d359b334d7cB88995751F7eC5E13" urlId="964_0xf09AFe78d3c7d359b334d7cB88995751F7eC5E13" urlClass="erc-token-address" /> |
1035+
| Name | Chainlink Token on Bittensor EVM Mainnet |
1036+
| Symbol | LINK |
1037+
| Decimals | 18 |
10381038

10391039
## <img src="/assets/chains/blast.svg" style="height: 24px; width: auto; margin-right: 8px;" />Blast
10401040

‎src/content/vrf/llms-full.txt‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2513,7 +2513,7 @@ This guide explains how to test Chainlink VRF v2 on a [Remix IDE](https://remix-
25132513
Complete the following tasks to test your VRF v2 consumer locally:
25142514

25152515
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.
2516-
2. Deploy the [MockV3Aggregator](https://github.com/smartcontractkit/chainlink/blob/contracts-v1.3.0/contracts/src/v0.8/shared/mocks/MockV3Aggregator.sol) contract.
2516+
2. Deploy the [MockV3Aggregator](https://github.com/smartcontractkit/chainlink/blob/contracts-v1.3.0/contracts/src/v0.8/tests/MockV3Aggregator.sol) contract.
25172517
3. Deploy the [LinkToken](https://github.com/smartcontractkit/chainlink/blob/contracts-v1.3.0/contracts/src/v0.8/shared/token/ERC677/LinkToken.sol) contract.
25182518
4. Deploy the [VRFV2Wrapper](https://github.com/smartcontractkit/chainlink/blob/contracts-v1.3.0/contracts/src/v0.8/vrf/VRFV2Wrapper.sol) contract.
25192519
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.

‎src/content/vrf/v2/direct-funding/examples/test-locally.mdx‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ This guide explains how to test Chainlink VRF v2 on a [Remix IDE](https://remix-
2727
Complete the following tasks to test your VRF v2 consumer locally:
2828

2929
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.
30-
1. Deploy the [MockV3Aggregator](https://github.com/smartcontractkit/chainlink/blob/contracts-v1.3.0/contracts/src/v0.8/shared/mocks/MockV3Aggregator.sol) contract.
30+
1. Deploy the [MockV3Aggregator](https://github.com/smartcontractkit/chainlink/blob/contracts-v1.3.0/contracts/src/v0.8/tests/MockV3Aggregator.sol) contract.
3131
1. Deploy the [LinkToken](https://github.com/smartcontractkit/chainlink/blob/contracts-v1.3.0/contracts/src/v0.8/shared/token/ERC677/LinkToken.sol) contract.
3232
1. Deploy the [VRFV2Wrapper](https://github.com/smartcontractkit/chainlink/blob/contracts-v1.3.0/contracts/src/v0.8/vrf/VRFV2Wrapper.sol) contract.
3333
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.

‎src/features/feeds/data/StreamsNetworksData.ts‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -283,12 +283,12 @@ export const StreamsNetworksData: NetworkData[] = [
283283
mainnet: {
284284
label: "HyperEVM Mainnet",
285285
verifierProxy: "0x60fAa7faC949aF392DFc858F5d97E3EEfa07E9EB",
286-
explorerUrl: "https://hyperliquid.cloud.blockscout.com/address/%s",
286+
explorerUrl: "https://hyperevmscan.io/address/address/%s",
287287
},
288288
testnet: {
289289
label: "HyperEVM Testnet",
290290
verifierProxy: "0x60fAa7faC949aF392DFc858F5d97E3EEfa07E9EB",
291-
explorerUrl: "https://evm.hyperstats.xyz/address/%s",
291+
explorerUrl: "https://testnet.purrsec.com/address/%s",
292292
},
293293
},
294294
{

0 commit comments

Comments
 (0)