A testnet is a separate blockchain network that mirrors a production chain’s rules and functionality but uses tokens with no monetary value. It is where developers break things, test upgrades, and discover bugs before those bugs can cost anyone real money.

Every piece of software ships with bugs. The question is whether those bugs are discovered in a controlled environment or in production, where they can destroy value. In traditional software development, staging environments and QA processes serve this function. In blockchain, testnets serve the same function but with a critical difference: blockchain bugs are often irreversible.

A smart contract that contains a vulnerability on a testnet loses nothing because the tokens are worthless. The same vulnerability on a mainnet can drain millions of dollars in minutes. The history of decentralized finance is littered with exploits that could have been caught on a testnet if the testing had been more thorough.

This article explains what testnets are, how they work, why they matter for the security of every blockchain protocol, and what their limitations are. If you interact with any blockchain application, the quality of its testnet phase directly affects the safety of your funds.

How testnets work

A testnet runs the same node software as its corresponding mainnet but operates on a separate network with its own genesis block, its own chain of blocks, and its own set of validators or miners. Transactions on a testnet are processed using the same consensus rules, the same virtual machine, and the same transaction format as mainnet transactions. The only fundamental difference is that the tokens have no market value.

This separation is enforced at the network level. Testnet nodes connect to other testnet nodes, not to mainnet nodes. The chain IDs are different, which prevents testnet transactions from being replayed on mainnet and vice versa. When a developer deploys a smart contract to a testnet, that contract exists only on the testnet and has no effect on the mainnet state.

Testnet tokens are distributed through faucets, which are simple web applications that send a small amount of test tokens to any wallet address that requests them. Most faucets impose rate limits to prevent abuse. Some require completing a captcha or connecting a social media account. The tokens have no monetary value by design, though there have been instances where testnet tokens have traded on secondary markets, which defeats their purpose and is generally discouraged by protocol teams.

Developers use testnets to deploy and interact with smart contracts exactly as they would on mainnet. They can test function calls, simulate user interactions, measure gas consumption, and verify that error handling works correctly. Wallet applications, decentralized exchanges, lending protocols, and NFT marketplaces all go through testnet deployment before launching on mainnet.

Types of testnets

Not all testnets serve the same purpose. Public testnets are open to anyone and mirror mainnet conditions as closely as possible. They are used for final stage testing before mainnet deployment and for community members who want to try new features. Ethereum’s Sepolia and Holesky are public testnets. Base’s Beryl testnet is another example of a public testnet used to test protocol upgrades before mainnet deployment.

Private or permissioned testnets are operated by specific development teams and are not open to public participation. These are used for early stage development where the protocol may be unstable or where the team wants to control the testing conditions. Many projects run private testnets for months before opening a public testnet.

Local development networks, sometimes called devnets, run on a developer’s own machine. Tools like Hardhat and Foundry for Ethereum allow developers to spin up a local blockchain instance, deploy contracts, and run tests in seconds without connecting to any external network. These are not true testnets but serve a similar function for unit testing and rapid iteration.

Shadow forks are a newer concept where a testnet replays real mainnet transaction data against a modified version of the protocol. This allows developers to test upgrades against realistic transaction patterns and state sizes rather than the synthetic and often unrealistic conditions of a standard testnet. Ethereum used shadow forking extensively during the preparation for The Merge in 2022.

Why testnet phases matter for protocol upgrades

Major blockchain upgrades follow a predictable lifecycle: specification, implementation, testnet deployment, monitoring, and finally mainnet activation. The testnet phase is where the implementation meets reality. Bugs that were invisible in unit tests become apparent when the code runs on a distributed network with independent operators, network latency, and concurrent transactions.

Ethereum’s Pectra upgrade, which introduced account abstraction and increased blob capacity, was deployed to the Hoodi testnet months before reaching mainnet. During the testnet phase, developers discovered edge cases in the account abstraction implementation that would have caused transaction failures for a subset of users. These were fixed before mainnet deployment.

Cardano’s van Rossem hard fork followed a similar pattern, with the upgrade reaching its public testnet weeks before the mainnet governance vote that activated it. The testnet phase allowed stake pool operators to update their nodes and verify compatibility before the hard fork went live.

The length of the testnet phase varies by the complexity and risk of the upgrade. Simple parameter changes might spend days on a testnet. Fundamental consensus changes like The Merge spent months across multiple testnets. The pressure to move quickly is always present, but the cost of shipping a mainnet bug that could have been caught on a testnet is high enough that most serious protocol teams err on the side of longer testing periods.

The gap between testnet and mainnet

Testnets are valuable but imperfect. Several categories of problems are difficult or impossible to reproduce on a testnet. Economic attacks, where an attacker exploits the relationship between token prices and protocol mechanics, require real economic incentives that do not exist on a testnet. Miner or validator extractable value strategies, front running, and sandwich attacks depend on real financial motivation.

Scale related bugs also often escape testnet detection. A testnet with 100 validators processes transactions differently than a mainnet with 1,000 validators. Network congestion patterns, state bloat, and the behavior of the peer to peer gossip layer under load all change with scale. Some bugs only manifest when the state database exceeds a certain size or when transaction volume spikes above levels that testnets rarely experience.

The social and governance dimensions of blockchain also differ between testnet and mainnet. On a testnet, there are no real stakeholders with financial exposure who might resist an upgrade. The politics of hard fork coordination, which can involve exchanges, wallet providers, major token holders, and application developers, do not exist on a testnet. A protocol change that works perfectly on a testnet can still fail on mainnet if the coordination required to activate it breaks down.

