OpenDev — 21 July 2026, 14:00 UTC (Agenda)

[jessechejieh]

Tuesday, 21 July 2026 · 14:00 UTC
Host: Jesse Chejieh — @jessechejieh:matrix.org (Rank II)
Previous proceedings: 30 June 2026 · Proceedings published within 72h.

Preliminary agenda (posted ~2 weeks out, per the hosting pilot). Ordered by anticipated ecosystem / roadmap impact. This thread will be the source of truth.

• Add your topic — comment below (active Fellowship members), reply in the Fellowship Element channel, or DM me.
• Every item needs a speaker so I can confirm availability the week before. (Speaker = whoever raised it; correct if it should be someone else.)
• Please add by Tue 17 July — after that the agenda locks and I confirm speakers.
• Can't attend live? Comment with links/context and flag it — I'll cover it or capture it in the proceedings.

---

Topics

Discussion topics for the call — comment below to add yours (active Fellowship members). Ordered by impact during the call

Format example (click to expand)

Topic: Revive precompiles & Solidity DevEx
Speaker: a Fellowship member
Why it matters: Revive / PolkaVM is the smart-contract path on the Polkadot roadmap; a standard developer-experience layer for precompiles lowers the barrier for Solidity teams to build on Polkadot.
Proposal: A Standard DevEx Layer for Revive Precompiles · Context: State of Precompiles in the Revive Ecosystem

---

RFCs

Have an RFC up for review or discussion? Comment to add it.
Format: RFC title — [name](github profile) · RFCs#<num> · why it matters

Prevent Transaction Replay via CheckCreatedAtHeight — Josep M Sobrepere · RFCs#173

Binds each signed transaction to its sender's account-lifecycle epoch, so reaping and re-funding an account invalidates its old transactions. Closes a replay hole CheckMortality doesn't cover, across immortal, mortal, and intra-block cases, and makes tx hashes unique identifiers, which unblocks hash-indexed archive RPCs (json-rpc-interface-spec#182).

Speaker: Josep M Sobrepere

Fellowship — members, promotions, retention

Submitting a promotion, retention, or membership argument? Comment so it gets airtime. (Open arguments only.)
Supporting an applicant? Add a brief line on why — not just an emoji — for real visibility.

Calls for review

A Fellowship member wants eyes on a PR? Comment to add it.
Format: PR title — [name](github profile) · repo#<num> · why it matters