My take on the partnership between @redstone_defi and @Brickken: 1. T+0 settlements via Settle could bring the most value to Brickken's ecosystem. Price feeds and credit ratings are offered by multiple providers, but turning T+N settlement into T+0 liquidity addresses one of RWA's biggest pain points. Brickken has supported over $660M in tokenized assets, spanning equity, real estate, and energy. Many of these asset classes are traditionally illiquid, with lengthy redemption cycles. RedStone Settle uses solvers to provide immediate liquidity, while solvers take over the positions and handle redemption. If executed well, this could unlock more Brickken assets as collateral in defi lending markets. 2. Expanding agent-ready RWAs on Brickken Brickken already offers APIs, an MCP server, and SDKs that allow AI agents to interact with tokenized assets. RedStone adds three key infrastructure components: - Pricing to determine asset valuations. - @CredoraNetwork to assess credit risk. - Settle to support exits and liquidations. Together, these components could help AI agents move beyond executing transactions toward managing RWA positions autonomously. 3. An institutional moat is taking shape RedStone is expanding vertically across pricing, risk, and settlement rather than competing solely as an oracle provider. Through Brickken, RedStone gains an opportunity to integrate all three layers with asset issuers from the tokenization stage. As issuers and lending markets adopt the full stack, switching costs could rise, making the infrastructure harder to replace. imo, that's where RedStone's long-term institutional moat could emerge, with Settle as its strongest differentiator.

ngl, keeping up with hundreds of sanctions lists is a headache for defi teams. so @redstone_defi built a Sanctions Oracle that lets protocols screen wallet addresses against 463 sources covering OFAC, UN, EU, and other sanctions lists through a single onchain check. protocols can query the oracle during a transaction and revert if an address is flagged, embedding sanctions screening directly into the execution flow. updates are pushed onchain weekly with a timestamp, so protocols can set limits on how old the screening data can be. the contract also uses the same interface as Chainalysis’ sanctions oracle, simplifying integration for protocols already using that interface. potential use cases include: - stablecoin issuers - tokenized funds - lending protocols - permissioned pools imo, the key shift is making sanctions screening part of how a protocol operates. for institutional, that means access rules can be enforced directly by smart contracts at execution time.