• Bitdeer’s $36M Nevada factory will produce up to 10,000 SEALMINER rigs monthly by late 2026.

• The 187,000-square-foot Sparks facility becomes Bitdeer’s first U.S. manufacturing and assembly site.

• Record-low hash price continues squeezing Bitcoin mining margins after the 2024 halving and rising hashrate.

• Bitdeer mined 921 Bitcoin in May as its self-mining hashrate climbed to 70.2 EH/s year over year.

Bitdeer has started construction on a $36 million advanced electronics manufacturing facility in Sparks, marking its first U.S. manufacturing and assembly site. The project adds a domestic production base at a time when Bitcoin mining margins remain under heavy pressure.

According to an X post by WuBlockchain, the 187,000-square-foot Nevada factory is expected to be completed by the end of 2026 and produce up to 10,000 SEALMINER rigs each month. The site is also expected to create about 70 local jobs across engineering, skilled technician, and support roles.

Hash Price Slump Puts New Mining Capacity To The Test

The buildout comes as hash price, a key revenue measure for miners, remains near record-low levels. Hashrate Index showed spot hash price at about $29.81 per PH/s/day, while Luxor previously recorded a daily low of $27.89 on February 24. Luxor also noted that March posted a record-low monthly average of $31.27.

Those figures show how difficult the operating environment has become since the April 2024 halving. The event reduced block rewards, while a rising network hashrate and weak transaction-fee revenue further reduced income per unit of computing power.

As a result, profitability has become more concentrated among miners with low-cost electricity and newer machines. Older rigs, on the contrary, face longer payback periods, especially when revenue per unit of hashrate remains compressed.

To manage that pressure, Bitdeer is leaning further into vertical integration instead of relying only on outside hardware suppliers. The company has developed its own SEALMINER machines and has been deploying them across its self-mining fleet.

In April, it launched mass production of the SEALMINER A4 series, which has an efficiency of 9.45 joules per terahash. That matters as power efficiency is central to mining costs when Bitcoin production revenue is under pressure.

U.S. Manufacturing Push Expands Bitdeer’s Growth Strategy

The Nevada site also expands Bitdeer’s U.S. footprint beyond mining and data center operations. In addition, it will complement the company’s existing U.S. data centers and its innovation hub in San Jose, California.

Paul Hanson, chairman of Bitdeer Industrial, said the Sparks facility supports supply-chain resilience and brings production closer to U.S. customers. Similarly, Catherine Guo, CEO of Bitdeer Industrial, cited Nevada’s workforce, logistics network, and business environment as reasons behind the location.

The expansion follows a strong operational update for May. At the time, Bitdeer reported 921 Bitcoin mined during the month, a 370% increase from the same period last year. Its self-mining hashrate also reached 70.2 EH/s.

The company is also growing outside traditional mining. It reported about $69 million of annualized recurring revenue from its AI Cloud business. It further added that it was in advanced negotiations for a potential colocation tenant at its Tydal, Norway, site.

Bitdeer has additionally launched the SEALMINER DL1 Hydro, a hydro-cooling machine for Scrypt-algorithm mining. The unit supports networks such as Litecoin and Dogecoin, with a 52.5 GH/s hashrate and 149 J/GH efficiency.

The Nevada project therefore places manufacturing inside a broader operating strategy. For miners, the timing is difficult. For Bitdeer, the factory adds U.S. production capacity while the hardware market becomes more selective.

Key Takeaways

• Nasdaq 100 futures climbed 0.7%, S&P 500 futures gained 0.2%, Dow futures remained essentially unchanged
• Overnight military exchanges between US and Iran failed to dampen market sentiment significantly
• SK Hynix prepares for Thursday pricing with IPO demand reaching 7x available allocation
• Crude oil prices retreated modestly despite continued Middle East hostilities, Brent down to $77.75
• Pepsi quarterly results revealed consumer spending pullback amid economic uncertainty

US equity futures advanced during Thursday’s pre-market session as market participants set aside concerns over escalating US-Iran military actions and refocused on artificial intelligence opportunities.

The Nasdaq 100 futures contract rose 0.6%, while S&P 500 futures increased 0.2%. Dow futures showed minimal movement, edging up less than 0.1%.

