OpenDev Call — 17 November 2026, 14:00 UTC (Agenda) #23
jessechejieh
started this conversation in
General
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Tuesday, 17 November 2026 · 14:00 UTC
Host: Jesse Chejieh —
@jessechejieh:matrix.org(Rank II)Previous proceedings: 20 October 2026 · Proceedings published within 72h.
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: Road to JAM
Speaker: Bastian Köcher
Why it matters: Parity's Road to JAM thread (September) sets out the four workstreams the Fellowship will be tracking: PolkaJAM, Minimal Relay (AHM v2), offchain messaging replacing HRMP, and the parachain service switchover. The parachain service design (polkadot-sdk#11883) is still open and actively updated. What is already working, what does the parachain service still need, and when do parachains move?
Topic: JAM port and bootnode discovery
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 the replacement. Since the October demo: the v0.5 spec-msg primitives merged upstream (polkadot-sdk#12676, merged 6 November); the design moved from v0.5 to v0.6 with audit fixes, simpler channel management and a simpler fetch protocol (primitives #13759, collator scheduling-signal #13767). The team can now stand up a JAM testnet with the parachain service, which was October's stated blocker, and bootnode discovery is the active workstream: design in polkadot-sdk#12809, working PoC on JAM in alistair-singh/polkadot-sdk#2.
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
All reactions