From 089d12a06291bf83104eca427547be3e43731427 Mon Sep 17 00:00:00 2001 From: alchemy-bot <80712764+alchemy-bot@users.noreply.github.com> Date: Mon, 2 Mar 2026 19:57:28 +0200 Subject: [PATCH 1/3] docs(specs): update OpenRPC specifications from Daikon --- content/api-reference/frax/frax-api-overview.mdx | 2 +- src/openrpc/chains/frax/frax.yaml | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/content/api-reference/frax/frax-api-overview.mdx b/content/api-reference/frax/frax-api-overview.mdx index 5f5d17c8b..348863e78 100644 --- a/content/api-reference/frax/frax-api-overview.mdx +++ b/content/api-reference/frax/frax-api-overview.mdx @@ -7,7 +7,7 @@ slug: docs/frax/frax-api-overview ## Frax APIs -📙 Get started with our [Frax API Quickstart Guide](/docs/reference/frax-api-quickstart). +📙 Get started with our [Frax API Quickstart Guide](/docs/frax). | | | | ----------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- | diff --git a/src/openrpc/chains/frax/frax.yaml b/src/openrpc/chains/frax/frax.yaml index f71ac456d..951324bda 100644 --- a/src/openrpc/chains/frax/frax.yaml +++ b/src/openrpc/chains/frax/frax.yaml @@ -9,8 +9,8 @@ info: servers: - url: https://frax-mainnet.g.alchemy.com/v2 name: Frax Mainnet - - url: https://frax-hoodi.g.alchemy.com/v2 - name: Frax Hoodi + - url: https://frax-sepolia.g.alchemy.com/v2 + name: Frax Sepolia methods: - $ref: ../_components/evm/methods.yaml#/components/methods/eth_blockNumber - $ref: ../_components/evm/methods.yaml#/components/methods/eth_call From 2b346cb9f2d9935becb982d828a8fbed58522345 Mon Sep 17 00:00:00 2001 From: dslovinsky Date: Mon, 2 Mar 2026 13:27:18 -0500 Subject: [PATCH 2/3] chore: undo frax quickstart link change --- content/api-reference/frax/frax-api-overview.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/api-reference/frax/frax-api-overview.mdx b/content/api-reference/frax/frax-api-overview.mdx index 348863e78..5f5d17c8b 100644 --- a/content/api-reference/frax/frax-api-overview.mdx +++ b/content/api-reference/frax/frax-api-overview.mdx @@ -7,7 +7,7 @@ slug: docs/frax/frax-api-overview ## Frax APIs -📙 Get started with our [Frax API Quickstart Guide](/docs/frax). +📙 Get started with our [Frax API Quickstart Guide](/docs/reference/frax-api-quickstart). | | | | ----------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- | From 0aea1557117944930fbb22a99b7a7c38f3511589 Mon Sep 17 00:00:00 2001 From: dslovinsky Date: Mon, 2 Mar 2026 13:31:33 -0500 Subject: [PATCH 3/3] chore: fix/exclude flaky link check domains --- .../smart-contract-basics/upgradeable-smart-contracts.mdx | 2 +- lychee.toml | 1 + 2 files changed, 2 insertions(+), 1 deletion(-) diff --git a/content/tutorials/alchemy-university/smart-contract-basics/upgradeable-smart-contracts.mdx b/content/tutorials/alchemy-university/smart-contract-basics/upgradeable-smart-contracts.mdx index 788e20359..b77849288 100644 --- a/content/tutorials/alchemy-university/smart-contract-basics/upgradeable-smart-contracts.mdx +++ b/content/tutorials/alchemy-university/smart-contract-basics/upgradeable-smart-contracts.mdx @@ -33,7 +33,7 @@ Upgradeable smart contracts are a pattern composed of **THREE contracts**: ![upgrading-sc](https://alchemyapi-res.cloudinary.com/image/upload/v1764180180/docs/tutorials/alchemy-university/smart-contract-basics/Untitled_20.png) -The above diagram shows what is called the [transparent proxy pattern](https://blog.openzeppelin.com/the-transparent-proxy-pattern/). This pattern uses `call`, `delegatecall` and the three-contract design in order to achieve a super cool infrastructure. 💥 +The above diagram shows what is called the [transparent proxy pattern](https://www.openzeppelin.com/news/the-transparent-proxy-pattern). This pattern uses `call`, `delegatecall` and the three-contract design in order to achieve a super cool infrastructure. 💥 Here is a breakdown of the diagram flow, from the user's perspective: diff --git a/lychee.toml b/lychee.toml index 640e20a54..6442f81b2 100644 --- a/lychee.toml +++ b/lychee.toml @@ -44,6 +44,7 @@ exclude = [ ".*codeburst\\.io.*", # TLS/certificate validation fails for crawler clients ".*temp-mail\\.org.*", # Bot protection blocks crawlers with 403 ".*metamask\\.zendesk\\.com.*", # Zendesk knowledge base pages can require auth / block crawlers + ".*openzeppelin\\.com.*", # Bot protection blocks crawlers ] # Include these patterns even if they match exclude patterns