Thursday’s gains represent a reversal from Wednesday’s turbulent trading. The Dow Jones Industrial Average plummeted nearly 600 points following President Trump’s declaration that the Iran ceasefire had concluded, triggering a spike in energy markets.

Military actions continued through the night. American forces conducted airstrikes against 90 Iranian installations. Iran retaliated with strikes targeting US-allied nations throughout the Middle East region.

Nevertheless, market sentiment showed signs of stabilization. Citi’s Scott Chronert characterized the move as a “short-term reversal,” noting Trump’s ongoing commitment to resolving the confrontation.

Oil prices moderated during Thursday’s early trading. Brent crude declined 0.4% to $77.75 per barrel while West Texas Intermediate dropped 0.3% to $73.26 per barrel.

Additionally, the US government terminated a temporary exemption on Iranian oil sanctions, which had contributed to Wednesday’s crude price surge.

Memory Chip Maker’s Nasdaq Listing Draws Strong Interest

Market focus is pivoting toward SK Hynix’s anticipated Nasdaq listing. The South Korean semiconductor manufacturer plans to finalize its US IPO pricing Thursday, with shares expected to begin trading Friday.

Subscription demand has reached seven times the available share count, demonstrating robust investor interest in AI-related semiconductor opportunities.

This listing follows recent volatility in chip equities that shook confidence in artificial intelligence investments. Market watchers are evaluating whether the IPO can reinvigorate sector momentum.

The 10-year Treasury yield decreased 1 basis point to 4.57%. The US dollar weakened 0.1% versus a currency basket as investors reduced safe-haven positioning.

Consumer Behavior and Economic Indicators

Pepsi released quarterly earnings revealing American consumers moderating discretionary spending. While revenue exceeded analyst projections, the figures highlighted increasing financial constraints stemming from economic volatility.

Weekly unemployment claims figures are scheduled for Thursday release and may shape interest rate expectations moving forward.

Gold recovered above the $4,100 threshold but confronts headwinds from a hawkish Federal Reserve posture. Bitcoin registered modest gains despite geopolitical turbulence, reacting to recently published Fed meeting minutes.

European equity markets opened higher as technology and financial sector shares rebounded. South Korea’s technology sector also advanced, with market observers predicting an extended semiconductor growth cycle.

As of Thursday’s pre-market session, Nasdaq 100 futures traded at 29,741.50 and S&P 500 futures stood at 7,545.

Strip Bitcoin and Ethereum out of the crypto market and what remains has shed almost a quarter of its value in the first half of 2026, falling to $666 billion while liquidity retreats into a handful of survivors. This is not a crash; crashes end. It is something slower and stranger: a depression in the long tail of crypto, with its own causes, its own refugees, and its own short list of assets that refuse to participate.

The number that best describes crypto in mid-2026 is not Bitcoin’s price. It is this one: the total market capitalization of every cryptocurrency except Bitcoin and Ethereum fell 22.84% in the first half of the year, down to $666.58 billion as of July 2. Bitcoin, for all its drama, a 21-month low of $58,188 in late June, a bounce back above $62,000, trades within a wide band it has occupied before. The long tail is somewhere it has not been in years: bleeding steadily, month after month, with no single catastrophic day to blame and no capitulation candle to mark a bottom.

The individual charts are grim in a way indexes flatten. Ethereum, the second pillar, just closed three consecutive red quarters for the first time in its history, down 28% in the second quarter alone to trade near $1,740, roughly 65% below its August 2025 peak. Solana sits in the high $70s to low $80s. Worldcoin fell 80% over seven months; Pi Network printed all-time lows 96% below its peak; MicroStrategy’s stock, the market’s favorite leveraged proxy, was the worst performer in the entire Nasdaq-100 last year and trades 85% below its 2024 high. The Fear and Greed Index touched 12 this month, readings last seen at the bottom of the previous cycle, and sentiment surveys read like obituaries.

And yet, scattered across the wreckage, a short list of assets is behaving as if none of this is happening: a perp exchange token near all-time highs, a lending token up 40% in a month on a buyback, a supposedly dead layer-1 up 31% in a week. The pattern of who is exempt is as informative as the destruction itself. This piece maps the altcoin depression properly: how the damage is distributed, the three structural forces that caused it and distinguish it from an ordinary bear market, the anatomy of the exceptions, the honest bull and bear cases for what comes next, and the historical precedents that both camps are quoting at each other.

