Flare + Songbird „Rumours“

https://x.com/derivexyz/status/2087887038775435295?s=12&t=ThNULxlfKzMwAaNfSr5F1Q

https://x.com/flarenetworks/status/2087513289085403364?s=12&t=ThNULxlfKzMwAaNfSr5F1Q

https://x.com/flaredevhub/status/2085694694915531026?s=52&t=ThNULxlfKzMwAaNfSr5F1Q

https://x.com/hugophilion/status/2084332143325622682?s=46&t=ThNULxlfKzMwAaNfSr5F1Q You can now use XRP to borrow RLUSD without selling it, and Flare Smart Accounts are getting ready to make the entire process seamless: sign once and receive RLUSD, while the FXRP minting, bridging, and borrowing happen behind the scenes.

✅ Banknotez ☀️ (793) “Agents paying for APIs has been real for a while now. x402 fixed the payment flow problem.What it did not fix: who holds the key, and who gets to say no. That is what I've been building for @FlareDevHub Flare Summer Signal. If the agent has the key, you are exposed. If the rules are on chain, they are public. If they live in someone's backend, you are trusting whoever runs it. @agentvault_flr is my shot at something else. You fund a vault you control. The agent never sees the key. Flare confidential compute checks your policy in private and signs only if the spend is allowed. The vault verifies that on chain before anything moves. That's the whole reason I built this on Flare. Private rules without a black-box backend. Verifiable settlement without putting your budget on chain for everyone to read. You can't get private rules and verifiable settlement in one flow without the FCC. @FlareNetworks” 🗓 6 hours ago · 📊 2.6k 💗 31🔁 7💬 6

https://x.com/wietsewind/status/2082796820174934101?s=12&t=ThNULxlfKzMwAaNfSr5F1Q

https://x.com/theblockco/status/2082744034179846156?s=12&t=ThNULxlfKzMwAaNfSr5F1Q

https://fsa.flare.network/vaults

https://x.com/flarenetworks/status/2082118657069494571?s=12&t=ThNULxlfKzMwAaNfSr5F1Q

https://youtu.be/85Rjr3LwPLI?is=Lxx79ALkIoJ6SkJM

https://x.com/flarenetworks/status/2079500033465151851?s=12&t=ThNULxlfKzMwAaNfSr5F1Q

https://x.com/flarenetworks/status/2079400985978396911?s=12&t=ThNULxlfKzMwAaNfSr5F1Q

https://x.com/hugophilion/status/2078425581213851699?s=52&t=ThNULxlfKzMwAaNfSr5F1Q

https://x.com/flarenetworks/status/2077118990951076257?s=12&t=ThNULxlfKzMwAaNfSr5F1Q

https://x.com/flarenetworks/status/2074206748198736183?s=52&t=ThNULxlfKzMwAaNfSr5F1Q

Flare Confidential Compute is ready for its first deployment on Songbird. It's the first delivery of the Flare 2.0 vision. Pending governance, this proposal brings two pillars to a live canary network: → Protocol Managed Wallets, controlled execution on external chains, starting with XRPL → A compute-extension framework for confidential and verifiable compute Alongside them comes an upgraded Flare Data Connector (FDC V2): faster, individually handled attestations for anyone building on Flare, and the proof layer that makes Protocol Managed Wallets trustworthy. Voting starts 6 July. Full breakdown in the blog: https://flare.network/news/flare-confidential-compute-votes-to-launch-on-songbird

https://x.com/robinhoodapp/status/2062553493764768141?s=12&t=ThNULxlfKzMwAaNfSr5F1Q

https://x.com/ripplexdev/status/2060443829652578670?s=12&t=ThNULxlfKzMwAaNfSr5F1Q

https://x.com/flarenetworks/status/2057958752175772070?s=52&t=ThNULxlfKzMwAaNfSr5F1Q