This gap is why many blockchain projects now use incentivized testnets, where participants earn rewards for finding bugs, stress testing the network, or running validators. Robinhood’s chain testnet recorded 4 million transactions in its first week, partly because of incentive programs that attracted real users performing realistic interactions rather than synthetic test scripts.

What testnets do not cover

Testnets do not test economic security. The value of tokens on a testnet is zero, which means rational economic actors behave differently than they would on mainnet. A protocol that appears secure on a testnet may be vulnerable to economic exploits that only become apparent when real money is at stake.

Testnets do not test long term stability. Most testnets are reset periodically, which means issues related to state growth, database performance over time, and the accumulation of edge cases in long running chains are not tested. Some protocols run long lived testnets specifically to catch these issues, but the practice is not universal.

Testnets do not test user behavior. On a testnet, users have no reason to optimize gas usage, rush to complete transactions before a deadline, or engage in arbitrage. The transaction patterns on a testnet are fundamentally different from mainnet patterns, which means performance metrics measured on a testnet may not translate to mainnet conditions.

Practical checks for using testnets

If you are a developer, always deploy to a testnet before mainnet. This sounds obvious but a surprising number of smart contract exploits involve code that was deployed directly to mainnet without adequate testnet coverage. Use automated testing frameworks to run your test suite against a testnet deployment, not just a local node.

If you are a user, check whether the applications you use went through a public testnet phase. Serious projects publish testnet addresses, invite community testing, and often run bug bounty programs during the testnet phase. A project that skips the public testnet phase and launches directly to mainnet is taking a risk with its users’ funds.

When interacting with testnets, use a separate wallet from your mainnet wallet. While testnet transactions cannot affect mainnet, using the same private key on both networks is a bad security practice. If a testnet application is compromised or contains malicious code, having your mainnet private key in the same wallet creates unnecessary risk.

Monitor the testnet phase of upgrades to networks where you hold assets. If a major upgrade encounters problems on a testnet, it may be delayed or modified before mainnet deployment. Understanding the testnet timeline gives you advance notice of potential disruptions or opportunities.

Frequently asked questions

Disclaimer: This article is for informational purposes only and does not constitute financial, investment, or legal advice. Cryptocurrency investments carry significant risk. Always conduct your own research before making any investment decisions. Information is accurate as of August 1, 2026.

Crypto holders used to focus on diversifying their coins. Now, following a $70 million Coldcard exploit, they’re being told to diversify their wallets as well.

On Saturday, Binance founder Changpeng Zhao, known as CZ, asked crypto holders to split their funds across multiple wallets following a major security failure in popular Coldcard hardware devices.

“Even hardware wallets can have bugs. Even old wallets (with long history) can have bugs. How to mitigate? Split your funds in a few wallets maybe? This has a different set of risks. Nothing is 100%. Stay informed. Stay SAFU!,” he said.

On July 30, some bitcoin users discovered that funds from their Coldcard wallets had been stolen in a series of unexpected transactions. The attacker exploited a firmware flaw dating to March 2021 that weakened the randomness used to generate recovery seeds on certain Coldcard models. By reconstructing private keys offline, the attacker was able to drain funds without ever physically accessing the devices.

Initial reports said about 594 BTC, worth $38 million at the time, were drained from around 500 wallet in a 25-minute window. Subsequent analysis by Galaxy Research expanded the scope to 1,082.65 bitcoin, valued at approximately $70 million, drained from 1,196 addresses over about 41 minutes. Many of the affected wallets had sat dormant for years.

Coldcard maker Coinkite has acknowledged the bug, apologized, and released emergency firmware updates. The company has advised users who generated seeds on affected versions to create entirely new seeds on patched devices and carefully migrate funds, noting that simply updating firmware does not secure an already-created vulnerable seed.

The episode has renewed debate over the limits of self-custody. Hardware wallets are widely viewed as one of the strongest options for securing bitcoin offline, yet the Coldcard case shows that even long-established devices can harbor critical flaws that remain undetected for years.

CZ’s suggestion of diversification acknowledges that spreading risk comes with its own practical challenges, including more complex key management.

A mainnet is the production version of a blockchain network where transactions carry real economic value and are permanently recorded. When a cryptocurrency project launches its mainnet, it moves from concept to reality, and every line of code becomes a financial commitment.

In software development, production is where the stakes are real. A bug in a development environment is a learning opportunity. A bug in production is an incident report. In blockchain, the gap between these two states is even wider because blockchain transactions are, by design, difficult or impossible to reverse.

A mainnet is a blockchain’s production environment. It is the live, operational network where tokens have market prices, smart contracts control real funds, and the consensus mechanism protects real economic value. Everything that happens before mainnet, including testnets, audits, and governance votes, exists to reduce the probability that something goes wrong after mainnet launch.

This article explains what a mainnet is, how mainnet launches work, what happens when mainnets are upgraded through hard forks, and what risks remain even after a successful launch. If you hold cryptocurrency on any blockchain, you are interacting with a mainnet, and understanding how it works is fundamental to understanding the security of your assets.

What makes a mainnet different from a testnet

The technical infrastructure of a mainnet and its corresponding testnet is largely identical. Both run the same node software, use the same consensus algorithm, and process transactions using the same virtual machine. The differences are economic and social rather than technical.