Aave Labs, the organization behind the largest decentralized lending platform Aave AAVE$91.11, is rolling out vaults to help fintech companies offer yield on stablecoins without requiring users to interact directly with crypto rails.

The new Stable Vaults let wallets, exchanges and payment providers embed stablecoin earning through a single connection. Behind the scenes, the vaults allocate deposits across approved decentralized finance (DeFi) lending strategies while the customer continues using a familiar app interface.

“Stable Vaults make predictable stablecoin earning simple to plug into any fintech application,” Aave founder Stani Kulechov said in a statement.

The move comes as stablecoins has become increasingly part of everyday payments and digital banking. As more fintech firms adopt stablecoins for moving money globally, many are looking for ways to let customers earn a return on idle balances without leaving blockchain rails or navigating crypto-native applications.

Vaults have emerged to fill that role. They are a piece of infrastructure that automatically move users’ deposits between lending and yield strategies based on predefined rules, allowing investors to earn returns without actively managing positions or monitoring markets.

Multisignature wallets guard most of the serious money in crypto: DAO treasuries, exchange cold storage, protocol funds, and the savings of the security-conscious. They are also at the center of the industry’s biggest heists, from Bybit’s $1.5 billion to this year’s UXLINK breach, because attackers stopped picking locks and started fooling the people holding the keys. This guide explains how multisig actually works, the M-of-N design choices, how the famous multisig hacks really happened, and how to run one without becoming a case study.

Ask where crypto’s serious money lives, and the answer, overwhelmingly, is behind multiple signatures. A majority of institutional custodians run multisignature arrangements; DAO treasuries holding billions coordinate through them; exchanges guard cold storage with them; custody chains behind institutional products depend on them; and protocols park their upgrade keys and reserve funds inside them, most commonly in Safe, the contract system formerly known as Gnosis Safe, which alone secures values rivaling large banks. The idea is old, borrowed from bank vaults and nuclear launch protocols: no single person, key, or machine should be able to move what matters. Require M signatures out of N keys, 2-of-3, 3-of-5, and a thief must compromise several independent guardians instead of one.

And yet the largest theft in crypto’s history, Bybit’s $1.5 billion, walked out through a multisig. So did this year’s $11.3 million UXLINK breach, and the Ronin bridge’s $600 million before them. The pattern is the most instructive fact in modern crypto security: the multisig math has never been broken; the humans and interfaces around it are broken constantly. Multisig eliminates the single point of failure and replaces it with a subtler question, whether your several points of failure are actually independent, and the industry’s disaster record is a catalog of discovering they were not.

This guide covers the mechanism and its failure modes with equal seriousness: how multisignature schemes actually work on Bitcoin and on smart-contract chains, how to choose M and N and what each choice trades, the anatomy of the great multisig heists and the blind-signing problem at their core, multisig against its modern rivals, MPC and smart accounts, and the operational playbook that separates the treasuries that survive from the ones that headline.

The mechanism: M-of-N, on two architectures

A multisig wallet requires a threshold of signatures, M, from a set of authorized keys, N, before any transaction executes. A 2-of-3 personal setup might split keys across a hardware wallet at home, a second device in a bank box, and a trusted relative; a 4-of-7 DAO treasury spreads keys across council members on different continents. The threshold is the design’s dial: security against compromise rises with M, resilience against key loss rises with the gap between N and M, and operational friction rises with both.

Under the hood, two architectures implement the idea. On Bitcoin, multisig is native to the protocol’s scripting: an address encodes the M-of-N requirement itself, and spending requires the signatures to be presented and verified by the network. It is minimal, battle-tested, and rigid, changing signers means moving funds to a new address. On Ethereum and similar chains, multisig lives in smart contracts: a program, such as a Safe, holds the funds and enforces the policy, collecting signatures until the threshold is met and then executing. The contract approach is vastly more flexible, signers can be rotated, thresholds changed, daily limits and timelocks and module extensions added, and that flexibility is double-edged: the policy is code, code can have flaws, and, as the disaster section will show, the richness of what a contract wallet can execute is exactly what modern attackers exploit.

