OpenDev - 15 September 2026, 14:00 UTC (Agenda)

[jessechejieh]

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

Agenda. Fourth call of the hosting pilot. Speakers below are confirmed, and the agenda is close to full, so anything added now may be held over to the next call.

• 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 10 September — 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: Fellowship salary — what replaces the current structure
Speaker: Bill, Web3 Foundation
Why it matters: Referendum 1940 asked for 4,800,000 DOT converted to HOLLAR over twelve months from October 2026, against a projected twelve-month salary need of $3,525,000. Referendum 1941 cancelled it at 99.2% aye, on the grounds that multiple Fellows had concluded the current salary structuring is not aligned with Polkadot's long-term success. The account is running down with no replacement agreed. The Web3 Foundation remains supportive but wants substantive changes to the payment structure.

Topic: Individuality — how proof-of-personhood lands in the Fellowship's runtimes
Speaker: George Pisaltu
Why it matters: individuality-community is now public. It is the Individuality SDK, described as an in-development upgrade of the People chain plus integration pallets that let other chains interoperate with it, and it carries 25 pallets spanning personhood registration and attestation, the economics layer, the game and its airdrops, and the XCM plumbing that ships ring roots to consuming chains, with reference runtimes for both sides on Paseo.

Topic: JAM: Parachain Service Design
Speaker: Bastian Köcher
Why it matters: the design that gets parachains running on JAM, now up as polkadot-sdk#11883. Writing a Quint formal specification alongside the written spec surfaced a run of corner cases and clarified what the system requires, which Bastian reported at the close of the 18 August call with no time to go into it.

Security

Security-relevant items the room should know about. Comment to add.
Format: Item — [link] · what it means for us

RFCs

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

Snowbridge Circuit Breaker — Clara van Staden · RFCs#167

The proactive half of the pair. Where RFC 166 reacts once an exploit is spotted, this adds per-asset velocity caps on the Ethereum Gateway: net flow per asset is tracked over a rolling window, an asset exceeding its cap is locked, and the lockdown lifts when the window passes. Caps are set per asset by governance. Clara deferred this on 18 August as the more complicated of the two, to be taken on its own day.

Speaker: Clara van Staden

On demand as core scheduling — Sergej Sakac · RFCs#175

Carried from 18 August, where it had been open for a day and nobody had read it yet. It moves on-demand coretime sales off the relay chain in line with RFC-32 (Minimal Relay): orders are placed, priced and paid on the Coretime chain, the broker commits individual blocks as one-shot core assignments, and the relay chain's on_demand pallet is removed. Sergej is gathering feedback ahead of the call. His question of whether the approach adapts cleanly once JAM lands is still open, so it pairs with the parachain service design above.

Speaker: Sergej Sakac

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