Skip to content

40X fix links #3297

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
khadni merged 3 commits into from
Dec 15, 2025
Merged

40X fix links #3297

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
782b682
fix links
khadni Dec 15, 2025
f737dc0
fix links
khadni Dec 15, 2025
0db9ffb
fix links
khadni Dec 15, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
26 changes: 13 additions & 13 deletions reports/llms-report.json
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
{
"startedAt": "2025-12-12T21:54:23.121Z",
"startedAt": "2025-12-15T18:30:25.869Z",
"siteBase": "https://docs.chain.link",
"sections": [
{
Expand All @@ -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",
Expand All @@ -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",
Expand Down Expand Up @@ -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",
Expand Down Expand Up @@ -123,5 +123,5 @@
"deltaBytes": 0
}
],
"finishedAt": "2025-12-12T21:54:26.892Z"
"finishedAt": "2025-12-15T18:30:30.307Z"
}
3 changes: 0 additions & 3 deletions src/components/Footer/Footer.astro
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,9 +59,6 @@
<li class="footer-list-item">
<a href="https://chain.link/community" class="footer-list-item-link"> Community overview</a>
</li>
<li class="footer-list-item">
<a href="https://chain.link/community/grants" class="footer-list-item-link"> Grant program</a>
</li>
<li class="footer-list-item">
<a href="https://chain.link/community/events" class="footer-list-item-link"> Events</a>
</li>
Expand Down
7 changes: 0 additions & 7 deletions src/content/cre/llms-full-ts.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14491,13 +14491,6 @@ const onLogTrigger = (runtime: Runtime<Config>, log: EVMLog): string => {
}
```

<Aside type="note" title="Using contract ABIs">
For type-safe event handling, organize your contract ABIs in separate TypeScript files (e.g.,
`contracts/abi/MyContract.ts`) as demonstrated in the [demo
workflow](https://github.com/smartcontractkit/cre-cli/tree/main/examples/proof-of-reserve). Define ABIs as `const`
arrays with full JSON ABI structures for optimal TypeScript type inference with viem.
</Aside>

---

# SDK Reference: HTTP Trigger
Expand Down
7 changes: 0 additions & 7 deletions src/content/cre/reference/sdk/triggers/evm-log-trigger-ts.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -274,10 +274,3 @@ const onLogTrigger = (runtime: Runtime<Config>, log: EVMLog): string => {
return "Log decoded"
}
```

<Aside type="note" title="Using contract ABIs">
For type-safe event handling, organize your contract ABIs in separate TypeScript files (e.g.,
`contracts/abi/MyContract.ts`) as demonstrated in the [demo
workflow](https://github.com/smartcontractkit/cre-cli/tree/main/examples/proof-of-reserve). Define ABIs as `const`
arrays with full JSON ABI structures for optimal TypeScript type inference with viem.
</Aside>
2 changes: 1 addition & 1 deletion src/content/data-feeds/l2-sequencer-feeds.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -92,7 +92,7 @@ The diagram below shows how these feeds update and how a consumer retrieves the
<ClickToZoom src="/images/data-feed/l2-diagram-arbitrum.webp" />

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.

Expand Down
4 changes: 2 additions & 2 deletions src/content/data-feeds/llms-full.txt
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down Expand Up @@ -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.

Expand Down
2 changes: 1 addition & 1 deletion src/content/data-feeds/svr-feeds/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down
6 changes: 0 additions & 6 deletions src/content/resources/contributing-to-chainlink.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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).
2 changes: 1 addition & 1 deletion src/content/resources/hackathon-resources.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down
20 changes: 8 additions & 12 deletions src/content/resources/link-token-contracts.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 | <Address contractUrl="https://taostats.io//address/0xf09AFe78d3c7d359b334d7cB88995751F7eC5E13" urlId="964_0xf09AFe78d3c7d359b334d7cB88995751F7eC5E13" urlClass="erc-token-address"/> |
| Name | Chainlink Token on Bittensor EVM Mainnet |
| Symbol | LINK |
| Decimals | 18 |
| Parameter | Value |
| :-------- | :---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Chain ID | `964` |
| Address | <Address contractUrl="https://taostats.io/address/0xf09AFe78d3c7d359b334d7cB88995751F7eC5E13" urlId="964_0xf09AFe78d3c7d359b334d7cB88995751F7eC5E13" urlClass="erc-token-address"/> |
| Name | Chainlink Token on Bittensor EVM Mainnet |
| Symbol | LINK |
| Decimals | 18 |

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

Expand Down Expand Up @@ -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` |
Expand Down Expand Up @@ -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` |
Expand All @@ -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 |
| :------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
Expand Down
Loading
Loading