Skip to workspace
Mainnet reads · Testnet actions
Mainnet dataTestnet actions
Install Freighter
Freighter is not installed

Freighter is not installed. Install the browser extension to connect a Stellar wallet. Everything on this workspace reads without one.

This workspace expects Stellar Testnet. Ryntra never receives a key, never signs on your behalf, and a signature is never a submission.

Send XLM

About Send XLM

A wallet signature is not a Ryntra authorization, and a signature is not a submission. This surface makes both visible: you authorize an exact intent here, Freighter signs it, and what comes back is compared field by field against what you authorized. Only bytes that matched can be submitted — the submit function takes the cleared verdict rather than an XDR, so there is no way to hand it anything else.

Then the lifecycle finishes rather than stopping: the ledger is read back from Horizon independently, what it actually did is compared against what was authorized, and the result is a receipt whose every hash you can recompute on the Receipts page.

Fixed to Stellar Testnet, where the assets have no worth. Ryntra holds no key, signs nothing, and never relays a signed transaction — the signature happens inside Freighter and the submission goes from your browser straight to the public Stellar endpoint.

Testnet · user-signed

Prepare a payment

TESTNET
Why testnet only

This surface exists to show the authorization gate and the lifecycle behind it, not to move value. It is fixed to Stellar Testnet, where the assets have no worth, and nothing it produces can reach mainnet.

No wallet connected

A wallet supplies the source account and the signature. Everything else on this workspace reads without one.

What you authorize

EMPTY
What a fingerprint is

The fields that decide what the transaction does, captured before the bytes leave this page. Signing appends signatures and necessarily changes the bytes, so the comparison afterwards is over these fields and never over raw XDR.

Authorizing also starts a clock. The transaction carries an upper time bound of 300 seconds, so a signature that is never submitted expires instead of waiting indefinitely for a moment nobody intended.

Nothing built yet

Build a transaction to see exactly what a signature would cover.

A signature is not a submission.

Lifecycle

OPEN
  1. Ryntra checks what can be known first
  2. Ryntra builds the exact transaction
  3. You authorize this exact intent
  4. Freighter signs it
  5. Ryntra compares what came back
  6. Your browser submits it
  7. The ledger is read back
  8. Expected against actual

What the ledger did

NOT SUBMITTED
How this is checked

The ledger is read back from Horizon independently of the submission — the credits and debits it recorded, the fee it charged, and whether it applied the transaction at all. Those are compared against what you authorized, movement by movement, with amounts compared in stroops so the same amount written two ways is one amount.

A fee lower than the ceiling you authorized is normal and is not a deviation. Anything the comparison cannot model is reported as unchecked rather than counted as agreement.

Nothing submitted

Build a transaction, authorize it, and sign it. Only bytes that matched what you authorized can be submitted from here.