On a mainnet, tokens have market value. This means validators and miners have financial incentives to act honestly because their staked tokens or mining hardware represents real capital at risk. It also means attackers have financial incentives to exploit vulnerabilities because successful attacks can be monetized. This duality, where real value creates both stronger defense and stronger offense, is the fundamental characteristic of a mainnet.

The validator set on a mainnet is typically much larger and more geographically distributed than on a testnet. Ethereum mainnet has over 1 million active validators as of mid 2026. Its testnets have a few thousand. This scale difference affects network behavior, propagation times, and the difficulty of coordinating upgrades.

State size is another critical difference. Ethereum’s mainnet state, the accumulated data from every transaction since genesis in July 2015, is hundreds of gigabytes. Testnets are reset periodically and never accumulate state at this scale. Performance issues related to state bloat, database fragmentation, and node synchronization time are mainnet problems that testnets rarely surface.

Proof of work is a consensus mechanism that forces computers to spend measurable energy solving a mathematical puzzle before they can add a new block of transactions to a blockchain. It is the reason bitcoin has value as a settlement network and the reason that network consumes more electricity than some countries.

Most explanations of proof of work start with an analogy. They compare it to a lottery, a puzzle, or a race. These analogies are useful but they obscure the critical detail: proof of work is not about solving a problem. It is about proving that you spent resources attempting to solve it.

That distinction matters because it explains why bitcoin works as a decentralized ledger. No central authority decides who gets to write the next page of the transaction record. Instead, the network awards that right to whoever demonstrates the most computational effort. The cost of that effort is what makes the record trustworthy.

This article explains what proof of work actually does at a technical level, why it was chosen for bitcoin, how it compares to alternatives, and what it does not protect against. If you have heard that proof of work wastes energy or that it is obsolete, the arithmetic tells a more complicated story.

How hashing works

A hash function takes an input of any length and produces an output of fixed length. Bitcoin uses SHA-256, which produces a 256 bit output regardless of whether the input is a single character or an entire novel. The output looks random but is deterministic: the same input always produces the same output, and changing a single bit of the input produces a completely different output.

This property, called the avalanche effect, is what makes hashing useful for proof of work. There is no shortcut to finding an input that produces a specific output. The only way to find one is to try inputs until you get lucky. Every attempt costs a small amount of energy, and the probability of success on any single attempt is vanishingly small.

When a miner constructs a candidate block, they assemble a set of unconfirmed transactions, add a block header containing metadata like the previous block hash and a timestamp, and include a field called the nonce. The miner then hashes the block header repeatedly, incrementing the nonce each time, until the resulting hash is numerically below a target value set by the network. That target is what determines the difficulty.

Coinkite says an attacker used AI to find a flaw its own AI review missed, exposing 500 wallets to a seed generation bug that reduced 128 bits of entropy to 40.

The attack took 25 minutes. At 2:14 a.m. UTC on July 31, a single entity began sweeping bitcoin from Coldcard hardware wallets. By 2:39 a.m., 594 BTC had moved from approximately 500 wallets into a consolidation address. The funds, worth roughly $38 million at the time of the sweep, were not stolen through phishing, malware, or physical access to the devices. They were stolen because the devices generated predictable private keys.

Coinkite, the Toronto based company that manufactures Coldcard, published an advisory and a technical breakdown on July 30 after discovering the flaw. The company said a build error in its firmware caused seed generation to draw randomness from a software fallback rather than the hardware random number generator the device was designed to use. The bug had been present since firmware version 4.0.1, released in March 2021. Every seed generated on an affected Coldcard during the past five years was weaker than its owner believed.

The implications extend beyond the immediate financial loss. Coldcard has been the hardware wallet of choice for bitcoin maximalists, security researchers, and institutional custodians who prioritize air gapped, open source, bitcoin only security. If the most trusted hardware wallet in bitcoin could ship a five year old entropy bug without detection, the question is not whether Coldcard failed. The question is whether any hardware wallet can be trusted as a single point of custodial security.

The mechanism: how 128 bits became 40

The technical explanation is both simple and alarming. Coldcard’s firmware calls a function to fetch randomness during seed generation. Two implementations of that function existed in the codebase with identical signatures: the hardware random number generator that Coinkite wrote, and a software fallback inherited from MicroPython, the embedded Python runtime the firmware is built on.

A preprocessor guard was supposed to select the hardware implementation. But the guard checked only whether a configuration setting was defined, not whether its value was correct. When the firmware was compiled, the build system resolved the ambiguity by selecting the software fallback. The build completed without warnings. The resulting firmware generated seeds that appeared normal, produced valid bitcoin addresses, and accepted deposits without any indication that the underlying entropy was catastrophically weak.

On the Mk3, Coinkite estimates the effective search space for a seed generated under this condition at approximately 40 bits. A 128 bit seed has more possible combinations than there are atoms in the observable universe. A 40 bit seed has roughly one trillion combinations. That is within reach of a moderately resourced attacker using commodity hardware. The difference is not a rounding error. It is the difference between a lock that cannot be picked and a lock that can be kicked open.

The Mk4, Q, and Mk5 models include additional secure elements that mix their own entropy into the seed generation process. Coinkite estimates these models produce seeds with approximately 72 bits of effective entropy under the bug. That is materially better than 40 bits but still far below the 128 bit target. A 72 bit key space is not practically brute forceable with current consumer hardware, but it is within theoretical reach of a well funded adversary with access to specialized computing resources.

The most critical detail in Coinkite’s advisory is a single sentence: “Updating the firmware does not change or repair an existing seed.” Every Coldcard owner who generated a seed on affected firmware must create a new seed on patched hardware and migrate their funds. There is no software fix for a weak private key. The key itself must be replaced.

