Quote by @stani • Hey
LIP-5 created by @lens/zkjew to enable Lens to become permissionless. Discuss if Lens should become open for all. If there is enough support, the core team
Comments
- I guess this will be the place this LIP gets most attention :-) so maybe we should discuss here. (If the discussion is supposed to take place on github maybe someone can eli5 how lens users can join the discussion on github.
I've commented my thoughts regarding opening @lens/lens on an earlier post by @lens/stani ... would 🤍 to link it but after scrolling 15 minutes through my feed I gave up. A google like search feature would be amazing ;-). Is it required to onboard new users? probably not.
I think I have basically one (and a half) concern(s) regarding lens going permissionless and that's
(1) **spam protection** x (onboarding) **user experience**.
(.5) missing stickiness / pmf. (how to prevent growth = churn).
I guess some barrier of entry is required to avoid spam at scale. Rn the barrier of entry is getting an address allowlisted or 13 USD (current price of a lens handle on opensea). Both doesn't sound crazy to me but it looks like that it's a (the ?) reason for devs not to build on lens. Which is a major issue if true, imo.
So the main question we should find a solution for is imo: `how to create a barrier of entry that's spam protecting AND perceived negligible by devs (and users)`?
Imo lens becoming permissionless should come with an "**onboarding program**" helping new users to get an overview of the ecosystem and first steps to have fun and find frens on lens.
why? According to lenscan, lens had approx 3.5k DAU in average over the last 3 months vs 134 371 minted lens handles (!).
An onboarding program alone won't be the solution, but imo it's worth trying. (I'm happy to join the discussion how this program could look like and to look into the data from a churn pov in detail.)
`the upside` :-) I hope lens becoming permissionless helps devs to find and onboard niches easier, they can build unique UX for. **Solving irl problems and generating irl value**.
- @lens/punkess @lens/ryanfox @lens/iamyakuza @lens/0xzelda
- @lens/augustuscaesar @lens/jamesfinnerty @lens/chaoticmonk
- Full support for the LIP. The suggested staged opening makes total sense.
- Lets open it up!
- With fury, the official position of @lens/wav3s team is:
🏄🏄🏄
- I totally agree! I’m all for this Zk ! 💯
- adding a cute cat for engagement ;-)
- Support this major LIP
- https://hey.xyz/posts/0x2a6b-0x09
- This is pretty good in my opinion, but stani why should we discuss this anywhere else?
- I fully agree.
We need more life in the garden and more bros&sis 🍻🍻
- Agree for open and permissionless lens
- I’m not the most up to date on how I can comment on this LIP(didn’t see an option on GitHub), but just wanted to say that I would be fully in favor of this. I’ve seen a ton of folks who want to join Lens and think it would be a net positive for the community if Lens was permissionless. I also think it would make it easier to have composability across web3 social graphs(which would also be very cool).
- lets go permissionless @lens/stani
- Lens ecosystem is not ready to fully open up, but there's nowhere to hide, because the race is on. Going fully permissionless is too big of a bite for now, so the moderately paced (but not too slow) open-up is our best bet.
We must figure out few things:
➖ The right pace for opening up so apps have time to react and core team can measure what’s happening and adjust if needed.
➖ KPIs to measure success.
➖ List of what needs to be done for readiness.
The pace part is mostly the scope of this LIP and the remaining 2 items are about how to maximize success of the whole thing.
➡️ **The pace and whitelisting strategy (here’s a variant of what’s in the LIP):**
➖ Anybody can mint a handle + profile for ~$ 20. The most motivated ppl will come. It works for Farcaster.
➖ Whitelist all Farcaster users
➖ Whitelist a portion of the waitlist at a time (50k seems ok, but depends how big other invite items are)
➖ Whitelist wallets with sufficient funds and livelihood on Mainnet and L2, certain NFT holders etc.
➖ Whitelist Crypto Twitter users with engagement metrics above a certain engagement threshold
➖ Give each new user some invites based on their prominence (e.g.: waitlist and buyers - 0 invites, Farcaster - 3 invites, Crypto OGs - 10 invites, etc. There must be a way to engineer this smartly)
The above can be done in batches. Item lines can be fine grained with more detail. Let’s discuss sensible numbers.
➡️ **KPIs:**
➖ Number of sign ups
➖ Engagement curve of new users
➖ Churn rate of new users (on top of that, we ideally want to know why people are leaving, so we can react, but that’s always the hard part)
➡️ **Preparation:**
➖ Onboarding process / wizard. Invite/find your friends from Twitter and Farcaster, get recommendations on who to follow, what to use etc.
➖ Anti spam measures
➖ App quality baseline (to minimize churn). Ensure that key apps are stable and that the lingering bugs are fixed and that missing rudimentary features are added. Provide resources if needed.
Your thoughts are welcome 🙏.
- 100% permissionless. This will open the doors for social logins as well. Imagine I'm using my email ID to create an account (smart contract account) and then minting my lens handle using this account. Now, I can use my email address to access the account. This is what every Web2 user is looking for.
- in my opinion you could better Give something for loyalty users before going to public