The House Edge

Appearance

Chapter 7 — Research Note (Phase 1) ​

Status: RESEARCH (Phase 1 — written by agent, awaiting Nick's review) Date: 2026-05-14 Working chapter: 07 — Exclusive Order FlowCarries forward from: SPEC.md

How to read this note ​

The research surfaced exactly what the chapter's central claim needs: defensible empirical anchors plus a clean cross-disciplinary parallel. Four things to know up front:

  1. The "access vs operational" decomposition the SPEC asked for is real and defensible. The Harmonic client-choice gap (Syndica: +33% to +101% per-block priority fees vs network median) dwarfs the operational/timing-games gain (Chorus One: ~+3% total rewards from full timing-and-scheduler optimisation) by roughly an order of magnitude. The chapter can make the claim with concrete numbers.

  2. Two strong academic anchors quantify Ethereum exclusive flow at the structural level. Wu et al. (arXiv 2405.01329) identified 75 Exclusive Order Flow arrangements accounting for approximately 71% of trading-related Ethereum builder revenue. Pahari and Canidio (arXiv 2509.16052, November 2025) found that 77.2%–84% of total fees paid in winning Ethereum blocks come from exclusive transactions. These are the two most load-bearing citations the chapter has.

  3. Maestro pairs with Beaverbuild, not Titan. The SPEC speculated Maestro was a Titan partner. Per Wu et al., Maestro's exclusive arrangement is with Beaverbuild (~6% of estimated proposer losses), not Titan. Banana Gun is the named Titan exclusive (~37.1% of estimated proposer losses). The chapter should not name additional Titan exclusives because no public source identifies them.

  4. The PFOF parallel is structurally rich. US wholesaler concentration is similar in shape to Ethereum builder concentration (Citadel + Virtu + G1 = >80% of US wholesale flow; Titan + BuilderNet + Quasar = ~91% of Ethereum builder share). But the 2026 regulatory landscape has split sharply: the EU PFOF ban takes effect 30 June 2026 (six weeks after the chapter's writing date), while the SEC withdrew 14 PFOF-restricting rule proposals on 12 June 2025. The on-chain version has no analogue to either regulator.

1. Key claims ​

Each numbered claim is something the chapter is allowed to state. Sources cited inline.

The chapter's central claim and its supporting evidence

  1. The difference between a top-quintile and bottom-quintile validator on most chains is no longer primarily explained by operational excellence (uptime, latency, hardware) but by access to specific infrastructure relationships — client choice, builder relationships, RPC partnerships, exclusive-flow arrangements. The chapter's load-bearing assertion. Supported by:

    Comparison: client-choice gap (access) ≈ +33% to +101% per block; timing-and-scheduler gap (operational) ≈ +3%. Access dwarfs operational by approximately an order of magnitude.

Direct exclusive arrangements: Titan + Banana Gun

  1. Titan's exclusive arrangement with Banana Gun is the canonical published case in 2026. Of approximately 4,466.89 ETH paid by Banana Gun users to Titan over the documented period, only 2,915.65 ETH reached Ethereum proposers (validators); approximately 2,271.26 ETH was retained by Titan exclusively. The deal lifted Titan's share of Ethereum block construction from less than 1% to approximately 40% (and subsequently to ~51.5% per relayscan May 2026 figures from Chs 5-6). (Techub News / PANews coverage via Gate.io)

  2. Titan's reported builder margin under the Banana Gun exclusive is approximately 17.75%, versus Beaverbuild's pre-BuilderNet margin of approximately 9% and Flashbots' near-zero historical margin under its non-exclusive model. (Observers — How Two Block Builders Monopolized Ethereum Block Production; already cited in Chapters 5 and 6.)

  3. The Maestro trading bot is paired exclusively with Beaverbuild, not Titan. Wu et al.'s academic analysis identifies the top five "pivotal providers" of exclusive flow on Ethereum, including Banana Gun (Titan) and Maestro (Beaverbuild). Banana Gun accounted for approximately 37.1% of estimated proposer losses from exclusive arrangements; Maestro for approximately 6%. (Wu et al. — Decentralization of Ethereum's Builder Market, arXiv:2405.01329)

The structural scale of exclusive flow on Ethereum

  1. Pahari and Canidio's November 2025 academic analysis (using Agnostic Relay data from December 2024) finds that exclusive transactions account for 77.2% to 84% of total fees paid in winning Ethereum blocks. Only approximately 7%–8.4% of on-chain exclusive transaction value comes from senders routing exclusively to one builder — meaning most exclusivity is dynamic, not contractually locked, but the aggregate fee impact is concentrated in transactions that are not available through public order flow. (Pahari & Canidio — How Exclusive are Ethereum Transactions?, arXiv:2509.16052)

  2. Wu et al. identified 75 Exclusive Order Flow arrangements that collectively account for approximately 71% of trading-related Ethereum builder revenue. The arrangements are not formally disclosed in any regulatory filing; they exist as private commercial contracts between named trading firms and named builders. (Wu et al. — arXiv:2405.01329, op. cit.)

Pipeline relationships: Helius + wallet customers

  1. Helius's 50/50 wallet-rebate split is the canonical pipeline-level exclusive flow arrangement on Solana. The user (or wallet) earns 50% of any MEV extracted through Helius's backrun-rebate mechanism; Helius retains 50%. Mechanism: private auction with pre-approved KYC'd searchers; post-trade backruns only; paid in SOL in the same block. Helius's wallet partners include Phantom, Backpack, Solflare, Trust, Bitwise (the exclusive Solana ETF staking provider), Coinbase, Jupiter. (Helius — Backrun Rebates Documentation; already cited in Chapter 6.)

  2. The aggregate dollar volume passing through the Helius rebate pipeline in 2026 is not publicly disclosed. The downstream split between Helius and its wallet customers (and whether wallets pass the rebate through to users or retain it as platform revenue) is similarly opaque. The chapter notes the opacity as itself a chapter-level point — Helius's rebate flow is structurally important but commercially private. Phantom's reported 2025 revenue of approximately $79.1 million is the best indirect anchor for the wallet-side scale; the firm's psSOL liquid-staking product shares MEV tips and priority fees with stakers. (SQ Magazine — Phantom Wallet Statistics 2026)

Validator-side fragmented surfaces: the persistent grey market

  1. The Solana Foundation removed more than 30 validators from its delegation program in June 2024 for participating in private mempools enabling sandwich attacks (Chapter 3 footnote 7). Tim Garcia, the foundation's validator-relations lead, stated that "enforcement actions are ongoing." No public list of additional removals between June 2024 and May 2026 has been published, though Garcia's framing committed the Foundation to continued enforcement. The chapter treats this as a chapter-level observation: the Foundation's enforcement is asserted but not publicly itemised after the initial action. (CoinDesk — Solana Heavyweights Wage War Against Private Mempool Operators, June 2024)

  2. The named pre-shutdown grey-market case — the DeezNode operator (validator address HM5H6…jdMRA) running the Vpe sandwich program — peaked in December 2024 to January 2025 at approximately 1.55 million sandwich transactions per 30 days for 65,880 SOL (~$13.43 million) in profit. The validator's delegated stake was approximately 811,604 SOL (~$168.5 million). The arrangement reportedly offered a 50% revenue share to opting-in validators. (Helius Solana MEV Report; Anarcaze / Medium analysis; both already cited in Chapter 3.)

BuilderNet as the structural alternative

  1. BuilderNet's open-source refund rule is the published commitment to non-exclusive flow in 2026 Ethereum infrastructure. Flashbots' launch announcement explicitly framed the design: "These opaque off-chain agreements have entrenched a duopoly in the builder market and created an unequal playing field for apps and users who do not have access to the same preferential treatment." BuilderNet's refund rule compensates contributors based on contribution to winning blocks; transactions sent via mev-share or the public mempool are excluded from refund distribution. (Flashbots — Introducing BuilderNet, November 2024; already cited in Chapter 6.)

  2. BuilderNet's growth came at Beaverbuild's expense, not Titan's. Live relayscan.io May 2026 snapshot: Titan ~52.16%, BuilderNet ~24.63%, Beaverbuild ~1.83% of Ethereum blocks. The open-refund-rule design did not displace Titan's exclusive-flow margin; it absorbed Flashbots' and Beaverbuild's standalone flow. The structural lesson: exclusive flow is competitively durable. A non-exclusive multi-operator protocol can capture share from other non-exclusive operators but does not appear (so far) to dent the exclusive-flow incumbent. (relayscan.io; previously cited in Chapter 6.)

CoW DAO solver concentration

  1. Barter is the dominant CoW Swap solver, having acquired Copium Capital's solver codebase in September 2025 and is targeting more than 50% of CoW solver market share. Barter has settled approximately $19 billion since January 2023, overtaking Wintermute's Rizzolver as the #1 solver by 30-day volume share. (Blockworks — Barter Buys Rival Solver Codebase, September 2025; DL News coverage)

  2. On the UniswapX side, two solvers (SCP and Wintermute) account for more than 90% of volume, with SCP earning approximately 2× the per-dollar profit of Wintermute. The CoW and UniswapX solver markets — designed as competitive auctions — are operating as near-duopolies in 2026, structurally similar to the exclusive-flow concentration in builder markets. (Khakhar et al. — Execution Welfare Across Solver-based DEXes, arXiv:2503.00738; already cited in Chapter 3.)

Hyperliquid: the structural counterpoint

  1. Hyperliquid does not operate a traditional exclusive-flow surface. Bitwise's April 2026 amendment to its proposed Hyperliquid ETF S-1 names Wintermute, Flowdesk, Nonco, and FalconX as approved trading counterparties, but the filing explicitly notes that there is "no obligation on the sponsor to route every transaction through any specific firm." This is an approval relationship, not an exclusivity arrangement. (Crowdfund Insider — Bitwise files second amendment to Hyperliquid ETF, April 2026; already cited in Chapter 5.)

  2. Hyperliquid's HIP-3 (builder-deployed perpetuals) creates a different structural primitive: builders who stake 500,000 HYPE (~$25 million) gain the right to deploy permissioned perpetual markets on the chain, with validators enforcing eligibility standards and slashing on validator vote. Builder codes have generated approximately $40 million in cumulative builder revenue since launch, and approximately 40% of Hyperliquid daily active users now trade through third-party frontends. This is less an exclusive-flow surface than a permissioned-deployment surface — the structural difference matters. (Hyperliquid — Builder Codes Documentation; Dwellir analysis)

Lido's curated operator set

  1. Lido's Ethereum stake is operated by a ~36-operator curated set (Chorus One, P2P, Allnodes, Stakefish, Kiln, Figment, others). The DAO take rate was raised from 4.96% to 6.11% (+23%) for the Curated Module in February 2026. CSM v2 (mainnet October 2025) raised the CSM stake-share limit to 5%; ValMart (the planned validator marketplace) is targeted for mid-2026 to move stake allocation to a market-driven model. (Lido DAO — Tokenholder Update, February 2026; Lido CSM v2 documentation)

  2. The Lido curated set is not an exclusive-flow arrangement in the builder-relationship sense — operators have their own builder relationships with Titan, BuilderNet, Quasar, etc., and Lido itself does not appear to broker EOF deals on their behalf. But it is structurally an exclusivity-of-stake arrangement: the 36 operators have privileged access to Lido's substantial stake pool that non-curated operators do not. The chapter treats this as a different category — exclusivity at the staking-pool layer rather than at the builder-flow layer.

The TradFi PFOF parallel — 2026 updates

  1. The SEC withdrew 14 Gensler-era rule proposals on 12 June 2025, including the Order Competition Rule (which would have required wholesalers to expose retail "segmented orders" to 100–300ms auctions on open venues) and Regulation Best Execution. With these withdrawals under the Atkins administration, "the foundational business model of bilateral agreements between brokers and wholesalers can continue unimpeded." No new PFOF-restricting rulemaking is pending. (SEC — Notice of Withdrawal of Proposed Regulatory Actions, 12 June 2025; Proskauer alert)

  2. The EU's PFOF ban takes definitive effect on 30 June 2026 — six weeks after this chapter's writing date. Germany is the only Member State that exercised the temporary exemption (notified March 2024) for domestic investment firms; the exemption expires at the same time. After 30 June 2026, PFOF is prohibited bloc-wide across all EU member states. (ESMA — list of EU Member States using temporary PFOF exemption; Hogan Lovells analysis)

  3. US wholesaler concentration is largely unchanged from the figures cited in Chapter 1 (via the SEC DERA paper). Citadel Securities approximately 41%, Virtu approximately 26%, G1 Execution Services approximately 16% — together more than 80% of US retail equity wholesale flow. No 2026 update to the three-firm concentration ratio has been published. Citadel Securities paid approximately $2.6 billion in PFOF over 2020–2021; Virtu approximately $654 million.

  4. The structural similarity to on-chain builder concentration is strong: Titan + BuilderNet + Quasar = ~91% of Ethereum builder share (Chapter 6), versus Citadel + Virtu + G1 = >80% of US wholesale flow. The structural difference is the regulatory regime: PFOF is regulated under SEC Rule 605 (and is being banned in the EU), with disclosure requirements and best-execution obligations; on-chain exclusive flow operates with no analogous disclosure regime, no rule-605-style reporting, no regulator monitoring of the rebate flows.

2. Numbers to verify ​

#NumberSourceDateFlag
N1Solana validator profit Gini coefficient ~0.93Placeholder VCSept 2025Strong; the chapter's headline structural-inequality stat
N2Harmonic client-choice gap: +101% / +39% / +36% priority fees vs medianSyndica March 2026Mar 2026Already cited Chs 5, 6; the chapter's "access" anchor
N3Chorus One timing-games + optimisation gain: +3.0% total rewards (~27 bps annualised)Chorus OneAug 2025Already cited Ch 5; the chapter's "operational" anchor
N4Titan/Banana Gun dollar trace: 4,466.89 ETH paid → 2,915.65 ETH to proposers → 2,271.26 ETH retained by TitanGate.io / Techub / PANews coverage2024-25Strong; the chapter's worked-example dollar anchor
N5Titan margin ~17.75% under Banana Gun exclusive; Beaverbuild ~9% pre-BuilderNetObservers2025Already cited Chs 5, 6
N6The Banana Gun deal lifted Titan from <1% to ~40% builder share (subsequently ~51.5% per relayscan May 2026)Gate.io coverage; relayscan.io2024–2026Strong
N7Pahari/Canidio: exclusive transactions = 77.2%–84% of total fees in winning Ethereum blocksarXiv 2509.16052Nov 2025Strong academic anchor; the chapter's strongest single ETH-side stat
N8Wu et al.: 75 Exclusive Order Flow arrangements = ~71% of trading-related ETH builder revenuearXiv 2405.013292024–2025Strong academic anchor
N9Banana Gun ~37.1% of estimated proposer losses from EOF; Maestro ~6% (paired with Beaverbuild)Wu et al.2024–2025Corrects SPEC's assumption that Maestro was a Titan partner
N10Helius 50/50 wallet-rebate split; backrun-only; KYC'd searchersHelius docs2025–2026Already cited Ch 6
N11Aggregate Helius MEV-rebate flow in 2026: not publicly disclosedn/an/aFlag as opaque
N12Phantom 2025 revenue ~$79.1M; tracks fees 1:1 weeklySQ Magazine2026Indirect proxy for the wallet-side rebate scale
N13DeezNode/Vpe: 1.55M sandwich tx / 30 days; 65,880 SOL ($13.43M) profit; 811,604 SOL delegated; 50% revenue share offerHelius MEV Report; Anarcaze MediumQ4 2024 / Q1 2025Already cited Ch 3
N14Solana Foundation enforcement: >30 validators removed June 2024; no public list of subsequent removalsCoinDeskJune 2024Already cited Ch 3
N15BuilderNet vs Titan May 2026: Titan ~52.16%, BuilderNet ~24.63%, Beaverbuild ~1.83%; BuilderNet growth from Beaverbuild migration, not from Titanrelayscan.ioMay 2026Already cited Chs 5, 6; load-bearing for the "exclusive flow is durable" argument
N16Barter ~28%+ of CoW solver share, targeting >50%; $19B settled since Jan 2023; overtook Wintermute RizzolverBlockworksSept 2025Already cited Ch 3
N17SCP + Wintermute = >90% of UniswapX volume; SCP earns ~2× per-dollar profit of WintermutearXiv 2503.00738March 2025Already cited Ch 3
N18Bitwise HYPE ETF "approved trading counterparties": Wintermute, Flowdesk, Nonco, FalconX — explicitly NOT exclusivityCrowdfund InsiderApril 2026Corrects SPEC's framing
N19HIP-3 builder codes: >$40M cumulative builder revenue; ~40% of HL DAU through 3rd-party frontends; 500K HYPE (~$25M) staking requirement for deployersHyperliquid docs; Dwellir2025–2026Strong
N20Lido Curated Module take rate raised 4.96% → 6.11% (Feb 2026); CSM v2 stake-share limit raised to 5%; ValMart mid-2026Lido DAOFeb 2026
N21SEC withdrew 14 Gensler-era rule proposals incl. Order Competition Rule on 12 June 2025SEC; ProskauerJune 2025Strong; the regulatory environment changed
N22EU PFOF ban effective 30 June 2026; Germany only exemption-using member stateESMA; Hogan Lovells2024–2026Strong; 6 weeks from publication
N23US wholesaler concentration: Citadel ~41%, Virtu ~26%, G1 ~16% = >80% of US retail equity wholesale flowSEC DERA paper / Wharton / The TRADE2024–2025Already cited Ch 1; unchanged in 2026
N24Citadel paid ~$2.6B PFOF 2020–2021; Virtu ~$654MWharton / SEC2020–2021

Deliberately not pinned:

  • Aggregate dollar value of Helius MEV-rebate flow in 2026 (not publicly disclosed)
  • Titan's full list of exclusive partners beyond Banana Gun (no public source)
  • Specific Solana Foundation removals between June 2024 and May 2026 (no published list)
  • Flashbots' quantitative comparison of BuilderNet's open-refund-rule trade-off vs Titan's exclusive-flow margin (not published)

3. Contested or evolving claims ​

  • The "Bitwise approved trading counterparties" framing. I initially read this (in the Ch 5 SPEC) as an exclusivity arrangement. The actual filing says the sponsor has no obligation to route through any specific firm. This is approval (the firms have passed Bitwise's diligence) not exclusivity. The chapter should correct the framing — Hyperliquid's permissioned-but-non-exclusive validator set is the structural counterpoint to Ethereum's exclusive flow.

  • The Maestro-Beaverbuild relationship. The SPEC speculated Maestro was paired with Titan. Per Wu et al., Maestro's exclusive arrangement is with Beaverbuild. The chapter should name only Banana Gun as a Titan exclusive and Maestro as a Beaverbuild exclusive; no public source documents other Titan exclusives.

  • The grey-market private mempool surface, post-enforcement. The Solana Foundation has stated enforcement is "ongoing" but has not published an itemised list of removals after June 2024. The chapter cannot assert specific 2025–2026 removals; it can frame the enforcement as committed-but-not-publicly-itemised.

  • The "access vs operational" decomposition. The chapter's central claim is supported by two clean signals: Harmonic client-choice gap (Syndica) versus timing-games/scheduler-optimisation gain (Chorus One). A formal econometric decomposition has not been published. The chapter constructs the comparison from the two sources; this is defensible synthesis but is not directly cited.

  • The PFOF parallel in 2026. The on-chain version of exclusive flow is structurally similar to PFOF in concentration shape but is operating during a sharp regulatory bifurcation: the EU is banning PFOF outright (effective 30 June 2026); the US has withdrawn its proposed Order Competition Rule and is moving in the opposite direction. The chapter's PFOF analogue lands well in 2026 specifically because both regulators are taking incompatible positions — and the on-chain version has no regulator at all.

4. Characters introduced ​

No new "Meet the actor" sidebar. Per the SPEC, the chapter develops relationships rather than introducing new actor types.

Returning named institutions with new role-developments:

  • Banana Gun + Titan: the canonical published Ethereum exclusive arrangement (4,466.89 ETH paid, 2,271.26 ETH retained by Titan, ~17.75% margin)
  • Maestro + Beaverbuild: the second-most-cited exclusive arrangement (per Wu et al., ~6% of proposer losses)
  • Helius + Phantom / Backpack / Solflare / Bitwise: the pipeline-rebate model (50/50 split; aggregate flow opaque)
  • DeezNode + Vpe (returning from Ch 3 with no new updates; the Foundation has not removed DeezNode publicly)
  • BuilderNet (Flashbots + Beaverbuild + Nethermind): the non-exclusive multi-operator alternative whose ~24.63% share grew from Beaverbuild's migration, not from Titan's loss
  • Barter + CoW DAO: the solver auction with implicit exclusivity (one firm at 28%+ targeting 50%+)
  • SCP + Wintermute + UniswapX: the duopoly disguised as competitive auction (>90% of volume between two firms)
  • Bitwise + Wintermute + Flowdesk + Nonco + FalconX (Hyperliquid): the approval-not-exclusivity arrangement; the structural counterpoint
  • Lido Curated Set: the stake-side exclusivity arrangement (36 named operators get privileged access to Lido stake; not a builder-flow EOF in the Ethereum sense)
  • Citadel Securities, Virtu Financial, G1 Execution Services: the TradFi PFOF concentration anchor (≥80% of US retail wholesale flow; structurally similar to Ethereum's 91% three-firm builder share)

No named individuals introduced for the first time. All named individuals (Mert Mumtaz, Kubi Mensah, Lucas Bruder, Ben Coverston, Hasu, Phil Daian, Anatoly Yakovenko, Tim Garcia) are returnees.

5. Worked example candidates ​

The SPEC offered three options. The research strengthens the paired Candidate A + B recommendation.

Candidate A — Titan + Banana Gun as the named-firm anchor ​

The chapter walks the published dollar trace: a Banana Gun user submits a swap → Banana Gun's infrastructure constructs a bundle → the bundle is routed exclusively to Titan → Titan constructs the block including the bundle → Titan bids on the proposer's signature (with margin retained by Titan) → the proposer signs and the block is finalised → Banana Gun captures its share of the user's fee → the user receives execution at a slightly worse price than they would on a non-exclusive route. The 4,466.89-ETH / 2,271.26-ETH-retained dollar trace from the Gate.io / Techub coverage is the concrete anchor.

  • Pros: cleanest published case in the book; sourced numbers; reader can follow the dollar from a single user's swap through every actor.
  • Cons: Ethereum-only; needs Solana and Hyperliquid paragraph cameos.

Candidate B — Validator-quintile decomposition (the empirical argument) ​

The chapter assembles the published data to support its central claim. Top-line: client-choice (access) produces ~+33% to +101% per-block revenue lift; operational-and-timing-game optimisation produces ~+3%. The Gini coefficient of 0.93 anchors the inequality scale. The chapter shows the access-vs-operational gap as an order-of-magnitude difference, defends the central claim explicitly, and frames the implications for validators without infrastructure relationships.

  • Pros: the empirical version of the chapter's argument; lets the chapter defend the load-bearing assertion with sourced numbers.
  • Cons: not narratively vivid; the decomposition is its own argumentative project.

Agent's recommendation ​

Candidate A (Titan + Banana Gun) as the chapter's named anchor at §4, with Candidate B's empirical decomposition as a substantial subsection (§5d) developing the validator-quintile claim. The combination lets the chapter make both moves the SPEC asked for: the vivid named-case (Banana Gun → Titan → 2,271.26 ETH retained) and the empirical structural argument (access dwarfs operational by an order of magnitude).

6. Open questions for Nick ​

Q1 — Word budget. Comparable to Ch 6 (~7,000–7,500 words including footnotes). The chapter has rich primary-source material (two academic papers, the Banana Gun dollar trace, the Syndica + Chorus One decomposition, the Lido curated-set data, the PFOF 2026 regulatory bifurcation). Acceptable, or do you want a tighter version?

Q2 — The Maestro-Beaverbuild correction. The SPEC speculated Maestro was a Titan partner. Per Wu et al., Maestro pairs with Beaverbuild. The chapter will name Banana Gun as the Titan exclusive and Maestro as the Beaverbuild exclusive. Confirm.

Q3 — The Bitwise "approved trading counterparties" correction. The Bitwise HYPE ETF S-1 names Wintermute / Flowdesk / Nonco / FalconX as approved counterparties but explicitly disclaims exclusivity. The chapter frames this as the structural counterpoint to Ethereum's exclusive flow — approval-but-not-exclusivity. Confirm.

Q4 — The PFOF 2026 framing weight. The PFOF parallel is structurally rich (similar concentration shape, very different regulatory regime, with the EU PFOF ban taking effect just six weeks after the chapter's writing date). Should the chapter develop PFOF as a substantial subsection (Candidate option) or as a recurring frame through the chapter? My recommendation: a substantial subsection at the end of the mechanics (the "TradFi parallel" section that closes the mechanics before the chain-comparison).

Q5 — The Hyperliquid framing. The chain's architecture eliminates the traditional exclusive-flow surface (Bitwise's "approved trading counterparties" notwithstanding), but HIP-3 builder codes introduce a different permissioned-but-non-exclusive primitive. Should the chapter develop HIP-3 in the chain-comparison box, or save it for Chapter 9? My recommendation: paragraph cameo in §6, full treatment in Ch 9.

Q6 — The Solana Foundation enforcement question. No public list of removals after June 2024 exists. The chapter cannot assert specific 2025–2026 enforcement events; it can frame the enforcement as committed-but-not-publicly-itemised. Acceptable framing?

Q7 — Lido's curated set as exclusive flow. The chapter's treatment: Lido is structurally an exclusivity-of-stake arrangement (36 named operators get privileged access to Lido stake) rather than a builder-flow EOF. Should this be a substantial subsection (it could anchor an L1 vs LST framing) or a paragraph cameo? My recommendation: paragraph cameo. The chapter's central argument is about builder-flow EOFs; Lido's stake-side exclusivity is structurally different.

Sources cited ​

Primary academic research:

Primary protocol / institutional research:

Primary regulatory and academic-legal:

News and analytical coverage:

Phase 1 is complete. Per the user's compressed-review pattern, Phase 2 (OUTLINE.md) follows immediately.