The AI dimension

Coinkite’s advisory introduced a claim that drew immediate scrutiny from the security community. The company said it believes “someone used AI to review previous versions of our firmware” to discover the bug. It added that it had run “one of the best available models” over the same code weeks before the attack, and the model “did not find this bug or anything serious.”

The claim is plausible but unverified. The Coldcard firmware is open source and publicly available on GitHub. Any person or automated system can review it. The specific class of bug, a preprocessor guard that checks definition rather than value, is the kind of subtle code path error that large language models have shown varying ability to detect depending on context, prompt engineering, and the model used.

The asymmetry Coinkite described is real even if its specific attribution is speculative. Attackers and defenders do have access to the same AI tools. But attackers have a structural advantage: they need to find one exploitable flaw, while defenders need to find all of them. An AI that reviews code and reports nothing serious provides false confidence. An AI that reviews code and finds a single exploitable path provides the attacker with everything needed.

The incident also raises questions about the security audit process for hardware wallets more broadly. Coldcard has been praised for its open source approach, which allows anyone to inspect the firmware. But open source visibility is only as valuable as the quality of the inspections performed. If the manufacturer’s own AI review, presumably conducted with full context about the codebase’s architecture and intent, missed the bug, the open source advantage becomes theoretical, not practical.

The security research community has debated the AI attribution claim with skepticism. Several researchers noted on social media that the specific bug class, a preprocessor guard checking definition versus value, is well documented in embedded systems literature and could have been found through conventional code review. The AI framing, they argued, risks obscuring a more fundamental failure: that Coinkite did not have sufficient human review processes in place for a critical code path that had not changed in five years. Whether AI found the bug or a human researcher did, the underlying problem is the same. The code was public, the bug was subtle but not novel, and nobody on the defending side caught it.

Block published an independent technical analysis on July 31 confirming that none of its products, including Bitkey, are affected. Block’s hardware lead Max Guise urged anyone with an affected Coldcard to “move funds as soon as they safely can.” Trezor confirmed its devices use a different entropy generation approach and are not vulnerable. Ledger has not published a formal response but its Secure Element architecture uses a dedicated hardware random number generator that operates independently of the firmware.

The five year window

The timeline of the vulnerability is as damaging as the vulnerability itself. Firmware version 4.0.1, which introduced the bug, was released in March 2021. Every seed generated on an affected Coldcard between March 2021 and the patched firmware releases on July 31, 2026, is potentially compromised. That is five years and four months of affected seed generation.

During that window, Coldcard shipped the Mk3 (affected at 40 bits), the Mk4 (affected at 72 bits), and the Q (affected at 72 bits). The Mk5, released in 2026, is also affected at 72 bits. Coinkite released multiple firmware updates during this period, none of which addressed or detected the entropy issue. The company’s own security reviews, including the recent AI audit, did not catch it.

The five year window also coincided with a period of significant bitcoin price appreciation. Seeds generated on affected Mk3 devices in 2021, when bitcoin traded between $29,000 and $69,000, now protect holdings at prices above $60,000. The economic incentive for an attacker to invest computational resources in brute forcing 40 bit keys increased with every price rally. A wallet holding 1 BTC that was worth $30,000 when the seed was generated is now worth twice that. The attacker’s return on investment improved simply by waiting.

The number of affected wallets is difficult to estimate precisely. Coinkite does not publish sales figures. The 500 wallets drained in the initial attack represent the most exposed subset, likely Mk3 users with the weakest 40 bit entropy who held balances large enough to justify the attacker’s computational investment. The total number of wallets with compromised seeds across all affected models could be significantly larger.

The attacker’s consolidation pattern suggests systematic preparation. The 594 BTC were swept from approximately 500 wallets into a consolidation address and then moved to a single address holding 562 BTC. The 25 minute execution window and the number of wallets targeted simultaneously indicate the attacker had precomputed the vulnerable keys before initiating the sweep. This was not an opportunistic attack. It was an operation that required weeks or months of preparation.

On chain analysis of the sweep shows a methodical execution sequence. The attacker did not broadcast all 500 transactions simultaneously, which would have risked mempool congestion and potential front running by MEV style bots monitoring for unusual transaction patterns. Instead, the transactions were batched in groups, each batch confirming within one or two blocks. The consolidation address received funds across multiple blocks before a final transaction moved 562 BTC to what appears to be a long term holding address. As of this writing, the funds have not moved further.

The migration problem

Coinkite’s remediation guidance asks affected users to perform a wallet migration: generate a new seed on patched firmware, verify the backup, send a test transaction, and then move remaining funds. The process is straightforward for users with a single wallet and moderate balances. It is significantly more complex for users with multisig setups, timelocked transactions, or wallets that serve as one key in a larger custodial arrangement.

The migration also creates its own security risks. Moving funds from a compromised wallet to a new wallet requires the compromised wallet to sign a transaction. If the attacker has already computed the private key, the attacker can front run the migration by monitoring the blockchain for any transaction from the compromised address and immediately sweeping remaining funds. Users with significant balances face a race condition between their own migration and the attacker’s sweep.

For users holding bitcoin in multisig arrangements where a Coldcard served as one of multiple signing devices, the migration is more complex but the risk is partially mitigated. A 2 of 3 multisig wallet where only one key was generated on an affected Coldcard remains secure as long as the attacker cannot compromise a second key. However, the compromised key still weakens the overall security model and should be replaced. The process requires coordinating with all key holders to construct a new multisig wallet with a replacement key, sign a migration transaction with the existing quorum, and verify the new arrangement before moving remaining funds.

