NEAR Protocol is a smart contract capable, public Proof-of-Stake (PoS) blockchain that was conceptualized as a community-run cloud computing platform. Built by the NEAR Collective, NEAR was designed to host decentralized applications (dApps), and strives to compete with Ethereum and other leading smart contract-enabled blockchains like EOS and Polkadot. NEAR’s native token is also called NEAR, and is used to pay for transaction fees and storage. NEAR tokens can also be staked by token holders who participate in achieving network consensus as transaction validators.

NEAR Protocol is focused on creating a developer and user friendly platform. To accommodate this mission, NEAR has incorporated features like human-readable account names as opposed to only cryptographic wallet addresses, and the ability for new users to interact with dApps and smart contracts without requiring a wallet at all.

Projects building on NEAR include Mintbase, a non-fungible token (NFT) minting platform, and Flux, a protocol that allows developers to create markets based on assets, commodities, real-world events, and more.

data from : gemini

• Keypom is a zero-friction onboarding protocol and access key factory built on NEAR, which lowers the barrier to entry to Web3 for both new and existing users

• Keypom Drops : highly customisable, granular, affordable, Keypom Drops feature multiple use cases, including NFT ticketing, recurring payments, event analytics, backend servers, and token / NFT drops.

• Keypom Trial Accounts : lets users experience the value of a product and later convert the trial account into a full-blown wallet retaining their transactions and tokens

• Essentially, projects can use Keypom to let users experience the value of a specific product / dApp without creating a wallet, via the simple click of a link

data from : medium

Icebreak is a messaging application that allows rewarding replying. Write your message, attach your reward and share the conversation link.

data from : icebreak

We analyzed and tracked users' activity and interactions with Keypom by using the near.core.fact_actions_events_function_call table and, specifically, the receiver_id as v2.keypom.near, which is a Keypom. And we pull data from overtime and put it in terms of weekly for every chart created.

Next to the Icebreak , we used and tracked users' activity with this by using near.core.fact_actions_events table and identifying the receiver_id as icebreak.near to find out their activity with this app as well.

Lastly , we separated into four tabs that we have analyzed about this, of which the first three belong to Keypom and one tab is Icebreak as well.