Ceramic Network 

Ceramic works on top of  IPFS
It will be possible to make write operations in the background one or two minutes after the user was online in an app. 
On Ceramic, all data is published to the open web where it's easy to share streams between different organizations and applications without centralized servers or APIs, link multiple streams together to form a graph of relationships, or fork and remix existing streams into entirely new creations.  https://ceramic.network
On Ceramic, each piece of information is represented as an append-only log of commits, called a Stream. Each stream is a DAG stored in IPLD, with an immutable name called a StreamID, and a verifiable state called a StreamState. Streams are similar in concept to Git trees, and each stream can be thought of as its own blockchain, ledger, or event log.  https://blog.ceramic.network/what-is-ceramic
Dazuck on discord (28/12/2021): yep, as Spencer said long-term the network will be self-sustaining with a token. We'll be sharing more on that design in the new year. Until then, we're in no danger of going away. We actually raised another $3M in 2020 that we never announced, and much more than that since that we'll announce soon. So in terms of platform risk: core team is funded for 3+ years, all code is permissively open source, and the goal is to begin moving governance, operations, contributions and ownership of the network to the community ASAP (progressively) 
Some trust in a remote node: Stream processing and state validation happens on a remote node which the JS HTTP Client trusts. However, it is important to note that user's keys always live client-side and all updates are signed on the JS HTTP Client and then sent to the HTTP endpoint for processing.  https://developers.ceramic.network/build/javascrip...
user's keys always live client-side and all updates are signed on the JS HTTP Client and then sent to the HTTP endpoint for processing.  https://developers.ceramic.network/build/javascrip...
It's slow: 
it still takes several seconds to update data. Even with the most updated version of go-ipfs, it still takes ~2 seconds to put new data and query data. In a social app with more than tens of thousands of users, it is very unlikely for users to stand more than one-second response time. — Feb 2022,  https://mirror.xyz/0x2f3b5b6d852Fb097Df4d119728785...
Notes that link here:
Please sign up or log in to add comments and/or write your own notes and articles