Tuesday, 30 June 2026 · 14:00 UTC
Host: Jesse Chejieh — @jessechejieh:matrix.org (Rank II)
Agenda thread: help-center#18
This was the first call of the hosting pilot. The conversation centred on RFC #171 — Asset-Based Storage Deposit Payments.
Security
Oliver Tale-Yazdi reported that the Security Working Group has been fuzzing runtime calls and XCM transfers to catch memory and invariant issues, and that AI-assisted auditing has proven effective enough at finding code issues that the group recommends doubling down on it. The group is also exploring an incident response plan, which Adrian is taking forward. Runtime disclosures continue to be tracked in security-findings (members-only).
Asset-Based Storage Deposit Payments
Pablo Dorado presented RFC #171, which would let users pay storage deposits in assets other than DOT, removing the requirement to acquire DOT before using the ecosystem. A proof of concept already exists on the Consideration trait (source): extensions set an asset ID for the deposit, and the asset is held directly rather than converted to DOT.
The discussion turned first to economics. Oliver Tale-Yazdi and Kian Paimani highlighted that a DOT deposit already functions as rent, since the depositor forgoes staking rewards while the deposit is locked, whereas a stable-asset deposit carries different economics. Kian supported the direction, noting that the rigid DOT-only deposit model is currently blocking the personhood initiative, but cautioned that the proposal should be treated as a mid-term solution and aligned with the broader flexible resource-management system George is working on. Josep M Sobrepere challenged the need for protocol-level changes, arguing that the runtime already supports paying fees in pooled assets and the problem might be solved with better tooling instead; Pablo answered that while an external solution is possible, the RFC collapses the deposit flow into a single step, a user-experience improvement. On implementation, the group established that consideration tickets are stored per-pallet, and that an aggregating pallet and ticket-update conveniences are both feasible within the existing structure.
The discussion produced two outcomes. The RFC’s direction needs further work to align with long-term resource management, which Pablo and George will coordinate. Independent of that, the group agreed that migrating pallets off hardcoded Currency/hold-mutate deposits onto Consideration is a necessary architectural step and should be prioritised.
Inductions & Promotions
This period brought multiple advancements across the ranks. To name a few: Josep M Sobrepere, who leads Polkadot-API (PAPI), received a fast promotion to Rank 2 (Evaluations#303); Alin Dima was promoted to Rank 3 (Evaluations#302); and Victor Oliva received a fast promotion to Rank 2 (Evaluations#304).
Calls for review
Pablo Dorado asked for eyes on polkadot-sdk#11109, which migrates pallet-treasury from Currency to Fungible, completes the deprecation of the legacy spend_local mechanism, and adds a fungible-based slashing handler. The work is a blocker for other pallet migrations, and is tested and ready for review.
Victor Oliva requested review of polkadot-sdk#11524: when a referendum fails today, the submission deposit remains stuck in storage with no mechanism for removal. The PR adds a slash_submission_deposit extrinsic to burn it.
Closing updates
Oliver Tale-Yazdi closed the call with two governance notes: the multi-asset bounty is now on-chain, allowing governance to create bounties denominated in assets other than DOT, and a referendum is open to change the primary salary asset.
This is the first call of the hosting pilot, and the format is being iterated. Tell us what to change in the feedback form. Next call: Tuesday, 21 July 2026 · agenda thread opens ~2 weeks out.