Post by @watchereth • Hey

Ok so just tried to do an LIP had everything written out and once I submitted I got an auth error 🥲 Feeling a bit to lazy to write everything again but I

Stats

Comments

i like it
@lens/watchereth put the above through chat gpt and submit it. Share an old LIP and ask it to structure it in that manner 😁
Ah bummer that the LIP didnt publish. Weird bug.
On the proposal, I personally agree, I think the Lens community would benefit from having unified tools and frameworks for cross-chain interactions. Here are my thoughts on both ideas you proposed and what I think the community could do to enable them: **1. Allow addresses to delegate calls from other chains** It is possible to trigger Lens transactions from other networks using bridges already, described in more detail in (2). However, I'm not aware of an implementation of this yet. Some ideas to make this idea more viable for users/developers: a. designating an official LensHub deployment or messaging bridge on another chain to execute transactions on behalf of users on Polygon b. delegated executor supports relaying transactions on this contract (a) to Polygon c. index transactions from contract (a) directly Even though your initial idea wasn't deploying Lens primitives to other chains (like LIP-15, LIP-20) I think these ideas are directly linked and should be discussed together because they involve the same underlying decisions: how to manage identity and access controls between chains, tradeoffs of relaying vs indexing, feature composability, trust assumptions. I think the best way to move this conversation forward is a discussion in the LIP repo "Lens Cross-Chain Framework" that can serve as a place for community members to discuss all of the different options and tradeoffs in detail. **2. Lens interactions through cross-chain bridges** Lens -> Any Chain interactions are already supported through smart contracts and delegated executors. Modules can embed any contract call, including cross-chain messaging. This means that a publication could embed an open action such as minting an NFT on another chain -> user executes by submitting a Lens act call on Polygon (can be sponsored) -> call is bridged and executed on another chain. The same also works in reverse. A call on another chain can bridge a transaction to Lens on Polygon, such as relaying a transactions with signed data (postWithSig, commentWithSign, etc.) or a bridge can execute directly if the profile (or protocol, idea 1a) approves the bridge as a delegated executor. On this topic, I think rather than an LIP, the best way for the community to coordinate is through examples and tutorials. There is already progress being made on contract and frontend examples for cross-chain modules (https://github.com/lens-protocol/verified-modules/blob/9e9cc10b6cf81a5cb393a423f5f246f9a90968d4/open-actions.json#L78) so expect some updates on this from me in the near future.
To submit an LIP pull request you'll need to go to the main repo (https://github.com/lens-protocol/LIPs) -> click "Fork" -> push changes to your fork repo -> open pull request back to main repo. These steps should definitely be added to the README, and ideally I think all proposals should start as a GitHub "Discussion" so it's easier to create and organize. I'm working on an LIP this week, so I'll plan to submit another for these housekeeping changes.
Hmm 🤔🧐