[LIP-8]: Momoka Open Action

[h4x3rotab]

Abstract

This LIP introduces a method for enabling Open Actions on off-chain Momoka publications. It details the integration of an oracle-based attestation system to fetch, verify, and utilize off-chain Momoka data for on-chain transactions, thereby addressing the challenge of immediate data availability required by Open Actions. The proposal also outlines the necessary smart contract modifications, including new functions and an encoded publication ID system, to facilitate seamless interaction between on-chain and off-chain components.

Motivation

In the current Lens Protocol ecosystem, an essential feature known as "Open Actions" allows Web3 applications to interact with and extend the functionality of on-chain publications. However, this capability is not yet available for "Momoka publications," which are stored off-chain on a data storage solution like Arweave. This limits the potential of Lens Protocol to scale and integrate more deeply with Web3 applications.

Momoka serves as a scaling solution capable of handling higher transaction throughputs than platforms like Twitter while maintaining cost-effectiveness. The integration of Open Actions with Momoka publications is therefore critical for enabling mass adoption and fostering innovation within the Web3 space.

The challenge lies in bringing off-chain Momoka data onto the blockchain in real-time, as required by Open Actions. Traditional oracles, which are off-chain services that fetch external data for smart contracts, introduce block latency that is incompatible with the atomicity needed for Open Actions. To address this, this proposal presents an innovative oracle-based attestation designed to utilize off-chain Momoka data for on-chain transactions without the typical delays.

By implementing this solution, it aims to overcome the barriers to Open Action availability for Momoka publications, thereby unlocking new possibilities for the Lens Protocol and its users.

Specification

To learn more details, please refer to the markdown file in the PR.

[height]

Link Height tasks by mentioning a task ID in the pull request title or commit messages, or description and comments with the keyword link (e.g. "Link T-123").

💡Tip: You can also use "Close T-X" to automatically close a task when the pull request is merged.

[datArtist-io]

Interesting!

[defispartan]

This is an interesting proposal.

@h4x3rotab What do you see as the main benefit of enabling Momoka to execute open actions compared to using act with signature or a delegated executor?

[h4x3rotab]

This is an interesting proposal.

@h4x3rotab What do you see as the main benefit of enabling Momoka to execute open actions compared to using act with signature or a delegated executor?

The significant difference is that, currently it's not supported to add Open Action to any Momoka publication. Both "act with signature" and "delegated executor" supports only on-chain publication. In the future, it's likely 99% of the publication will be on Momoka as it's much cheaper and has higher throughputs. So adding Open Action to Momoka publications is necessary.