We built this to show you what Trimmy can do. In four steps you will produce
a real XRPL payment that arms a real rule on Flare, and before you send it you will read,
in plain English, exactly what signing it authorises.
Everything happens in this browser. There is no wallet to connect, nothing to install, no FLR
to hold, and no server sees your rule. The XRP is testnet XRP and is worth nothing. Everything
else behaves exactly as it would with real money, which is the point of showing it to you.
Whose rule is this?
Flare works out which contract address your XRPL account controls. This is read-only and
changes nothing.
The address is checked against its own four-byte checksum first, here, before anything
touches a chain. Flare would accept a mistyped one and quietly derive an account nobody
controls, and the payment could not be recalled.
What should happen, and when?
Every bound below is fixed the moment the rule is armed. Nothing can change them afterwards,
including us.
Read this before you send anything
An XRPL payment cannot be recalled. The 42-byte memo is the only thing that decides what
happens on Flare, and it is unreadable by eye. So below is that memo decoded independently,
from the bytes themselves rather than from what you typed.
Your price does not travel in the payment
It cannot. Anything inside an XRPL payment is on a public ledger forever.
Arming creates the rule with no threshold at all.
The number is delivered separately, encrypted to the enclave's own key, so that nobody,
including us, can read it. The chain holds only a hash of it.
After the payment settles and your rule exists, run this once.
Send it from your own wallet
Three fields, and the memo matters most. Trimmy never sees your keys and cannot send this
for you.
Do not add a destination tag.
A registered tag overrides the memo entirely and credits the tag holder instead. The payment
would be silently donated to a stranger.