Re: [CfC] Call for Consensus: Storage TF resolutions from 2026-07-16 call

Hey Dmitri:

On the DIF side, Secure Data Storage working group is just on "hiatus", it was never disbanded or spun down, and all its work items were joint work items with CCG already, so all DIF asks is to be informed if work is spinning up again and what the meeting cadence is to advertise it to DIF members. Whether meetings are on DIF Zoom links or CCG jitsi links doesn't matter, as long as both [near-identical] IP policies are enforced, and some kind of minutes are published for passive participation and for reading people in who get involved later. EDV spec never hit v1 so shifting or expanding the targeted use-cases is fine as long as it's public-- CfC emails like these are enough for that.

Thanks,
__bf

---
bumblefudge
janitor [@Chain Agnostic Standards Alliance](https://github.com/chainagnostic/CASA)
contractable via [learningProof UG](https://learningproof.xyz)
mostly berlin-based

On Friday, July 17th, 2026 at 12:41 AM, Dmitri Zagidulin <dzagidulin@gmail.com> wrote:

> (Minutes from the first Capability-Based Storage Task Force can be found at: https://hedgedoc.socialweb.coop/C8Mx-uH7QdiGbcBxNRaGjg )
>
> This TF would like to adopt a "Call for Consensus" notification mechanism, to make explicit that we recognize that participation in sync task force calls is not available to everyone, and we only want to make binding decisions (resolutions) with input from members who could not attend.
>
> The following resolutions were passed on today's call, which starts the 7 day waiting period (giving members who couldn't object a chance to object or amend). (These are all fairly non-event items, but we want to start as we mean to go on, CfC wise.)
>
> 1. RESOLVED: Create a [task force] work item (CCG repo), Capability-Based Storage Use Cases document (covering usecases for all 3 specs).
>
> 2. RESOLVED: Create a [task force] work item using the [Wallet Attached Storage draft](https://w3c-ccg.github.io/wallet-attached-storage-spec/) as input document
>
> 3. RESOLVED: Adopt Encrypted Data Vaults spec as a [task force] work item, with consensus from DIF.