Further

Further is a global investment platform connecting pioneering financial infrastructure with global capital markets.

[Further @further]

ABEX (@abexcapital) welcomes @further Asset Management as a strategic investor to advance institutional digital asset trading standards.

Full release 👉https://t.co/5Em7HUge7e

[Further @further]

In this segment from the #FurtherNetworkSummit 2025, Matthew White, CEO @varadubai, explains how regulatory clarity in Dubai is designed to give companies legal certainty locally👇

[Twinstake @twinstake_io]

Should Ethereum fund its developers by redirecting validator rewards?

Our CEO Andrew Gibb told @Cointelegraph's @christinacomben it would narrow the addressable staking market, with reward-sensitive allocators likely to reassess.

[DFNS @dfnsHQ]

🚨 What happens to your assets if your infra gets breached?

For most vendors, that's a very uncomfortable question. Not for @dfnsHQ.

Today, we’re introducing 𝗩𝗮𝗹𝗶𝗱𝗮𝘁𝗶𝗼𝗻 𝗚𝗮𝘁𝗲 ✨

It’s a final checkpoint for every action that runs inside your infrastructure (not ours).

DFNS already enforces policies before anything is signed: approval quorums, limits, allowlists, screening. For most institutions, that's exactly the control they need.

But those checks run inside DFNS infrastructure. So the most security-minded institutions ask:
𝘸𝘩𝘢𝘵 𝘪𝘧 𝘋𝘍𝘕𝘚 𝘪𝘵𝘴𝘦𝘭𝘧 𝘪𝘴 𝘤𝘰𝘮𝘱𝘳𝘰𝘮𝘪𝘴𝘦𝘥?

Validation Gate closes that gap.

It gives you a last check, performed on your own infrastructure, right before a signature is produced. Even if an attacker reached the signing layer directly, you can detect the request and stop the signature.

Because the check runs inside your own environment, it doesn't depend on DFNS being intact.

It doesn't replace our Policy Engine. It complements it.

Rich, business-level policies can live inside DFNS, while a final, sovereign checkpoint at the moment of signing runs inside your infrastructure that we cannot touch.

For an institution whose mandate is to trust no single party with its assets, that's the difference between a strong control model and a complete one.

🟢 Available now for both MPC and HSM-based deployments, on-premise or hybrid.

📑 Read it: https://t.co/YADqTGO9Mq
📩 Talk to our team: [email protected]

[Further @further]

In this week’s #WeAreHiring series, we’re highlighting two roles from @pave_bank and @grvt_io!

1️⃣@pave_bank Senior QA Automation Engineer 👉https://t.co/kmwDLX8qQv

2️⃣@grvt_io Marketing Designer 👉https://t.co/6NGasw904U

[Twinstake @twinstake_io]

Staking and DeFi are often grouped together.

The underlying risk profile is not the same.

Two positions can offer similar returns while behaving very differently under stress.

That’s why understanding the character of the risk matters as much as the headline number.

👇

[Fuze @fuzefinance]

Institutional-grade security is no longer optional in digital assets.

We're proud to announce our strategic partnership with @HalbornSecurity to help banks and fintechs launch secure, compliant digital asset services.

Regulated infrastructure meets best-in-class security.

[DFNS @dfnsHQ]

🌍 @dfnsHQ is on the road this summer.

If you're rethinking how your institution holds, moves, and governs digital assets, come say hello 👇

🇨🇭 Point Zero Forum in Zurich
June 23–25 · https://t.co/kXUlfuZKgY
Meet: Thibault Murel and @donald_brouwer

🇺🇸 Fintech Cookout in New York
July 16 · DM us
Meet: @christophergdf, @clarisse_hagege, and @KleeBeard

🇧🇷 Blockchain Rio in Rio de Janeiro
August 12–13 · https://t.co/9s7pA84XKc
Meet: Leandro Pereira

🇮🇩 Coinfest Asia in Bali
August 20–21 · https://t.co/OhHaSDFY0B
Meet: Felix Eigelshoven