Coinkite addressed one edge case that provides partial relief. Users who added at least 50 independent dice rolls during seed generation contributed enough external entropy to bring the total above 128 bits regardless of the firmware bug. The dice input was hashed together with the device generated randomness, so strong dice entropy compensated for weak device entropy. Users who added 99 or more rolls contributed approximately 256 bits from dice alone.

The dice exception highlights an irony. The users most likely to have added extensive dice rolls during seed generation are the most security conscious users, precisely the demographic that chose Coldcard specifically because of its reputation for superior security practices. For these users, their own paranoia about entropy quality may have inadvertently protected them from the manufacturer’s failure to deliver it.

What this means for hardware wallet security

The Coldcard incident is not the first hardware wallet compromise. Ledger faced a database breach in 2020 that exposed customer information. Trezor disclosed a physical extraction vulnerability in 2023. But those incidents involved either metadata exposure or physical access requirements. The Coldcard bug is different because it undermines the fundamental security promise of the device: that it generates truly random private keys.

The timing compounds the damage. The incident arrives as bitcoin trades near all time highs, and institutional adoption of self custody solutions has accelerated. Companies and family offices that selected Coldcard specifically for its security reputation now face an urgent operational decision: migrate funds on potentially compromised keys while racing against an attacker who may have already computed those keys.

The incident challenges several assumptions that the bitcoin community has treated as foundational. The assumption that open source firmware is inherently more secure than proprietary firmware because it can be audited. The assumption that hardware random number generators in dedicated bitcoin devices are more trustworthy than software alternatives. The assumption that a device focused exclusively on bitcoin, rather than supporting multiple cryptocurrencies, will have a simpler and therefore more auditable codebase.

None of these assumptions are wrong in principle. They are wrong only as absolutes. Open source firmware can be audited, but it was not audited effectively. Hardware random number generators are more trustworthy, but only when the build system actually links to them. A bitcoin only codebase is simpler, but simplicity did not prevent a five year old bug from going undetected.

The practical lesson is that hardware wallets should not be treated as the sole custodial layer for significant bitcoin holdings. Multisignature arrangements that distribute keys across multiple devices from different manufacturers, combined with independently generated entropy sources, provide defense in depth that no single device can match. The Coldcard incident demonstrates that even the most trusted device can fail in ways that are invisible to the user until the funds are gone.

The broader question is whether the hardware wallet industry’s security review processes are adequate for the assets they protect. A $38 million loss from a single firmware bug suggests they are not. The self custody model that bitcoin advocates promote requires custodial tools that meet a standard of reliability comparable to the banking infrastructure they seek to replace. After Coldcard, that standard has not been met.

What to watch

• The attacker’s movement of the 562 BTC consolidation. Whether the funds are mixed, sent to exchanges, or held in place will provide information about the attacker’s sophistication and jurisdiction. Chain analysis firms are already monitoring the address.

• Additional affected wallets beyond the initial 500. The attacker may have computed keys for additional wallets but chose not to sweep them simultaneously. The total exposure across all affected Coldcard models could be significantly larger than the initial $38 million.

• The pace of user migration. Coinkite cannot force users to generate new seeds. The number of wallets that remain on compromised seeds after 30, 60, and 90 days will indicate how effectively the advisory reached the affected user base.

• Regulatory response. A $38 million loss caused by a manufacturer’s firmware bug in a consumer financial product would trigger regulatory action in traditional finance. Whether consumer protection agencies or financial regulators respond to this incident will signal how governments classify hardware wallets.

• Competing manufacturers’ security disclosures. Block, Trezor, and Ledger have confirmed they are unaffected. Whether they publish detailed technical analyses of their own entropy generation processes will indicate whether the industry treats this as a Coldcard specific failure or a systemic review opportunity.

Frequently asked questions

Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. The information presented reflects publicly available data as of July 31, 2026. Readers should conduct their own research and consult qualified professionals before making security or custody decisions.

Bitcoin price hovered near $63,000 on Aug. 1 as US ETF outflows, weakening momentum and regulatory uncertainty kept buyers on the sidelines.

Bitcoin price struggles to hold $63,000

According to data from crypto.news, Bitcoin (BTC) price traded at approximately $63,082 at the time of writing after briefly falling below $63,000 during the latest selloff. The asset has now erased most of its recovery from the July 21 high near $66,900.

The daily chart places Bitcoin directly below the 78.6% Fibonacci retracement level at $63,150. This level is measured from the decline between the May peak of $82,492 and the June low of $57,884.

A daily close below $63,150 would confirm that buyers failed to defend the retracement level. Bitcoin could then retest the $62,000 area, followed by the psychological $60,000 support if selling accelerates.

Holding the current zone would leave room for another consolidation phase. However, Bitcoin must recover above $64,000 before the immediate pressure begins to ease.

Bitcoin momentum indicators turn bearish

Momentum readings on the daily and 4-hour charts favor sellers.

Bitcoin’s daily relative strength index has fallen to 45.12, below its moving average of 51.99. The reading is not yet oversold, meaning the market could decline further before reaching conditions that typically attract dip buyers.

The daily moving average convergence divergence indicator has also produced a bearish setup. The MACD line has crossed below its signal line, while the histogram has moved into negative territory at −218.84.

