Flare Coston2 · Confidential Compute
Your stop-loss is
public right now.
Every onchain automation protocol publishes your trigger price in the clear. It sits there for days, telling everyone exactly where you will be forced to sell. Wraith encrypts the condition to a trusted enclave, so there is nothing to hunt.
Stop-loss hunting is not a conspiracy. It is arithmetic.
A resting stop order is a public commitment to sell at a known price. Anyone reading the chain can see the level, the size, and who owns it. Pushing price into a cluster of stops is profitable precisely because the cluster is visible.
Traders have exactly two defences today. Keep the stop on a centralised exchange and accept custody risk, or keep it in your head and accept that you will be asleep when it matters. Neither is a good trade.
- 01
Seal
Your condition is ECIES-encrypted in your own browser and stored onchain as bytes. The chain holds ciphertext and escrow. It never holds your trigger price.
- 02
Watch
A keeper pokes the order on a schedule. Inside the enclave the TEE decrypts it and reads FTSO itself — so the keeper forwards bytes it cannot read, and cannot lie about the price it did not supply.
- 03
Fire
When the condition is met the enclave signs a settlement. The contract checks that signature against Flare's TEE registry, consumes the action id so it cannot be replayed, then swaps or redeems FXRP to native XRP.
Wraith hides intent, not execution.
Once a trigger fires, the resulting trade is an ordinary public transaction and is as exposed to execution-moment MEV as any other. A TEE does not make a trade invisible, and anyone claiming otherwise is selling you something.
The narrower claim is the one that holds: the condition was never public, so it could never be hunted. Every assumption behind that — onchain ciphertext exposure, simulated attestation on testnet, what the registry does and does not guarantee — is written down rather than glossed over.
Set a stop nobody can see.
Running on Coston2 against live FTSO feeds. Testnet only — Flare Confidential Compute is itself pre-release, so do not put real funds behind it.
Open the appContract 0x9271f82D…00A6ec62