Core Insights

  1. Airdrops are way to align incentives. Users get value in return of the value they create for a protocol.
  2. Sybil is one of the core issues in any airdrop or any kind of incentives program. Dishonest players can bot the system easily to draw maximum incentives. This leads to high inefficiencies in incentives structure where real user contributions are less incentivised then a professional incentive farmer.
  3. Projects are creating their own point system to create a more structured incentive program but these can be easily farmed. Some projects are trying to innovate on their incentive structure wanting more real users and real contributions to be incentivised more.
  4. Quest as a discovery mechanism is still there and will still be there. More discovery mechanisms will come with platforms like Farcaster, KOLs network directly picking up points program, etc.
  5. Post first airdrop of a project, project still has a treasury and most of the time they launch more seasons of their airdrop to continue the activity they got in their first airdrop.

Vision

Personal Data Autonomy, PDA, Infrastructure

Our vision is to create a Personal Data Autonomy Infrastructure that empowers users to own and control their digital identities and behaviours. This infrastructure will enable personalised incentives and experiences, optimised advertising, and secure, trustworthy interactions, fundamentally transforming user engagement and data utilisation.

By placing data autonomy and control in the hands of users, we aim to create a more equitable and efficient digital ecosystem where trust and authenticity are paramount, and where users are rightfully rewarded for their genuine contributions.

We can position this infra in 3 ways:

  1. Building the infra verticalised for incentive design use case
    1. Here the stakeholders will be dapps and users
  2. Building the infra verticalised for ad-tech use case
    1. Here the stakeholders will be dapps, users and players who own attention of users (social media platforms like Farcaster, KOLs, etc)
  3. Building the infra horizontally and let builders create different use cases on top
    1. Here the stakeholders will be data providers, users and developers/builders