Skip to content

Latest commit

 

History

History
79 lines (55 loc) · 4.19 KB

File metadata and controls

79 lines (55 loc) · 4.19 KB
Error in user YAML: (<unknown>): mapping values are not allowed in this context at line 4 column 76
---
cip: 147
title: Swap Stream
author: Aaron Goldman (@aarongoldman), Mohsin Zaidi (@smrz2001)
discussions-to: <URL to a topic under the CIP category on the Ceramic forum: https://forum.ceramic.network/c/cips>
status: Draft
category: <Core | Networking | Interface | RFC | Meta>
created: 2023-08-21
edited: 2023-08-23
requires: <EIP number(s)>
replaces: <EIP number(s)>
---

Simple Summary

A new stream type where the stream state corresponds to the latest event.

Abstract

A Swap Stream enables you to replace the entire content of a stream. This is different from existing Ceramic streams, which consist of a sequence of PATCH operations that must all be considered in order to determine the state of the stream.

Motivation

When dealing with a Patch Stream, aggregating the stream state requires following events back to the Init Event. A Swap Stream SWAP operation allows a Ceramic node to ignore previous data in the stream, and a STOMP operation allows the node to ignore previous headers and data. This removes the need to constantly follow events back to the Init Event.

Specification

Specification goes here.

Rationale

Rationale goes here.

Backwards Compatibility

Backwards compatibility goes here.

Implementation

Implementation goes here.

Security Considerations

Security considerations go here.

Copyright

Copyright and related rights waived via CC0.