🇧🇷 Febraban Tech in São Paulo
August 24–26 · https://t.co/OaeO61ffrX
Meet: Leandro Pereira

Stablecoin settlement, tokenization, treasury, cross-border payments: wherever you are on that journey, we'd love to show you what a 𝘤𝘰𝘳𝘦 𝘣𝘢𝘯𝘬𝘪𝘯𝘨 𝘱𝘭𝘢𝘵𝘧𝘰𝘳𝘮 𝘧𝘰𝘳 𝘥𝘪𝘨𝘪𝘵𝘢𝘭 𝘢𝘴𝘴𝘦𝘵𝘴 makes possible.

📅 Book time with our team: [email protected]

[DFNS @dfnsHQ]

🆕 DFNS now supports @movement_xyz

$685 billion moves across borders every year. Most of it still takes 3–5 days to settle.

Stablecoins have now reached $265 billion in circulation. The asset layer is here. The next requirement is a settlement layer fast enough to move digital dollars at institutional scale.

Movement is built for that purpose: fast, low-cost settlement with finality. But for institutions, settlement speed is only one part of the equation.

Production requires accounts, controls, workflows, audit logs, secure signing, and policy enforcement across the full transaction lifecycle.

That is where @dfnsHQ comes in ✨

On top of Movement, and across every network we support, DFNS provides the operating layer institutions need to run financial products in production:

✔️ Transaction management from intent to finality
✔️ Treasury and tokenization to manage balances and service assets

📑 Read more: https://t.co/aXtGYCvdKo
⌨️ Start building today on DFNS: https://t.co/EaYdvatcvM

[Twinstake @twinstake_io]

We're at @DutchBlockWeek. Ross Derrick is in Amsterdam this week, 24–25 June at the Johan Cruijff ArenA.

Allocating to or building around institutional staking? Find him at the venue or reply here to set up a chat.

[DFNS @dfnsHQ]

🆕 DFNS now accepts inbound assets through one operation.

On many chains, a wallet can't just receive an asset. It has to opt in before it can hold it.

Send USDC to a wallet that hasn't opted in, and the payment simply fails ⛔

Every chain does this differently:
@CantonNetwork → 𝘁𝗿𝗮𝗻𝘀𝗳𝗲𝗿 𝗽𝗿𝗲𝗮𝗽𝗽𝗿𝗼𝘃𝗮𝗹
@StellarOrg → 𝗖𝗵𝗮𝗻𝗴𝗲𝗧𝗿𝘂𝘀𝘁 (𝗮 𝘁𝗿𝘂𝘀𝘁𝗹𝗶𝗻𝗲)
@XRPLF → 𝗧𝗿𝘂𝘀𝘁𝗦𝗲𝘁 (𝗮 𝘁𝗿𝘂𝘀𝘁𝗹𝗶𝗻𝗲)
@Algorand → 𝗮𝘀𝘀𝗲𝘁 𝗼𝗽𝘁-𝗶𝗻
@hedera → 𝗧𝗼𝗸𝗲𝗻𝗔𝘀𝘀𝗼𝗰𝗶𝗮𝘁𝗲

That's five different mechanisms to implement and maintain, just to let wallets hold assets.
We unified them into one.

With a single operation, 𝘈𝘤𝘤𝘦𝘱𝘵𝘐𝘯𝘣𝘰𝘶𝘯𝘥𝘈𝘴𝘴𝘦𝘵, @dfnsHQ constructs the right transaction for each chain, signs it, and broadcasts it. You provide the asset, we handle the per-chain mechanics.

For institutions, it's the prerequisite that makes inbound token transfers and distribution actually land. And it's controlled like any other transactions, so which wallets can hold which assets stays auditable.

📖 Read the full breakdown: https://t.co/szqdLAuzXm
📑 Explore the docs: https://t.co/F6VhwvDEz0
🛠️ Start building: https://t.co/EaYdvasEGe

[Fuze @fuzefinance]

Fuze Finance is heading to #iFXExpo Cyprus.

