dApp onboarding patterns (comparing to web2 precedent)

From another thread:

I find this problem especially interesting in generalized context of blockchain adoption. Web2 apps will give free access/trials/credits to get users hooked. In blockchain that model is difficult because transactions cost real money and are permanent. Web3 trials get attacked by bots in attempts to syphon funds.

One approach: the funds never exist in the users wallet, instead the platform covers costs at the time of contract calls. Downside is that it’s centralized. It can still be attacked even if the attacker doesn’t make gains, the company gets hurt/drained by subsidizing spam content. Need to study DeFi loans to see if this has been tackled.

This is something @ross and I have spoken about a bit, would be interesting to hear if any further insights have been gleaned from his growth hacking adventures.

1 Like

A common answer for a broad range of Web3 applications is difficult, but for NFTs, if the artist provides a link to the media (IPFS, not sure how to do this for ArWeave, cause it also cost something…) the first NFT can be minted for his from the store owner.

As a more general solution: if the onboarding candidate provides something valuable to show his/her interest (link to a post in social media, where he promotes the service; prove of holding some social tokens), only in that case he is funded.

In case of social tokens holding, recently the term “merit” is pretty popular: how much and for how long the tokens are hold. This approach will benefit not only “whales” (holders of a big amount of tokens), but also loyal users (holding/staking a small amount but for a long period).