# What is Roup
Roup is the key channel for rolling up BRC20 assets to Bitcoin Layer2 trading, initiated by the community and with revenues fed back to the community.
# Cutting-edge Technology
Reducing BRC20 transaction gas fees by a factor of 100
It possesses cutting-edge technology that sets it apart from any centralized BRC20 bridge using multi-signature technology. That's because Roup adopts MAP Protocol's BRC201 standard, which is a secure cross-chain solution that inscribe the bridging details on top of bitcoin and can be traced thoroughly. Rolling up BRC20 tokens to MAP Protocol's second layer transactions will save users more than 100 times the gas fee costs.
# Fair Token Distribution
Fairly launched through inscription
Before Roup, projects that adopted a fair launch of BRC20 tokens were basically meme coins with few, if any, DApps. Or they were issued on ERC20, with development teams and VCs getting a large number of unfair tokens first. However, Rolluper is one of the few fairly launched BRC20 tokens with a use case. ROUP is Rolluper's BRC20 platform token, with a total issuance of 2.1 billion tokens, and each engraving is limited to 10,000 tokens. The BRC20 community is a community-built ecosystem, and the vast member base is key to the success of a token and a project. In a sense, the larger the scale of engraving, the more success each member of the community will have.
# Dazzling BRC20 Tokenomics
Revenue will buy back tokens for destruction until deflation to the last token
Roup is a product in short supply in the market, and the BRC20 community suffers from high gas fees. The fee revenue generated by Roup will be returned to the community in its entirety, adhering to the principle that Roup is owned by everyone. The return methods include buy-back and destruction, among others, with specific ratios to be voted on by all token-holding users after the ROUP inscription is complete. It should be noted, however, that the developer community, as the initial initiators and developers of the project, need to receive at least a 30% share of the fee revenue to motivate them to work better for the community.
# How does Roup work
The Roup mainly utilizes the BRC201 cross-chain protocol developed by Map Protocol to assist BRC20 assets in achieving traceable cross-chain capabilities, and those assets can also be implemented and expanded with new tokennomies on the MAPO L2 playground.
# BRC201
**Introduction**
BRC-201 proposes **an extension protocol to the BRC-20 standard**. It is aimed to be backward compatible with BRC-20, to improve scalability, especially to bridge BRC-20 tokens to chains with smart contract support, such as Ethereum, BNB Chain, Near, etc.
**Ordinals and BRC-20**
[Ordinal theory](https://docs.ordinals.com/) imbues satoshis with numismatic value, allowing them to be collected and traded as curios. Individual satoshis can be inscribed with arbitrary content, creating unique Bitcoin-native digital artifacts that can be held in Bitcoin wallets and transferred using Bitcoin transactions.
[BRC-20](https://domo-2.gitbook.io/brc-20-experiment/) is experimental token standard by Domo. Tokens can be deployed, minted, and transferred using Ordinal inscriptions.
**Definition**
BRC-201 is an extension of the BRC-20 token standard that enhances the Transfer operation. This extension remains compatible with the BRC-20 protocol.
BRC-20 token transfer looks like this:
```
{
"p": "brc-20",
"op": "transfer",
"tick": "ordi",
"amt": "100"
}
```
BRC-201 extend operation looks like this:
```markdown
{
"p": "brc-20",
"op": "transfer",
"tick": "ordi",
"amt": "100",
"chain": "eth",
"ext": "bridge-out/in",
"ref": "address/txhash"
}
```
BRC-201 introduces three additional fields: "chain", "ext", and "ref".
If an indexer does not support the BRC-201 protocol, the transaction will be treated as a regular transfer operation.
However, an enhanced indexer that supports BRC-201 can parse additional extension operations.
Currently, the BRC-201 specification defines "Bridge In" and "Bridge Out" as extension operations.
# Tech Workflow
From Bitcoin to Mapo L2
1. Users will initiate a new ***BRC201 inscription***. They will need to input parameters including the ***destination chain, destination address, token ticker, token amount*** and ***fee rate***.
2. After a new BRC201 gets inscribed, it needs to be transferred to our ***ROUP Vault Address*** in order to be rolled up
3. After the confirmation of the transfer, the ***Token Asset Contract*** on the MAPO L2 will mint the corresponding amount of tokens to user specified address
From Mapo L2 to Bitcoin
4. Users will initiate the cross-chain transaction by specifying ***destination chain, destination address, token ticker and token amount***.
5. The ***Token Asset Contract*** will burn users token at the MAPO L2
6. The cross-chain transaction will gets verfied
7. A new BRC201 will be inscribed and transferred to user specified bitcoin address
# User Workflow
### Select Chain
* Select the destination chain and source chain (currently only Bitcoin and Mapo L2 are supported)
### Select Token
* Currently only whitelisted token will be able to roll up using Roup
### Inscribe a new BRC201
* Click on '**+ Inscribe New BRC201'**
* Fetch the destination chain address by clicking '**connect wallet**' button and the address will be filled in automatically
* input **token amount** that will be transferred
* select a proper **fee rate**
* confirm the **inscribe transaction**
{% hint style="warning" %}
the inscribed BRC201 will be first shown in the '**BRC201 Inscription**' tab within the **History Panel** and it will then be moved to the '**Available BRC201 Rollup'** list once it is confirmed on chain.
{% endhint %}
### BRC201 Inscribtion History and Status check
* BRC201 Inscription history and details can be checked in '**BRC201 Inscription**' tab within the **History Panel.**
* '**Add to wallet**' button can add the **selected token** on the **destination chain** into metamask automatically.
* **Unconfirmed** means the token is still in progress of inscription; **Confirmed** means the token is successfully inscribed and transferred to the original address.
### Complete the roll-up transfer
* Select an inscribed BRC201 record in the '**Available BRC201 Rollup'** list.
* Verify the **BRC201 rollup** details.
* '**Add to wallet**' button can add the **selected token** on the **destination chain** into metamask automatically.
* Select an appropriate **fee rate.**
* confirm the **rollup transaction.**
{% hint style="info" %}
After a transaction is successfully sent, it will disappear from the '**Available BRC201 Rollup**' list and it will appear in the **History Panel**.
{% endhint %}
#### BRC201 Rollup History and Status check
* Rollup history and details can be checked in '**BRC201 Rollup**' tab within the **History Panel**
* **Unconfirmed** means the token is still in progress of rolling up; **Confirmed** means the token is successfully minted at the destination chain
# Deployed Contracts
| Contract Name | Contract Address |
| ------------- | ------------------------------------------ |
| Manager | 0xD3Be0DC4dbfAA84255d92252d996589419EB415b |
| ROUP(brc-20) | 0x3e76deF74d4187B5a01aBE4E011Bd94d9f057d94 |
| MAPO (brc-20) | 0x3b7fC78434B00586a2ad7c3DAd821e1b02fcA66f |
| STST (brc-20) | 0xb84e5EF60f73ed0da684bC3C5d7962f3839ae619 |
| ORDI (brc-20) | 0xB719e46B6eB5b23E2759526CdE24589d87097733 |
| RATS (brc-20) | 0xcAF17cDdb80F72484e5A279921b98a0a9A2391ee |
| MMSS (brc-20) | 0x8fDFa5E7b01a344710d7F73818eeF0234108F6a0 |
| CSAS (brc-20) | 0x640a4C0AaA4870BaDE2F646B7Da87b3D53819C4f |
| BTCS (brc-20) | 0x0e2cA3e003f3c73C8cC18ec244d46DB9d4c4DCEB |
| 3518 (brc-20) | 0xC605D440954239Fb72dd37908c444BC974817D90 |
# Already inscribed BRC-20 Transfer
### Why BRC-20 Transfer can't be used in ROUP?
Since Roup is using **BRC-201** as the underlying protocol for helping users to rollup their BRC-20 assets, it will require users to inscribe a **BRC-201** before starting the process. Hence, a normal inscribed **BRC-20 Transfer** will not be able to use in ROUP and users need to make the **BRC-20 Transfer back** to **BRC-20** before starting the rollup process.
###
### How to make inscribed BRC-20 Transfer back to normal BRC-20?
1. open your wallet (UNISAT, OKX)
2. Find the assets that contains i**nscribed BRC-20 Transfer**
3. Click on the **Transfer Button** in the wallet and select the **BRC-20 Transfer** you want to use
4. Click on **Next** and enter your **own wallet address** in **Receiver** box
5. Select fee rate and confirm the transaction
6. Wait till the transaction is confirmed on-chain and your BRC-20 assets will be back to normal.
