Versioned Walrus

This project involves the creation of a library built on top of WalrusDB, designed to provide robust version control functionality for document storage. The system utilizes WalrusDB as the underlying storage solution, while metadata is stored on the client side to track different versions of documents.

Key Features: WalrusDB-Based Storage: The system uses WalrusDB to store contract files, ensuring data immutability and decentralized storage for long-term persistence.

Version Control:

Supports uploading different versions of the same contract, allowing agents to easily manage updates over time. Previous versions of documents are tracked, allowing for easy navigation and auditability of historical changes. Version control is handled at the metadata level, making it possible to skip uploading files that already exist to avoid redundancy. When a new version of a document is uploaded, the system automatically creates and links it as a new version, tracking the relationship between versions. Contract Management:

Agents can upload contracts onto WalrusDB, leveraging the version control system to manage multiple versions of a contract for clients. The system allows agents and clients to sign a specific version of a document. Upon signing, a signature file is generated, which logs the action in the format: [addr] has signed [BlobID], providing cryptographic proof that a specific version has been signed by a particular party. Signing Workflow:

Agents or clients can sign individual versions of documents, with the system automatically generating a signature file. This file contains details such as the signer’s address and the BlobID of the signed document, ensuring traceability and proof of signature. Use Cases: Contract Versioning: An agent can upload multiple versions of the same contract as needed, allowing for smooth management of changes over time. The system tracks all previous versions, ensuring complete transparency and traceability.

Document Signing: Both agents and clients can sign specific versions of documents. The system generates signature metadata files that certify the signing event and provide an audit trail.