Money is becoming software. HIFI is the infrastructure it runs on. We've raised a $37 million Series A led by @leftlanecap. Thank you to the customers who run on HIFI, the team that builds it, and the investors who back it. Demand is accelerating. We now process more than $7 billion a year, and existing customers have grown their usage more than 400% in the past six months. Together, they've onboarded more than 10,000 businesses and 200,000 individuals through HIFI. Our technology runs from Wall Street to everyday payments. In July, HIFI's platform was part of DTCC's pilot for tokenized repo. And through our partnership with Visa, developers can pair HIFI's stablecoin settlement with Visa Direct to move money globally. With this round, we're building toward the full stack of tokenized money, from payments and stablecoin cards to tokenized capital markets. We're growing our teams in New York and key international markets, acquiring strategic regulatory licenses, and reimagining new products for the partners building on HIFI. We're just getting started. → Read our blog: go.hifi.com/bmyAiJe → Read the exclusive in Axios: go.hifi.com/hUflHxN

Your SOC should have detection rules for every system that can move money. Starting today, @dfnsHQ can export its audit trail to your SIEM, starting with @datadoghq Cloud SIEM 🐕 Privileged action signed on DFNS, like moving funds, exporting a key, changing a user, a policy, or an access control, arrives in your security operations as a structured log the moment it resolves. It will show you: 𝗮𝗹𝗹𝗼𝘄𝗲𝗱, 𝗱𝗲𝗻𝗶𝗲𝗱, or 𝗳𝗮𝗶𝗹𝗲𝗱. This includes the attempts, such as a transfer signed and denied by policy. The type of signal that reveals stolen credentials or insider testing limits... What your SOC can now do with it: ⚠️ Alert on any key export, anywhere, instantly ⚠️ Flag policy changes outside the change window ⚠️ Catch a spike in denied actions from one user ⚠️ Surface a transfer at 3am from someone who's never operated at night ⚠️ Correlate a DFNS action with the same user's suspicious IdP login 20 minutes earlier 🛡️ We built SIEM Export like a security control. It never blocks the action it observes, but instead runs on an isolated channel so a SIEM outage can't touch your webhooks. Your API key is encrypted and never logged. When your analysts see something, DFNS can: → suspend an Org → revoke a User → tighten a Policy → deny a Wallet Your SIEM also holds an independent copy of the record, in your domain. Even if DFNS itself were ever compromised, your SOC keeps the history. That's what onchain core banking is for. 📖 Read the announcement: dfns.co/article/siem-export ⌨️ Start building today: app.dfns.io/get-started

That's a wrap! Our offsite was last week, and sadly, it’s already over... We were 10 people short. To all our new parents and everyone who has been on the road too much lately: we missed you! Since last week, @dfnsHQ ranks as 𝘵𝘩𝘦 4𝘵𝘩 𝘮𝘰𝘴𝘵 𝘵𝘢𝘭𝘦𝘯𝘵-𝘥𝘦𝘯𝘴𝘦 𝘤𝘰𝘮𝘱𝘢𝘯𝘺 𝘪𝘯 𝘍𝘳𝘢𝘯𝘤𝘦, just behind Mistral AI and AMI (which have raised $4 billion). We raised 1% of that. And that says a lot about who we are and who chooses to work at DFNS. If you want to build the new internet for finance with people like these, we’re hiring across engineering, product, security, legal, and go-to-market. ➡️ Apply here: jobs.deel.com/dfns