The transaction flow in both worlds follows the same rhythm. Someone proposes a transaction, recipient, amount, and, on contract wallets, arbitrary program calls. The proposal circulates to signers, each of whom reviews and cryptographically approves it with their own key, on their own device. When approvals reach the threshold, the transaction becomes executable and is broadcast. Every step is auditable: the chain records exactly which keys approved what, creating the accountability trail that makes multisig the governance tool of choice for DAO treasuries whose control is otherwise contested through token votes, for corporate funds requiring officer sign-off, and for escrow arrangements where a neutral third key arbitrates disputes, the human-governed cousin of the time-locked contracts that automate escrow on-chain.

Choosing M and N: the design space

The threshold choice is a risk allocation, and the standard configurations each answer a different question. 2-of-2 is a partnership with no tiebreaker and no recovery, one lost key strands the funds, and is mostly used with one key held by a service. 2-of-3 is the individual’s workhorse: it survives the loss of any one key, resists the compromise of any one key, and keeps signing friction tolerable; the classic personal build spreads three hardware keys across locations, and the classic collaborative-custody build gives one key to a professional service that can co-sign recovery but can never move funds alone. 3-of-5 and up is institutional territory, tolerating multiple losses and requiring multiple corruptions, at the price of coordination overhead that, in practice, tempts organizations into the worst sin of the genre: concentration, several keys held by one person, one office, one laptop, or one cloud account. A 3-of-5 whose keys live in three browsers and two drawers of the same office is a 1-of-1 with extra steps, and post-mortems of real losses find this shape constantly. The rule the design space reduces to: the security of a multisig is the security of its most correlated keys, and independence, of people, devices, software, and geography, is the entire point of the exercise.

Key-holder policy matters as much as the numbers. Every signer is a target the moment the arrangement is visible on-chain, and large treasuries are visible by definition, tracked by the same wallet-attribution lens that maps every whale. Serious operations therefore treat signers as an attack surface: hardware keys only, dedicated signing devices, no signer identities published unnecessarily, and procedures rehearsed before they are needed, because the day a treasury must move funds under pressure is the worst day to discover the third signer’s key is in a safe nobody can open.

How multisigs actually get robbed

The heist record is where this subject earns its place in a security curriculum, because the attacks share an anatomy and it is not the one intuition expects. No major multisig loss has come from breaking the cryptography. They come from making the right people sign the wrong thing.

The Bybit theft, $1.5 billion, the largest in industry history, is the canonical case. The exchange’s cold storage sat behind a multisig with executives as signers, exactly as best practice prescribes. Attackers, attributed to North Korea’s Lazarus Group, compromised the infrastructure of the wallet interface the signers used, so that when the executives performed a routine, scheduled transfer, their screens showed the legitimate transaction while their hardware keys signed a different payload, one that handed the attackers control of the wallet’s logic. Every signature was genuine. Every signer was diligent by the standard of what they could see. The vault held; the vault’s window lied. The Ronin bridge before it fell differently but rhymes: a 5-of-9 arrangement whose keys were insufficiently independent, with one organization controlling enough of them that compromising it, via a social-engineered employee, crossed the threshold, the key-compromise pattern behind the largest bridge disasters. And this year’s UXLINK breach showed the small-scale version: attackers who gain threshold control do not just drain, they use the wallet’s own administrative powers, adding themselves as signers, ejecting the owners, because on a contract multisig, governance of the wallet is itself just another transaction.

The common thread is blind signing. A hardware key protects the signature; it does not tell the signer, in honest human terms, what they are signing, and complex contract-wallet payloads are unreadable hashes on a tiny screen. Attackers therefore aim at the layer between intention and signature: the web interface, the signer’s laptop, the proposal pipeline, the human’s routine. The defenses that address this are specific and increasingly standard: independent verification of every payload on a second channel before signing, signing devices that decode and display transaction meaning, simulation tools that preview a transaction’s actual effects, timelocks that delay large movements long enough for review, and the simple institutional rule that no transaction is routine, because routine is precisely the state of mind the Bybit attackers were waiting for.

From Bitcoin script to Safe: how the standard was built

Multisig’s history is the history of crypto custody growing up, and its milestones explain today’s defaults. The capability is nearly as old as Bitcoin itself, formalized in the protocol’s early years through pay-to-script-hash addresses that let spending conditions, including M-of-N signature requirements, be encoded on-chain. The first institutional era was built directly on it: the early exchange and custody pioneers ran Bitcoin multisig vaults, and the first collaborative-custody businesses sold 2-of-3 arrangements to individuals a decade ago. The idea crossed to Ethereum as smart-contract wallets, where the flexibility of code produced both the triumphs and the scars: an infamous 2017 library bug in a widely used contract wallet froze hundreds of millions permanently, the formative lesson that flexible custody code is itself an attack surface, and the survivor of that era’s consolidation, Gnosis Safe, hardened through years of audits and adversarial value into the default it is now.