On the 4-hour chart, Bitcoin is trading below the Bollinger Band midpoint at $63,886 and close to the lower band at $62,489. The upper band near $65,284 marks the first major volatility-based resistance.

Chaikin Money Flow has dropped to −0.22 on the same timeframe. The negative reading indicates that capital is leaving Bitcoin as it trades near support, reducing the strength of any short-term recovery attempt.

ETF outflows add pressure on Bitcoin

US spot Bitcoin ETFs posted a combined net outflow of approximately $265 million on July 31, according to SoSoValue data.

BlackRock’s iShares Bitcoin Trust led the withdrawals with $123 million in net outflows. Fidelity’s FBTC followed with approximately $54.8 million.

The daily outflow ended a two-session inflow streak and showed that institutional demand remained fragile at the start of August. Total assets held by the US spot Bitcoin ETFs stood at approximately $76.29 billion, equivalent to 6.04% of Bitcoin’s market value.

Traders are also monitoring the CLARITY Act negotiations in Washington. The White House is expected to review a bipartisan ethics proposal as lawmakers seek enough support to move the market structure bill forward before the Senate’s August recess.

Polymarket traders placed the probability of the CLARITY Act becoming law in 2026 at just 27% on Aug. 1. Prediction-market odds reflect trader positioning rather than a reliable legislative forecast, but the decline points to limited confidence that lawmakers will resolve their differences quickly.

Liquidation map identifies $62K and $65K targets

Bitcoin’s one-week liquidation heatmap shows large concentrations of leveraged positions on both sides of the current price.

The nearest downside liquidity cluster sits around $62,000. A break below the 4-hour lower Bollinger Band at $62,489 could push Bitcoin toward this area as long positions are forced to close.

A smaller concentration appears near $63,300, which could act as an immediate target during a rebound. Above that level, the strongest nearby short-liquidation zones extend from approximately $65,000 to $66,000.

These concentrations can attract price as exchanges close leveraged positions, but they do not guarantee direction. Bitcoin could first sweep liquidity below $63,000 before attempting to recover, particularly while money flow remains negative.

Can Bitcoin price rebound toward $65,000?

Bitcoin needs to reclaim the 4-hour Bollinger midpoint near $63,886 to establish an initial recovery signal. A move above $64,000 would open a path toward $65,000 and the upper Bollinger Band at $65,284.

Clearing that area could trigger short liquidations and allow Bitcoin to retest $65,800 to $66,000. The broader recovery would remain incomplete until price breaks above the July high near $66,900 and the 0.618 Fibonacci level at $67,284.

Crypto analyst Ali Martinez also identified a TD Sequential sell signal on Bitcoin’s three-day chart.

“Bitcoin is flashing a warning sign,” Martinez said, adding that the signal appeared shortly before the start of August.

The TD Sequential attempts to identify trend exhaustion, but it does not independently confirm a decline. Bitcoin’s reaction at $63,150, ETF demand, and developments around the CLARITY Act will provide more immediate signals.

A sustained break below $62,000 would weaken the outlook and expose $60,000, followed by the June low near $57,884. Conversely, a recovery above $65,284 would reduce the immediate bearish pressure and shift attention back toward $67,284.

Tether earned $1.5 billion in three months while its safety cushion fell by half, raising questions about whether the world’s largest stablecoin can sustain its reserve strategy through a rate cycle.

The numbers look strong. Tether generated $1.5 billion in net operating profit during the second quarter of 2026, according to its latest attestation prepared by BDO and released on July 31. The stablecoin issuer’s total assets stood at $187.75 billion against $183.64 billion in liabilities. USDT retained more than 60% of the global stablecoin market. By every headline metric, the quarter was a success.

But the headline metrics obscure a structural shift in Tether’s balance sheet that deserves closer examination. The company’s excess reserves, the buffer between what Tether owns and what it owes to USDT holders, fell from $8.23 billion to $4.11 billion in a single quarter. That is a 50% decline in the safety cushion that Tether has spent years building. A company that earned $1.5 billion in profit somehow ended the quarter with half the reserve buffer it started with.

The explanation involves gold, bitcoin, secured lending, and the fundamental question of what a stablecoin issuer’s balance sheet should look like. Tether’s Q2 results reveal a company caught between its role as the infrastructure layer for global dollar access and its ambition to operate as a diversified financial conglomerate.

Where $4 billion went

The arithmetic of the reserve decline is straightforward. Tether entered Q2 with $8.23 billion in excess reserves. It earned $1.5 billion in operating profit. Without any other changes, the buffer should have grown to approximately $9.7 billion. Instead, it fell to $4.11 billion. That implies roughly $5.6 billion in value left the balance sheet through some combination of unrealized losses, capital deployment, and operational expenditure.

The two largest contributors were gold and bitcoin. Tether increased its gold holdings from 132.2 metric tons to 146.2 metric tons during the quarter, purchasing approximately 14 additional tons. But the price of gold fell roughly 15% to just above $4,000 per ounce during the same period. The result: the value of Tether’s gold position declined from $19.84 billion to $18.84 billion despite the company buying more of it. The net loss on gold was approximately $1 billion.

Bitcoin told a similar story. Tether added 1,796 BTC to reach a total of 98,933 coins. But the bitcoin price used in the attestation declined from $68,200 to $58,600 during the quarter. The value of the bitcoin position fell from $6.62 billion to $5.80 billion, a decline of approximately $820 million despite the additional purchases.

Between gold and bitcoin alone, Tether absorbed roughly $1.8 billion in unrealized losses during Q2. Combined with the capital deployed to purchase additional gold and bitcoin, the expansion of the USAT stablecoin infrastructure, and operating expenses, the $5.6 billion gap between expected and actual reserve growth becomes explicable. But explicable is not the same as comfortable.

The secured lending reduction added another dimension. Tether cut its outstanding secured loans by approximately $2.38 billion, a 15% decline. Reducing secured lending is generally positive for reserve quality because it replaces counterparty risk with direct asset holdings. But the timing of the reduction, during a quarter when the reserve buffer was already under pressure from mark to market losses, suggests that some of the lending reduction may have been involuntary. Tether did not disclose the identities of borrowers or the collateral involved, leaving analysts to speculate about whether loans were called, matured, or deliberately wound down.

The net effect is a balance sheet that looks materially different from three months earlier. At the end of Q1, Tether could point to $8.23 billion in excess reserves as evidence that USDT holders had a substantial cushion beyond dollar for dollar backing. At the end of Q2, that cushion is half the size despite continued profitability. The trajectory matters more than any single quarter’s snapshot.

The reserve composition question

Tether’s reserve strategy has evolved significantly over the past three years. The company has shifted the majority of its reserves into US Treasury securities and short duration government debt, a move that addressed years of criticism about the transparency and quality of its backing. The Treasury portfolio is now the primary source of Tether’s operating profit and the foundation of its claim that USDT is fully backed by liquid, high quality assets.

But Tether has simultaneously built substantial positions in gold and bitcoin, assets that do not generate yield and are subject to significant price volatility. At the end of Q2, Tether held approximately $18.84 billion in gold and $5.80 billion in bitcoin. Together, these positions represented roughly $24.6 billion, or about 13% of total assets.

For a company whose core obligation is maintaining a 1:1 peg to the US dollar, holding 13% of reserves in volatile non dollar assets creates a structural tension. When gold and bitcoin rise, the excess reserve buffer expands and Tether looks increasingly overcollateralized. When they fall, as they did in Q2, the buffer shrinks rapidly even as the operating business continues to generate profit.

The question is whether Tether’s reserve strategy is optimized for the stablecoin business or for Tether the company. A pure stablecoin issuer would hold 100% of reserves in short duration dollar denominated instruments, maximizing liquidity and minimizing volatility. Tether’s choice to hold gold and bitcoin reflects a different objective: building long term value for the company’s owners beyond the stablecoin operation itself.

The interest rate dependency

Tether’s $1.5 billion quarterly profit depends almost entirely on one variable: the yield on short term US government debt. The company earns its revenue by holding USDT holders’ dollars in Treasury bills and repo agreements. When rates are high, Tether is extraordinarily profitable. When rates fall, that profit declines proportionally.

The Federal Reserve’s current policy rate makes Tether one of the most profitable financial operations in the world on a per employee basis. The company reportedly has fewer than 100 employees. Its annualized revenue per employee exceeds $60 million, a figure that dwarfs the most profitable technology companies. But this profit model has no moat. It depends on a macroeconomic condition, high US interest rates, that Tether cannot control and that most economists expect to reverse over the next 12 to 24 months.

Paolo Ardoino, Tether’s CEO, framed Q2 as evidence of resilience. “Through all of the volatility, USDT remained fully backed with our reserves still exceeding liabilities by $4.11 billion,” he said in the company’s statement. The framing is technically accurate. But “fully backed” and “safely buffered” are different standards, and the Q2 results expose the gap between them.

If the Fed cuts rates by 200 basis points over the next year, Tether’s annualized operating profit would fall from approximately $6 billion to roughly $3 billion, assuming constant USDT supply. That is still an enormous figure, but the trajectory matters. A declining profit stream makes it harder to rebuild the reserve buffer, fund expansion projects, and maintain the gold and bitcoin positions that have already demonstrated their ability to consume billions in unrealized losses during a single quarter.

The GENIUS Act’s 2028 compliance deadline adds a regulatory dimension to the interest rate question. If Tether must restructure its reserves or operations to comply with US stablecoin legislation, the cost of compliance will arrive precisely when falling rates are already compressing margins.

The audit that has not arrived

Tether announced in March 2026 that it had engaged KPMG to conduct its first full financial audit. The engagement was widely reported as a milestone for a company that had faced years of criticism for relying on quarterly attestations from smaller accounting firms rather than a comprehensive audit from a Big Four firm.

Five months later, the KPMG audit has not been completed. Tether’s Q2 attestation was again prepared by BDO, the same firm that has handled previous attestations. The Q2 release stated that “the Big Four audit process continued” but provided no completion date, interim findings, or timeline.

An attestation and an audit are fundamentally different exercises. An attestation verifies that a company’s stated financial figures are accurate at a specific point in time. An audit examines the company’s financial statements, internal controls, and accounting practices over a full reporting period. The distinction matters because an attestation can confirm that Tether held $187.75 billion in assets on June 30 without examining how those assets were managed, valued, or moved during the preceding 90 days.

The delay is not necessarily a red flag. Big Four audits of complex financial institutions routinely take 12 to 18 months. But the absence of a timeline creates uncertainty that compounds with each quarterly attestation that arrives without the audit attached. Tether’s competitors, including Circle, which issues USDC, already publish audited financial statements. The longer the KPMG process takes without a public update, the more the engagement risks becoming a liability for Tether’s credibility rather than an asset. If the audit eventually produces a clean opinion, the delay will be forgotten. If it surfaces material findings or qualifications, the five month silence will look like a warning that the market ignored.

The competitive landscape

Tether’s 60% market share is formidable but not unassailable. USDC, issued by Circle, has grown steadily and now represents approximately 25% of the stablecoin market. Circle completed its IPO in early 2026 and publishes regular financial disclosures as a public company. For institutional users who require audited counterparties, Circle’s transparency advantage is significant.

The emerging regulatory framework in the United States may further reshape the competitive landscape. The GENIUS Act, if enacted in its current form, would require stablecoin issuers serving US customers to meet specific reserve, disclosure, and compliance standards. Tether’s offshore corporate structure, domiciled in El Salvador, could complicate its ability to meet these requirements without significant restructuring.

Meanwhile, new entrants continue to arrive. PayPal’s PYUSD has captured modest market share. Banks including JPMorgan and Bank of America have launched or announced proprietary stablecoin products. The common thread among these competitors is that they operate within established regulatory frameworks, a characteristic that could become a decisive advantage as stablecoin regulation matures.

Tether’s response has been to expand beyond stablecoins entirely. The company has invested in bitcoin mining, artificial intelligence infrastructure, and telecommunications. It has also launched USAT, a US focused stablecoin that recently deployed on Celo as its second mainnet. These diversification efforts may generate value over time, but they also consume capital that could otherwise strengthen the reserve buffer. In Q2, the buffer declined while the company continued to fund expansion.

The private ownership structure adds another layer of complexity. Unlike Circle, which must answer to public shareholders, Tether operates with minimal external governance. The company’s capital allocation decisions, including the choice to hold nearly $25 billion in gold and bitcoin, are made by a small group of executives and owners without the scrutiny that comes with public listing. The Q2 reserve decline occurred under conditions that a public company board would likely have flagged for discussion well before the buffer halved.

The $184.6 billion question

USDT supply grew by only $446 million during Q2, the slowest quarterly growth in more than two years. For a token that added tens of billions in supply during 2024 and early 2025, the near stagnation is notable. The slowdown occurred despite continued growth in Tether’s user base, which the company said expanded by more than 30 million users during the quarter.

The disconnect between user growth and supply growth suggests that new USDT users are transacting in smaller amounts or using the token primarily for payments and transfers rather than as a store of value. That is consistent with Tether’s narrative about serving the unbanked and providing dollar access in emerging markets. But it also means the USDT supply, and therefore Tether’s revenue base, may be approaching a plateau at current interest rates and market conditions.

The 30 million new users Tether cited represent a significant expansion of its reach, particularly in regions where traditional banking infrastructure is limited or where local currencies face sustained devaluation. Tether has actively pursued partnerships in Africa, Latin America, and Southeast Asia to position USDT as everyday payment infrastructure. The Nairobi Securities Exchange memorandum of understanding, signed on July 28, is the latest example of this strategy. But payment volume and stablecoin supply are different metrics. A user who receives $50 in USDT, spends it within hours, and never holds a balance contributes to transaction volume but not to the outstanding supply that generates Tether’s revenue.

The slowdown in supply growth also coincides with increased competition from USDC in institutional and regulated markets. As Circle’s public listing provides greater transparency and US based stablecoin legislation approaches, some institutional flows that previously favored USDT may be shifting to USDC or emerging alternatives. Tether’s dominance in retail and emerging market payments remains unchallenged, but the marginal growth that drives supply expansion may increasingly come from segments where per user balances are small.

If USDT supply growth has stalled while the reserve buffer is declining, Tether faces a narrowing path. The company needs strong operating profits to rebuild reserves. Those profits depend on high interest rates and growing supply. Rates are expected to fall. Supply growth has slowed. The buffer is the variable that absorbs the difference.

At $4.11 billion, the excess reserve buffer represents approximately 2.2% of USDT’s total supply. That is a thin margin for a $184.6 billion obligation, particularly when 13% of the backing assets are subject to significant price volatility. The record $8.23 billion buffer reported at the end of Q1 provided a 4.5% cushion. The halving of that cushion in a single quarter demonstrates how quickly market conditions can erode what took years to build.

What to watch

• The KPMG audit timeline. Tether has said the process is ongoing but has not provided a completion date. The first audited financial statement from Tether would be a watershed event for stablecoin transparency. Continued delays without explanation will erode the credibility advantage the engagement was intended to create.

• Gold and bitcoin price movements in Q3. If gold and bitcoin recover in the third quarter, Tether’s reserve buffer will expand mechanically without any operational improvement. If they decline further, the buffer could fall below $3 billion, a level that would intensify scrutiny from regulators and analysts.

• Federal Reserve rate decisions. Each 25 basis point cut reduces Tether’s annualized operating profit by approximately $450 million. The timing and pace of rate cuts will determine whether Tether can maintain its current profit trajectory or faces a structural decline in earnings.

• USDT supply growth trajectory. Whether the $446 million quarterly growth in Q2 was a temporary slowdown or the beginning of a plateau will shape Tether’s revenue outlook for the next 12 months. Supply growth in Q3 will provide a clearer signal.

• GENIUS Act implementation timeline. The 2028 compliance deadline gives Tether approximately 18 months to determine whether and how to restructure for US market access. Any public statements about compliance strategy will signal whether Tether intends to compete directly in the US or cede that market to regulated competitors.

Frequently asked questions

Disclaimer: This article is for informational purposes only and does not constitute financial or investment advice. The information presented reflects publicly available data as of August 1, 2026. Readers should conduct their own research and consult qualified professionals before making financial decisions.