
RWA · Stablecoins & FX · ARYZE
Multi-currency RWA stablecoins and FX tokens.
Multi-currency RWA stablecoins and FX tokens.
Machine-readable protocol knowledge for agents
Multi-currency RWA stablecoins and FX tokens.
aryze · v1.0.0
Facts
| category | Network |
| symbol | ARYZE |
| tagline | Multi-currency RWA stablecoins and FX tokens. |
| arbitrumNative | no |
| chains | unspecified |
| security | audited (OZ-derived · reported audited (no public link)) |
| memberCoins | none tracked |
| universalMetricsSyncedAt | 2026-08-23T06:42:49Z |
Sections
Multi-currency RWA stablecoins and FX tokens.
Multi-currency RWA stablecoins and FX tokens.
- Digital Cash (eEUR / eUSD / eGBP): ARYZE's core product: a series of full-reserve fiat stablecoins ('Digital Cash') pegged 1:1 to the euro, US dollar and British pound, issued as ERC-20 tokens. Reserves are held in short-term government bonds/assets under a full-reserve banking model. - reForge API / E-Assets smart contracts: ARYZE's smart-contract framework and reForge API providing built-in cross-chain transfer support for its E-Assets, intended to move tokens across chains without third-party bridging or wrapping services. - Stablecoin-as-a-Service infrastructure: A unified stack that combines stablecoin/tokenised-RWA issuance with bank-to-bank fiat on- and off-ramp (fiat rails) for licensed issuers, aiming to replace multiple fragmented vendor integrations. - Pay by Bank: An account-to-account payments product built on Open Banking (operated via ARYZE ApS in the UK), letting merchants accept bank-rail payments alongside the stablecoin stack.
- Reserve / Depeg: Digital Cash is only as sound as ARYZE's full-reserve claim; there is no public, recurring third-party reserve attestation or audit report found, so backing quality (short-term government bonds) is self-reported and depeg risk is unverified. - Counterparty: Tokens are issued by ARYZE BVI (British Virgin Islands) rather than a regulated EU bank; holders rely on that entity and its custodial banking relationships to honor 1:1 redemption. - Regulatory: As an EU/Danish fiat-referenced stablecoin issuer, ARYZE is exposed to MiCA e-money-token requirements and EMI licensing; the company markets to 'licensed issuers' but no completed EMI/MiCA authorization was found in public sources, creating regulatory execution risk. - Smart Contract: eEUR/eUSD/eGBP are upgradeable proxy contracts (ERC1967Proxy) whose implementation can be changed by the admin, and the cross-chain reForge/E-Assets transfer mechanism concentrates trust in ARYZE's own contracts and admin keys. - Systemic: Very low on-chain adoption (tens of holders, ~272 eEUR supply on Ethereum) means the tokens are early-stage and illiquid, amplifying the impact of any single redemption, issuer or banking-partner failure.
- Regulated e-money / prepaid balances (e.g. bank-issued e-money): similar in that Both represent fiat value redeemable 1:1 and aim to be a cash-like store of value backed by safe reserves.; differs in that ARYZE Digital Cash is a bearer ERC-20 token that moves on public blockchains 24/7 and can swap between currency pairs on-chain; traditional e-money is account-based, closed-loop and settles through bank rails. - Money market funds / short-term government bond holdings: similar in that Reserves for ARYZE stablecoins are held in short-term government bonds, similar to the assets underpinning a government MMF.; differs in that Holders of ARYZE Digital Cash receive a transferable payment token pegged 1:1 rather than fund shares, and (as marketed) do not receive fund yield distributions.
Actions
| Name | Signature | Access |
|---|---|---|
getProfile Read the CanHav profile for Aryze. | research_getEntity({ slug: "aryze" }) | read-only |
listMembers List the member coins (stablecoins / tokens / RWAs) under this network. | research_listByCategory({ category: "networks" }) | read-only |
readLiveMetrics Read live on-chain supply / metadata for a member contract (Arbitrum). | chain_readLive({ address: "0x..." }) | read-only |
getHistory Pull historical peg / TVL series for a member protocol. | research_getHistory({ slug: "<member-slug>", metric: "peg" | "tvl" }) | read-only |
Glossary