Today Safe-style contracts secure treasuries whose combined value rivals major banks, the DAO era having made the multisig council crypto’s standard governance executive, and Bitcoin’s own multisig lineage continues in parallel, favored for deep cold storage precisely because its rigid, minimal script surface offers so little to exploit.

The standardization has a consequence worth naming: concentration of a different kind. When one contract system secures the majority of on-chain treasuries, its code, its interface, and its upgrade process become systemic infrastructure, and the Bybit attack’s compromise of interface infrastructure was, among other things, a demonstration that the ecosystem’s eggs share more baskets than the M-of-N math suggests. The response, interface diversity, independent transaction verification services, signing-device decoding, is effectively the community rebuilding independence one layer up the stack, the same principle the wallets encode, applied to the tooling around them.

Setting one up: the individual’s path

For an individual reader, the practical on-ramp deserves concreteness. A personal 2-of-3 today is a weekend project: three hardware keys, ideally from two different vendors to avoid a shared firmware flaw; a contract wallet on an inexpensive network or a native Bitcoin multisig, depending on holdings; owner addresses triple-checked before deployment, because a mistyped owner is a permanent stranger with signing power; and the three keys distributed across genuinely separate locations, home, bank box, trusted party, with recovery instructions that someone other than you can follow.

The recurring costs are minor, deployment gas and slightly larger transaction fees, and the recurring disciplines are not: test the setup with small amounts first, rehearse a lost-key migration before losing one, keep a small gas balance where the contract needs it, and revisit the arrangement whenever a signer, device, or living situation changes. The friction is real, every transaction becomes a small ceremony, and the friction is the feature: a wallet that requires deliberation cannot be drained by one bad click, which, given that a single mistaken approval is how most individual losses now happen, is the entire value proposition in one sentence.

Multisig and its rivals: MPC and smart accounts

Two adjacent technologies answer the same single-point-of-failure problem, and choosing among them is a real decision, not branding.

Multi-party computation, MPC, splits one key into mathematical shares held by different parties, who jointly compute a signature without the full key ever existing anywhere. To the blockchain, the result looks like an ordinary single signature: cheaper, private, chain-agnostic, and revealing nothing about the policy behind it. The trade is opacity and dependence: the threshold logic lives in the providers’ off-chain software rather than in public code, there is no on-chain trail of who approved what, and the institutional MPC market is dominated by vendors whose systems must be trusted. Institutions increasingly use both, MPC for operational hot flows, multisig for deep cold governance.

Smart accounts, account abstraction, generalize the contract-wallet idea: programmable accounts with recovery guardians, spending policies, session keys, and multisig as merely one available policy among many. They are the likely long-term home of these ideas for individuals, folding multisig-grade protection into interfaces normal users can operate. For treasuries today, the audited, battle-hardened dedicated multisig remains the standard, precisely because its decade of scars, documented above, produced a decade of hardening.

Between the architectures sits a question every treasury eventually asks: how many signers is too many? The coordination cost of thresholds grows faster than linearly, five signers across five time zones can turn a routine payment into a week, and organizations respond with delegation structures that deserve scrutiny because they quietly re-centralize. Common patterns include a small operational multisig with spending limits for daily flows, governed by a larger cold council for everything above the limit; module systems that pre-authorize specific recurring actions; and role separation between proposers, who prepare transactions, and signers, who approve them, narrowing what any single compromised seat can initiate. Each pattern trades purity for function, and the honest evaluation standard is the same one the thresholds themselves answer to: enumerate what the compromise of each seat, device, and interface enables, and check that no enumeration ends in everything. Treasury security is not a product purchased once; it is that enumeration, repeated, forever, against adversaries who read the same post-mortems.

One misconception deserves explicit correction before the playbook: multisig does not protect against approving a bad idea unanimously. If all required signers are deceived by the same forged interface, the same fraudulent counterparty, or the same internal fraudster’s paperwork, the threshold is met and the mathematics executes the mistake faithfully. Signature independence protects against compromised keys; only verification independence, different signers checking the payload through different tooling and channels, protects against compromised information, and the great heists were failures of the second kind wearing the confidence of the first.

