Lenscribe

The project builds a blogging platform on top of the Lens ecosystem, crucially differentiating from traditional blogging platforms in a number of key ways. Long form content generates 8x more page views, 3x more social shares and 9x more leads. Yet Lens is still dominated by short form. There’s also a huge open issue with age verification of content.

We combine a blogging platform on Lens, with PolygonID age verification for certain pieces of content that are otherwise freely available on the major content platforms, such as adult blog content. By setting an age query the user will simply need to scan with the PolygonID app and we will only need to receive a Y/N response using the ZK Proof. We also provide proof of humanity through WorldID, with only verified creators being able to receive tips. Tips to unverified creators will automatically be given to projects supporting education in countries with a lack of education. We know that verification on WorldID is not globally available yet on the Orb so therefore mobile verification will be accepted. This will drastically reduce the volume of spam content, and if there is still too much spam content we will increase the level so that all authors will need WorldID verification. Authors that are WorldID verified will also have their content rise to the top of the feed through our algorithms.

We will also leverage and build on the functionality within the Lens ecosystem that opens up many more features within this platform, and we plan to open up DMs and other creator set rewards based on the tip levels given by users. So for example, DMs will open up from reader to creator for tipping or subscribing to a certain level. Further functionality will also include a “share on…” function that will allow sharing across the Lens ecosystem with the share creating its own module (NFT) that will then earn a set % share of all future tips using that link, and shares that originate from their share, building upon ERC6551, although this needs further development study and research. Tips can also be set to either go to one or multiple wallets by writing multiple wallet addresses into the LensAPI, or, a writer can choose to give tips to one of a selection of charities that support basic education in underdeveloped countries.

By creating this platform, we also enable freedom of speech, but would like to move towards and explore community moderation in future where certain community members may get paid a percentage of tip and subscription revenues to jointly moderate content, although this of course opens up to centralised and subjective disadvantages.

Finally - we would aim to implement AI writing assistants to the web app, and launch an IOS / Android app which would be available for reading content, not creating.

We used the LensAPI to communicate with Lens, to sign in, and to get the top 20 published posts. For the writing and posting we used the LensAPI to post written content to Lens, that we would then as a next step implement the follower modules (not built this weekend.) . We used typescript, js, html for the build and the platform is a react app. At the moment you need to sign the transactions to post for example but in future we will setup dispatchers to make the experience smoother.

The blogging platform uses Next.js for the build. We followed the documentation from WorldID and the aid of several repos, and when we hit several barriers for implementation then we got help from other hackers to find solutions to problems we encountered. Approvals from users are stored on Firebase. A one-time query against the Lens NFT holder wallet address, this will verify simply that the wallet has demonstrated proof of humanity.

For the PolygonID implementation, we started to look at, but ran out of time, we will implement the verifier credentials behind the blocks of the 18+ content, requesting a Y/N response using ZK Proof to ensure the reader is 18+, before reading this content. This will then unlock the blocks for this content and allow its consumption.

We didn’t implement the code for co-creating content, revenue sharing, and tipping based on highlighting different sections of text as we spent the first 18 hrs trying to work out the Lens SDK which eventually we had to switch to doing manually via the LensAPI.