R2: Interchain Incentivisation

Web3 space is actively fighting against fragmented liquidity: bridges, cross-chain protocols, interoperability, shared DEX pools. Having this tooling enables projects to choose chains based on available infrastructure and suiting the use-case, instead of running for TVL.

Every chain is interested in keeping users inside of its own ecosystem, while serving a good value for the chain, it is harmful for applications. User base becomes scattered and locked inside of the protocol - there is little to no exposure to others chain applications. This is called Fragmented Attention.

Introducing R2 - Roketo Interchain Incentivisation

As a meta-chain protocol our infrastructure allows to build chain-interconnected applications on a protocol level. Let's break R2 into it's component to dive deeper in how it enables growth for the whole Web3 ecosystem.

R2 core components:

  • Omni-chain Identity Beacon

  • On-Chain & Off-Chain DApp SDK

  • Loyalty Points Platform

That's a lot. Let's break those one-by-one.

Omni-Chain Identity Beacon

R2 Collects transaction data across all chains business-wise. This stream of data is piped into processor units. Processors compress that data to be reflected in Omni-Chain Identity Beacon.

Omni-Chain Identity Beacon - is an on-chain identifier, accessible directly from smart contracts calls and off-chain API calls. It contains a scored breakdown of an account activity to reflect its authenticity, activity interests and gives optional methods for a deeper verification. It's auto-generated and is free of charge for any user. Important feature of the R2 Beacon is that it contests current web3 idea of "forever imprinted". Beacon degrades over time, if no new activity is present. This approach allows it to reflect actual state of an account instead of historical and to be on-par with web3 newcomers. No more gatekeeping!

On-Chain & Off-Chain SDK

While R2 will by default track all transactional data, it gives higher priority to actions which are business-aware.

What is a business-aware action? Suppose there is a contract deployed at 0x9999..999 and we see a transaction which calls method mint . We will see a value attached of 0.1 ETH and some internal transfers. But that's it. We are not business-aware about consequences of that action. The same action will be read differently if we are business-aware of it's value: User bought a music streaming subscription in Spotify for 1 year

Now R2 is able to update the beacon with business-aware information.

To enable this type of messaging contract can be registered in R2 registry with certain tags, categories and a list of available actions.

OnChain SDK
Off-Chain SDK

Integration

Requires contract modification

Can be applied to existing contracts

Cost

Free

Per transaction pricing

To learn more on how to integrate with R2, navigate to integration guide


Loyalty Points Platform

All of the indexed actions and activity data is regularly imprinted into Omni-Chain Identity Beacon of the account on R3 chain. DApps can opt-in to enable cash-backs for certain actions in $ tokens or, on the other hand offer products for the $ROVE inside of the Loyalty Points Platform or directly in the app.

$ROVE token is omni-chain by design. User can freely transfer it across EVM chains to be used where user finds it most convenient.

R2 has multiple ways of distributing $ROVE tokens to end-users including:

  • Daily allocated rewards funded by Roketo protocol itself

  • As on-chain reward from actions invoked via R2Reward.sol interface

  • As off-chain reward applied from application pool via RewardSDK

Last updated