Jonathan Rigg will be meeting with industry leaders to discuss stablecoin infrastructure, institutional crypto adoption, and OTC liquidity.

If you're attending, let's connect.

#FuzeFinance #Stablecoins #DigitalAssets

[DFNS @dfnsHQ]

Payments company @stables_money has chosen @dfnsHQ 🖊️ ☑️

Stables is building something hard: one API to collect, convert, and move money across Asia and MENA.

What used to take five banking vendors stitched together, collection, conversion, settlement, compliance, Stables delivers in a single integration a developer can ship in an afternoon.

The scale is already real:
→ $2B+ in annual USDt volume
→ 160+ markets
→ Under 1h to settle on average
→ 99.99% uptime, SOC 2, FATF travel rule, PCI-DSS

Stables moved from Fireblocks to DFNS for reasons that map directly to running payments at scale:

✔️ 𝗔𝗻 𝗔𝗣𝗜, 𝗻𝗼𝘁 𝗮 𝗱𝗮𝘀𝗵𝗯𝗼𝗮𝗿𝗱 𝘄𝗶𝘁𝗵 𝗮𝗻 𝗔𝗣𝗜 𝗮𝘁𝘁𝗮𝗰𝗵𝗲𝗱. Every capability is programmable. Integrate once, access everything, automate your flows, add corridors by configuration.

✔️ 𝗥𝗲𝗹𝗶𝗮𝗯𝗶𝗹𝗶𝘁𝘆 𝗮𝘁 𝗽𝗮𝘆𝗺𝗲𝗻𝘁𝘀 𝘀𝗰𝗮𝗹𝗲. A failed payment isn't a retry, it's a lost client. DFNS runs its node infra companies like Stripe rely on for thousands of daily transactions at near-zero failure rates.

✔️ 𝗣𝗿𝗶𝗰𝗶𝗻𝗴 𝘁𝗵𝗮𝘁 𝘀𝗰𝗮𝗹𝗲𝘀 𝘄𝗶𝘁𝗵 𝘁𝗵𝗲 𝗯𝘂𝘀𝗶𝗻𝗲𝘀𝘀. No fees on assets under custody, no cut of transaction volume. We're a technology provider, not a financial institution.

DFNS, as their new core wallet layer, enables Stables to focus on what makes them uniquely valuable: virtual accounts, quote-first transfers, embedded compliance, and AI-operated payments.

Proud to power you, Stables. 🤝

📑 Read the announcement: https://t.co/bsbvfWBXhu
⌨️ Start building: https://t.co/EaYdvasEGe

[Finternet @Finternetasia]

Why does Asia prioritize API-first?

Felix Eigelshoven, Head of APAC & Global Partnership Strategy lead at @dfnsHQ explains 👇

[DFNS @dfnsHQ]

🟢 @dfnsHQ now supports @circle's CCTP.

USDC is issued on many chains. But sometimes you need to move a dollar between chains.

Today, moving USDC across chains usually means leaving your platform…

Bridging through a third-party UI, holding native gas on the destination to claim it, accepting a wrapped version instead of real USDC, waiting on unpredictable finality, and so forth.

For an institution, that's custody exposure to a bridge and a workflow you can't govern or automate.

We removed all of it ✨

With one API call from a source wallet, USDC now moves natively across chains and lands in a destination wallet on DFNS.

Across EVM to EVM, EVM to Solana, and Solana to EVM.

𝘞𝘰𝘳𝘵𝘩 𝘯𝘰𝘵𝘪𝘯𝘨: cross-chain moves follow the same DFNS transaction lifecycle. Approvals, limits, allowlists, and screening happen before signing, so USDC movements across chains remain controlled, auditable, and inside your policy framework.

⏭️ Next: deeper Circle support, with USDC minting into DFNS wallets.

📑 Read the announcement: https://t.co/ikBogNSgaO
⌨️ Start building: https://t.co/EaYdvasEGe

[DFNS @dfnsHQ]

A freelancer in Manila earns $5,000 from a US client 🇺🇲→ 🇵🇭

Her local bank takes up to 8% to receive it…

