On this page
What backs USDRIF?
ROC uses RIF and DOC collateral in coordinated buckets. Both support one USDRIF supply. DOC is itself a stablecoin issued by Money On Chain, so that bucket introduces exposure to its functioning and backing. A bucket is a separate accounting compartment for one collateral asset.
Is USDRIF different depending on the collateral?
No. USDRIF is fungible across the buckets. You can request redemption into a supported collateral asset regardless of its issuance origin, but the selected bucket must have sufficient attributed USDRIF liabilities and satisfy operational rules.
Can I exchange DOC for USDRIF?
Yes. In Exchange, choose DOC as input and USDRIF as output to mint through the DOC bucket. Reverse the pair to redeem USDRIF for DOC. A near-1:1 reference quote is not a guarantee of a fixed net output after fees and execution.
What are RIFP and RIFPRO?
RIFP is the interface ticker for RIF Pro, called RIFPRO in the whitepaper. It represents residual value in the RIF bucket. It does not have USDRIF’s stability objective.
Why is minting USDRIF with RIF sometimes limited?
The RIF bucket needs sufficient collateral coverage. A simple mint may be restricted when its required buffer would be breached. Combined minting adds RIF while issuing USDRIF and RIFP together, subject to validation.
Can I always redeem RIFP?
A standalone redemption can be limited by coverage and system state. A combined redemption burns both RIFP and USDRIF for RIF, reducing stablecoin liabilities alongside collateral withdrawal. You need both input tokens in the required amounts; execution is still subject to limits.
Does “No limit” mean any operation will succeed?
No. Global and bucket-specific metrics have different scopes. Balance, allowances, available liabilities, coverage, volume controls, execution costs and operational state can still restrict a request. Check the live pair-specific quote.
What does an operation cost?
Check the displayed protocol fee and payment currency, plus network gas and applicable execution costs. MOC may be a fee payment option. A zero protocol fee does not mean a transaction is free. Approvals can require additional gas. Historical fee references and screenshot values should not be treated as current tariffs.
Why is my operation queued?
The protocol delays execution of supported operations through a queue. Confirmation of submission is different from completion. Check Last Operations and the execution transaction. Quotes can change, and a request can fail if its bounds or protocol conditions are no longer met.
Does using smart contracts remove all risk?
No. Collateral price changes, DOC peg risk, smart-contract failures, external service failures and adverse protocol states remain relevant. Residual tokens can absorb losses, including severe losses. The peg is a protocol objective supported by collateral and rules, not a guarantee of a market price or redemption under every condition.
What do I need to operate?
Connect a compatible wallet on Rootstock Mainnet (chain ID 30), with the tokens you will send and rBTC for gas and execution costs. In Exchange, choose the input/output pair and enter the amount. Check the quote, fees and Price Variation Tolerance. Approve the input token if requested, then confirm Exchange in your wallet and follow Last Operations until final execution.
What is an allowance?
It is the amount of an ERC-20 token that an authorized address (the spender), such as the protocol contract, can spend from your wallet. Review the spender and amount before confirming approval. Approval does not execute the exchange; submit the operation afterward. A combined redemption may require an allowance for each of its two input tokens.