Quote attributions on /what-is-the-ethereum-network/ point to outdated EF roles (+ CommentCard layout regression on title wrap)

[konopkja]

Context

/what-is-the-ethereum-network/ contains two CommentCard quotes attributed to EF protocol researchers:

• Tim Beiko, "Protocol Coordination, Ethereum Foundation" (gas/fees section)
• Barnabé Monnot, "Protocol Architecture, Ethereum Foundation" (staking section)

Both attributions were introduced in 51c0522a (Sept 2025) when those affiliations were current. Both contributors have since left EF, so the unqualified affiliations now read as inaccurate.

Why this is worth handling carefully

These quotes carry editorial weight specifically because of named expert + EF affiliation. Search engines and LLM-based answer engines (ChatGPT, Claude, Perplexity, AI Overview) do entity extraction on the visible card text and treat named experts plus a recognizable organization as authority signals. Stripping the affiliation weakens the page's E-E-A-T / AEO posture; misattributing is worse.

The structured data in page-jsonld.tsx does not reference either person by name — author / publisher resolve to ETHEREUM_COMMUNITY / ETHEREUM_FOUNDATION, and the contributor array is auto-built from git history. So the authority signal for these two quotes lives entirely in the visible title= text. Whatever string we choose is what crawlers index.

Options considered

Approach	Person entity	Org (EF) entity	Role entity	Honesty	Effort
Add date suffix (2025)	✅	✅	✅	Anchors quote to date	trivial
Then …, Ethereum Foundation	✅	✅	✅	Explicitly historical	trivial
Drop EF affiliation	✅	weakened	✅	reads evasive	trivial
Remove quote, fold into prose	—	—	—	loses voice	minor
Fresh quote from current EF role-holder	✅	✅	✅	best	outreach

Chosen: date-suffix. Minimally invasive, preserves all three crawler-relevant entities, and a year is the lowest-noise way to mark "true at time of writing."

CommentCard layout regression (exposed by the change)

Adding (2025) made both titles wrap to two lines, which surfaced a pre-existing layout bug in src/components/CommentCard/index.tsx. Measured with Playwright on the live page:

1. Avatar squeezed to an oval. flex-shrink: 1 default + min-width: auto let the title's min-content pressure squeeze the 32px avatar horizontally. Actual measurements: 29.34 × 32 px (Tim) and 29.64 × 32 px (Barnabé) instead of 32 × 32.
2. Avatar vertically centered against taller content. items-center centered the 32px avatar against the ~70px tall name+title column. User-visible result: avatar floated against the middle of the text block.
3. Visible misalignment between avatar top and name top. Even with items-start, the name <p>'s default line-height: 1.6 padded the visible glyph down inside its line-box by ~5px, so the avatar's visible top sat above the name's visible top by half-leading.

The fix is small and only touches CommentCard itself, so it improves every page that uses the component (including /ethereum-history-founder-and-ownership/).

Proposed scope

• app/[locale]/what-is-the-ethereum-network/page.tsx — append (2025) to both CommentCard title= props. These two strings are hardcoded English (not in i18n JSON), so no translation fanout.
• src/components/CommentCard/index.tsx — items-start + shrink-0 on avatar; leading-tight on name; leading-snug mt-1 on title; bump card space-y-1 (4px) → space-y-4 (16px).

Verified after fix: both avatars 32 × 32 (aspectIsCircle: true), deltaAvatarTopVsGlyphTop: 0.00.

Follow-ups (out of scope here)

• Consider moving name= / title= props on this page into i18n JSON for consistency with /ethereum-history-founder-and-ownership/ (which uses t(...)) and translatability.
• Consider upgrading page-jsonld.tsx with schema.org/Quotation nodes whose spokenByCharacter Person carries affiliation with startDate / endDate — gives crawlers a structured "true at time" representation. Most LLM crawlers still lean on visible text, so this is a nice-to-have rather than required.
• Longer-term: replace these dated quotes with fresh ones from whoever currently holds Protocol Coordination / Protocol Architecture leadership at EF. Open question for EF docs/comms.

---

PR in progress.