@SmashPayX fixes that. And they're building it on @dfnsHQ.

SmashPay is a USD account for the people the traditional system serves the worst: freelancers, remote workers, and distributed teams who earn in dollars but live outside the US.

Stablecoins are the rail underneath, the way ACH sits under a payments app.

That's where DFNS comes in ✨

For a product like this, the layer that holds balances, moves money across rails, and enforces the controls a regulated business needs isn't a back-office detail.

DFNS gives SmashPay that layer as one system:

✔️ A wallet for every user, provisioned invisibly to smooth the experience.
✔️ The transaction processing behind multi-rail sends and batch payouts.
✔️ Treasury tooling to manage USD balances.
✔️ Policy and governance that screen and approve before anything moves.

This is what onchain core banking platform is for.

Welcome to DFNS, SmashPay. 🤝

📑 Read the full story: https://t.co/8VCgRIt8Sl
⌨️ Get started today. https://t.co/ogU5abTrDV

[Further @further]

@dfnsHQ @circle 7/▪️@ZodiaCustody CEO Julian Sawyer on Forum Stage at Point Zero Forum Zurich on June 23 (👉https://t.co/Au4dFvIz96)

#FurtherSignal

[Further @further]

1/▪️@dfnsHQ now supports @circle's CCTP (👉https://t.co/QwBIviE5qR)
▪️@dfnsHQ participates in FinTech Innovation Lab Demo Day at @BNY (👉https://t.co/t4fAWB6lSj)

[DFNS @dfnsHQ]

🟢 @dfnsHQ now supports @circle's CCTP.

USDC is issued on many chains. But sometimes you need to move a dollar between chains.

Today, moving USDC across chains usually means leaving your platform…

Bridging through a third-party UI, holding native gas on the destination to claim it, accepting a wrapped version instead of real USDC, waiting on unpredictable finality, and so forth.

For an institution, that's custody exposure to a bridge and a workflow you can't govern or automate.

We removed all of it ✨

With one API call from a source wallet, USDC now moves natively across chains and lands in a destination wallet on DFNS.

Across EVM to EVM, EVM to Solana, and Solana to EVM.

𝘞𝘰𝘳𝘵𝘩 𝘯𝘰𝘵𝘪𝘯𝘨: cross-chain moves follow the same DFNS transaction lifecycle. Approvals, limits, allowlists, and screening happen before signing, so USDC movements across chains remain controlled, auditable, and inside your policy framework.

⏭️ Next: deeper Circle support, with USDC minting into DFNS wallets.

📑 Read the announcement: https://t.co/ikBogNSgaO
⌨️ Start building: https://t.co/EaYdvasEGe

[Further @further]

@dfnsHQ @circle 5/▪️@TheiaInsights welcomes Jonathan Strauss as Regional Sales Director for North America (👉https://t.co/kEVr0gGFhf)

▪️@ZodiaCustody CEO Julian Sawyer on stage at The Network Forum Annual Meeting in Paris (👉https://t.co/fsRcWj1WwP)

[Further @further]

@dfnsHQ @circle 3/▪️@dfnsHQ now supports HashSphere — @Hashgraph's private permissioned network built with @hedera technology (👉https://t.co/yP9Acgv54O)

4/▪️@fuzefinance CEO @Moaliyusuf joined the "Digital-First Pioneers" fireside at @hub71ad Impact Event 2026 (👉https://t.co/zrDMyU65Co)

[DFNS @dfnsHQ]

🟢 @dfnsHQ now supports HashSphere.

HashSphere is @hashgraph's private, permissioned network built with @hedera technology.

It’s designed for institutions that need both the control of a private ledger and Hedera-grade performance.

✔️ Permissioned by design, limited to verified institutions
✔️ Data residency, privacy, and internal governance
✔️ EVM compatibility and core Hedera services
✔️ Public interoperability with Hedera mainnet

But a permissioned ledger only answers one question for a bank:
𝘸𝘩𝘦𝘳𝘦 𝘥𝘰 𝘮𝘺 𝘵𝘳𝘢𝘯𝘴𝘢𝘤𝘵𝘪𝘰𝘯𝘴 𝘴𝘦𝘵𝘵𝘭𝘦, 𝘱𝘳𝘪𝘷𝘢𝘵𝘦𝘭𝘺 𝘢𝘯𝘥 𝘤𝘰𝘮𝘱𝘭𝘪𝘢𝘯𝘵𝘭𝘺?

It doesn't answer the other half of it:
𝘩𝘰𝘸 𝘥𝘰 𝘐 𝘳𝘶𝘯 𝘧𝘪𝘯𝘢𝘯𝘤𝘪𝘢𝘭 𝘱𝘳𝘰𝘥𝘶𝘤𝘵𝘴 𝘰𝘯 𝘪𝘵, 𝘸𝘪𝘵𝘩 𝘵𝘩𝘦 𝘤𝘰𝘯𝘵𝘳𝘰𝘭𝘴 𝘮𝘺 𝘣𝘰𝘢𝘳𝘥, 𝘢𝘶𝘥𝘪𝘵𝘰𝘳𝘴, 𝘢𝘯𝘥 𝘳𝘦𝘨𝘶𝘭𝘢𝘵𝘰𝘳𝘴 𝘦𝘹𝘱𝘦𝘤𝘵?

That's the gap DFNS fills.

HashSphere is the network a bank settles on. DFNS is the core system that runs on top. Two systems built to institutional standards, meeting where regulated finance is heading.

HashSphere joins 60+ networks on DFNS, powering 400+ fintech and institutional clients globally.

🔗 Learn more: https://t.co/SlAByWONQ9
📩 Talk to our team: [email protected]

[Further @further]

@dfnsHQ @circle 2/▪️Payments company @stables_money choses @dfnsHQ (👉https://t.co/VRT4tPUHL9)
▪️@dfnsHQ now accepts inbound assets through one operation via AcceptInboundAsset (👉https://t.co/Md5LkZoaQW)

[DFNS @dfnsHQ]

🆕 DFNS now accepts inbound assets through one operation.

On many chains, a wallet can't just receive an asset. It has to opt in before it can hold it.

Send USDC to a wallet that hasn't opted in, and the payment simply fails ⛔

Every chain does this differently:
@CantonNetwork → 𝘁𝗿𝗮𝗻𝘀𝗳𝗲𝗿 𝗽𝗿𝗲𝗮𝗽𝗽𝗿𝗼𝘃𝗮𝗹
@StellarOrg → 𝗖𝗵𝗮𝗻𝗴𝗲𝗧𝗿𝘂𝘀𝘁 (𝗮 𝘁𝗿𝘂𝘀𝘁𝗹𝗶𝗻𝗲)
@XRPLF → 𝗧𝗿𝘂𝘀𝘁𝗦𝗲𝘁 (𝗮 𝘁𝗿𝘂𝘀𝘁𝗹𝗶𝗻𝗲)
@Algorand → 𝗮𝘀𝘀𝗲𝘁 𝗼𝗽𝘁-𝗶𝗻
@hedera → 𝗧𝗼𝗸𝗲𝗻𝗔𝘀𝘀𝗼𝗰𝗶𝗮𝘁𝗲

That's five different mechanisms to implement and maintain, just to let wallets hold assets.
We unified them into one.

With a single operation, 𝘈𝘤𝘤𝘦𝘱𝘵𝘐𝘯𝘣𝘰𝘶𝘯𝘥𝘈𝘴𝘴𝘦𝘵, @dfnsHQ constructs the right transaction for each chain, signs it, and broadcasts it. You provide the asset, we handle the per-chain mechanics.

For institutions, it's the prerequisite that makes inbound token transfers and distribution actually land. And it's controlled like any other transactions, so which wallets can hold which assets stays auditable.

📖 Read the full breakdown: https://t.co/szqdLAuzXm
📑 Explore the docs: https://t.co/F6VhwvDEz0
🛠️ Start building: https://t.co/EaYdvasEGe