Create an account
Use a separate XMRVM account to authorize contract actions. Your Monero seed is never needed.
A programmable layer for Monero
Monero,
made programmable.
Put XMR to work in applications like escrow, exchanges, lending, and treasuries—while keeping native Monero deposits and withdrawals in the picture.
A separate account for contracts. Your Monero wallet keys stay yours.
x
PROTECTED EXECUTION
MONERO ↗
ACCOUNT PREVIEW
Runtime balance
— XMR
AvailableAfter confirmation
PendingTracked separately
YOUR WALLET, YOUR KEYS✳CONTRACTS IN A PROTECTED RUNTIME✳NATIVE XMR IN & OUT✳YOUR WALLET, YOUR KEYS✳CONTRACTS IN A PROTECTED RUNTIME✳NATIVE XMR IN & OUT✳
01 / THE FLOW
From your wallet
to what’s possible.
XMRVM connects a distinct contract account to native XMR transfers. You stay in control of your Monero wallet; the runtime balance is used by applications and is subject to the published reserve and withdrawal rules.
Review the runtime
Check the network, approved runtime details, reserve policy, and available attestation evidence.
Deposit native XMR
Send from your normal Monero wallet. Credit follows the published confirmation policy.
Use applications
Interact with contracts using your internal runtime balance. Contract calls are not Monero transactions.
Withdraw to Monero
Request a native XMR payout. The amount stays reserved while the payment is processed.
02 / APPLICATIONS
One balance.
Many possibilities.
Contracts can coordinate activity inside XMRVM. Each application defines its own rules; explore the examples below.
Escrow
Hold funds to agreed conditions, then release or refund through contract rules.
Exchanges
Trade internal assets against a pool, according to its contract.
Lending
Coordinate deposits, positions, and application-specific lending rules.
Treasuries
Manage funds or governance actions according to a treasury’s rules.
03 / TRUST, IN CONTEXT
Know what’s
running—and
how it’s secured.
Attestation lets you check which measured workload is running. It is a core part of the trust model, alongside reserve controls and published withdrawal rules.
Read the important detailsBEFORE YOU USE THE RUNTIME× /
01
↗
Check the evidence
Review network, runtime version, code and configuration identifiers, and attestation status.
02
↗
Understand reserve controls
Your runtime balance represents an entitlement backed by reserves and published controls.
03
↗
Know privacy boundaries
The private runtime keeps application state off public ledgers; each application defines what it records.
04 / GOOD TO KNOW
Before you
get started.
Clear answers matter when value is involved.
Does XMRVM need my Monero seed?
No. Your Monero wallet keys remain with you and should never be entered into the dApp, XMRVM, or the TEE. A separate XMRVM account key authorizes contract actions.
Is a contract action a Monero transaction?
No. Contract actions update XMRVM state. Native Monero transactions are used for deposits and withdrawals.
Are withdrawals instant?
Withdrawal timing depends on reserve availability, the signer, and the Monero network. A pending amount stays reserved while a signed payout confirms.
Read the model. Make your own call.
Start with
understanding.
Review how accounts, runtime balances, reserves, and withdrawals fit together before you use a service.
Explore the flow05 / AN EXAMPLE, IN MOTION
Follow the funds.
Not just the arrows.
A buyer funds an escrow, the agreed conditions are met, and the seller withdraws. Walk through the flow step by step.
Choose a step or press Play to start.
Buyer’s walletNative Monero
XMRVM runtimeAccounts + escrow contract
Seller’s walletNative Monero
01 / BEFORE ANY FUNDS MOVE
Separate accounts. Clear responsibilities.
Buyer and seller use separate XMRVM accounts for contract actions. They review the runtime, attestation evidence, reserve controls, and escrow terms. Their Monero wallet seeds stay private.
EXAMPLE RUNTIME STATE
- Buyer available
- 0 XMR
- Escrow locked
- 0 XMR
- Seller available
- 0 XMR
- Withdrawal reserved
- 0 XMR
01 / 06