Kari Protocol

Kari Protocol:

Direct-to-wallet advertising platform.

Problem:

Marketing in web3 is hard. Community-driven marketing is hard to scale to the next 100 million users. Targeted digital advertising has proven to be extremely effective in web2 spaces. There are so much useful data available publicly on-chain. We wanted to experiment with ways we can leverage these data in the advertising context.

What is Kari Protocol:

We are building a platform that allows web3 companies to advertise to specific customer groups based on their on-chain assets and activities.

How it works:

Web3 companies can create an advertising campaign with your content. You can then select and filter the audiences that you wanted to target, based on on-chain data (such as what assets users are holding or protocols that they have interacted with). You can also choose whether you want to attach financial incentives to reward users for watching the ads.

Users will then be able to visit our Kari DApps to consume the advertisement and claim the rewards. The performance statistics such as CTR and CPM would be available on the ads manager page.

Example use case:

Let's say if you are working on a new web3 gaming project, you might want to advertise directly to Axie or StepN users for a more direct reach. Send them advertising materials like your launch video, and maybe attach them with a special reward code for claiming free in-game items.

Market:

Digital ad is a $560B industry, it's only a matter of time for Web3 to catch on.

In addition to our own DApps, we aim to build more ways for ads to be delivered such as via API integrations (for email & messaging services) and integrating with web3 publishers (dashboards, wallets, DApps & metaverses)

Follow us on Twitter: https://twitter.com/KariProtocol

Overview:

• Smart Contract: we use Solidity and use Foundry as development environment.

• Backend data preparation: we get the list of each lending protocol by using the existing subgraph from The graph.

• Frontend: we use React framework with NextJS with Material UI (MUI)

• Wallet Integration: we use Metamask for the web browser and Wallet Connect for the use with a mobile wallet.

---

For the sponsor technologies, we use them as follows:

• Aave: Use as an example client for our demo showcases: targeting Defi users who haven't tried out Aave before

• Cronos: Deploy receiver contract on Cronos, allowing the user to claim ads incentives on Cronos

• ENS: Use as naming service for wallet address

• EPNS: We use them as a messaging infra between the sender (the ads manager) and the receiver (the Kari user Dapps). The sender can send any message to the specific wallet addresses or segments based on the user's on-chain data. The receiver can read the message if they are subscribed to the receiver channel.

• IPFS: For storing off-chain information like image attachments for our delivered contents

• Optimism: Deploy receiver contract on Optimism, allowing the user to claim ads incentives on Layer 2

• Polygon: Utilising EPNS on the Polygon chain, leveraging the advantage of low gas fee

• The Graph: We use the existing deployed subgraph to query data (e.g. list of wallets that interacted with specific smart contracts)

• XMTP: We use them as a p2p messaging infra for help desk support with our team. We can extend this use case for this tech like p2p messaging between wallet addresses that are in the same channel (Aave user, NFT holder, etc.)