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 is an XRP account that only does what you allow.
keyless-testnet.vercel.app
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.
The policies are separate contracts on @FlareNetworks .
Anyone can inspect what each account is allowed to do.
Adding a new policy doesn't mean changing the thing holding the key.
The enclave stays the same.
The policy changes.
Four accounts.
Four jobs.
One key nobody has ever seen.
The XRP signing key is generated and kept inside @FlareNetworks Confidential Compute.
It never leaves the enclave.
4/ Earn
Turn $XRP into $FXRP with FAssets.
Put it to work through @FlareNetworks Smart Accounts.
Keyless restricts the account so funds can only move between you and the approved vault and back to accounts you allow.
@FlareDevHub makes the workflow possible.
3/ Subscription
Set the recipient, amount and payment schedule.
The account can keep paying for the service it's meant for, but can't send funds somewhere else.
One account. One recurring job.
2/ Agent allowance
Give software an account without giving it unlimited power.
Set how much it can spend and how often it refills.
@FlareDevHub 's infrastructure checks the policy before anything gets signed.
1/ Exchange savings/allowlist
You define exactly which addresses this account can pay.
Anything else is refused, not warned about.
For an exchange, you can also pin the destination tag, so a payment can't be silently redirected to another account.
You hold XRP.
One key can send everything, anywhere.
Keyless changes that with @FlareDevHub 's Confidential Compute.
Create accounts that each do one job: exchange/allowlist, agent spending, subscriptions, or earning- while the key stays inside the enclave.
Here's how 👇
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
@FlareDevHub and @fassko answered the question that reshaped our roadmap: what happens when a TEE restarts?
Threshold key backup is now our top roadmap item.
Building continues.
keyless-testnet.vercel.app
It got better because people actually used it and gave us valuable feedback.
That feedback changed the product: mandatory key backup, on-chain recovery, and safer account flows.
Building in public means letting users show you what needs fixing.
Our Summer Signal submission is in.
Someone gets your key. On XRPL, that's the end of it - one key, unlimited authority, forever.
So we built an XRP account where the key lives in a @FlareNetworks Confidential Compute enclave and can only sign what an on-chain policy approved.
It got better because people actually used it and gave us valuable feedbacks.
That feedback changed the product: mandatory key backup, on-chain recovery, safer account flows e.t.c.
Building in public means letting users show you what needs fixing.
That's exactly the goal.
Keep your XRP under policy control, mint FXRP to access @FlareNetworks DeFi, and let every action stay governed by the rules you set.
20 unique users.
53 accounts created.
48 live policies.
Countless ideas, bug reports, and UX suggestions.
Thank you to everyone who tested, questioned assumptions, and helped make Keyless better. ❤️
So keep trying and tell us what you find
keyless-testnet.vercel.app
Some users permanently locked their policies.
On purpose.
No future edits. No back door. No second thoughts.
That was the last thing I expected to see and probably the strongest signal we received all month
$FXRP got the same treatment.
Hold $XRP in your Keyless account, mint FXRP, and put it to work in DeFi yield vaults on @FlareDevHub .
Your XRP never leaves the protection of your Keyless account, only what your policy allows.