Proving a commitment in digital assets has always meant handing them over 😨 Capital would usually leave your control to prove a point and it would sit under someone else's risk until the point no longer needs proving. Today, we're releasing 𝗟𝗼𝗰𝗸𝘀 so you can commit funds to a counterparty 𝘸𝘪𝘵𝘩𝘰𝘶𝘵 𝘮𝘰𝘷𝘪𝘯𝘨 𝘵𝘩𝘦𝘮. A lock is a reservation inside your vault. Nothing moves onchain. Your counterparty gets an enforceable guarantee, you keep custody, and only the net result ever settles. We built the feature so neither side takes the other's word for anything: 🔒 Nothing locks without you. Every lock clears your approval quorum, enforced below the API. 🔓 Nothing unlocks without them. Only the lock owner can release, reduce, or settle against it. 🔙 Nothing unwinds it from the side. While a lock is active, the owning account can't be edited. Three use cases, one primitive: ✔️ Settlement: trade all day against 5 BTC locked at home. Sold 2? One transfer settles, 3 release back. ✔️ Collateral: the lender locks collateral in your vault. It can't be spent by you, can't be rehypothecated by them. A margin call is a lock increase, with your approval. Repayment is a release. ✔️ Escrow: funds locked until delivery. No third-party custody, no wire out and back. For a treasury, it's the difference between capital that works and capital that waits. That's what onchain core banking is for. 📖 Read it: dfns.co/article/locks ⌨️ Start building today: app.dfns.io/get-started

Every fee on @arc is priced in dollars 💲 BlackRock, DTCC, Visa, and Mastercard run the validators. And it's on @dfnsHQ from day one. @circle's mainnet blockchain went live today, and DFNS supports it as a full Tier-1 network from launch. Arc is what a blockchain looks like when it's built for stablecoin finance instead of adapted to it: ✔️ USDC as native gas. Fees denominated in dollars, so treasury never holds a volatile gas token ✔️ Deterministic finality in under half a second, with no reorganization risk once a block is final ✔️ Full EVM compatibility, so existing contracts and tooling deploy unchanged ✔️ A founding validator set of @BlackRock @The_DTCC @galaxyhq @GlobalPayInc @ICE_Markets @Mastercard @MoneyGram @StanChart @Visa Sumitomo and SBI. For institutions on DFNS, this completes the Circle stack on one platform. 1️⃣ Mint USDC from a Circle treasury through Circle Mint. 2️⃣ Move it across chains through CCTP. 3️⃣ Settle payments and tokenized assets on Arc. Redeem to fiat. Every step through the same Policy Engine, in the same audit trail. Wallets, native and token transfers, smart contract execution with your own ABI, signing with no single point of failure, balances, webhooks. The full Tier-1 set, live today 🟢 That's what onchain core banking is for. 📖 Read it: dfns.co/article/arc-tier-1-s… ⌨️ Start building today: app.dfns.io/get-started

👁️ You can now watch any address on DFNS. Today, we released 𝗔𝗱𝗱𝗿𝗲𝘀𝘀 𝗪𝗮𝘁𝗰𝗵𝗲𝘀. Register any onchain address, DFNS treats it like your wallet. The industry usually calls this a “read-only wallet.” But those usually hide a key somewhere. Whereas an Address Watch on DFNS has none. No private key, no public key, no view key. Finance on shared ledgers means reacting to accounts you don't own. → A network operator's contract records a settlement. → A counterparty's address receives what you're owed. → A market infrastructure emits the event your back office is waiting for. So far that meant running your own indexing, polling nodes, and decoding logs for every network. Now it's one registration and the webhook you already use ✅ What you get: ✔️ Every value transfer touching the address from the moment the watch starts ✔️ Balances across the address's assets ✔️ Decoded smart contract events, event name plus fields, as structured data ✔️ Three additive webhooks with addressWatchId instead of walletId And the part your security team will like the most is that the transfer, signing, and export endpoints don't exist for Address Watches. Nothing on the platform can sign for an address it holds no key for. 🟢 Live on Ethereum, its testnets, and Besu-based private EVMs. 📖 Read it: dfns.co/article/address-watc… ⌨️ Start building today: app.dfns.io/get-started

For institutions, vendor onboarding can take months… Whereas it could only take 5 minutes with @awscloud ☁️ Today, @dfnsHQ goes live on 𝗔𝗪𝗦 𝗠𝗮𝗿𝗸𝗲𝘁𝗽𝗹𝗮𝗰𝗲 🎉 Banks, fintechs, trading firms, payment services, and enterprises can now procure the world’s leading core banking platform for digital assets the way they procure the rest of their cloud stack. Through their AWS account, on their AWS bill. ✔️ One consolidated invoice. No new supplier record. ✔️ Purchases can count toward committed AWS spend. ✔️ Private Offers for enterprise terms. ✔️ Starter Plan at $70/mo. Start today, scale without re-platforming. For AWS-native institutions, the stack is now complete: keys in your own AWS CloudHSM, confidential computing on AWS Nitro, and your new operating layer procured through the same account. That's what onchain core banking is for. 🔗 View the listing: aws.amazon.com/marketplace/p… 📖 Read the announcement: dfns.co/article/dfns-availab… ⌨️ Start building today: app.dfns.io/get-started

