OpenDev Call — 20 October 2026, 14:00 UTC (Agenda)

[jessechejieh]

Tuesday, 20 October 2026 · 14:00 UTC
Host: Jesse Chejieh — @jessechejieh:matrix.org (Rank II)
Previous proceedings: 15 September 2026 · Proceedings published within 72h.

Agenda. First call after the hosting pilot

• Add your topic — comment below (active Fellowship members), reply in the OpenDev Element channel, or DM me.
• Every item needs a speaker so I can confirm availability. (Speaker = whoever raised it; correct if it should be someone else.)
• Please add by Thursday 15 October — 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

Topic: Asset Hub Migration v2

Speaker: Ank4n

Why it matters: AHM v2 is landing in the Fellowship's runtimes, behind the ahm-v2 feature: the stage machine (#1285), the full integrated PoC (#1284), the relay/coretime lockdown that freezes balances, holds and proxies while they move (#1321), the accounts stage (#1324) and manager multisig voting by unsigned extrinsic (#1325).

Security

Security-relevant items the room should know about. Comment to add.

RFCs

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

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.
Format: Name — rank action · Evaluations#

Calls for review

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

[jessechejieh]

Topic: Offchain Messaging MVP

Speaker: Alistair Singh / Snowfork team

Why it matters: HRMP puts message payloads and queue mechanics in the settlement path, making it a blocker for the JAM Parachain Service. Snowfork's four-month MVP proposal funds a reference implementation on JAM or Polkadot, HRMP-level latency in this initial phase, and integration and adversarial tests that leave the work ready for audit. The team will demo progress and surface PRs and blockers.