The operational playbook

Everything in this guide compresses into a practice list, and the list is the difference between the mechanism and its reputation. Choose thresholds for both compromise and loss: 2-of-3 personal, 3-of-5 or higher institutional. Make independence real: different people, devices, vendors, physical locations, and no key in a browser. Verify what you sign: second-channel confirmation of every payload, simulation before approval, and a standing suspicion of anything urgent. Add time as a defense: timelocks on large transfers turn a successful deception into a recoverable one. Rehearse recovery: a lost-key drill and a signer-rotation drill, run before either is needed. And treat the wallet’s own governance, adding or removing signers, changing thresholds, as the crown jewels, because the UXLINK lesson is that whoever can edit the signer set owns everything the signatures guard.

Multisig, honestly summarized, is the most successful security primitive crypto has deployed: it moved the industry’s treasuries from single hackable keys to arrangements that require conspiracies to rob, and the conspiracies, note, have had to grow to nation-state sophistication to succeed. Its failures are not refutations but curriculum, each one converting a blind spot into a checklist item, and the checklist is public. The vault works. Guard the window.

Two closing perspectives round out the subject. The first is the defender’s asymmetry, and it is encouraging: every major multisig loss has produced a specific, adoptable countermeasure, payload verification after Bybit, key-independence audits after Ronin, signer-set timelocks after the takeover breaches, and the countermeasures compound while the attacks must be reinvented. A treasury running the current playbook is not facing the same odds its predecessors did; it is facing adversaries who must now defeat every lesson previous victims paid for. Security in this domain is cumulative, and the cumulation is public.

The second is the philosophical point hiding in the mechanism, worth one paragraph because it explains multisig’s cultural weight in crypto. A multisignature arrangement is a constitution in miniature: a written rule about who may act, enforced by mathematics instead of courts, visible to everyone it governs. That is why the technology became the executive branch of the DAO era, why its failures feel like institutional scandals rather than mere thefts, and why its steady hardening matters beyond the funds it guards. Crypto’s founding claim was that agreements could be enforced without trusted enforcers, and the multisig, requiring humans to agree while preventing any of them from betraying the agreement, is the claim’s most widely deployed, most thoroughly attacked, and most durably successful embodiment. The vaults hold more than money.

For further orientation, the study list is mercifully practical: the post-mortems of the major incidents named above, each a free masterclass in one failure mode; the documentation of the dominant contract systems, whose security recommendations encode the industry’s accumulated scar tissue; the transaction-simulation and payload-decoding tools that address blind signing directly; and, for organizations, the published treasury-operations frameworks that DAOs and custodians have converged on. Multisig is the rare corner of crypto where the best practices are written down, battle-tested, and free, and where the distance between the average outcome and the best outcome is almost entirely a matter of reading them.

And if this guide leaves a single instinct behind, let it be this one: in multisig, the question is never whether the mathematics will hold, because it will. The question, every time, for every transaction, is whether the humans holding the keys know what they are signing, and every practice in the playbook above is, in the end, a different way of making sure the answer is yes.

Disclaimer: This article is for educational purposes only and does not constitute investment or security advice. Digital asset custody carries significant risk, and no arrangement eliminates it. Details are current as of July 9, 2026. Always do your own research.

Frequently asked questions

Interpol says a cryptocurrency wallet tied to a suspected romance-scam money launderer processed more than $122.5 million over a 10-month period, underscoring how online fraud networks are increasingly using crypto rails to complicate enforcement.

In a statement released Thursday, Interpol said Thai authorities arrested two suspects and dismantled a money-laundering operation that routed proceeds from romance scams into cryptocurrencies. Interpol added that the scheme relied on cross-chain token swaps to obscure the origin of funds as they moved through different networks.

Key takeaways

• Interpol reported a suspected romance-scam laundering wallet handled over $122.5 million in 10 months.
• Thai investigators linked the activity to laundering techniques that used cross-chain token swaps to mask transaction trails.
• Operation First Light 2026 ran across 97 countries and territories, focusing on fraud networks and the financial infrastructure behind them.
• The operation resulted in 5,811 arrests and the seizure of $293 million in illicit assets, according to Interpol.
• Interpol used its payment-freezing tool (Global Rapid Intervention of Payments) to help block transfers involving both fiat and crypto assets.

