lessons: fix 15 broken external URLs surfaced by the new link checker (EN+JA)

Fixes all broken external URLs the new external-link CI script flagged on first run. After fixes: 0 broken out of 162 checked.

Real link rot — content moved or repos renamed:
- vitalik.ca/.../rollup.html → vitalik.eth.limo (Vitalik's blog migrated to eth.limo years ago)
- paradigm.xyz/2023/11/shared-sequencer (removed) → Astria docs intro on shared sequencer
- docs.optimism.io/builders/chain-operators/architecture → docs.optimism.io/op-stack/protocol/getting-started
- paradigmxyz/op-rbuilder → flashbots/op-rbuilder (link text also updated to match)
- paradigmxyz/rbuilder → flashbots/rbuilder
- paradigmxyz/reth/tree/main/crates/optimism (extracted/restructured) → paradigmxyz/reth root
- paradigmxyz/reth/tree/main/crates/ress/protocol → paradigmxyz/ress (already-extracted crate)
- paradigmxyz/revm-rs (never existed; link-text mismatch) → bluealloy/revm
- ethereum/tests/tree/develop/GeneralStateTests (reorganized) → ethereum/execution-spec-tests (new canonical tests repo)
- sei-protocol/revm → sei-protocol/sei-chain (main repo)
- flashbots/mev-boost-spec → flashbots/mev-boost (main repo)
- hyperliquid.gitbook.io/.../consensus → hyperliquid.gitbook.io/.../about-hyperliquid (consensus page consolidated into about)
- docs.cosmos.network/v0.50/learn/advanced/upgrade → docs.cosmos.network/ (v0.50 path restructured)
- docs.flashbots.net/.../architecture-overview → docs.flashbots.net/flashbots-mev-boost/introduction
- coinbase/sponsored-erc20 (deleted repo; link text was mislabeled "Soneium" — never matched the URL) → removed reference, kept the OpenZeppelin citation

Also expanded check-external-links.ts EXCLUDE_PATTERNS with 3 more illustrative/RPC URLs (api.hyperliquid.xyz, aviationstack.mpp.tempo.xyz, crates.io with bot-protection 403).

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: psyto

.github/scripts/check-external-links.ts

@@ -51,11 +51,14 @@ const EXCLUDE_PATTERNS = [
   /^https:\/\/mpp\.dev\/api/,
   /^https:\/\/eth\.llamarpc\.com/,
   /^https:\/\/ethereum-rpc\.url/,
+  /^https:\/\/api\.hyperliquid\.xyz/,
+  /^https:\/\/aviationstack\.mpp\.tempo\.xyz/,
 
   // Sites with aggressive bot protection — false-positive 403/429 in CI but
   // resolve fine for humans. Trade-off: occasional real rot here goes uncaught.
   /^https:\/\/www\.coinbase\.com\/blog/,
   /^https:\/\/www\.coindesk\.com/,
+  /^https:\/\/crates\.io/,
 ];
 
 const CONCURRENCY = 8;

prisma/seed-reth-building-en.ts

@@ -1834,7 +1834,7 @@ Walk:
 - **\`SignedAuthorization::decode_2718\`** — the inverse of the \`encoded_2718\` the user sent. **One round-trip, no manual byte fiddling.**
 - **\`from = sponsor, to = user\`** — this is the heart of the design. The tx is *from the sponsor* (paying gas, signing the outer envelope) but *to the user's EOA* (which now executes as if it were the delegate). Anyone watching the tx sees Bob as initiator and Alice's address as the call target — and the **logs come from Alice's address** because that's the address running the delegate's code.
 - **\`with_authorization_list(vec![signed_auth])\`** — the line that makes this a Type 4. Add multiple \`SignedAuthorization\`s here and you're now batching multiple users into one tx (drill 3).
-- **The delegate's \`executeBatch\` is a convention, not a protocol mandate.** Most EIP-7702 delegate contracts in the wild expose a similar method (see [Soneium](https://github.com/coinbase/sponsored-erc20)'s pattern, OpenZeppelin's reference impl). Pick the convention your delegate uses.
+- **The delegate's \`executeBatch\` is a convention, not a protocol mandate.** Most EIP-7702 delegate contracts in the wild expose a similar method (see OpenZeppelin's reference impl). Pick the convention your delegate uses.
 
 > 🛑 **Anti-fluency check.** Without scrolling: when Bob (sponsor) submits this tx, **whose nonce increments**? Bob's, Alice's, both? Hint: think about which nonce is in the outer tx envelope vs. what the authorization's \`nonce\` field is for.
 

prisma/seed-reth-building-ja.ts

@@ -1834,7 +1834,7 @@ Walk:
 - **\`SignedAuthorization::decode_2718\`** — ユーザが送った \`encoded_2718\` の逆操作。**1 往復、手動の byte いじりなし。**
 - **\`from = sponsor、to = user\`** — これがデザインの心臓部。tx は *sponsor から* 出る (ガス支払い、外側の envelope に署名) が、*user の EOA に向かう* (今や delegate であるかのように実行する)。tx を観察する誰もが Bob を発信者、Alice のアドレスを call ターゲットと見る — そして **ログは Alice のアドレスから出る**。delegate のコードを走らせているのがそのアドレスだからだ。
 - **\`with_authorization_list(vec![signed_auth])\`** — これを Type 4 にする 1 行。複数の \`SignedAuthorization\` をここに足せば、複数ユーザを 1 つの tx にバッチしていることになる (drill 3)。
-- **delegate の \`executeBatch\` は慣例であってプロトコル必須ではない。** 実運用される EIP-7702 delegate コントラクトの大半が似たようなメソッドを公開する ([Soneium](https://github.com/coinbase/sponsored-erc20) のパターン、OpenZeppelin の参照実装等を参照)。あなたの delegate が使う慣例を選ぶ。
+- **delegate の \`executeBatch\` は慣例であってプロトコル必須ではない。** 実運用される EIP-7702 delegate コントラクトの大半が似たようなメソッドを公開する (OpenZeppelin の参照実装等を参照)。あなたの delegate が使う慣例を選ぶ。
 
 > 🛑 **理解度チェック。** スクロールを戻さずに: Bob (sponsor) がこの tx を提出する時、**誰の nonce が増える** か? Bob、Alice、両方? ヒント: 外側の tx envelope に入るのはどの nonce か、authorization の \`nonce\` フィールドは何のためかを考えてみる。
 

prisma/seed-reth-consensus-engineering-en.ts

@@ -597,7 +597,7 @@ For each chain, identify the consensus family and one design choice:
 ## 8. Reading list
 
 - [HotStuff paper](https://arxiv.org/abs/1803.05069) — the original 2018
-- [Hyperliquid whitepaper](https://hyperliquid.gitbook.io/hyperliquid-docs/about-hyperliquid/consensus) — what's public
+- [Hyperliquid whitepaper](https://hyperliquid.gitbook.io/hyperliquid-docs/about-hyperliquid) — what's public
 - [DiemBFT spec](https://developers.diem.com/docs/technical-papers/the-diem-blockchain-paper/) — the production HotStuff variant (defunct project but public docs)
 
 > Final check: in one sentence, what makes HotStuff superior to PBFT for chains like Hyperliquid? **If your answer is just "faster," go deeper — name the specific structural change.** Reference §2 if needed.`,

prisma/seed-reth-consensus-engineering-ja.ts

@@ -597,7 +597,7 @@ Tendermint との比較: Tendermint のほうが単純だが pipelining は積
 ## 8. 読み物
 
 - [HotStuff 論文](https://arxiv.org/abs/1803.05069) — 2018 の原典
-- [Hyperliquid ホワイトペーパー](https://hyperliquid.gitbook.io/hyperliquid-docs/about-hyperliquid/consensus) — 公開情報
+- [Hyperliquid ホワイトペーパー](https://hyperliquid.gitbook.io/hyperliquid-docs/about-hyperliquid) — 公開情報
 - [DiemBFT 仕様](https://developers.diem.com/docs/technical-papers/the-diem-blockchain-paper/) — 本番 HotStuff variant (廃止プロジェクトだが公開文書あり)
 
 > 最終チェック: 一文で、Hyperliquid のような chain で HotStuff が PBFT より優れている理由は? **「速い」だけなら掘り下げる — 具体的な構造的変更を名指しで挙げる**。必要なら §2 を参照。`,

prisma/seed-reth-expert-en.ts

@@ -1258,7 +1258,7 @@ Two production Rust stateless clients exist as of 2026. They were built by diffe
 - **Repo:** [\`paradigmxyz/ress\`](https://github.com/paradigmxyz/ress)
 - **Target chain:** Ethereum mainnet, fully validating.
 - **Disk:** 14 GB (vs ~3 TB for full Reth).
-- **Witness source:** any full Reth node running with \`--ress.enable\`. Ress peers with it over a dedicated RLPx subprotocol named \`ress\` — see [\`crates/ress/protocol\` in Reth](https://github.com/paradigmxyz/reth/tree/main/crates/ress/protocol).
+- **Witness source:** any full Reth node running with \`--ress.enable\`. Ress peers with it over a dedicated RLPx subprotocol named \`ress\` — see [\`crates/ress/protocol\` in Reth](https://github.com/paradigmxyz/ress).
 - **Witness format:** Merkle Patricia Trie proofs (the format you saw in the MPT lesson — same \`AccountProof\` / \`StorageProof\` shape).
 - **Bytecode:** fetched from the stateful peer **on demand** (via a separate \`GetBytecode\` message). Ress caches what it has seen; missing entries pull from the peer.
 - **Validation flow:** consensus client sends \`NewPayload\` → ress requests witness + missing bytecode from a Reth peer → validates payload in memory → returns \`PayloadStatus\`.
@@ -1341,7 +1341,7 @@ If 1–4 are shaky, scroll back. If you can't argue 5, **you haven't internalize
 ## Further reading
 
 - [Paradigm blog: Stateless Reth Nodes](https://www.paradigm.xyz/2025/03/stateless-reth-nodes) — the use-case framing in Section 1 comes from here.
-- [\`paradigmxyz/ress\`](https://github.com/paradigmxyz/ress) — README, then \`bin/\` entry point, then the RLPx subprotocol in [\`paradigmxyz/reth/crates/ress/protocol\`](https://github.com/paradigmxyz/reth/tree/main/crates/ress/protocol).
+- [\`paradigmxyz/ress\`](https://github.com/paradigmxyz/ress) — README, then \`bin/\` entry point, then the RLPx subprotocol in [\`paradigmxyz/reth/crates/ress/protocol\`](https://github.com/paradigmxyz/ress).
 - [\`megaeth-labs/stateless-validator\`](https://github.com/megaeth-labs/stateless-validator) — README, then \`crates/stateless-core/src/pipeline\`, then \`crates/stateless-core/src/executor.rs\`.
 - [\`megaeth-labs/salt\`](https://github.com/megaeth-labs/salt) — the authenticated KV store that replaces the MPT in MegaETH's witness format.`,
                 },
@@ -1915,7 +1915,7 @@ After drill 5, you have the full mental model for shipping a Revm/Reth fork with
 ## 📺 Further reading
 
 - [execution-spec-tests docs](https://eest.ethereum.org/) — the spec-test framework
-- [\`paradigmxyz/revm-rs\` fuzzing harnesses](https://github.com/paradigmxyz/revm-rs) — reference implementations of the differential pattern
+- [\`bluealloy/revm\` test crates](https://github.com/bluealloy/revm) — reference implementations of the differential pattern
 - The historical [Geth Yellow Paper Test Suite](https://github.com/ethereum/tests) — for understanding test-corpus evolution
 
 `,
@@ -2405,7 +2405,7 @@ Everything else (P2P, MDBX storage, staged sync, ExEx, trie commitments) **comes
 
 Order them from "shipped to mainnet" → "R&D":
 
-1. **\`crates/optimism/\`** in [paradigmxyz/reth](https://github.com/paradigmxyz/reth/tree/main/crates/optimism) — Optimism / Base / Mode / OP Stack. The most production-tested extension on the planet.
+1. **\`crates/optimism/\`** in [paradigmxyz/reth](https://github.com/paradigmxyz/reth) — Optimism / Base / Mode / OP Stack. The most production-tested extension on the planet.
 2. **[paradigmxyz/alphanet](https://github.com/paradigmxyz/alphanet)** — Paradigm's own OP-Stack testnet for trying custom precompiles (EIP-7212 P-256 verify, etc.) before they exist on mainnet.
 3. **[SovaNetwork/sova-reth](https://github.com/SovaNetwork/sova-reth)** — Reth as a Bitcoin execution layer.
 4. **[SeismicSystems/seismic-reth](https://github.com/SeismicSystems/seismic-reth)** — Reth with encrypted transactions.
@@ -2444,7 +2444,7 @@ Optimism is the canonical "Reth-based L2." Its node code lives at \`paradigmxyz/
 
 ## 1. Where to look
 
-Browse: [paradigmxyz/reth → crates/optimism/](https://github.com/paradigmxyz/reth/tree/main/crates/optimism)
+Browse: [paradigmxyz/reth → crates/optimism/](https://github.com/paradigmxyz/reth)
 
 You will see subcrates roughly along these lines (exact names drift across reth versions — verify in source):
 
@@ -2768,7 +2768,7 @@ The reth ecosystem has multiple payload builders to study:
 | :--- | :--- | :--- |
 | Default Ethereum builder | \`crates/payload/builder/\` | Mainnet validators |
 | OP payload builder | \`crates/optimism/payload/\` | OP Stack sequencer |
-| **op-rbuilder** | [paradigmxyz/rbuilder](https://github.com/paradigmxyz/rbuilder) | High-perf external block builder for OP Stack |
+| **op-rbuilder** | [flashbots/rbuilder](https://github.com/flashbots/rbuilder) | High-perf external block builder for OP Stack |
 
 The first two are inside reth. **op-rbuilder** is a separate repo, more aggressive about MEV and ordering policy, and is the production builder several OP Stack chains use.
 
@@ -2802,7 +2802,7 @@ The choice ends up in the **payload builder's source code**, gated by feature fl
 
 ## 5. op-rbuilder — the production-grade reference
 
-[paradigmxyz/rbuilder](https://github.com/paradigmxyz/rbuilder) is the external builder Paradigm built for OP Stack. Worth studying because:
+[flashbots/rbuilder](https://github.com/flashbots/rbuilder) is the external builder Paradigm built for OP Stack. Worth studying because:
 
 - It implements **bundle merging** (private order flow + public mempool)
 - It supports **sealing strategies** (greedy, parallelizable algorithms)
@@ -2830,7 +2830,7 @@ Open \`crates/optimism/payload/\` and:
 3. **Identify** where the block gas cap is enforced
 4. **Find** the function that signs/seals the built block
 
-Then read [op-rbuilder's README](https://github.com/paradigmxyz/rbuilder) for the "external builder" model.
+Then read [op-rbuilder's README](https://github.com/flashbots/op-rbuilder) for the "external builder" model.
 
 > Final check: in one sentence, what does the payload builder **decide** that the executor does not? If your answer doesn't include the word "ordering" or "selection," go back and re-read section 3.`,
                 },

prisma/seed-reth-expert-ja.ts

@@ -1250,7 +1250,7 @@ witness はどこからか来なくてはならない。あらゆるステート
 - **リポジトリ:** [\`paradigmxyz/ress\`](https://github.com/paradigmxyz/ress)
 - **対象チェーン:** Ethereum メインネット、完全検証。
 - **ディスク:** 14 GB (フル Reth の ~3 TB に対して)。
-- **Witness ソース:** \`--ress.enable\` で起動した任意の Reth フルノード。ress は専用 RLPx サブプロトコル \`ress\` でピアリングする — [Reth の \`crates/ress/protocol\`](https://github.com/paradigmxyz/reth/tree/main/crates/ress/protocol) 参照。
+- **Witness ソース:** \`--ress.enable\` で起動した任意の Reth フルノード。ress は専用 RLPx サブプロトコル \`ress\` でピアリングする — [Reth の \`crates/ress/protocol\`](https://github.com/paradigmxyz/ress) 参照。
 - **Witness フォーマット:** Merkle Patricia Trie の証明 (MPT レッスンで見たもの — \`AccountProof\` / \`StorageProof\` と同じ形)。
 - **バイトコード:** ステートフルピアから **オンデマンド** で取得 (\`GetBytecode\` メッセージ経由)。ress は見たものをキャッシュし、未取得分はピアから引く。
 - **検証フロー:** コンセンサスクライアントが \`NewPayload\` 送信 → ress が Reth ピアに witness と不足バイトコードを要求 → メモリ上で payload を検証 → \`PayloadStatus\` を返す。
@@ -1333,7 +1333,7 @@ stateless-validator しか読まなかったら、こう思い込んでしまう
 ## 追加で読むもの
 
 - [Paradigm ブログ: Stateless Reth Nodes](https://www.paradigm.xyz/2025/03/stateless-reth-nodes) — セクション 1 のユースケース整理はここ由来。
-- [\`paradigmxyz/ress\`](https://github.com/paradigmxyz/ress) — README → \`bin/\` のエントリ → [\`paradigmxyz/reth/crates/ress/protocol\`](https://github.com/paradigmxyz/reth/tree/main/crates/ress/protocol) の RLPx サブプロトコル。
+- [\`paradigmxyz/ress\`](https://github.com/paradigmxyz/ress) — README → \`bin/\` のエントリ → [\`paradigmxyz/reth/crates/ress/protocol\`](https://github.com/paradigmxyz/ress) の RLPx サブプロトコル。
 - [\`megaeth-labs/stateless-validator\`](https://github.com/megaeth-labs/stateless-validator) — README → \`crates/stateless-core/src/pipeline\` → \`crates/stateless-core/src/executor.rs\`。
 - [\`megaeth-labs/salt\`](https://github.com/megaeth-labs/salt) — MegaETH の witness フォーマットで MPT を置き換える authenticated KV store。`,
                 },
@@ -1904,7 +1904,7 @@ Reth ではこれは: 実行中にプロセスを kill し再起動して DB が
 ## 📺 関連リンク
 
 - [execution-spec-tests docs](https://eest.ethereum.org/) — spec-test フレームワーク
-- [\`paradigmxyz/revm-rs\` fuzzing harnesses](https://github.com/paradigmxyz/revm-rs) — differential パターンのリファレンス実装
+- [\`bluealloy/revm\` のテストクレート](https://github.com/bluealloy/revm) — differential パターンのリファレンス実装
 - 史的な [Geth Yellow Paper Test Suite](https://github.com/ethereum/tests) — テストコーパス進化を理解するため
 
 `,
@@ -2394,7 +2394,7 @@ Reth ベースの chain が典型的に override するスロット:
 
 「mainnet 出荷済み」→「R&D」の順:
 
-1. **\`crates/optimism/\`** in [paradigmxyz/reth](https://github.com/paradigmxyz/reth/tree/main/crates/optimism) — Optimism / Base / Mode / OP Stack。世界で最も本番運用された extension。
+1. **\`crates/optimism/\`** in [paradigmxyz/reth](https://github.com/paradigmxyz/reth) — Optimism / Base / Mode / OP Stack。世界で最も本番運用された extension。
 2. **[paradigmxyz/alphanet](https://github.com/paradigmxyz/alphanet)** — Paradigm 自身が運営する OP Stack 互換テストネット。mainnet に実装される前の custom precompile (EIP-7212 P-256 verify など) を試す場。
 3. **[SovaNetwork/sova-reth](https://github.com/SovaNetwork/sova-reth)** — Reth を Bitcoin の execution layer として動かす。
 4. **[SeismicSystems/seismic-reth](https://github.com/SeismicSystems/seismic-reth)** — 暗号化 tx 対応の Reth。
@@ -2433,7 +2433,7 @@ Optimism は「Reth ベース L2」の正典です。その node コードは \`
 
 ## 1. 見る場所
 
-ここを開く: [paradigmxyz/reth → crates/optimism/](https://github.com/paradigmxyz/reth/tree/main/crates/optimism)
+ここを開く: [paradigmxyz/reth → crates/optimism/](https://github.com/paradigmxyz/reth)
 
 ざっくり以下のような sub-crate が並んでいるはず (正確な名前は reth のバージョンで揺れるので、ソースで確認すること):
 
@@ -2757,7 +2757,7 @@ Reth エコシステムには複数の payload builder が存在します:
 | :--- | :--- | :--- |
 | Default Ethereum builder | \`crates/payload/builder/\` | Mainnet validator |
 | OP payload builder | \`crates/optimism/payload/\` | OP Stack sequencer |
-| **op-rbuilder** | [paradigmxyz/rbuilder](https://github.com/paradigmxyz/rbuilder) | OP Stack 向けの高性能な external block builder |
+| **op-rbuilder** | [flashbots/rbuilder](https://github.com/flashbots/rbuilder) | OP Stack 向けの高性能な external block builder |
 
 最初の 2 つは reth 本体に入っています。**op-rbuilder** は別 repo で、MEV と ordering policy にずっと積極的、複数の OP Stack chain が本番で使用しています。
 
@@ -2791,7 +2791,7 @@ Sequencer が取れる立場は 3 つ:
 
 ## 5. op-rbuilder — 本番グレードのリファレンス
 
-[paradigmxyz/rbuilder](https://github.com/paradigmxyz/rbuilder) は、Paradigm が OP Stack 向けに作った external builder。読む価値がある理由:
+[flashbots/rbuilder](https://github.com/flashbots/rbuilder) は、Paradigm が OP Stack 向けに作った external builder。読む価値がある理由:
 
 - **Bundle merging** が実装されている (private order flow + public mempool)
 - **Sealing strategy** (greedy、並列化可能なアルゴリズム)
@@ -2819,7 +2819,7 @@ Tempo が sequencer モード block 生成に op-rbuilder を採用または拡
 3. **特定**: block の gas cap が強制されている箇所
 4. **特定**: 構築した block を sign / seal する関数
 
-そのあと [op-rbuilder の README](https://github.com/paradigmxyz/rbuilder) を読み、"external builder" モデルの考え方を掴んでください。
+そのあと [op-rbuilder の README](https://github.com/flashbots/op-rbuilder) を読み、"external builder" モデルの考え方を掴んでください。
 
 > 最終チェック: 1 文で、payload builder が **決定する** けれども executor は決定しないものは? 答えに "ordering" または "selection" が出てこないなら §3 を再読。`,
                 },

prisma/seed-reth-p2p-networking-en.ts

@@ -526,12 +526,12 @@ If you build a node that participates in HL's network, you'd need to understand
 1. Sketch a 2-message protocol for "broadcast my merchant attestation"
 2. Identify: how does the allowlist prevent Sybil attacks?
 3. Think: what's the bandwidth cost of broadcasting 1000 messages/sec to 10 peers?
-4. Read [MEV-Boost spec](https://github.com/flashbots/mev-boost-spec) and find the relayer protocol
+4. Read [MEV-Boost spec](https://github.com/flashbots/mev-boost) and find the relayer protocol
 
 ## 10. Reading list
 
 - [reth network crate](https://github.com/paradigmxyz/reth/tree/main/crates/net)
-- [MEV-Boost docs](https://docs.flashbots.net/flashbots-mev-boost/architecture-overview)
+- [MEV-Boost docs](https://docs.flashbots.net/flashbots-mev-boost/introduction)
 - [libp2p tutorials](https://docs.libp2p.io/) — for understanding modular networking
 
 > Final check: in one sentence, why is "custom gossip" the natural extension for chain-specific applications like MEV markets and payment routing? **If your answer doesn't reference "default gossip is for canonical chain data only," re-read §1.**`,