Description:

Lit Actions + PKPs + web3 storage can be a replacement for a traditional web2 backend. Imagine a web3 Twitter clone that stores the data on Ceramic. You could create a PKP that owns a Ceramic stream, and then grant access to sign with that PKP to a group of Lit Actions for things like createPost() and likePost(). Your Lit Actions can work just like a web2 backend, with business logic to ensure that only correct data is written to your Ceramic Stream. For example, the likePost() function could check that a user has not already liked a post, and only write the like to the stream if they have not already liked it. Read more about Lit Actions and PKPs here.

Get started with PKP-controlled Ceramic streams.

Why?

Social apps like Twitter and Instagram make millions of dollars off of the monetization user data, raising questions over privacy and security. The data contained within these apps also suffers from a severe lack of portability, making it difficult or impossible to transfer your information between providers.

At Lit, we are striving to build a Web owned by its users. We believe in providing individuals with tools that give them full control over their digital identity.

What will this tool enable?

This SDK should provide developers with a foundation for building web3-native social applications on top of Lit and Ceramic.

Implementation Guidelines:

Get started with PKPs here.

Lit x Ceramic integration.

Working with the Lit JavaScript SDK.