Data oracles provide external data to Newton’s policy engine for evaluation. Integrations such as @redstone_defi can provide asset prices and other financial data used by Newton policies when evaluating transactions.

Yesterday at @summit_defi, @Shebitweet from Safe Research showed a deny-by-default policy engine for Safe smart accounts: anything not explicitly allowed is blocked. The code is open source: Watch the talk:

.@TheBlockCo has reviewed Bron for its guide to the best crypto wallets of 2026, and called the security policy engine "Bron's most impressive feature". Read the full review here:

NEW: @Ripple Custody adds @CantonNetwork support, letting institutions hold and transfer Canton assets within the same custody platform, policy engine and audit trail as their other digital assets.

Fordefi now supports @plumenetwork. Plume is an EVM-compatible chain built for tokenized real-world assets. 🏦 Hold and transfer assets on Plume with MPC self-custody 🔗 Connect to Plume dapps via the Fordefi extension 🛡️ Policy Engine on every transaction Learn more →

Fordefi supports @Arc from day one. Arc mainnet is live with stablecoins as gas, starting with USDC. 🏦 Hold and transfer ethereum:0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48 on @arc with MPC self-custody 🔗 Connect to Arc apps via the Fordefi extension 🛡️ Policy Engine on every transaction Explore Arc →

AI-driven financial operations need clear boundaries. In a conversation with @_sarthakarora at @lifiprotocol, our co-founder @jakemargs explains how Reah’s Programmable Policy Engine governs agents through defined roles, authorization limits and approval flows.

Google wants to hold a piece of your bank's crypto keys, but never the whole thing. @googlecloud showcased its Multi-Party Compute service at a New York event this week. It's in private preview, with general availability planned for early 2027 and no pricing yet. The service splits a wallet's private key into shares. One sits with Google Cloud, one in the bank's own hardware and one can sit with a rival cloud. No single party, Google included, ever sees the full key. Signing takes a threshold of shares, like 2-of-3 or 5-of-7. A policy engine checks every transaction against rules such as spending caps and approved wallets before anything gets signed. Alphabet already uses it for its own $ETH and $SOL, and unnamed banks are testing it. That puts Google up against custody specialists like @FireblocksHQ and @BitGo. Would you trust a bank that splits its keys with Google?

Defensive security needs to compound at the same rate as, if not faster than, offensive security in this age of AI-driven-exploits. Our approach at @safe A battle tested account layer — the multisig. A new robust onchain policy engine. A decentralized security protocol leveraging independent security teams to verify, attest and enforce onchain. Pair those with all the excellent cybersecurity web2 practices that have been perfected over the years. Combining our Cypherpunk values and approaches with Enterprise grade rigor is what we refer to as “Cypherprise”. DeFi won’t scale without robust security foundations that scale with the evolving threat landscape. This is why we’re building smart accounts, the policy engine, safe pro and and we need the community’s help and support to make self-custody more resilient. We’re increasingly positioning $SAFE towards the mission of making self custody easy and secure. We need to step up big time!