CryptoReceh · Internal Infrastructure

Receh IDR (IDRR)

A blockchain-based stablecoin designed for internal use within the CryptoReceh ecosystem, combining a 1:1 IDR value reference with reserve-based backing and additional on-chain backing through RECEH and USDT.

Internal-use scope: IDRR is designed specifically for services, transactions, products, testing, settlement flows, and other activities operated within the CryptoReceh ecosystem. It is not intended for general use outside that ecosystem.
01 · Overview

What is IDRR?

Receh IDR (IDRR) is the internal stablecoin layer used by CryptoReceh to give selected blockchain activities a consistent fiat-denominated reference while keeping the asset fully represented on-chain.

1:1

1:1 IDR value reference

The target value of IDRR is pegged 1:1 to IDR. The reserve model is designed so that circulating IDRR corresponds to the amount of IDR reserves held or provided as backing.

▣

Reserve-backed supply

The circulating supply is tied to the real amount of IDR reserves allocated to support IDRR, creating a direct relationship between issued tokens and the underlying reserve position.

↗

Additional on-chain backing

In addition to the off-chain reserve model, IDRR is supported on-chain by RECEH and USDT, providing an additional layer of blockchain-native backing within the CryptoReceh infrastructure.

02 · Reserve Model

1:1 value reference and circulating supply

The core model is simple: the circulating supply of IDRR is intended to remain in direct proportion to the amount of IDR reserves allocated to back that supply.

1 IDRR=1 IDR value reference↔1 IDRR circulating↔1 IDR reserve backing
IDRReserveReal reserve backing IDRRCirculating SupplyOn-chain representation Value reference1 : 1IDRR ↔ IDRInternal CryptoReceh use
Conceptual model: reserve backing and circulating IDRR are maintained in a direct 1:1 relationship under the IDRR reserve policy.

Reserve side

The reserve side represents the actual IDR amount held or made available by CryptoReceh to support the circulating IDRR supply. The reserve is the off-chain component of the backing model.

Token side

The token side represents the same value on-chain. Because IDRR uses 6 decimals, the smallest on-chain unit is 0.000001 IDRR.

03 · On-chain Backing

Off-chain reserve + on-chain support

IDRR is not designed around a single layer of value support. Its model combines the IDR reserve relationship with blockchain-native assets held as additional backing within the CryptoReceh infrastructure.

IDR Reserve1:1 reserve relationship RECEH + USDTAdditional on-chain backing IDRRInternal value layer CryptoRecehProducts & services Receh DEX Client services Internal settlement
The diagram illustrates the intended architecture: IDR reserves provide the 1:1 value reference, while RECEH and USDT provide additional on-chain support within the CryptoReceh infrastructure.
Important distinction: RECEH and USDT are described here as additional on-chain backing within the CryptoReceh infrastructure. They do not replace the 1:1 IDR reserve relationship that defines the primary IDRR value reference.
04 · Internal Use Cases

Why IDRR exists inside CryptoReceh

IDRR provides a stable, blockchain-native reference for activities where CryptoReceh needs a token whose value is expressed against IDR without making IDRR a general-purpose external asset.

Use case A

Testing token pairs on Receh DEX

A CryptoReceh client wants to test a trading pair for a newly created token on Receh DEX. The client needs a comparison asset with a stable fiat-denominated reference. IDRR can serve as that internal reference token.

Client token→Receh DEX pair→IDRR reference
Use case B

Service reward → DANA balance

A CryptoReceh service customer receives a token-based reward and wants to withdraw it as DANA balance. Where the relevant service flow supports it, the reward can be converted into IDRR first, then processed through the available withdrawal flow to DANA.

Token reward→IDRR→Withdrawal→DANA

Internal settlement

Provide a consistent unit of account for supported CryptoReceh services and internal settlement flows.

Web3 product testing

Give developers and clients a stable-value reference when testing token pairs, liquidity concepts, or application flows.

Service-linked withdrawals

Support selected CryptoReceh service workflows where token rewards or balances are converted into IDRR before an available off-chain withdrawal method.

05 · On-chain Identity

Token contract

The following identifies the IDRR token currently deployed on BNB Smart Chain. Always verify the contract address before interacting with any token claiming to be IDRR.

Contract address

0x3A04b8947f3880dB19545a76cf4f51aFb3B3b953
Name Receh IDR
Symbol IDRR
Network BNB Smart Chain
Decimals 6
Value reference 1:1 IDR
Use CryptoReceh Internal
06 · FAQ

Frequently asked questions

What is the target value of 1 IDRR?

1 IDRR is designed with a 1:1 value reference to IDR. The reserve model is intended to keep circulating IDRR directly corresponding to the IDR reserves allocated to support it.

What backs IDRR?

IDRR uses two layers of support: an IDR reserve relationship for its primary 1:1 value reference, plus additional on-chain backing through RECEH and USDT within the CryptoReceh infrastructure.

Is IDRR intended for general external use?

No. IDRR is specifically designed for internal use within the CryptoReceh ecosystem. It is not intended to function as a general-purpose external asset or payment instrument outside the ecosystem.

Why would a client use IDRR on Receh DEX?

IDRR can provide a stable-value reference when a client is testing a token pair on Receh DEX and needs a blockchain asset whose value is referenced 1:1 to IDR.

Can IDRR be used in a reward withdrawal flow?

Where supported by the relevant CryptoReceh service, a token reward may be converted into IDRR and then processed through an available withdrawal flow, such as conversion into DANA balance.

Which network and contract does IDRR use?

IDRR is deployed on BNB Smart Chain with 6 decimals. The contract address is 0x3A04b8947f3880dB19545a76cf4f51aFb3B3b953.