Program what your XRP can do. Secure, programmable XRP accounts powered by @FlareNetworks. It only does what you allow.
Joined February 2026
- Tweets77
- Following7
- Followers83
- Likes55
Keyless retweeted
Can’t wait to see this fully deployed on mainnet!
How the FCC works in simple terms:
1. Smart contracts on Flare handle extension registration, TEE attestation, and instruction issuance.
2. Data providers and cosigners relay instructions once they reach the required signature threshold (using
the same signing policy as FTSO and FDC).
3. Registered TEE machines verify the threshold, execute the action, and sign the output with a key
generated inside the enclave.
4. Signed results (transactions, attestations, or computation outputs) are returned for onchain use.
TEE machines must register with reproducible build proofs so their identity and code can be independently verified.
Keyless retweeted
☀️ Some projects from the Flare Summer Signal hackathon that have already been deployed on testnet (mostly Coston2):
• QuietLine (@QuietLine__) – Private credit: lock FXRP → borrow USD₮0, position fully private via FCC
Demo: quietline.vercel.app
• QuietShare (@Datweb3guy) – Private group money-sharing app using TEE
(Landing page recently redesigned)
• Lodestar (@lodestar_flr) – Lending against FXRP/sFLR with no liquidations, fixed rate
Demo: lodestarprotocol.xyz
• Solvra (@RaphElevator) – Private solvency/creditworthiness proofs for FAssets agents (FCC + FTSO + FDC)
Live on Coston2
• Keyless Accounts (@KeylessAccounts) – Programmable XRP accounts with key stored in FCC enclave
Demo: keyless-testnet.vercel.app
• Torch (@torchxrponflare) – Perp trading with XRP (Flare margin + Hyperliquid hedge), key in TEE
Demo: usetorch.xyz
• Sotto (@okey_amy) – Confidential payroll: private contractor payments, gasless claims
Demo: sotto.okeyamy.xyz
• FlareGPT (@Flare_GPT) – AI copilot for wallets & DeFi on Flare
Demo: flaregpt.io
Builders are still shipping after the deadline. Winners will be announced on August 24.
@FlareDevHub @FlareNetworks @HugoPhilion
Keyless retweeted
Conditional payment. Only allows payment if an event has been attested on @FlareNetworks data connect.
Someone can steal your key and still not drain your Keyless account.
Not because we'd stop them.
Because before any signature exists, your policy runs inside @FlareDevHub 's Confidential Compute.
Here's exactly how policies works. 👇
Keyless retweeted
Flare is building toward a powerful stack for autonomous financial applications.
Oracles provide the signals.
Flare Confidential Compute executes strategies privately and verifiably.
Protocol Managed Wallets will let those strategies take action across chains.
Together, that gives applications the ability to observe external state, compute decisions under verifiable rules, and execute across multiple networks.
Keyless retweeted
Keyless Accounts is now open for public testing.
Create an XRP account, set on-chain policies, then try to break them.
- Exchange & Allowlist policy
- Spending Limit policy
Built on @FlareDevHub 's Confidential Compute.
Feedback is everything
keyless-testnet.vercel.app
Keyless retweeted
Every wallet promises to protect your key.
Building @KeylessAccounts led us to a different question:
What if someone steals your control key anyway?
The clip in the thread is our answer.
Even with the control key, the account refuses anything your policy doesn't allow.
Built with @FlareDevHub Confidential Compute.
Still early. Still Building
Keyless retweeted
Everyone's building with @FlareNetworks confidential compute.
We're using it to rethink the wallet itself.
Instead of protecting a private key, @KeylessAccounts protects your intent, transactions are only signed when your predefined policy allows them.
An XRP account that only does what you allow.
I took a quick look at some of the projects being built for Flare Summer Signal. Here are some of the main ideas behind them:
• Keyless (by @KeylessAccounts)
Policy-controlled XRP accounts where signing keys stay inside confidential compute and transactions are only signed when predefined rules allow them.
• Encrypted Finance (by @EncryptedFi)
A private DeFi execution layer using confidential compute, encrypted instructions and shared execution wallets to reduce exposure of user activity onchain.
• FlightGuard (by @_ace_won)
Parametric flight insurance using FDC Web2Json to attest real flight outcomes, FTSO for pricing, and FXRP/USDT0 for premiums and settlement.
• Torch (by @Big14teru)
XRP-margined perpetuals with a TEE-controlled executor, moving trade execution into Flare Confidential Compute so operators do not directly control the signing key.
• Lodestar (by @lodestar_flr)
Fixed-term lending using FXRP as collateral and USDT0 liquidity, replacing continuous health-factor liquidations with deadline-based default settlement anchored to FTSOv2 pricing.
A good snapshot of how builders are exploring confidential compute, XRPFi, external data, and new financial primitives on @FlareNetworks.
Keyless retweeted
@CryptonistNord Great question. The XRP always stays on the XRPL, the TEE only holds the signing key and will only sign transactions your rules allow.
Unlocked: No. You can always update the rules and move your funds.
Locked (opt-in, one-way): Yes. If you intentionally lock an account with a rule that allows nothing, the funds become permanently inaccessible.
That's why Keyless is designed to validate your policy before you lock it, helping ensure the rule does exactly what you expect.
Keyless retweeted
Flare Summer Signal: save the key dates.
June 29: Registration + submission opens
August 14: Final submission deadline
August 15–21: Judging period
August 24: Winner announcement ceremony
Build something useful. Ship real progress. Make your Flare integration count. ☀️
Keyless retweeted
Flare Summer Signal hackathon is in full swing. Tbh, I can't overstate that devs have very cool ideas on top of Flare Confidential Compute (TEEs) that I didn't even think of. You still can join and build on Flare. dorahacks.io/hackathon/flare…