We have used lens protocol deeply in our application and same for infura for every api fetch.
We deployed on base and we actually use base as our main chain for any contract interaction. We believe base is the best choice for us, since we really need a fast layer2 supporting account abstraction. Our product will have many one to five dollar purchases, and we believe account abstraction will give users a much better experience, since users will not need to confirm every transaction.
We have built a social-fi app using lens. We support lens login, use lens profile and use lens posts to build a web3 Q&A platform. Our product allows a user to ask a question to a sensei by putting certain money up front and lock it in the smart contract. The sensei can verify that the money is in the smart contract and decide whether to answer or not. If answered, the sensei can withdraw the money and if not, the user can withdraw the money after 48hs. Furthermore, if another user observes this question being asked and answered, that user can pay simply one dollar to see the answer. We call this feature eavesdrop and the proceeds of the eavesdrop will be split btw the questioner and the answerer, an ask-to-earn product.
We have built a social-fi app using lens. We support lens login, use lens profile and use lens posts to build a web3 Q&A platform. We are in the process of supporting follow, mirror, and collect.
We r building a 100million product and potentially gaining over 10million users.
We have deployed to almost every chain that infura supports. We primarily use base as our main chain, but the contracts are deployed to every evm compatible chain.
We have integrated web3auth into our wallet connect page using Gelato, further boosting us to provider user with a better UX using account abtrasction.
We have supported USDC in our app and plan on using usdc as our primary payment method.
Deployed on scroll.
We are building a social-fi, NFT product that allows users to mint their favorite posts. Our product allows a user to ask a question to a sensei by putting certain money up front and lock it in the smart contract. The sensei can verify that the money is in the smart contract and decide whether to answer or not. If answered, the sensei can withdraw the money and if not, the user can withdraw the money after 48hs. Furthermore, if another user observes this question being asked and answered, that user can pay simply one dollar to see the answer. We call this feature eavesdrop and the proceeds of the eavesdrop will be split btw the questioner and the answerer, an ask-to-earn product.
We have deployed on scroll and have used lens everywhere in our social-fi app.
OpenAsk leverages the StandardBounties protocol to create a platform where people can send conditional payments upon fulfilment of a request by the receiver. The protocol supports payment in ETH and ERC20 tokens, so creators will also be able to receive payment in their personal token. The response is private by default but other users can also eavesdrop on the response by paying a $1 fee which is split between the asker and answerer evenly. Due to the nature of frequent transcations of low value, having low gas fees is a high priority. That's why we chose to deploy on the Base rollup, and also use Gelato's gasless wallet sdk to provide a seamless ux for non-crypto native people. Users are able to have gasless transactions at low cost. We have also integrated Lens profiles and posting on Lens so people can use their Lens profile instead of twitter profile and choose to post on Lens as well..
Our vision is to enable creators to have a plethora of ways they can earn revenue as well as co-create content with their community. In the future we can further integrate Lens to take advantage of other features such as token gating content. The StandardBounties protocol also supports all kinds of customisation like delegating a smart contract to approve responses, community contributions to a reward pool, and more.
We have also deployed the contract on Scroll :)