# R2: Interchain Incentivisation

{% hint style="success" %}
**TL:DR;**

R2 allows developers to connect their DApp on any chain to an unified incentivisation program to gain access to a vast userbase and bootstrap their application growth with ability to fine-tune marketing campaigns.
{% endhint %}

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.***

{% hint style="warning" %}
Fragmented Attention limits opportunities for on-chain projects to gain users and build traction.
{% endhint %}

## 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.<br>

#### R2 core components:

* Omni-chain Identity Beacon&#x20;
* 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!***

{% hint style="success" %}
**Omni-Chain Identity Beacon -** is an ultimate solution for anti-sibyl checks, airdrop-bot  farming protection. Web3 transparency is finally accessible for everyone without compromising privacy and security.
{% endhint %}

#### On-Chain & Off-Chain SDK

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

{% hint style="info" %}
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.<br>
{% endhint %}

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

<table><thead><tr><th width="137"></th><th width="250" align="center">OnChain SDK</th><th align="center">Off-Chain SDK</th></tr></thead><tbody><tr><td><strong>Integration</strong></td><td align="center">Requires contract modification</td><td align="center">Can be applied to existing contracts</td></tr><tr><td><strong>Cost</strong></td><td align="center">Free</td><td align="center">Per transaction pricing</td></tr><tr><td></td><td align="center"></td><td align="center"></td></tr></tbody></table>

To learn more on how to integrate with R2, navigate to [integration guide](/roketo-docs/infrastracture/r2-interchain-incentivisation/r2-integration-guide.md)

{% hint style="success" %}
Business-aware indexing allows developers to setup fine-tuned rewarding inside of a R2 and serves as a automatic KYC process without exposing any personal or off-chain data.
{% endhint %}

***

**Loyalty Points Platform**

All of the indexed actions and activity data is regularly imprinted into [Omni-Chain Identity Beacon](#omni-chain-identity-beacon) of the account on R3 chain.\
DApps can opt-in to enable cash-backs for certain actions in $ROVE[^1] tokens or, on the other hand offer products for the $ROVE inside of the **Loyalty Points Platform** or directly in the app.

{% hint style="info" %}
$ROVE token is omni-chain by design. User can freely transfer it across EVM chains to be used where user finds it most convenient.&#x20;
{% endhint %}

&#x20;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`

{% hint style="success" %}
`RewardSDK`  - allows reward allocation for both Web3 & Web2 applications, serving as a plug\&play API to distribute rewards for any business, with zero integration costs.
{% endhint %}

[^1]: ROVE- is a unified loyalty program tokens


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://read.roke.to/roketo-docs/infrastracture/r2-interchain-incentivisation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
