docs(specs): update OpenRPC specifications from Daikon [Bot]

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:
 

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

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