Operation First Light 2026 targets both scams and laundering

Interpol framed the Thai case as part of Operation First Light 2026, an Interpol-coordinated push to disrupt social engineering scams and the laundering channels used to convert fraudulent proceeds into transferable value.

According to Interpol, the campaign involved authorities in 97 countries and territories and used data analysis to trace patterns across cases connected to online fraud. Interpol said the operation analyzed 152,808 cases, blocked 31,014 bank accounts, resolved 23,715 investigations, and identified 15,606 suspects.

Interpol also said authorities employed its Global Rapid Intervention of Payments system to support rapid freezing of payments—an approach designed to stop illicit transfers before funds move further. The tool can be used to block transfers involving fiat and virtual assets, Interpol said.

Crypto laundering via cross-chain swaps increases tracing difficulty

While social engineering tactics remain central to romance scams, Interpol’s disclosure highlights the evolving mechanics of laundering. In the Thai investigation, Interpol said proceeds were funneled into cryptocurrencies and that cross-chain token swaps were used to make the trail harder to follow.

Cross-chain activity can introduce additional hops, route changes, and token transformations that complicate straightforward attribution. In this case, Interpol’s emphasis on swaps points to a strategy criminals are using to break linkages between the original scam payments and the eventual destination of funds.

From an investor or market participant perspective, these reports reinforce a recurring risk: illicit demand for liquidity and conversion services may intersect with otherwise legitimate crypto markets. Even when the volumes are linked to scams rather than “organic” trading, they can still affect on-chain flows and increase compliance pressure on exchanges and service providers.

Global scale: arrests, seizures, and additional action in Palau

Interpol said Operation First Light 2026 culminated in 5,811 arrests and the seizure of $293 million in illicit assets related to fraud and money laundering. Interpol also highlighted the operational breadth of the campaign, describing it as coordinated across many jurisdictions rather than a single-country investigation.

Beyond the Thai operation, Interpol said authorities in Palau deported 22 people allegedly involved in two hotel-based scam centers. Interpol linked those centers to schemes that used cryptocurrency and illegal gambling websites to target victims abroad.

Together, the Thai and Palau developments show how enforcement efforts are increasingly addressing the broader ecosystem around online fraud: recruitment and victim targeting, the movement of funds, and the systems used to keep perpetrators hard to trace.

Romance scams remain a focus amid growing US losses

Interpol said social engineering scams continue to be a major threat and argued that no single country can tackle the problem alone. The statement reflects ongoing international attention to fraud schemes—especially those branded as romance scams or “pig butchering,” where criminals cultivate trust before steering victims toward fake investment opportunities.

The crackdown also arrives as regulators and investigators continue to document high losses from crypto-linked scams. In April, the US Federal Bureau of Investigation (FBI) reported that Americans filed 181,565 crypto-related scam complaints totaling more than $11 billion in losses in 2025, according to coverage that referenced the FBI data.

Romance scams often use social media, messaging apps, and dating platforms to build legitimacy. Once a victim is persuaded to move funds, crypto can be presented as a convenient, fast transfer method—while laundering techniques such as token swaps can further delay attribution and seizure.

What to watch next

Interpol’s figures show how international enforcement is trying to follow money across borders and across crypto networks, but criminals’ use of cross-chain swaps suggests evasion tactics will keep evolving. Readers should watch whether future operations increasingly focus on transaction-level tracing and rapid freezing capabilities—and how quickly authorities can convert blockchain activity into recoverable assets.

Revolut has announced that it will remove support for the Tether USDT stablecoin for customers in the European Economic Area (EEA) and Switzerland, citing MiCA-related regulatory and risk review. The company said the change is limited to those regions, while USDT support will continue in other markets where it is currently offered.

In a statement provided to Cointelegraph, a Revolut spokesperson said the decision follows a periodic review of its cryptocurrency offering in light of the evolving European Union regulatory framework under the Markets in Crypto-Assets Regulation (MiCA). Revolut also previously removed USDT from its Revolut X trading platform for EEA customers, with the latest step completing the withdrawal from its retail crypto offering in the EEA.

Key takeaways

