Watch an XRP account refuse to be drained.
The signing key is born inside a secure enclave and never leaves. It can only sign what your rules allow.
Steal the key. Hijack the app.
It still can't be robbed. ๐งต
@FlareDevHub We've been building @KeylessAccounts . Public testing is live, and we've already received valuable feedbacks from early testers through our feedback form on the product. Looking forward to hearing from even more users. ๐
https://t.co/MhPA2U15Ih
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
https://t.co/82gOCwVuSJ
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
https://t.co/82gOCwVuSJ
@FlareDevHub@FlareNetworks We'd love the community to stress test it. Break assumptions. Find edge cases. Tell us what feels confusing.
Your feedback will shape the next policy templates before production.
https://t.co/Mjl6LSWkKc
#xrp#flr#flare#fxrp
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
https://t.co/82gOCwVuSJ
@FlareDevHub Coming next week:
@FlareNetworks FXRP Mint Policy and Conditional Policy powered by @FlareDevHub FDC attestations
The goal is simple: programmable XRP accounts without giving up control of your key.
@JerryMusaga@WizbarloTV@WizbarloTV And yes, you can customize the rules within a policy.
Think of the policy as the template, and the rules as the parameters you configure (approved addresses, spending limits, conditions, etc.).
Watch an XRP account refuse to be drained.
The signing key is born inside a secure enclave and never leaves. It can only sign what your rules allow.
Steal the key. Hijack the app.
It still can't be robbed. ๐งต
If there's no key to steal, how does an attacker even attack?
Good question.
The answer is: two keys.
And @FlareNetworks Confidential Compute makes neither one capable of draining your XRP. ๐งต
@FlareNetworks@FlareDevHub This is what @FlareNetworks unlocks for XRP: policy-constrained accounts.
Native XRP, with every signature checked against your rules.
The rules aren't for you.
They're for whoever gets in.
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
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.
@FlareNetworks Lock the policy and it's permanent, not even you can weaken it later.
Someone steals your control key...
...your funds still can't be sent anywhere your policy doesn't allow.
Powered by @FlareDevHub's confidential compute ๐ฅ
#xrp#xrpaccounts#flare#flr#crypto
@FlareNetworks You fund it like any XRP account.
Every payment checks your policy before it's signed.
Exchange โ โ Approved
Unknown address โ โ Refused
The funds never move.