🗞️ By now you've heard about the Coldcard incident. More than 1,700 Bitcoin, over $140 million, left their owners' wallets last month. The owners did nothing wrong. No phishing. No malware. No leaked backup. Every wallet was offline. No key was ever exposed. What happened was worse than a breach. The keys were weak the moment they were created. And they stayed that way, unseen, for 5 years 🥷 For a decade the industry has repeated one promise: 𝗼𝗳𝗳𝗹𝗶𝗻𝗲 = 𝘀𝗮𝗳𝗲. ❌ That promise broke last month. An air gap protects a secret that already exists. It says nothing about whether the secret was sound when it was born. The lesson goes beyond one device. A weak key at birth is a weak key forever. And a key created by one device, alone, has no one to catch the mistake. Our security team studies every major incident to extract the lessons, help our clients navigate, and hold our own systems to the same scrutiny. Our CISO Thibault Murel wrote the full account. It takes apart the debates this incident revived: ☑️ Custodial vs self-custody. The wrong question. ☑️ HSM vs MPC. A comfortable argument that misses the failure. ☑️ Cold storage. A phrase that no longer means what people think. And one question worth asking at your next internal sync: 𝘞𝘩𝘰 𝘷𝘦𝘳𝘪𝘧𝘪𝘦𝘥 𝘵𝘩𝘢𝘵 𝘵𝘩𝘦 𝘤𝘰𝘥𝘦 𝘨𝘦𝘯𝘦𝘳𝘢𝘵𝘪𝘯𝘨 𝘺𝘰𝘶𝘳 𝘬𝘦𝘺𝘴 𝘪𝘴 𝘵𝘩𝘦 𝘤𝘰𝘥𝘦 𝘵𝘩𝘢𝘵 𝘢𝘤𝘵𝘶𝘢𝘭𝘭𝘺 𝘳𝘶𝘯𝘴? 📖 Read the full analysis: dfns.co/article/the-coldcard…

🆕 Our integration with @elliptic is live ✔️ One of the pioneers of blockchain analytics, mapping the crypto ecosystem since 2013, now feeds the DFNS Policy Engine as a transaction screening provider. Your compliance team picks the intelligence, our control plane enforces it. This is how it works: ⬆️ 𝗢𝘂𝘁𝗯𝗼𝘂𝗻𝗱: destinations are screened synchronously, before broadcast. Policies block, hold for approval with the full Elliptic evaluation shown to the approver, or record and proceed ⬇️ 𝗜𝗻𝗯𝗼𝘂𝗻𝗱: sources are screened the moment funds arrive, with reports going to your systems instantly 🌡️ 𝗬𝗼𝘂𝗿 𝗿𝗶𝘀𝗸 𝗺𝗼𝗱𝗲𝗹: set a score threshold, and name rule categories, sanctions, mixers, darknet, that trigger regardless of score. The risk appetite you tuned in Elliptic becomes enforcement in DFNS 🚫 𝗙𝗮𝗶𝗹-𝗰𝗹𝗼𝘀𝗲𝗱 𝗯𝘆 𝗱𝗲𝗳𝗮𝘂𝗹𝘁: if Elliptic is unreachable during an outbound prescreen, the transfer is on hold. Every screening leaves evidence in the logs. The analysis ID and full evaluation, persisted per transfer, can be retrieved by API and dashboard. So when the examiner asks, the answer is the record itself. Activation takes only minutes with your Elliptic credentials. 🟢 Live at launch on Ethereum, Base, BNB Smart Chain, Optimism, and Solana. Intelligence can come from anywhere, so the best feed should win. But enforcement should live in one single place, inside the platform that has the power to sign off. And that's what onchain core banking is for. 📖 Read about the integration: dfns.co/article/elliptic-int… ⌨️ Start building today: app.dfns.io