Liran Cohen LiranCohen

Proposal: DWN-to-DWN Sync and Multi-Party Record Delivery

Status

Draft — capturing research and design direction for future implementation.

Problem Statement

DWN synchronization today is entirely agent-initiated. The user's agent (running on their device) holds a local DWN and orchestrates bidirectional sync with each remote DWN listed in their DID document's #dwn service endpoint:

Keybase proof

I hereby claim:

I am lirancohen on github.
I am lirancohen (https://keybase.io/lirancohen) on keybase.
I have a public key ASB-irvvN7OBAMioXejWJwVY_TSq72Fip8kNXkY0ivCkvgo

To claim this, I am signing this object:

	{
	"schemaVersion": 1,
	"label": "CI",
	"message": "passing",
	"color": "3F8624",
	"labelColor": "2b2b2b",
	"style": "for-the-badge"
	}

	const { did, web5 } = await Web5.connect({
	didCreateOptions: {
	dwnEndpoints: ['https://dwn.gcda.xyz'] // User provides google's community DWN instance
	},
	registration: {
	onSuccess: () => {
	// Registration succeeded, set a local storage value to indicate the user is registered and registration does not need to occur again.
	},
	onFailure: (error) => {
	// Registration failed, display an error message to the user, and pass in the registration object again to retry next time the user connects.

	const { app } = require('electron');

	app.whenReady().then(() => {
	(async () => {
	const cek = crypto.getRandomValues(new Uint8Array(16));
	const cryptoKeyCek = await crypto.subtle.importKey(
	"raw",
	cek,
	{ name: "HMAC", hash: "SHA-256" },
	true,