Further

Today, @The_DTCC launched its Tokenization Service 🇺🇸 It’s worth pausing on what this day is. DTC replaced paper certificates with electronic records in 1973. Today, it’s bringing securities 𝗼𝗻𝗰𝗵𝗮𝗶𝗻 while preserving existing rights and protections. With over $114 trillion in custody, this is how market infrastructure upgrades, and more importantly, this is what leadership looks like 👏 The Tokenizaton Service (DTS) allows DTC to issue tokenized versions of the securities they hold in custody. These tokens have the same ownership rights and investor protections as the initial securities, and can move in between classic and tokenized form. 20 DTC Participants have already signed on as the first batch. @dfnsHQ is proud to be among the 15 official partners and distributors 🤝 We now support DTS on @CantonNetwork and DTCC’s Besu network: ☑️ On Canton, you can use DFNS-operated validators or connect your own. DFNS indexes and decodes tokenized securities, and enables pre-approved deliveries and settlement against cash. ☑️ On Besu, you can connect your own network and hold, receive and transfer tokenized securities. Every transaction is checked against their policies before signing. ✅ On both networks, financial institutions can track balances and transactions, receive real-time triggers, webhooks and keep a single audit trail for every operation. Tokenized securities are moving into regulated markets, and institutions need a secure way to manage them under their own controls, no matter the network used for settlement. We’re honored to work with DTCC and the wider industry to make that possible. 📖 Read more: dfns.co/article/dts-integrat… ⌨️ Start building today: app.dfns.io/get-started

With Bitget, the signer trusted the wrong host. With NEAR Intents, the signer did everything right, but the ledger it trusted was wrong. The result: $3.87 million stolen ⛓️‍💥 @dfnsHQ CISO, Thibault de Lachèze-Murel, has written another piece on the NEAR hack as a follow-up to his Bitget analysis. Together, the two incidents show two sides of the same problem: Signers must verify who can authorize a transaction, and they must be able to trust the data behind it. Here’s what happened to NEAR: 1️⃣ The system tracked what users were owed in an internal ledger, backed by funds held in vaults. 2️⃣ The attacker made 23 deposits that appeared in the ledger but failed to settle onchain. 3️⃣ The tokens were returned to the attacker… but the credits remained. 4️⃣ The attacker then withdrew the fake balance using real funds from the vaults. The signers ran in secure enclaves and checked the ledger before signing. But the ledger was wrong and nothing checked that the balances matched the actual funds. The lessons here are simple: → Credit deposits only after onchain confirmation. → Continuously check that balances match available funds. → Set withdrawal limits that the ledger cannot override. → Treat external calls as untrusted and stop when they fail. → Monitor the system for inconsistencies, not just individual components. A signer can control who authorizes a transaction. It cannot guarantee that the balance behind it is real. That needs a separate control. That’s what onchain core banking is for. 📖 Read more: dfns.co/article/the-near-hac… ⌨️ Start building: app.dfns.io/get-started

📈 He scaled a core banking platform to nearly 1M transactions a day. Now he's building @dfnsHQ in Singapore. Please welcome Zakarya Ali, our first software engineer in APAC. Zakarya has spent more than ten years building systems where money, data and reliability meet: → At Majority in Stockholm, he ran core banking engineering. He lifted payment success and designed a double-entry ledger all under PCI and SOC 2 → At Thales in Singapore, he led data and machine learning work for SMRT, Singapore's transit operator, and later led AI implementation for 15 engineers across Paris and Singapore → In six months there, he architected five production AI products, including a stablecoin payment agent, and an agentic system that cut its own running cost by 41% → He began at Accenture in Paris, building for clients such as Orange, La Banque Postale and EDF Few engineers have worked on both sides of what DFNS does: the core banking systems that keep an institution's books, and the modern platforms that move value at scale. Zakarya has. In Singapore, he'll work across our core platform and alongside clients in the region, helping institutions design and deploy on DFNS, and helping us build our engineering team in Asia. Welcome, Zak. 🤝 📖 Read the announcement: dfns.co/article/welcome-zaka… 📮 See our open positions: jobs.deel.com/dfns

🇯🇵 In Japan, trust is built over decades. NEC has spent more than 125 years building it with financial institutions. Today, @NEC_jp and @dfnsHQ are partnering to explore digital asset infrastructure for Japanese financial institutions 🤝 The two companies have signed a Memorandum of Understanding to explore how DFNS can fit into NEC’s systems, including its planned custody offering. The goal is to help Japanese institutions adopt digital assets without compromising their security, compliance, data residency or existing systems. The partnership will focus on three areas: 1️⃣ Integrating DFNS wallets, key management, policies and transaction management into NEC’s digital asset infrastructure. 2️⃣ Adapting the platform to Japanese regulations and each institution’s security and operating requirements. 3️⃣ Supporting different deployment models, from SaaS to hybrid and fully on-premises, including air-gapped environments. Institutions will be able to keep their keys, data and operations in Japan, in line with their requirements. NEC will also explore support for digital securities alongside crypto assets, helping institutions develop new digital asset services. That’s what onchain core banking is for. 📖 Read more: dfns.co/article/partnering-w… ⌨️ Start building: app.dfns.io/get-started

Two years ago, we published our insurance policy when no one would. Today, we’re sharing our newest insurance upgrade brought to us by Native. On October 1, @dfnsHQ moved its insurance program to @LloydsofLondon. Both policies are now backed by Lloyd’s syndicates @Mosaic1609 and @markel_ger. ☑️ Technology and cyber: Coverage increased 4x, from $2.8M to $11.2M with Mosaic. ☑️ Crime: $11.2M in coverage, led by Mosaic and supported by Markel. ✅ Total coverage: Increased from $13.9M → $22.3M worldwide, covering DFNS and its subsidiaries. Also: The two policies have separate limits, so a claim under one does not reduce the other. What hasn’t changed? 𝘐𝘯𝘴𝘶𝘳𝘢𝘯𝘤𝘦 𝘩𝘢𝘴 𝘭𝘪𝘮𝘪𝘵𝘴. It is 𝗻𝗼𝘁 𝗮 𝗿𝗲𝗰𝗼𝘃𝗲𝗿𝘆 𝗽𝗹𝗮𝗻 and it 𝗰𝗮𝗻𝗻𝗼𝘁 𝗰𝗼𝘃𝗲𝗿 𝗹𝗼𝘀𝘀𝗲𝘀 𝗼𝗳 𝗮𝗻𝘆 𝘀𝗶𝘇𝗲. Exclusions still apply, and we’re happy to walk clients through the details. ▶️ What’s next: We’re arranging additional coverage and will announce it soon. We’re also working with leading actors on specie insurance designed for multi-party compitation (MPC). Clients can request the insurance certificate and policy wording under NDA. We believe insurance should be clear, verifiable and part of taking responsibility for the risks we manage. That’s what onchain core banking is for. 📖 Read more: dfns.co/article/insured-by-m… ⌨️ Start building: app.dfns.io/get-started