Christopher Grilhault des Fontaines retweeted
.@christophergdf, CEO of @dfnsHQ, says that by next year, you’ll be using tokens without even realizing it.
“It’s gonna be kinda normal to have an account, a wallet, etcetera, and it’s gonna be normal to send and receive tokens.”
Done ✅
Until now, if we missed a deposit, you had to file a ticket and wait...
That changes today. You can now replay transactions yourself from @dfnsHQ 🟢
Replay any missed transaction by hash, from the dashboard or API. Available to every customer, at no extra cost.
Indexers can miss events when a node drops a block, a chain reorganizes, or a wallet is added after a deposit arrives. When that happens, you need to deal with missing balances, uncredited users, incomplete records, and more.
Now you can fix it yourself:
✔️ Paste the transaction hash in the dashboard or API.
✔️ DFNS re-fetches the transaction and updates history and balances within a minute.
✔️ Standard webhooks trigger your existing deposit and sweep workflows.
✔️ Replays are idempotent: no duplicate records or webhooks.
✔️ Access is limited to your own wallets and rate-limited.
No support ticket. No waiting. Just a complete transaction record.
It's a small feature that makes a big difference in support, speed, and reliability.
That's what onchain core banking is for.
📖 Read more: dfns.co/article/transaction-…
⌨️ Start building: app.dfns.io/get-started
Christopher Grilhault des Fontaines retweeted
🛡️ A certification is a promise. A surveillance audit checks you still keep it.
In August, @dfnsHQ passed its first ISO/IEC 27001, 27017 and 27018 surveillance audit, with a positive recommendation from MSECB on all three.
Over four days, auditors reviewed our security controls across SaaS and on-premises deployments, from risk management and disaster recovery to backups, incident response and employee training.
The result: all three certifications maintained. No major findings. One minor documentation issue, now corrected and closed ✅
This follows another year of work: SOC 2 renewed with no exceptions, new security controls, better monitoring and recovery, and a detailed analysis of the limits every provider faces.
Security isn’t a certificate on a wall. It’s the controls you run, test and improve every day.
The full audit report is available to clients under NDA.
⏩ Next: ISO 22301 for business continuity and SOC 1 for financial controls.
📖 Read more: dfns.co/article/iso-27001-27…
⌨️ Start building: app.dfns.io/get-started
Christopher Grilhault des Fontaines retweeted
“A good business to be in is physical custody.”
Because every tokenized asset is backed by something real, someone has to keep it “in a secure location” and certify that it’s there.
Says, @christophergdf, CEO of @dfnsHQ on the live show.
Christopher Grilhault des Fontaines retweeted
Usually, a margin call is a lock increase.
Now it's only one atomic change, not an unlock-and-relock anymore.
Our CPO Chris Sutton demos our latest upgrade to Vaults, enabling you to modify a locked position.
In the demo, Chris:
1️⃣ Opens a vault with 5 USDC locked and scrolls to the lock entry
2️⃣ Changes the locked amount from 5 to 10 USDC
3️⃣ Signs with a passkey.
✅ Locked balance: 10. Available: 10. One operation, no intermediate state
The alternative to atomic changes is to release the lock and create a new one, which opens a window where the collateral is briefly free. For a lender raising a margin requirement, or a venue extending a trading line, 𝘵𝘩𝘢𝘵 𝘸𝘪𝘯𝘥𝘰𝘸 𝘪𝘴 𝘵𝘩𝘦 𝘸𝘩𝘰𝘭𝘦 𝘳𝘪𝘴𝘬.
Modifying in place means the funds are never unlocked on the way to being locked for more. The commitment only ever moves in one step, and the counterparty's guarantee never lapses.
The same permission model holds throughout. Increases route through the committing party's approval, so a lock can't be enlarged unilaterally, and only the lock owner can reduce, release, or settle against it. Nothing locks without you, nothing unlocks without them, and now nothing changes size without both.
Off-exchange settlement, collateral, escrow. The same primitive, now adjustable without ever letting go.
That's what onchain core banking is for.
🔘 Watch the demo: youtu.be/XRrw6UV5Gtw
📖 Read it: dfns.co/article/locks
⌨️ Start building today: app.dfns.io/get-started
Done ✅
👥 Most access controls don't fail in a breach. They fail quietly through drift.
On most platforms, approval policies name specific people. So when someone joins or leaves a group, like the “treasury team,” an admin must manually update every policy that mentions them. Do that for a year and you end up with dozens of hand-maintained user lists that no one fully trusts.
Today we're introducing 𝗨𝘀𝗲𝗿 𝗚𝗿𝗼𝘂𝗽𝘀, so that never has to happen again.
A User Group is a named team the platform understands.
✔️ Assign permissions to the group and every member inherits them.
✔️ Name the group as the approver and the quorum is drawn from that team.
✔️ Someone joins? Add them to the group once.
✔️ Someone leaves? Remove them once. Every policy and permission self-updates.
You can create a group with the same name as the one in your identity provider, and from there we follow your IdP (e.g. Okta, Microsoft) at every login. A match adds the user, an absence removes them, including for admin access.
Because a group is a way to grant power, it's also governed like one:
→ Adding someone to a privileged group grants the same rights as assigning them directly
→ Deleted group names stay reserved and can’t be recreated with different rights
→ A floor guard prevents removing the last administrator, directly or through group deletion
→ Every membership change is signed, audited, and traceable
The org chart and the platform now say the same thing, and your auditors can prove it.
That's what onchain core banking is for.
📖 Read it: dfns.co/article/user-groups
⌨️ Start building today: app.dfns.io/get-started
Christopher Grilhault des Fontaines retweeted
A whole new world is being built in how banks move money.
Banks will soon settle payments with tokens while the underlying deposits stay on their books.
JPMorgan is already doing it with JPM Coin, its deposit token on Base.
“Banks and [payment companies], they will start committing to more token-first operations."
"The token will move, the underlying asset will sleep, and that is a whole new world.” — @christophergdf, CEO of @dfnsHQ
🚨 A must-read.
On September 24, @bitget lost $387.5 million. But no key was stolen.
The attacker took control of the server that told the signer what to sign, and the signer obeyed.
Our CISO, Thibault de Lachèze-Murel, breaks down the Bitget hack:
𝘞𝘩𝘢𝘵 𝘩𝘢𝘱𝘱𝘦𝘯𝘦𝘥, 𝘸𝘩𝘪𝘤𝘩 𝘤𝘰𝘯𝘵𝘳𝘰𝘭𝘴 𝘧𝘢𝘪𝘭𝘦𝘥, 𝘸𝘩𝘢𝘵 𝘵𝘰 𝘤𝘩𝘢𝘯𝘨𝘦, 𝘢𝘯𝘥 𝘸𝘩𝘢𝘵 𝘳𝘪𝘴𝘬𝘴 𝘳𝘦𝘮𝘢𝘪𝘯 𝘪𝘯 𝘰𝘶𝘳 𝘰𝘸𝘯 𝘮𝘰𝘥𝘦𝘭.
Based on interim reports from @Mandiant and @SlowMist_Team, here’s what happened:
→ A flaw in a third-party security product gave the attacker access 24 days before the theft.
→ A reused employee identity opened the way to the wallet server.
→ A withdrawal tool bypassed its own risk checks.
→ Bitget’s wallets signed the transfers as legitimate withdrawals.
→ $203 million moved across five chains in nine seconds.
→ Signing continued for 2h39 after the alert. Bitget stopped customer withdrawals, not the attacker.
The problem wasn’t key storage. It was who the signer trusted.
The signer checked where the request came from, not whether it was authorized. It had no proof that a person approved the transfer or that the destination and amount matched the approved instruction.
You can reduce this risk by:
✔️ Checking authority, not just origin.
✔️ Separating policy decisions from systems an attacker could compromise.
✔️ Requiring a client-controlled credential.
✔️ Limiting the warm tier with allowlists, quorums and velocity limits.
✔️ Practising how to stop signing independently of customer withdrawals.
But no vendor can eliminate every risk. Our analysis explains what providers can prevent, what clients must control, and what risks remain.
🛡️ Questions? [email protected]
📖 Read the analysis: dfns.co/article/the-bitget-h…
⌨️ Start building: app.dfns.io/get-started
Christopher Grilhault des Fontaines retweeted
On September 24, @bitget lost $387.5 million. But no key was stolen.
The attacker took control of the server that told the signer what to sign, and the signer obeyed.
Our CISO, Thibault de Lachèze-Murel, breaks down the Bitget hack:
𝘞𝘩𝘢𝘵 𝘩𝘢𝘱𝘱𝘦𝘯𝘦𝘥, 𝘸𝘩𝘪𝘤𝘩 𝘤𝘰𝘯𝘵𝘳𝘰𝘭𝘴 𝘧𝘢𝘪𝘭𝘦𝘥, 𝘸𝘩𝘢𝘵 𝘵𝘰 𝘤𝘩𝘢𝘯𝘨𝘦, 𝘢𝘯𝘥 𝘸𝘩𝘢𝘵 𝘳𝘪𝘴𝘬𝘴 𝘳𝘦𝘮𝘢𝘪𝘯 𝘪𝘯 𝘰𝘶𝘳 𝘰𝘸𝘯 𝘮𝘰𝘥𝘦𝘭.
Based on interim reports from @Mandiant and @SlowMist_Team, here’s what happened:
→ A flaw in a third-party security product gave the attacker access 24 days before the theft.
→ A reused employee identity opened the way to the wallet server.
→ A withdrawal tool bypassed its own risk checks.
→ Bitget’s wallets signed the transfers as legitimate withdrawals.
→ $203 million moved across five chains in nine seconds.
→ Signing continued for 2h39 after the alert. Bitget stopped customer withdrawals, not the attacker.
The problem wasn’t key storage. It was who the signer trusted.
The signer checked where the request came from, not whether it was authorized. It had no proof that a person approved the transfer or that the destination and amount matched the approved instruction.
You can reduce this risk by:
✔️ Checking authority, not just origin.
✔️ Separating policy decisions from systems an attacker could compromise.
✔️ Requiring a client-controlled credential.
✔️ Limiting the warm tier with allowlists, quorums and velocity limits.
✔️ Practising how to stop signing independently of customer withdrawals.
But no vendor can eliminate every risk. Our analysis explains what providers can prevent, what clients must control, and what risks remain.
🛡️ Questions? [email protected]
📖 Read the analysis: dfns.co/article/the-bitget-h…
⌨️ Start building: app.dfns.io/get-started
I'm joining @stabledash Live today at 3:00 PM ET to make the case that @dfnsHQ will always be a pure technology service provider.
xitter.cf/i/broadcasts/1DGLdZLkO…
Done ✅
🌐 Turn fiat payments into stablecoins cross 113+ countries.
Today, we’re launching 𝗣𝗮𝘆𝗶𝗻𝘀 on DFNS, starting with @borderlessxyz.
Until now, bringing fiat into a stablecoin operation meant leaving the platform. Separate portals, manual wallet mapping, and reconciliation between bank statements and blockchain transactions.
That changes with Payins ✔️
Now, you can:
1️⃣ Select the wallet where your stablecoins should arrive.
2️⃣ Enter the amount, country, and payment method.
3️⃣ Review the quote and sign with a passkey.
4️⃣ Send fiat to the bank details provided.
✅ Done! Any stablecoin in your wallet.
Through one API, we connect you to 19+ locally licensed payment providers, such as Cobre, Capa, Triple-A, Stripe, MoonPay, Walapay, and more, across 72+ currencies.
USD, EUR, GBP. MXN, BRL, COP, ARS. NGN, KES, ZAR. INR, PHP, AED.
No FX markups. A flat platform fee. Funds settle directly with the providers.
On DFNS, every payin has a status, an audit trail, and a destination governed by the same policy engine as the rest of your operations.
That’s what onchain core banking is for.
📖 Read it: dfns.co/article/payins
⌨️ Start building: app.dfns.io/get-started
Christopher Grilhault des Fontaines retweeted
Manage subsidiaries, teams, and clients from one place.
That's Tenants, and our CPO Chris Sutton shows the dashboard in under two minutes.
In the demo, he:
1️⃣ opens the Tenant and sees every Org (including one he has no access to because it belongs to a client or runs a workflow he shouldn't touch).
2️⃣ switches from the Tenant view into an Org’s dashboard and back. No need to re-login.
3️⃣ suspends an Org directly from the console, disabling all access in one action.
4️⃣ creates a new Org and assigns it a key store from the ones already configured or adding a new one.
5️⃣ archives it, then restores it (in regulated finance, you should never face an irreversible delete).
That's the shape of control from above:
✔️ See the whole estate
✔️ Reach only what you're meant to
✔️ Act on any part of it without touching the rest.
One passkey across every Org. One console for lifecycle, key stores, and access. Boundaries are as hard as you define them.
That's what onchain core banking is for.
🔘 Watch the demo: youtu.be/YQDTeLsbyn4
📖 Read the announcement: dfns.co/article/introducing-…
⌨️ Start building today: app.dfns.io/get-started
Christopher Grilhault des Fontaines retweeted
Here's where DFNS will be in November:
🇭🇰 Felix Eigelshoven leads our delegation at Hong Kong FinTech Week, from November 2 to 6.
🇳🇱 Donald Brouwer heads to Bitcoin Amsterdam on November 5 and 6.
🇬🇧 Then Donald joins Benoit Boudier in London for Digital Asset Summit 2026, from November 10 and 11.
🇨🇭 Midweek, Donald and Benoit join Clarisse Hagège and Christopher Grilhault des Fontaines for The Geneva Summit by The Big Whale, on November 12 and 13. DFNS is a premier sponsor and Clarisse leads a workshop wondering whether banks should build onchain infrastructure or not.
🇺🇸 The same week, Jared Klee and Andrew Pisano will attend the Digital Asset Forum in NY on November 13.
🇬🇧 And Benoit closes the month at Solana Breakpoint in London, November 15 to 17.
If you’re looking for the technology and partners to get started with digital assets and modernize your core for tokenized finance, get in touch.
📅 Meet us on the road: [email protected]
⌨️ Start building today: app.dfns.io/get-started
Done ✅
🆕 @dfnsHQ now supports @circle's CCTP on @StellarOrg.
The world's largest cash-to-stablecoin network just got connected to institutional USDC liquidity everywhere from DFNS.
Native USDC moves between Stellar in one governed transfer. The USDC that arrives is the same Circle-issued asset on both sides.
No wrapped variant. No third-party bridge. No custodian in the middle.
Now the flows that took two platforms run in one:
✔️ Collect USDC on Ethereum or Base, move it to Stellar, and pay out through their cash network.
✔️ Hold one USDC balance sheet and settle wherever with no liquidity pre-positioned on every network.
✔️ Deploy Stellar USDC on Solana or Ethereum when a counterparty requires it, bring it home for payouts
Use the same DFNS integration as any other CCTP route:
1️⃣ select Circle CCTP in Swaps
2️⃣ pick your wallets, review
3️⃣ sign with a passkey or an API call
4️⃣ Stellar’s address encoding and USDC precision are handled automatically.
Fiat in through Circle Mint. USDC across chains via CCTP. Cash out on Stellar.
That's what onchain core banking is for.
📖 Read it: dfns.co/article/cctp-support…@
⌨️ Start building today: app.dfns.io/get-started
Done ✅
🆕 @dfnsHQ now supports @circle's CCTP on Arc.
Just three weeks after Arc’s mainnet launch, you can now move native USDC to and from Arc.
USDC moves directly between Arc and every other CCTP-supported network. The USDC that arrives on Arc is native USDC and can be used to pay network fees. No wrapped tokens. No third-party bridge. No custodian in the middle.
Flows that once required two platforms can now run in one:
✔️ Hold USDC on Ethereum or Solana, move it to Arc when a counterparty settles there, settle in under a second, then move the proceeds back to treasury.
✔️ Issue tokenized assets on Arc and fund subscriptions with USDC from any supported chain.
✔️ Settle on Arc and pay out on Stellar, with CCTP connecting the two.
Circle Mint moves fiat in and out. CCTP moves USDC across chains. Arc handles settlement.
Use the same DFNS integration as any other CCTP route:
1️⃣ open Circle CCTP in Swaps
2️⃣ select your wallets
3️⃣ sign with a passkey or use an API call.
That’s what onchain core banking is for.
📖 Read it: dfns.co/article/cctp-support…
⌨️ Start building: app.dfns.io/get-started
Six years ago, DFNS was named "Xkey."
It was an MPC company. Threshold signatures, key shares, the math that lets several machines sign without any of them ever holding a key, etc.
We were, by category, a key management system.
Over the years, we outgrew that category. Our clients' problems got bigger, so did we. They needed an entirely new operating system between their business and the world, so we built it.
Building that layer is what turned DFNS into a core banking platform, and it's why we now find ourselves at the intersection of finance and technology rather than in a tooling niche beside it.
However, 𝚠̲𝚎̲ ̲𝚗̲𝚎̲𝚟̲𝚎̲𝚛̲ ̲𝚕̲𝚎̲𝚏̲𝚝̲ ̲𝙼̲𝙿̲𝙲̲ ̲𝚋̲𝚎̲𝚑̲𝚒̲𝚗̲𝚍̲...
MPC is the heartbeat of the new financial account layer.
Six years in, after measuring every serious protocol in production and watching audited code leak keys in the wild, we still believe MPC is the best key management technology in today's marketplace.
Not for everything, obviously. The handbook names the use cases where MPC loses too, and where DFNS uses instead HSMs, TEEs, and other KMS types.
Thank you to our scientific advisors @SmartCryptology @jon_katz @chelseakomlo and our team Antoine Urban, Denis Varlakov, Nikita Sorokovikov, Thibault Murel, Noah Cornwell, Brian KimJohnson, Thibaud Genty who runs threshold signing for over 500 institutions.
It's the handbook we wished existed when we started, written by the people who had to learn it the hard way. We hope it will come in handy!
📧 Email me if the handbook omits anything: [email protected]
➡️ Download here: dfns.co/handbook/multi-party…
Finance is moving onchain faster than anyone is writing the manual.
Stablecoins settle a trillion dollars a month. Banks that ran pilots two years ago run production today.
Yet, the multi-party cryptography that makes any of it safe is understood by a few hundred people on earth. That’s a serious problem. The marketing noise and vendor slides piled on top of it make it worse.
📖 Nobody wrote the handbook for MPC…
So we did. It's titled 𝙈𝙪𝙡𝙩𝙞-𝙋𝙖𝙧𝙩𝙮 𝘾𝙤𝙢𝙥𝙪𝙩𝙖𝙩𝙞𝙤𝙣.
42,000 words. 97 pages. 22 chapters.
Written with Antoine Urban, @SmartCryptology, Thibault de Lachèze-Murel, Noah Cornwell, and reviewed line by line by the people who run threshold signing in production for over 500 institutions.
A sneak peek:
→ The protocols compared on numbers we measured ourselves
→ The attacks that leaked keys from audited code, explained plainly
→ The chapters nobody publishes about what to do at 3 a.m.
→ The regulatory map across five regions
→ What an examiner will ask you in 2027
And the part most vendors avoid saying: where MPC loses ❌
To hardware. To transparency. To its own operators.
20% of all Bitcoin was lost due to key loss in this industry's first decade. The next decade, where finance lives onchain, cannot be built the same way.
Read it. Argue with it. Share it with your team.
📩 Dowload the handbook: dfns.co/handbook/multi-party…
⌨️ Start building today: app.dfns.io/get-started
Christopher Grilhault des Fontaines retweeted
👁️ Your SOC finally gets to watch what happens on DFNS.
SIEM Export streams your organization's audit events straight into your log manager, starting with @datadoghq Cloud SIEM.
Our CPO Chris Sutton shows the whole flow in about a minute.
In the demo, he:
1️⃣ Toogles on the Datadog integration: selects a Datadog site, adds an API key, and sets tags that ride on every forwarded event so analysts can find them instantly.
2️⃣ Initiates a transaction that trips a policy, then approves it, signed with a passkey
3️⃣ Switches to Datadog showing the policy decision which is already there with the forwarded evaluation from the DFNS audit log.
Every privileged action signed on DFNS (e.g., create a wallet, move funds, export a key, change a policy) lands in your SIEM with a status the same moment it gets resolved. The denied ones are the signal that reveals stolen credentials or insider testing limits.
We never block the actions that are observed. They run on an isolated channel so a SIEM outage can't touch your webhooks and your API key is encrypted and never logged.
Webhooks build. SIEM Export defends. And when your SOC sees something, the same API lets you act by suspending an Organization, revoking a user and every permission with them, or by tightening a policy.
That's what onchain core banking is for.
🔘 Watch the demo: youtu.be/dPG6WJkDWGw
📖 Read it: dfns.co/article/siem-export
⌨️ Start building today: app.dfns.io/get-started
Christopher Grilhault des Fontaines retweeted
In 2014, he built the exchange data partnerships behind @CMEGroup's crypto reference rates.
3 years before CME listed its first Bitcoin future. That's the kind of early we like.
Welcome @APisano13, our new VP of Sales, leading DFNS across the US.
Andrew has spent 20 years building the markets that followed:
1️⃣ Helped launch one of the world's first environmental derivatives exchanges, took its client base from zero to 25+ global banks, and advised California on its cap-and-trade framework
2️⃣ Spearheaded CME Group's exploration of crypto and DLT, and commercialized one of the first gold tokenization projects with The Royal Mint
3️⃣ At @digitalasset, converted enterprise blockchain pilots into $5M of recurring contracts with institutions
4️⃣ At Xpansiv and Fiùtur, launched tokenized commodity registries, secured the IATA partnership behind the Aviation Carbon Exchange, and led planning for a New York DFS-regulated trust company
The reference rates, registries, post-trade plumbing, and regulatory relationships that turn a promising instrument into something a Tier 1 balance sheet will actually hold.
That's the work in front of @dfnsHQ in the US.
Welcome, Andrew. 🤝
You'll find him at DC Fintech Week, Money20/20, and The Bridge in New York over the coming weeks.
📖 Read the announcement: dfns.co/article/welcome-andr…
📮 Apply today: jobs.deel.com/dfns
Very excited about this partnership!
🌏 They service 200,000 businesses in 200+ countries.
Now running on DFNS 🤝
@PhotonPay and @dfnsHQ have partnered to strengthen the infrastructure behind their growing stablecoin payment capabilities.
PhotonPay is the payment stack global commerce runs on with multi-asset wallets, global checkout, card issuing, global payout, on/off ramp, FX management, and embedded finance.
One platform for marketplaces, exporters, digital entertainment, agencies, and AI-native businesses.
This year, they made stablecoins a working rail:
→ One wallet for fiat and stablecoin, dual-rail payouts settled instantly
→ Recurring billing across fiat and stablecoin at ~0.8% versus 2.9% plus fixed fees on legacy cards
→ Stablecoins behind enterprise clearing, i.e., treasury teams get near-real-time settlement and steep cost cuts, but never touch a blockchain
An invisible rail has to be flawless underneath, and that's DFNS:
✔️ Stablecoin wallets provisioned programmatically for every business
✔️ End-to-end transaction lifecycle managed across 100+ networks
✔️ Policies, limits, allowlists, quorums, and screening before signing
✔️ Payment-grade reliability at near-zero failure on rails ran by Stripe
"𝘖𝘶𝘳 𝘱𝘢𝘳𝘵𝘯𝘦𝘳𝘴𝘩𝘪𝘱 𝘸𝘪𝘵𝘩 𝘋𝘍𝘕𝘚 𝘮𝘦𝘢𝘯𝘴 𝘵𝘩𝘦 𝘥𝘪𝘨𝘪𝘵𝘢𝘭 𝘢𝘴𝘴𝘦𝘵 𝘭𝘢𝘺𝘦𝘳 𝘣𝘦𝘯𝘦𝘢𝘵𝘩 𝘰𝘶𝘳 𝘴𝘵𝘢𝘣𝘭𝘦𝘤𝘰𝘪𝘯 𝘤𝘢𝘱𝘢𝘣𝘪𝘭𝘪𝘵𝘪𝘦𝘴 𝘮𝘦𝘦𝘵𝘴 𝘵𝘩𝘦 𝘴𝘢𝘮𝘦 𝘪𝘯𝘴𝘵𝘪𝘵𝘶𝘵𝘪𝘰𝘯𝘢𝘭 𝘴𝘵𝘢𝘯𝘥𝘢𝘳𝘥 𝘢𝘴 𝘦𝘷𝘦𝘳𝘺𝘵𝘩𝘪𝘯𝘨 𝘦𝘭𝘴𝘦 𝘸𝘦 𝘳𝘶𝘯," explained Gabriel J Pan, PhotonPay's Head of Global Partnership and Global Expansion. "𝘛𝘩𝘢𝘵'𝘴 𝘯𝘰𝘵 𝘢 𝘱𝘳𝘰𝘥𝘶𝘤𝘵 𝘥𝘦𝘤𝘪𝘴𝘪𝘰𝘯. 𝘐𝘵'𝘴 𝘵𝘩𝘦 𝘧𝘰𝘶𝘯𝘥𝘢𝘵𝘪𝘰𝘯 𝘧𝘰𝘳 𝘸𝘩𝘢𝘵 𝘨𝘭𝘰𝘣𝘢𝘭 𝘱𝘢𝘺𝘮𝘦𝘯𝘵𝘴 𝘭𝘰𝘰𝘬𝘴 𝘭𝘪𝘬𝘦 𝘰𝘷𝘦𝘳 𝘵𝘩𝘦 𝘯𝘦𝘹𝘵 𝘥𝘦𝘤𝘢𝘥𝘦."
That's what onchain core banking is for.
Welcome to DFNS, PhotonPay. 🤝
📖 Read the announcement: dfns.co/article/announcing-p…
⌨️ Start building today: app.dfns.io/get-started
🔥
Finance is about to have its HTTP moment.
Over 30 years ago, a protocol rewired how information moves, and every business had to rethink itself.
The same rewiring is now reaching money.
Stablecoins, tokenized deposits, tokenized funds, settlement in seconds, markets that never close. Finance is undergoing massive transformation.
It can be hard to keep up. Harder still to know exactly how to rethink a business as it moves onchain.
𝘞𝘩𝘪𝘤𝘩 𝘱𝘳𝘰𝘥𝘶𝘤𝘵𝘴? 𝘞𝘩𝘪𝘤𝘩 𝘰𝘱𝘦𝘳𝘢𝘵𝘪𝘯𝘨 𝘮𝘰𝘥𝘦𝘭? 𝘞𝘩𝘪𝘤𝘩 𝘤𝘰𝘯𝘵𝘳𝘰𝘭𝘴? 𝘞𝘩𝘪𝘤𝘩 𝘱𝘢𝘳𝘵𝘯𝘦𝘳𝘴? 𝘐𝘯 𝘸𝘩𝘪𝘤𝘩 𝘰𝘳𝘥𝘦𝘳?
The truth is nobody has the full map. But whatever the sequence, whatever the pace, you must be 𝙧𝙚𝙖𝙙𝙮.
And ready starts with being equipped: The accounts, the transaction processing, the treasury, the policy enforced, the secure signing, the data integrity, the nodes, the evidence a supervisor accepts, and more.
That's what we made this film about.
🤝 Book time with the team: [email protected]
📅 Full calendar: luma.com/dfns
⌨️ Start building today: app.dfns.io/get-started
🔘 Watch the trailer: youtu.be/tU9rW_vb1ko