use w3clock

[jchris]

Technical Plan: Cloud-Based Clock Event Broadcasting

This plan will outline the creation of a proof-of-concept application that leverages the w3clock service to store and manage prolly diffs, effectively broadcasting clock events throughout a cloud architecture. The app will be based on a publish-subscribe model for User-Controlled Access Networks (UCAN) invocation, ensuring secure, efficient, and distributed system updates.

General Model:

• Publish-Subscribe System for UCAN Invocation: We will use a publish-subscribe system to handle UCAN invocations.
  • Cryptographically Secure Update Function: We will implement an update function that securely directs all system actors to do their part of the work.
  • Filter Function on Stream: We will add a filter function on the stream to manage data flow.
  • Batch Operations: We will enable batch operations where the full operation will be executed by the client.
  • Diff Data: The client will send diff data for the operation to a remote location. The client will then update its latest reference with this and any other data. We will also incorporate a function to reject outdated updates from the queue.
  • State Updates: State updates will include the previous state. We will design a mutex batch update mechanism that takes previous blocks and uses them as source input for the next mutex batch update. These updates will be tracked as epochs in w3clock.

Proof-of-Concept App:

Step 1: Identify or Develop an App that Uses w3clock: The first step is to identify an existing application that uses the w3clock service, or alternatively, to develop a simple, new application that does. This application will serve as the basis for our proof-of-concept.

Step 2: Integration with w3clock Service: Once we have the application, we will integrate it with the w3clock service. We will focus on ensuring that the application can successfully store prolly diffs in the w3clock service.

Step 3: Testing: We will rigorously test the application to ensure that it accurately and effectively broadcasts clock events throughout the cloud architecture, according to the model outlined above.

This plan provides a practical and stepwise approach to developing the proof-of-concept application and integrating it with the w3clock service. This initial work lays the groundwork for more extensive utilization of the clock event broadcasting system in the future.

[jchris]

The way keys work in w3clock might make sense to use as branch names in Fireproof databases.