• Revolut is discontinuing USDT support for customers in the EEA and Switzerland, while keeping support elsewhere.
• The move is linked to a regulatory and risk review under MiCA, according to a company spokesperson.
• USDT was already removed from Revolut X for EEA users; this update finalizes the EEA retail removal.
• MiCA’s EEA relevance raises questions about why Switzerland is included despite not being directly covered by the regulation.

Revolut’s USDT exit tied to MiCA review

Revolut said it is “discontinuing support for USDT for customers in the EEA following a periodic review of our cryptocurrency offering in light of the evolving EU regulatory framework under MiCA,” according to its spokesperson. The announcement follows a broader period of adjustments across European crypto services as firms prepare for regulatory requirements associated with MiCA.

According to Cointelegraph’s earlier reporting, Revolut first notified some European users on Friday that USDT would be delisted from its platform by Aug. 31, 2026. Revolut said the process had already begun before that notification: it removed USDT from the Revolut X trading platform for EEA customers, and the latest decision completes the removal from its EEA retail offering.

Where the change applies—and where it doesn’t

Revolut’s spokesperson said the delisting affects customers in the EEA and Switzerland. The firm indicated that support for the stablecoin will continue in other markets, but it did not provide a list of jurisdictions where its crypto services—including USDT—are still available.

The regional framing also matters because MiCA is an EU regulation that has EEA relevance. Official documents from the European Securities and Markets Authority (ESMA) describe MiCA as extending to the broader EEA, which includes Norway, Iceland, and Liechtenstein in addition to EU member states. In that context, the mention of Switzerland stands out.

Switzerland is not part of the EU or the EEA and is not directly covered by MiCA. Revolut did not explain why Swiss customers were included in the delisting scope. Cointelegraph reported that the company did not respond to a request for clarification on the scope of its offering by the time of publication.

Broader EU trend after Tether’s MiCA posture

Revolut’s decision reflects a wider shift among crypto platforms operating across Europe. Cointelegraph noted that many firms have continued to phase out USDT after Tether—the issuer of the $184 billion stablecoin—opted not to pursue authorization under MiCA. While the mechanics of MiCA authorization depend on jurisdiction and a stablecoin’s compliance pathway, the direction of travel for intermediaries has been consistent: reduce exposure to stablecoins that may become harder to serve under the new regime.

For investors and traders, stablecoin availability is more than a convenience issue. When platforms change which assets they support, users can be affected in practical ways: execution routes may change, on-platform swaps may become unavailable, and users who rely on a specific stablecoin for custody or settlement may need to restructure how they manage balances.

Revolut’s staged approach—first removing USDT from its Revolut X trading platform for EEA customers, then completing the removal from its retail offering—also suggests the company is treating the MiCA transition as an operational transition rather than a single-day shutdown.

What Revolut’s timetable signals for users

The USDT delisting notice surfaced with a timeline for Aug. 31, 2026, implying that EEA users may still have access until then, subject to the platform’s operational changes already underway. Revolut did not provide further detail in the information available, including what specific account actions might be available during the wind-down period—such as whether USDT balances can be held, exchanged, or withdrawn during the transition.

Even without those specifics, the sequence described by Revolut matters: USDT trading on Revolut X for EEA customers had already been removed before the broader delisting plan was communicated. That kind of incremental reduction can reduce disruption for new trades while giving customers time to adjust their holdings.

Still, uncertainty remains for customers outside the affected regions, because Revolut did not publish a jurisdiction-by-jurisdiction breakdown of where USDT remains supported. For traders who operate across multiple venues—or who routinely move between regions—this becomes a risk management consideration: platform support can change as regulations evolve.

Keeping an eye on regulatory alignment beyond MiCA

While Revolut’s explanation points to MiCA as the driving regulatory framework, its inclusion of Switzerland—despite that country not being directly covered by MiCA—highlights a broader theme in Europe’s crypto compliance landscape: companies may be making decisions based on anticipated regulatory alignment, counterpart constraints, or internal risk frameworks that go beyond the narrow legal text.

Readers should watch for two things next: whether Revolut clarifies how Switzerland fits into its risk and regulatory rationale, and whether other platforms adjust their USDT support timelines or expand similar delistings in the EEA. As firms continue to reposition their stablecoin offerings, the most practical question for users will be which assets remain accessible on the platforms they use, and what transition paths are available when support ends.