REUR's public chain history runs ahead of its legal history. The contracts can count and restrict tokens precisely, while the programme Registry still cannot tell a holder which finalized issuer, reserve report or redemption agreement stands behind that count.
REUR is pinned to three addresses and 18 decimals. The official product page presents a EUR 1.00 design, but the programme's own Registry says Launch Preparation and leaves the legal issuer blank. CoinGecko's Hong Kong issuer label cannot repair an omission in the issuer's designated record.
TRON records creation on 10 February 2026 and Ethereum on 11 February. By the review date, the three independent ledgers summed to 5 billion units. That is total token accounting, not proof of 5 billion euros in circulation.
The Registry's 28 August status reverses the usual order: production contracts are supposedly still to be published after identifiable contracts already exist. A careful reader must therefore preserve both facts instead of silently declaring either a completed launch or a worthless deployment.
RoyalEuro.sol is fixed, non-proxy code, but its state is centrally operated. A master minter creates uncapped supply and appoints limited minters; separate roles pause every transfer and blacklist addresses; an administrator reallocates roles. Burning by a holder reduces that chain's balance but is not a euro redemption.
The same 20-byte address on Ethereum and BNB does not make balances fungible across chains. With no bridge or consolidated liability logic in the token contract, a reserve report would need to count each deployment and explain which units are issued, treasury-held, circulating or redeemable.
The website refers to segregated accounts, cash equivalents, buffers, PoR and independent assurance. It does not publish the REUR bank, custodian, account ownership, reserve composition, observation time or auditor conclusion. The transparency link returned 404 and the referenced API yielded no usable snapshot during review.
The linked CertiK material speaks to contract security and highlights centralization functions. Even a flawless contract could mint an unbacked balance; code auditors do not confirm euros in a bank. Reserve and code evidence answer different questions.
Authorized participants and compliance screening are a process outline, not a holder contract. Until fees, eligibility, settlement assets, timing, suspension events, governing law and direct versus intermediary claims are published, REUR's EUR 1.00 target remains a product intention. The most important milestone is not another listing: it is publication of the legal and reserve path from one token back to one euro.
TRONSCAN records creation of the REUR contract on this date. The later review snapshot on 2026-09-05 showed a 2 billion-unit total supply.
Verified RoyalEuro code appears at the exact product address; the initial chain later reports 1 billion units.
The separate BNB ledger later reports 2 billion REUR.
The project-hosted viewer describes a CertiK assessment; code review does not verify reserves.
Ethereum history shows the owner account renouncing roles, illustrating that ownership and AccessControl roles are separate.
The programme's official record says issuer, contracts, terms, review and transparency remain to be published.
Last evidence review: 2026-09-05
Royal Euro uses symbol **REUR**, not EURR. The exact records associated with CoinGecko id `royal-euro` are Ethereum and BNB Chain address `0x3ed0b3c4c0168a560d34e361b8130dcca4677736`, plus TRON address `TXUi9vL8Ltz4dVpC6RM8CdtKSTHxFZuFbz`; all use 18 decimals. This tuple excludes other euro stablecoins with similar names or tickers.
The product page calls REUR a euro-referenced stable-value token targeting EUR 1.00. Yet the programme's designated Registry, updated 28 August 2026, marks REUR **Launch Preparation** and says the legal issuer, production networks, verified contracts, whitepaper and terms, independent review, transparency and access channels remain to be published. The product page and CoinGecko metadata name The RIB Digital Holdings Limited of Hong Kong as issuer, but the designated official Registry leaves the legal issuer unpublished; the company attribution is therefore reported as a publisher claim rather than a settled legal identity.
A euro token needs more than a ticker and an exchange price. Holders need to know which legal person owes redemption, what assets are segregated, who holds them, how liabilities are reconciled across chains, and which rule determines fees and eligibility. REUR's public story promises institutional settlement while its official registry withholds those exact product facts.
This creates an unusual chronology: token contracts and billions of units exist first, while the programme still labels the product pre-launch. An ERC-20 balance proves that code assigned units; it does not prove that a bank holds a matching euro, that the unit is legally redeemable, or that an advertised EUR 1.00 target can be enforced.
On 5 September 2026 the Ethereum contract reported 1 billion REUR, the same-address BNB Chain contract 2 billion, and TRON 2 billion: 5 billion units across the three deployments. The contracts are separate ledgers, and the verified Ethereum code contains no cross-chain bridge or global supply reconciliation. CoinGecko's 15 million circulating figure is third-party/self-reported metadata, not derivable from totalSupply alone.
The EVM code is a non-proxy OpenZeppelin token. A default administrator can grant or revoke roles; a master minter can mint without a disclosed cap, configure allowance-limited minters, and remove them; a pauser can stop transfers, minting and burning; a blacklister can block addresses in either direction; and a rescuer can withdraw assets mistakenly held by the contract. Holders can burn their own balances. Both Ethereum and BNB Chain returned owner `0xc50ebe57ae937a8ac0bcaab8945777c3be54a511` and were unpaused at review time. No proxy upgrade path appears in the deployed EVM bytecode, although role holders can still change.
The product page says issuance and redemption run through authorized participants and approved counterparties after onboarding and compliance checks. It does not publish a fee schedule, minimum, settlement timeline, eligible jurisdictions, direct redemption agreement or procedure for an ordinary secondary holder. The Registry says terms and access channels are still in preparation. Accordingly, no enforceable one-for-one redemption right can be verified from the available official material.
Reserve language is similarly conditional. Product and RIB Digital pages say reserves may include cash in segregated financial-institution accounts and liquid cash equivalents, with reporting, PoR and independent verification. They do not identify the custodian, account bank, asset mix, valuation date, assurance firm or liability reconciliation for REUR. At review time the linked transparency route returned 404 and the linked euro-reserve API did not return a usable report. A smart-contract security review addresses code, not the existence or ownership of euros.
The asset indexed as `royal-euro` uses REUR. Its exact Ethereum and BNB address is `0x3ed0…7736`; its TRON address is `TXUi…uFbz`. EURR identifies other assets and must not be merged.
That remains unresolved in the controlling official Registry. The product page and CoinGecko name The RIB Digital Holdings Limited, Hong Kong, while the designated Registry says the legal issuer is to be published before issuance.
The project targets EUR 1.00 and describes reserve-based constraints, but no accessible dated attestation identified the bank, custodian, asset balance and matched REUR liability across the three chains.
No published official contract establishes that right. The product page mentions authorized participants and approved counterparties after onboarding; fees, thresholds, jurisdictions and ordinary-holder procedures are not published.
Yes. EVM master-minter and minter roles create units, the pauser stops all movement, and the blacklister blocks selected senders and receivers. Role administrators can grant and revoke privileges.
No proxy or upgrade function was found in the deployed Ethereum and BNB code. That limits in-place code replacement, but does not remove role changes, uncapped master minting or the possibility of a separately deployed successor.
No. A code audit or token scan assesses smart-contract behavior. It does not verify bank balances, segregated ownership, liabilities, regulatory authorization or redemption performance.
Choose a tracking site for Royal Euro:
