Base has delayed its Beryl mainnet upgrade by one day to ensure the B20 Activation Registry is fully operational before the hard fork goes live.

Base announced that Beryl will now activate on mainnet on June 26 at 18:00 UTC instead of the previously scheduled June 25 launch.

Source: basedocs.

The Ethereum layer 2 network attributed the delay to a timing dependency involving the B20 Activation Registry, which must complete its initialization before developers can deploy native B20 tokens.

The network explained that the Activation Registry controls whether B20 feature flags become available after the hard fork. Base added that the registry can take up to one hour to come online after activation, making the additional delay necessary before the upgrade proceeds.

B20 rollout and withdrawal changes

Beryl is Base’s second independent network upgrade after Azul, which reached mainnet in May. The release introduces B20, a protocol level token standard that allows issuers to create stablecoins and real-world asset tokens directly within Base’s node software instead of deploying conventional ERC 20 smart contracts.

Base previously said B20 remains compatible with the ERC 20 specification and supports ERC 2612 permit functionality, allowing existing wallets, exchanges, and indexers to work without modification. The protocol also includes an Issuer Toolkit that offers role-based permissions, mint and burn controls, transfer restrictions, optional supply limits, and freeze and seizure features for regulated issuers.

The hard fork also shortens the standard withdrawal period from Base to Ethereum from seven days to five days for the route used by most bridging providers. Base has previously attributed the reduction to improvements introduced through Azul’s Multiproofs framework, which reduced reliance on the original fault-proof challenge window. 

Beryl also integrates Reth V2, which the network said reduces storage requirements for nodes by up to 50% while supporting higher block gas targets.

Outage occurred before planned activation

Base originally scheduled Beryl for June 25, the same day the network experienced a block production outage that lasted for nearly two hours. The engineering team identified a consensus issue after an invalid block entered the sequencing pipeline and temporarily stopped new block creation.

Engineers restored normal block production later that day, while Base confirmed the incident was unrelated to the planned Beryl upgrade.

Blocks are being produced normally, and we have verified widespread recovery in the ecosystem.

Any remaining stuck Base nodes will recover upon restart and syncing.

The team has found the root cause for this halt and we’ll share a full post mortem based on our learnings and…

— Base Build (@buildonbase) June 25, 2026

Base creator Jesse Pollak also stated that user funds remained safe during the outage while acknowledging that network halts were unacceptable for infrastructure intended to support global financial activity.

Base has scheduled its next network upgrade, Cobalt, for September. The company expects that release to introduce native account abstraction, protocol level smart accounts, gas sponsorship, transaction batching, additional B20 capabilities, and a unified node binary that combines consensus and execution clients.

Every time you send crypto from one exchange to another above a certain amount, your identifying information may travel with it, shared between the platforms behind the scenes. That is the Travel Rule, a decades-old banking standard now reshaping crypto. This guide explains what it requires, why it exists, and what it means for your privacy.

The Travel Rule is an anti-money-laundering requirement that obliges financial institutions and crypto service providers to collect, share, and retain identifying information about both the sender and the recipient of a transfer above a certain value, so that the data effectively travels alongside the transaction. In the crypto context, this means that when you send digital assets above a threshold from one regulated platform to another, your platform may be required to transmit details about you, and to receive details about the recipient, behind the scenes.

The name comes from this idea of information traveling with the transfer, and the concept is not new: it has governed bank wire transfers for decades. What is new, and what makes it one of the most consequential pieces of crypto regulation in 2026, is that the same standard now applies to virtual assets, bringing crypto transfers under the kind of anti-money-laundering scrutiny long applied to traditional bank wires

For users accustomed to thinking of crypto as private or pseudonymous, the Travel Rule represents a significant shift, because it weaves identity and traceability into transfers that once felt anonymous.

Understanding the Travel Rule matters because it sits at the intersection of three related concepts that often get confused: know-your-customer checks, anti-money-laundering frameworks, and the specific obligation to share counterparty information on transfers. It also has real, practical consequences for how exchanges operate, what information they must gather from you, and how much privacy you can expect when moving crypto between regulated platforms.

This guide explains where the Travel Rule came from, how it was extended to crypto, exactly what information must be shared and how, who is covered and who is not, the wide variation in thresholds across countries, how the rule fits together with know-your-customer and anti-money-laundering obligations, a concrete worked example, and the genuine limits and privacy questions the rule raises.

The goal is to give you a clear picture of a regulation that increasingly shapes the everyday experience of using crypto, without either downplaying its reach or exaggerating its grip.

Where the Travel Rule came from

The Travel Rule did not begin with crypto; it began with banks, and its history explains both its logic and its name. In the United States, the rule traces back to the Bank Secrecy Act, the long-standing law designed to combat money laundering, and to guidance issued by the Financial Crimes Enforcement Network in the 1990s.

For decades, banks have been required to include identifying information, such as names and account numbers, when they pass funds from one institution to another in a wire transfer above a certain amount. The purpose was straightforward: by making identifying information travel with the money, regulators gained the ability to trace funds and flag suspicious activity, creating an auditable trail that makes it harder for illicit money to move undetected through the financial system. This original Travel Rule applied to traditional financial institutions and the wires they sent between one another.

When cryptocurrency emerged, and transactions began happening globally and at scale, regulators recognized that the same money-laundering risks applied, and that crypto’s pseudonymity could make it attractive for moving illicit funds.

The body that drove the extension to crypto is the Financial Action Task Force, an international organization that sets anti-money-laundering standards that countries around the world adopt into their own laws. In 2019, the Financial Action Task Force updated its guidance, specifically a provision known as Recommendation 16, to make clear that the Travel Rule should apply to virtual assets and to the businesses that handle them.

This extension meant that crypto exchanges, custodians, and similar providers would need to follow rules similar to those long applied to banks, collecting and sharing sender and recipient information on qualifying transfers. The guiding principle the Financial Action Task Force articulated was same risk, same rules: activities that carry similar money-laundering risks should face similar standards regardless of the technology involved.

Since 2019, countries have been writing their own versions of the crypto Travel Rule into national law, which is why the rule now exists worldwide but with meaningful variations from one jurisdiction to the next.

What information must be shared, and how

The substance of the Travel Rule is the specific information that must accompany a qualifying transfer, and understanding it clarifies what the rule actually does. When a transfer crosses the relevant threshold, the service provider of the sender, often called the originator, must share identifying details about that sender with the service provider of the recipient, often called the beneficiary, and in turn receive the beneficiary’s details. The information typically includes the names of both parties, their account or wallet identifiers, and, in some cases, additional details such as a physical address or an identification number. The aim is to attach a verifiable identity to both ends of the transfer so that, if needed, authorities can trace who sent value to whom.

A point that often surprises people is where this information goes, and the answer is that it does not go on the blockchain. The Travel Rule data is shared off-chain, through secure messaging channels directly between the two service providers, rather than being written into the public ledger. This design preserves the efficiency and privacy characteristics of the blockchain transaction itself while still meeting the compliance requirements, since the sensitive personal information moves through a separate, private channel between the regulated institutions. To make this work across a global industry, the sector has developed standardized messaging formats and protocols that let different providers exchange the required data reliably, along with services that help a provider verify the identity of the counterparty institution before sending personal information to it.

These solutions address a genuine technical challenge: a provider must confirm that the receiving institution is who it claims to be and can handle the data securely before transmitting a customer’s personal details, because sending such information to the wrong party would itself be a serious problem. The result is an off-chain layer of identity infrastructure running alongside the on-chain transactions, invisible to most users but increasingly central to how regulated crypto transfers work.

Who is covered and who is not

A crucial question for any user is whether the Travel Rule applies to them, and the answer depends on whether a regulated intermediary is involved. The rule applies to the businesses that handle crypto on behalf of customers, known in the relevant frameworks by various labels: virtual asset service providers, crypto-asset service providers, or money services businesses, depending on the jurisdiction. The covered entities include crypto exchanges, custodial wallet providers, over-the-counter trading desks, crypto payment processors, and regulated financial institutions that deal in digital assets. The common thread is that these are intermediaries that accept and transmit customer value, and the obligation falls on them, not on individual users directly, though the practical effect is that users of these services must provide the identifying information the providers are required to collect and share.

Equally important is what the Travel Rule does not cover. It generally does not apply to direct peer-to-peer transfers between two private, self-hosted wallets, sometimes called unhosted wallets, where no regulated intermediary is involved, because there is no service provider in the middle to collect and transmit the data. That said, the picture is more nuanced at the edges: when a regulated provider sends funds to or receives funds from an unhosted wallet, the provider may still be required to collect information about the transfer even if it cannot share it with a counterparty institution that does not exist.

Decentralized finance protocols and other non-custodial services occupy a genuinely ambiguous space because they often lack a clear intermediary to bear the obligation, and regulators are actively exploring how, or whether, to extend the rules to them. For most ordinary users, the practical takeaway is that transfers between regulated exchanges and custodial services are squarely within the rule’s scope and will involve information sharing, while transfers between two wallets you control personally generally are not, even as the boundaries around decentralized and self-custodied activity remain unsettled and under regulatory review.

How thresholds vary around the world

One of the most important practical features of the Travel Rule is that there is no single global threshold or authority; instead, each jurisdiction sets its own rules, and the variation is substantial. In the United States, the Travel Rule derives from the Bank Secrecy Act and is enforced by the Financial Crimes Enforcement Network, with a long-standing threshold of three thousand dollars for the obligation to attach identifying information, although proposals have circulated to lower that figure significantly for international transfers.

The European Union has taken the strictest approach through its Transfer of Funds Regulation, which took effect at the end of 2024 and applies a zero threshold to crypto transfers, meaning that every single crypto transfer between providers, regardless of amount, requires full Travel Rule compliance. This regulation operates alongside the broader Markets in Crypto-Assets framework, together forming Europe’s comprehensive crypto compliance regime across all member states.

Other major jurisdictions fall at various points along this spectrum. The United Kingdom introduced its own Travel Rule requirements in 2023, applying them to all transfers regardless of amount. Canada enforces the rule through its financial intelligence agency with a threshold of around 1,000 Canadian dollars, making it relatively strict. Switzerland has adopted one of the toughest versions, requiring firms to identify both parties even for amounts below the thresholds used elsewhere, reflecting its emphasis on strict financial oversight. 

Several Asian financial centers, including South Korea, Singapore, and Hong Kong, have implemented firm Travel Rule obligations, often pushing the industry toward standardized compliance technology, while other regions are still developing their frameworks. For users and businesses operating across borders, this patchwork is a genuine challenge, because the same transfer might be subject to full compliance in one jurisdiction and none in another, and a provider serving customers in multiple countries must navigate the strictest applicable requirements. The variation is not a sign of confusion so much as a reflection of how recently and unevenly the global standard has been adopted into national law.

How the Travel Rule fits with KYC and AML

The Travel Rule is often mentioned alongside know-your-customer and anti-money-laundering obligations, and clarifying how the three relate helps make sense of the broader compliance picture. Anti-money-laundering, usually shortened to AML, is the umbrella framework, the overall body of laws and practices designed to prevent the financial system from being used to launder the proceeds of crime or finance illicit activity. Within that framework sit specific obligations, and two of the most important are know-your-customer checks and the Travel Rule, which address different points in the lifecycle of a customer relationship and a transaction.

Know-your-customer, or KYC, refers to the process by which a service provider verifies the identity of its own customers, typically at the point of onboarding, by collecting documents and information to confirm who they are. It answers the question of whether the provider knows who its customer is. The Travel Rule addresses a different moment: it governs what happens when that customer makes a transfer, requiring the provider to share the customer’s identifying information with the counterparty provider on the other end of a qualifying transaction.

In other words, know-your-customer confirms identity at the door, while the Travel Rule makes that identity information move with transfers between institutions. The two interlock, because the provider can only share accurate sender information under the Travel Rule if it has properly verified that sender through know-your-customer in the first place. Sanctions screening adds a further layer, since providers must also check the parties to a transfer against sanctions lists to avoid processing transactions for prohibited persons.

Together, these obligations form a connected compliance system: know-your-customer identifies the customer, the Travel Rule shares that identity across transfers, sanctions screening checks it against prohibited lists, and the whole apparatus serves the overarching anti-money-laundering goal of keeping illicit funds out of the system.

A worked example: a transfer between two exchanges

A simple example makes the mechanics tangible. Suppose you hold Bitcoin on one regulated exchange, call it Exchange A, and you want to send an amount worth more than the applicable threshold, say more than $3,000  in a jurisdiction using that figure, to your account on another regulated exchange, Exchange B. When you initiate the transfer, the Bitcoin itself moves on the blockchain from Exchange A’s systems toward Exchange B’s, exactly as any Bitcoin transaction would. That part is visible on the public ledger, as Bitcoin transactions always are. What happens alongside it, invisibly to you, is the Travel Rule compliance.

Because the transfer exceeds the threshold and both ends involve regulated service providers, Exchange A is required to transmit your identifying information, as the originator, to Exchange B, and Exchange B, in turn, provides information about the beneficiary account. This exchange of data happens off-chain, through a secure messaging channel between the two exchanges, using a standardized format so that each can reliably read the other’s data. Before sending your personal details, Exchange A verifies that Exchange B is a legitimate, identifiable institution capable of receiving the information securely. Exchange B, on receiving both the Bitcoin and your information, can match the incoming transfer to the data and complete its own compliance checks, including screening against sanctions lists. From your perspective, you simply sent Bitcoin from one exchange to another, perhaps noticing only that both required your identity to be verified when you signed up.

Behind that ordinary experience, however, your identifying information traveled with the transfer between the two regulated institutions, which is the Travel Rule working exactly as intended. Had you instead sent the same Bitcoin from one personal wallet you control to another, with no exchange involved, the Travel Rule would generally not have applied, because there would have been no regulated intermediary to carry the obligation. 

Limits, gaps, and privacy considerations

For all its expanding reach, the Travel Rule has genuine limits and raises real questions, and an honest account should address them directly. The most discussed structural limit is what experts call the sunrise problem, which describes the uneven pace at which jurisdictions have adopted Travel Rule requirements. Because some countries enforce the rule fully while others have not yet implemented it, providers in jurisdictions without requirements may delay building compliance systems, creating gaps in the global information-sharing network the rule is meant to build. This patchwork reduces the incentive for universal adoption and means the rule’s effectiveness depends on how widely and consistently it is enforced, which remains a work in progress.

A determined bad actor can still seek out jurisdictions or services where the rule does not yet bite, which is precisely the kind of gap a global standard is supposed to close but has not fully closed.

The most significant concern for ordinary users, however, is privacy. The Travel Rule, by design, reduces the anonymity once associated with crypto, requiring that identifying information be collected, shared between institutions, and retained. This raises legitimate questions about data security, because personal information that is collected and transmitted can be exposed if a provider suffers a breach or if the data is mishandled, and the more institutions hold and share such data, the larger the potential attack surface.

Some users see the loss of financial privacy as a genuine drawback, while supporters argue that the same information sharing builds trust in platforms and aligns crypto with established financial standards, making it safer and more acceptable to mainstream institutions and regulators. There is also the unresolved tension around decentralized finance and self-custody, where applying a rule built for intermediaries to systems designed to operate without them remains genuinely difficult, and where overly aggressive extension could undermine the permissionless qualities that give those systems their value.

The honest summary is that the Travel Rule is a serious, expanding compliance obligation that brings real benefits in combating illicit finance and real costs in privacy and complexity, and that its boundaries, particularly around unhosted wallets and decentralized protocols, are still being worked out. For users, the practical reality is that moving crypto between regulated platforms now comes with identity sharing attached, and that is unlikely to reverse.

Frequently Asked Questions

This article is educational information, not legal or financial advice. Travel Rule requirements, thresholds, and enforcement vary by jurisdiction and reflect information available as of June 26, 2026, and can change. The treatment of self-hosted wallets and decentralized finance in particular remains unsettled. Verify the current rules in your jurisdiction from primary sources, and consult a qualified professional for guidance on your specific situation. 

Bitcoin is the largest pool of value in crypto, but on its own, it cannot touch Ethereum’s world of lending, borrowing, and yield. Wrapped Bitcoin is the bridge. This guide explains how WBTC works, the mint-and-burn model behind it, the alternatives, and the custodial risks that set it apart from holding real BTC.

Wrapped Bitcoin, known by its ticker WBTC, is an ERC-20 token that runs on the Ethereum blockchain and is backed 1:1 by real Bitcoin held in reserve, so that one WBTC is always meant to equal one Bitcoin. Its entire purpose is to solve a fundamental incompatibility in crypto: Bitcoin, the largest and most valuable cryptocurrency, lives on its own blockchain and cannot natively participate in the decentralized finance applications built on Ethereum, because those applications run on smart contracts that Bitcoin’s design does not support.

An enormous amount of crypto wealth sits in Bitcoin, while an enormous amount of programmable financial activity happens on Ethereum, and for years, there was no way to bring the two together. Wrapped Bitcoin is the bridge. By locking real Bitcoin with a custodian and issuing an equivalent Ethereum token against it, WBTC lets Bitcoin holders put their Bitcoin’s value to work inside Ethereum’s ecosystem, lending it, borrowing against it, trading it, supplying it to liquidity pools, and using it as collateral, all without selling their Bitcoin exposure. It was the first widely adopted way to do this, and it remains one of the most integrated.

The idea is simple, but the details are where the important nuances live, and they are worth understanding before using WBTC, because the convenience comes with trade-offs that holding plain Bitcoin does not have. A wrapped token introduces extra parties and extra trust assumptions, and the question of who holds the underlying Bitcoin, and whether you can always get it back, sits at the center of the whole arrangement.

This guide explains what WBTC is, why it is needed, exactly how the mint-and-burn mechanism works, who the custodians and merchants are, and why they matter, a concrete example of using WBTC in practice, how it compares to native Bitcoin and to newer alternatives like cbBTC and tBTC, and the specific risks that come with holding a wrapped asset rather than the real thing. The aim is to let you decide whether wrapped Bitcoin fits your needs or whether plain Bitcoin is the cleaner choice.

Why Bitcoin needs wrapping

To understand why WBTC exists, you have to understand a basic limitation of Bitcoin. Bitcoin was designed as a secure, decentralized system for holding and transferring value, and it does that job extremely well, but its scripting language is deliberately limited and is not built to run the complex, self-executing programs known as smart contracts.

Ethereum, by contrast, was built specifically to run smart contracts, and decentralized finance, the ecosystem of lending protocols, decentralized exchanges, and yield platforms, is constructed almost entirely on Ethereum and similar smart-contract blockchains.

The consequence is that Bitcoin, despite being the largest store of value in crypto, simply cannot plug into these applications directly. A Bitcoin holder who wanted to earn yield or use their holdings as collateral in DeFi had no native way to do so.

This is the gap wrapping fills. The core problem is one of interoperability, the ability to use an asset from one blockchain on another, and wrapping is one of the earliest and most widely used solutions to it. By representing Bitcoin as a token that conforms to Ethereum’s technical standards, specifically the ERC-20 standard that Ethereum applications are built to recognize, wrapped Bitcoin makes Bitcoin-linked value fully usable inside the Ethereum environment.

The ERC-20 standard is a set of rules that makes a token fully compatible and interchangeable across Ethereum’s smart contracts, so a wrapped Bitcoin token can be lent, borrowed, swapped, and used as collateral exactly like any other Ethereum token.

Wrapping, therefore, reduces the fragmentation between Bitcoin’s huge liquidity and Ethereum’s rich application layer, turning Bitcoin from an asset that sits outside DeFi into one that can be put to work within it. That is the entire reason wrapped Bitcoin was created, and why it found immediate demand. 

How the mint-and-burn model works

The mechanism that keeps wrapped Bitcoin backed 1:1 by real Bitcoin is called mint and burn, and it relies on a three-party system of custodians, merchants, and users.

The custodian is a regulated entity that holds the actual Bitcoin in secure reserve; for WBTC, this role has been played by the digital-asset custody firm BitGo. The merchant is an intermediary, such as an exchange or crypto business, that interacts with users, performs the necessary identity and compliance checks, and distributes the wrapped tokens. The user is the person who wants to convert between Bitcoin and wrapped Bitcoin. These three parties, coordinated by a set of smart contracts, keep the supply of WBTC matched to the Bitcoin held in reserve.

The process works in two directions. To create, or mint, wrapped Bitcoin, a user requests WBTC from a merchant, who carries out know-your-customer and anti-money-laundering checks to verify the user’s identity. The merchant then sends the corresponding Bitcoin to the custodian, who holds it in reserve and mints an equal amount of WBTC on Ethereum, which makes its way to the user.

To reverse the process, or burn the tokens, a user who wants their Bitcoin back submits a redemption request, the WBTC is destroyed in what is called a burn transaction, and the custodian releases the equivalent Bitcoin from reserve. Because every WBTC in existence is meant to correspond to a Bitcoin locked with the custodian, the token maintains its 1:1 peg, and its price tracks Bitcoin’s price closely.

Importantly, both the minting and the burning are recorded publicly on the Ethereum and Bitcoin blockchains, so anyone can verify the activity, and the system is periodically subjected to proof-of-reserve checks that confirm the Bitcoin backing actually exists. This transparency is meant to give holders confidence that the wrapped tokens are genuinely backed, though, as the risks section explains, it does not remove the reliance on the custodian.

Who governs WBTC, and why it matters

A wrapped token raises an obvious question: who controls the system, decides which custodians and merchants are trusted, and can change how it works. For WBTC, the answer is a decentralized autonomous organization known as the WBTC DAO, a governing body made up of a group of stakeholders that has included prominent names in the crypto space.

The DAO operates through a multi-signature wallet, meaning that changes require the agreement of multiple keyholders rather than any single party, and its members can vote to add or remove custodians and merchants and to make changes to the smart contracts on which the system runs. This governance structure exists specifically to reduce the centralization risk that would come from a single company controlling the entire arrangement, spreading authority across a set of stakeholders instead.

Why this matters became vivid in 2024, in what served as the clearest real-world stress test of WBTC’s governance. The custodian BitGo announced a change to its custody arrangements involving a partnership with another firm, and that change sparked significant concern across decentralized finance because of the new partner’s perceived links to a controversial figure and ecosystem.

The episode mattered because it went to the heart of the trust assumption underlying WBTC: holders were trusting that the Bitcoin backing their tokens was held safely and by parties they considered reliable, and a change in who effectively controlled that custody was enough to shake confidence and prompt many users and protocols to reconsider. It also accelerated the rise of alternative wrapped Bitcoin products with different custody models.

The lesson is that the governance and custody arrangements of a wrapped token are not background details; they are central to its safety, because the whole value of WBTC rests on the Bitcoin being there and being controlled by trustworthy parties. Who governs the system, and how, is therefore something a prospective holder should actually look into rather than take for granted.

A worked example: putting Bitcoin to work

A concrete example shows why someone would bother wrapping their Bitcoin in the first place. Imagine a person named Ezra who holds $2,000 worth of Bitcoin and believes in it as a long-term holding, but who also wants to earn a return on that value instead of letting it sit idle. The problem is that the lending protocol Ezra wants to use, which would pay interest on deposited assets, runs on Ethereum, and Ezra’s Bitcoin cannot be deposited there directly because it lives on a different blockchain that the protocol cannot interact with. Without wrapping, Ezra’s only options would be to sell the Bitcoin for an Ethereum-native asset, giving up his Bitcoin exposure, or to leave it earning nothing.

Wrapping solves this. Ezra converts his Bitcoin into wrapped Bitcoin, either by going through a merchant to mint it directly or, more commonly for an ordinary user, by simply swapping his Bitcoin for WBTC on an exchange or decentralized exchange, which avoids the need to interact with the custodians himself. Now holding WBTC, which is an Ethereum token tracking Bitcoin’s price 1:1, Ezra can deposit it into the lending protocol and earn interest, all while his position still rises and falls with the price of Bitcoin. He has kept his Bitcoin exposure and put it to work at the same time. Beyond lending, WBTC opens the same doors that any Ethereum token enjoys: Ezra could supply it to a liquidity pool on a decentralized exchange to earn trading fees, use it as collateral to borrow other assets, or deposit it into yield strategies.

A further practical benefit is speed, since transactions in WBTC settle on Ethereum, which produces blocks far more frequently than Bitcoin, so moving wrapped Bitcoin between Ethereum wallets and applications is quicker than moving native Bitcoin. This is the everyday appeal of wrapped Bitcoin: it lets Bitcoin holders participate in the full range of Ethereum-based finance without selling the Bitcoin they want to keep.

WBTC versus native Bitcoin and the alternatives

It is essential to be clear that wrapped Bitcoin is not the same as holding native Bitcoin, even though the two share a price.

With native Bitcoin, the only real question about safety is whether you control your own private keys; if you do, the Bitcoin is yours, secured by the Bitcoin network itself. With WBTC, the question expands considerably, because you are now also relying on the custodian to actually hold the backing Bitcoin, on the integrity of the reserves, on the governance of the system, and on the redemption process working when you want to convert back.

You may hold the WBTC token in your own wallet, but the wrapped asset still depends on institutional actors operating correctly behind the scenes. WBTC tracks Bitcoin’s market value, but it does not inherit Bitcoin’s trust model, and that difference is the single most important thing to understand about it. If your only goal is to hold Bitcoin for the long term and you have no interest in DeFi, native Bitcoin is the cleaner and simpler choice.

The 2024 custody controversy spurred the growth of alternative tokenized Bitcoin products, and they are worth knowing because they offer different trade-offs. One prominent alternative is cbBTC, issued by the exchange Coinbase, which appeals to users who already trust Coinbase’s custody and operate within its ecosystem. Another is tBTC, built by the Threshold Network, which is designed to avoid reliance on a single custodian in favor of a more decentralized model, appealing to users for whom minimizing custodial trust matters more than convenience. 

There are others as well, and the broader point is that the tokenized Bitcoin market has become fragmented, offering distinct choices for different priorities. The decision among them is fundamentally about trust model and use case instead of price, since they all track Bitcoin: choose WBTC for the deepest liquidity and the widest integration across established DeFi protocols, choose cbBTC if you prefer Coinbase’s custody, choose tBTC if avoiding a single custodian is your priority, and choose native Bitcoin if you do not need DeFi at all. Wrapped Bitcoin products are tools for a specific purpose, not upgrades to Bitcoin.

Risks and what to check before wrapping

The risks of wrapped Bitcoin all stem from the fact that it adds layers of trust on top of simply holding Bitcoin, and understanding them is essential before wrapping any meaningful amount. The primary risk is custodial centralization. Because the wrapped token is only as good as the Bitcoin held in reserve, the failure of the custodian, whether through a hack, insolvency, mismanagement, or loss of access, could impair the backing and leave holders with tokens that no longer correspond to real Bitcoin.

This is not a theoretical concern: history offers cautionary examples of wrapped or bridged Bitcoin products that became impossible to redeem after the entity backing them failed, turning Bitcoin-backed tokens supposedly into worthless or stranded assets. The custody arrangement is the foundation, and if it fails, everything built on it fails with it.

Several other risks compound the custodial one. Smart contract risk means that bugs or vulnerabilities in the Ethereum-side code, or errors in governance, could affect the token. Bridge risk arises when wrapped Bitcoin is moved onto other networks, such as Ethereum layer-two chains, through additional bridges, since each bridging layer adds another set of trust assumptions and another potential point of failure, and you may encounter bridged representations that wrap an already-wrapped token, compounding the risk further. Governance risk means that the parties controlling the system could make decisions, such as the contested custody change, that holders dislike or distrust. And regulatory risk means that official actions could affect redemptions or lead to address restrictions.

The practical advice that follows from all this is to verify before you wrap: check which specific wrapped token and contract you are holding, understand its custody model and who controls the reserves, confirm that proof-of-reserve attestations are current, and make sure you understand the redemption path back to native Bitcoin.

Reviewing the custodian’s transparency, the governance records, and any reputable audits or incident reports before committing meaningful funds is simply prudent. Wrapped Bitcoin is a useful tool that fills a real gap, but it should never be treated as identical to the Bitcoin it represents, because the trust model behind it is fundamentally different.

Frequently Asked Questions

This article is educational information, not financial advice. Wrapped Bitcoin and decentralized finance involve significant risks, including custodial failure, smart contract vulnerabilities, and loss of funds. Details of custodians, governance, and alternatives reflect information available as of June 26, 2026, and can change. Verify the current custody model, reserves, and redemption process of any wrapped token from primary sources, and consider your own circumstances before making any decision.

Key Highlights

• Micron rallied 17.1% following fiscal Q3 2026 results showing $41.46 billion in revenue, a 346% year-over-year increase, with EPS of $25.11 crushing the $20.5 consensus
• Company provided Q4 outlook of approximately $50 billion in revenue and roughly $31 EPS, significantly exceeding analyst projections
• Micron secured approximately $100 billion in multi-year strategic customer commitments through take-or-pay arrangements with 16 partners
• Leadership indicated supply won’t match demand until at least 2028
• Barclays upgraded MU price target by 70% to $2,000 from $1,175 while maintaining a Buy rating

---

Micron Technology posted a quarter for the history books on Wednesday, sparking an immediate and powerful response from investors.

Micron Technology, Inc., MU

The semiconductor manufacturer specializing in memory chips revealed fiscal Q3 2026 sales of $41.46 billion, representing a 346% year-over-year surge and landing approximately 17% higher than Wall Street’s projections. The company’s non-GAAP earnings per share reached $25.11, significantly exceeding the consensus forecast of $20.50. Gross margin expanded dramatically to 84.9%, a stark contrast to the 39% recorded in the same period last year.

MU stock climbed 17.1% following the announcement, reaching $1,209 per share — marking a fresh 52-week high.

While the quarterly performance was impressive in isolation, forward-looking guidance proved to be the real catalyst behind the stock’s momentum.

Micron projected fiscal Q4 revenue at approximately $50 billion with earnings per share around $31. These figures substantially exceeded Wall Street expectations, which had anticipated Q4 revenue near $43 billion and EPS of approximately $25.31.

$100 Billion Worth of Binding Customer Commitments

The chipmaker disclosed it has executed 16 Strategic Customer Agreements (SCAs) — binding take-or-pay contracts spanning data center, consumer, and automotive sectors. Fourteen of these arrangements include a combined minimum revenue obligation of $100 billion throughout their duration.

These represent firm commitments backed by real capital. Partners have already deposited $22 billion. Standard SCAs extend five years (2026–2030), while automotive-focused agreements run for three-year periods.

Barclays analyst Thomas O’Malley characterized the SCA disclosures as exceeding expectations in both dollar magnitude and customer count. He boosted his MU price target by 70% to $2,000 from $1,175, applying a 12x multiple to his updated 2027 EPS projection of $166.74.

O’Malley highlighted that existing SCAs represent roughly 20% of total DRAM volume and 33% of NAND volume. After finalizing all pending agreements, Micron anticipates over 50% of its revenue will originate from these contractual commitments.

Data-center segment revenue exceeded $25 billion during the quarter — translating to an annualized run rate surpassing $100 billion.

Supply Constraints Expected Through 2028

Micron CEO Sanjay Mehrotra stated the company sees “no line of sight” to supply equilibrium with demand occurring before 2028. DRAM pricing increased in the low-60s percentage range during the quarter, fueled by a fundamental supply shortage affecting the entire industry.

This supply-demand imbalance is visible across competitors as well. Samsung disclosed a 146% spike in DRAM average selling prices during Q1. SK Hynix reported mid-60s percent price increases.

The constrained supply environment is affecting all three leading memory manufacturers.

It’s notable that MU shares had declined 13.6% just 48 hours prior following news that SK Hynix was moderating its high-bandwidth memory (HBM) expansion plans. That selloff now appears to have been an overreaction.

Investors should monitor HBM scaling expenses and new fabrication facility construction, which will contribute approximately $1 billion to FY2027 operating costs, along with the eventual repayment of the $22 billion in customer deposits.

Wall Street maintains a Strong Buy consensus rating on MU, featuring 28 Buy ratings against just one Hold. The average analyst price target of $1,526.67 suggests approximately 36% potential upside from current trading levels.

Micron shares have appreciated 283% year-to-date.

Cardano wallet SecondFi has identified a recovery path for users affected by Tuesday’s exploit and expects to begin returning assets in about two weeks, following testing and security reviews.

According to a Saturday statement by Phillip Pon, CEO of SecondFi developer Emurgo, the company completed forensic investigations and established a recovery pathway for affected users. Pon said the coming week would be spent building the solution, followed by another week of testing before assets begin to be returned.

Pon urged users to refrain from migrating assets or taking actions outside official guidance, saying the recovery process was designed around existing wallet states and that independent action could complicate the secure return of funds.

SecondFi developer Emurgo shared an update on the wallet’s recovery efforts. Source: Emurgo

SecondFi disclosed a security breach on Tuesday that affected approximately 16 million ADA, worth about $2.4 million at the time, across 374 addresses. SecondFi previously said it traced the incident to an address-level issue in its Cardano web wallet generation software that exposed users’ private keys.

Related: Q2 2026 emerges as most-hacked quarter on record with 83 incidents

The company also said it secured roughly 129 million ADA through emergency measures and transferred the funds to an independent third-party custodian, where they will remain until the verification and recovery process is complete.

SecondFi has not yet published a comprehensive post-mortem detailing the vulnerability or how the exploit was carried out.

SecondFi warns of recovery-related scams

In a separate update on Saturday, SecondFi warned that malicious actors are circulating fraudulent messages impersonating the wallet while its recovery effort remains underway. 

The company said no recovery actions requiring user participation have begun and that it will never ask users for private keys, seed phrases, wallet credentials or direct wallet access.

SecondFi said any messages instructing users to submit wallet information, migrate assets or take immediate action outside its verified communication channels should be treated as fraudulent. 

It added that users requiring assistance should submit a ticket through its official support portal while the recovery process continues.

Magazine: AI is banking the unbanked in Africa… faster than crypto

Cointelegraph is committed to independent, transparent journalism. This news article is produced in accordance with Cointelegraph’s Editorial Policy and aims to provide accurate and timely information. Readers are encouraged to verify information independently.

Key Takeaways

• Oracle shares plummeted 19% over the past week — the most severe weekly decline since August 2001
• The company’s market valuation has dropped approximately 55% from its September peak near $900 billion
• Capital spending exploded 162% to almost $56 billion during fiscal 2026
• The company’s debt load reached approximately $130 billion by late May, accompanied by nearly $24 billion in negative free cash flow
• Despite the selloff, 71% of Wall Street analysts maintain Buy ratings — a 15-year high

---

Oracle has just endured its most punishing week on the stock market in a quarter century. Shares tumbled 19% over five straight trading sessions, with daily losses exceeding 2.6% each day. The last time the enterprise software giant experienced such a devastating stretch was during August 2001, amid the dot-com bubble collapse.

Oracle Corporation, ORCL

The recent downturn represents more than just a bad week. Oracle’s market capitalization has contracted by roughly 55% since reaching approximately $900 billion last September.

Both the extended decline and this week’s brutal selloff share a common culprit: the escalating expenses tied to Oracle’s artificial intelligence strategy.

Oracle has committed heavily to AI infrastructure development, particularly through its involvement with OpenAI as part of the Stargate initiative. Constructing this infrastructure demands massive capital investment — and currently, shareholders are paying a hefty price.

Financial Metrics Paint a Concerning Picture

As of May’s conclusion, Oracle’s outstanding debt stood at roughly $130 billion. The company’s capital expenditure soared 162% during fiscal year 2026, hitting close to $56 billion.

Free cash flow registered at nearly negative $24 billion for the fiscal year.

To continue financing its infrastructure expansion, Oracle intends to secure an additional $40 billion in fiscal 2027 through combined debt and equity offerings. This follows the previous year’s $43 billion in debt issuance plus $5 billion raised through equity sales.

The fundamental challenge is clear: Oracle finds itself competing against Amazon, Microsoft, and Google in the race to construct AI data center capabilities — yet unlike these rivals, it cannot offer a comprehensive technology ecosystem. This constraint puts pressure on margins for what amounts to an extraordinarily expensive gamble.

Analyst Community Remains Largely Optimistic

Remarkably, analyst confidence hasn’t wavered despite the sharp decline. FactSet data shows 71% of ORCL analysts maintain Buy ratings — representing the strongest bullish sentiment in 15 years. The overall consensus stands at Strong Buy, reflecting 28 Buy recommendations, five Hold ratings, and zero Sell calls over the most recent three-month period.

The mean price target stands at $263.86, suggesting potential upside exceeding 77% from present levels.

Evercore, which holds a Buy rating on the stock, explained the situation in Wednesday’s research note: “We expect financing/leverage and the pace of equity issuance to remain the central investor debate near term, even as demand signals stay strong.”

This disconnect between professional analyst optimism and actual market performance represents the key narrative entering the following week.

As a footnote, Oracle co-founder Larry Ellison has also dropped several spots on global wealth rankings this week, falling behind Google’s co-founders, Jeff Bezos, and Michael Dell.

Key Highlights

• Starting July 1, AWS will implement a 20% price increase on reserved GPU compute resources, affecting Nvidia B200, B300, H100, and H200 processors.
• H200 pricing has now increased for three consecutive quarters — AWS GPU reservation costs have surged 20–50% since the start of the year.
• Wells Fargo reaffirmed its Buy recommendation on AMZN with a $312 price objective, viewing the increase as confirmation of cloud infrastructure pricing strength.
• Analyst consensus shows 57 Buy ratings on AMZN, with an average price objective of $312.78 — suggesting approximately 38.5% potential appreciation from current prices.
• Institutional shareholders control 72.2% of AMZN shares, with several major funds expanding their holdings during Q1 2026.

---

Amazon (AMZN) shares climbed 2.5% Thursday following Wells Fargo’s positive commentary on AWS’s latest 20% reserved GPU compute price adjustment, interpreting the move as evidence of robust pricing dynamics and sustained AI infrastructure appetite.

Amazon.com, Inc., AMZN

AMZN began Friday’s session at $232.69. The shares currently trade beneath their 50-day moving average of $255.53 while maintaining a position above the 200-day moving average of $234.13. The stock’s 52-week trading band extends from $196.00 to $278.56.

The pricing adjustments become effective July 1 and apply to multiple Nvidia processor architectures — including the B200, B300, H100, and H200 models.

Regarding the H200 particularly, this marks the third straight quarter of upward pricing pressure. AWS implemented a 15% H200 price increase in Q1, followed by 10% in Q2, and now an additional 20% entering Q3. Cumulatively this year, AWS GPU reservation pricing has escalated between 20% and 50% across different chip configurations.

Wells Fargo analyst Ken Gawrelski maintained his Buy recommendation while establishing a $312 price objective. His interpretation: the sustained pricing increases demonstrate that AI compute demand continues exceeding available supply, enabling hyperscale providers like AWS to transfer elevated infrastructure expenses to end customers.

Understanding AWS Reservation Pricing Dynamics

AWS reservation blocks enable clients to secure GPU capacity for periods extending up to six months. The willingness of customers to accept escalating prices for guaranteed access reveals the persistent tightness in available supply.

Wells Fargo recognized that these price adjustments may not translate immediately into revenue gains, given that certain clients operate under existing contractual arrangements. Nevertheless, the firm views this development as reinforcing AWS’s extended growth trajectory.

AMZN maintains a Strong Buy consensus rating throughout Wall Street. Among analysts providing coverage within the last three months, 44 assign Buy ratings while one assigns a Hold rating. The consensus price objective stands at $319.24, implying roughly 38.5% upside potential.

Recent price objective adjustments include: JPMorgan elevating its target to $330, Truist increasing to $320, Wolfe Research establishing a $320 target, and Deutsche Bank moving to $315.

Institutional Holdings and Additional Growth Drivers

Institutional ownership represents 72.2% of outstanding shares. Clark Asset Management acquired 4,879 additional shares during Q1, expanding its complete AMZN holdings to 38,238 shares valued at approximately $7.96 million. Arrowstreet Capital expanded its position by 21% in Q4, currently maintaining over 24.6 million shares worth roughly $5.7 billion.

Beyond GPU pricing developments, Amazon has several additional strategic initiatives underway. The company revealed a $13 billion commitment to India extending through 2030 for AI and cloud infrastructure expansion. Prime Day performance also appears promising, with industry observers anticipating record-breaking sales figures.

Regarding potential headwinds, EU regulatory authorities have suggested AWS could encounter more stringent competitive oversight — representing a possible concern for investors. Certain analysts have additionally expressed reservations regarding the company’s substantial capital investment requirements.

Amazon’s latest quarterly performance delivered $2.78 EPS, exceeding the $1.63 consensus estimate by $1.15. Revenue reached $181.52 billion, representing 16.6% year-over-year expansion.

CEO Andrew Jassy divested 20,000 shares on May 21 at $263.42 through a previously established 10b5-1 trading arrangement.