




<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Crypto Hacks &amp; Exploits &#8211; BBVN Markets</title>
	<atom:link href="https://www.newsbbvn.com/tag/hacks/feed" rel="self" type="application/rss+xml" />
	<link>https://www.newsbbvn.com</link>
	<description>Live Crypto Prices &#38; Market Rankings in Vietnam</description>
	<lastBuildDate>Sat, 03 Oct 2026 20:03:01 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=7.1.4</generator>

<image>
	<url>https://www.newsbbvn.com/wp-content/uploads/2024/06/cropped-2024063005241379-32x32.png</url>
	<title>Crypto Hacks &amp; Exploits &#8211; BBVN Markets</title>
	<link>https://www.newsbbvn.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>How to Spot a Crypto Scam: Six Shapes, and the Step That Takes the Money</title>
		<link>https://www.newsbbvn.com/analysis/555.html</link>
					<comments>https://www.newsbbvn.com/analysis/555.html#respond</comments>
		
		<dc:creator><![CDATA[bbnn-z]]></dc:creator>
		<pubDate>Sat, 03 Oct 2026 20:00:50 +0000</pubDate>
				<category><![CDATA[Analysis]]></category>
		<category><![CDATA[Cybersecurity]]></category>
		<category><![CDATA[Exchange risk]]></category>
		<category><![CDATA[hacks]]></category>
		<category><![CDATA[regulation]]></category>
		<category><![CDATA[security]]></category>
		<guid isPermaLink="false">https://www.newsbbvn.com/markets/555.html</guid>

					<description><![CDATA[Every scheme that removes money in this market needs three things: a way to reach somebody, a period in which credibility is manufactured, and a final step that cannot be reversed. Six shapes account for most losses — a platform that does not exist, a relationship built slowly, a project that removes the floor, a signature that grants permission, a message from support, and a price that was arranged.]]></description>
										<content:encoded><![CDATA[<p>Fraud in this market is usually described by its names, which is the least useful way to understand it. Names come from headlines, they change, and they tell a reader nothing about what to look for. The shapes are more stable: every one of the schemes that removes money from a person requires three things &mdash; a way to reach them, a period during which credibility is built, and a final step that cannot be reversed. The variation across cases is almost entirely in how the first and third steps are performed, and the second step is where the money actually comes from.</p>
<p>Read that way, the subject becomes a catalogue rather than a series of warnings. Six shapes account for the great majority of losses, and each one can be described by how it arrives, what the decisive step is, and which ordinary assumption it exploits. The assumptions are the interesting part, because they are all reasonable, and each of them is true somewhere other than where the victim applied it.</p>
<figure class="wp-block-image size-large"><img decoding="async" loading="lazy" src="https://www.newsbbvn.com/wp-content/uploads/2026/10/scam-six-shapes.png" alt="Table diagram of six shapes of crypto fraud, how each reaches a victim, the decisive step, and what it exploits" width="1657" height="826" /><figcaption>Six shapes and the assumption each one exploits. In every case the assumption is reasonable, and in every case it is being applied in a context where it does not hold.</figcaption></figure>
<h2>The structure, before the shapes</h2>
<p>Contact is the first step, and it is usually indirect: an advertisement placed against a search term, a message in a group chat, a direct message from an attractive stranger, a sponsored link that sits above the real site. The channel matters less than its property, which is that the victim arrives at it rather than choosing it.</p>
<p>Credibility is the second step, and it is the part that takes time. A screen with a balance, a chart that goes up, a small withdrawal that clears, a support person who answers questions promptly: each of these is cheap to fabricate and each of them substitutes for the verification a person would perform in the physical world. The step is not designed to convince a sceptic. It is designed to make a final decision feel routine.</p>
<p>The third step is the irreversible one, and it takes exactly three forms. Paying something to receive something larger. Granting permission to move something held elsewhere. And disclosing a secret that constitutes ownership. Every shape below is a different costume on one of those three movements.</p>
<h2>Shape one: the platform that does not exist</h2>
<p>The first shape is the simplest and the largest by total loss. A convincing interface presents balances, prices, deposit addresses and a support channel, and the balance shown rises as the customer watches. Nothing behind the interface is real: the deposits have moved to an address controlled by the operators, and the balance is a number in a database.</p>
<p>The decisive step is a deposit, usually the second or third one, after a small withdrawal has been allowed to succeed. What the shape exploits is the assumption that a balance displayed by an application corresponds to value held somewhere &mdash; an assumption that holds for a bank and for a regulated broker, and does not hold for an address that somebody else controls. Recognizing that a screen can show anything is the entire defence, and it is harder than it sounds because every other financial interface a person uses behaves the way the fake one appears to.</p>
<h2>Shape two: the relationship built slowly</h2>
<p>The second shape is the one that produces the largest individual losses, and it is a social operation with a technical last mile. Contact comes from an ordinary conversation &mdash; a wrong number, a gaming partner, a professional networking message &mdash; and the relationship develops over weeks with no mention of money. When the subject does arrive it is framed as an opportunity the person has personally benefited from and is sharing generously.</p>
<p>The technical apparatus is the same as the first shape: a platform, a rising balance, a small withdrawal that clears. What differs is why the victim trusts it, which is not the platform at all. The scheme exploits the fact that a person who has spent a month being treated well will extend trust to the thing the other person recommends, and it is why the defence cannot be technological. Verbal warnings about platforms do not reach a mechanism that operates through a relationship.</p>
<p>Two features of this shape are worth knowing for anyone trying to help somebody who is in it. The first is that the relationship is real to the victim, so arguing about the platform is arguing about a friend. The second is that the sums escalate: the early deposits are small, the intermediate ones are affordable, and the largest one arrives when a withdrawal is blocked and a fee is demanded to release it.</p>
<h2>Shape three: the project that removes the floor</h2>
<p>The third shape does not require a victim to trust a stranger at all. A token is created, a pool of liquidity is provided so that the token can be bought and sold, and the price is supported by promotion. At a chosen moment the creators withdraw the liquidity they supplied, and the market for the token ceases to exist: buyers can still hold units, and there is nothing left to sell them into.</p>
<p>The decisive step is a withdrawal from a pool, and the mechanism is entirely transparent to anyone who reads the pool&#8217;s state. What the shape exploits is a misunderstanding about what a price is in a system with automated market making. A quoted price exists because somebody put assets into a pool; it is not a property of the token, and if the same party can remove what it deposited, then the price was a loan rather than a valuation.</p>
<p>The checkable signals are the same in nearly every case: a creator identity that appeared recently, liquidity that is not locked for a stated period, a supply concentrated in a few addresses, and promotion that arrives from accounts created within the same fortnight as the token. None of those proves intent, and all of them describe a structure in which a single party can end the market at will.</p>
<h2>Shape four: the signature that grants permission</h2>
<p>The fourth shape does not take anything at the moment it succeeds. It obtains a permission, and the theft happens later, when the attacker chooses to use it. A page requests a signature for a claim, an allow-list, a login or a verification, the amount displayed is zero, and the signature that results authorises a contract to move tokens the user already holds.</p>
<p>What the shape exploits is a difference the interface does not make obvious: sending and allowing are two different operations that arrive as the same gesture. <a href="https://www.newsbbvn.com/products/528.html">The mechanics of approvals and the pointers contracts can hold</a> are worth understanding precisely because the request looks like nothing, and the thing at risk is never the reward being advertised.</p>
<p>This shape deserves the most attention of the six, for two reasons. It is used against experienced participants as well as beginners, because the defence is not knowledge but the habit of reading each request. And the damage is not limited to what the page appears to offer, since a single unlimited approval can expose an entire balance of a token rather than a quantity anybody agreed to.</p>
<h2>Shape five: the message from support</h2>
<p>The fifth shape impersonates somebody with authority. A person receives a message that looks like it comes from a venue, a wallet provider or a project they use, and the message states that there is a problem to resolve: a security check, a withdrawal to confirm, a bonus to claim. The continuation is a link and either a request to connect a wallet or a request to enter a recovery phrase into a page.</p>
<p>The decisive step is a phrase typed into a website or shared with a person who claims to be helping. What the shape exploits is the most consequential asymmetry in the industry: the phrase is not a password, it is the asset, and there is no version of the arrangement in which a legitimate operator needs it. Channels are also impersonated at the platform level rather than the message level, which means a link sent through a genuine group chat can still lead to a fabricated destination.</p>
<p>The rule that covers this shape and most of the others is a single sentence. Any interaction initiated by somebody else should be treated as hostile until it has been verified through a channel the user opened, which means typing the address rather than following the link.</p>
<h2>Shape six: the price that was arranged</h2>
<p>The sixth shape is a market operation rather than a theft. A small token, thinly traded and loudly promoted, rises sharply as coordinated buying meets the absence of sellers, and the rise is reported as evidence that something is happening. Participants who buy into it find that the only liquidity available is the position being sold to them, and when the promotion stops the price returns to where it started.</p>
<p>The decisive step is a purchase into a rising market, which is why this shape is the one most likely to catch people who consider themselves careful. What it exploits is the assumption that a rising price reflects demand rather than supply management. In a market with thin depth, both look identical on a chart, and the difference is only visible in the order book and in the concentration of the holdings.</p>
<p>The variants are worth knowing. Volume can be manufactured by trading between addresses controlled by one party, which produces a convincing histogram and no economic activity. Supply can be released slowly into the rise rather than all at once. And the promotion itself can be outsourced to accounts that are paid to be enthusiastic, which means the people recommending it may also be victims of the arrangement.</p>
<h2>What never recovers money, and what sometimes does</h2>
<p>A transaction on a public ledger is irreversible by design, which removes the first remedy a person looks for. What remains is a short list, and all of it depends on actors other than the victim. A token issuer can freeze its own liability on a specific address, which is the mechanism that has recovered funds in some cases and which does not reach assets that have been converted into something else. A regulated venue can refuse a deposit, which forces the attacker to find venues with weaker controls and narrows the routes over time.</p>
<p>Investigators can trace, and tracing is easier than people assume: the record is permanent, funded addresses cluster together, and the exit step is visible. What tracing produces is evidence rather than restitution. And a report filed quickly is worth more than the same report filed later, because the first hours are when funds are still moving between intermediaries that can be asked to stop.</p>
<p>The practical ordering for someone who has just lost money is therefore short and urgent: revoke outstanding approvals, move whatever remains to a fresh address, preserve the transaction records, report to the relevant national authority and to any venues involved, and do not pay anybody who offers to recover the funds &mdash; a second scheme in this market is tailored precisely to people who are in the state that the first one created.</p>
<h2>Three sentences that cover almost everything</h2>
<figure class="wp-block-image size-large"><img decoding="async" loading="lazy" src="https://www.newsbbvn.com/wp-content/uploads/2026/10/scam-three-sentences.png" alt="Diagram of three warning patterns: a promise of a return, a reason to hurry, and a request to pay, permit or share a phrase" width="1587" height="676" /><figcaption>Three patterns that appear in almost every case, with the legitimate cousins each one has. None of the three is conclusive on its own, and together they are close to sufficient.</figcaption></figure>
<p>The first is a promise of a return. Markets price risk, and a marketed financial product that guarantees an outcome is either paying from a budget that will end or describing something that is not a return at all. Legitimate versions of this exist &mdash; an incentive programme is a real subsidy &mdash; and they are honest about being temporary.</p>
<p>The second is a reason to hurry. Urgency is the mechanism by which verification is prevented, and every legitimate process in finance tolerates the time it takes a customer to check. An opportunity that expires in ten minutes is an opportunity whose expiry is the product.</p>
<p>The third is a request to pay, to permit, or to disclose. A fee to release funds, an approval to claim a reward, a phrase to verify ownership: all three transfer value or control away from the person being asked. A legitimate service may charge a network fee and may ask for a signature, and it never asks for the ability to move assets it did not just receive.</p>
<h2>Where legitimate products look similar</h2>
<p>Two honest situations resemble the shapes above, and knowing them keeps the list from becoming a reason to distrust everything. The first is the genuine promotion: a new protocol paying above-market rates to acquire deposits, with a published schedule and a token that may or may not hold its value. The wording is similar to a scheme&#8217;s and the structure is verifiable, which is the difference.</p>
<p>The second is the legitimate request for permission. Every interaction with a decentralised application requires a signature, and a person who refuses all of them can use nothing. The distinction is not whether permission is requested but whether the request is understood, which is why the useful habit is not suspicion as a personality trait but a fixed routine: read the screen, verify the destination, and refuse to sign what cannot be explained.</p>
<h2>Why the interface is the weakest link</h2>
<p>Almost every shape above relies on the gap between what an interface shows and what an instruction does. A balance shown by an application is a number, a price shown by a pool is a quotation, an amount shown on a confirmation screen of zero is a description of the present rather than of the authority being granted. None of those displays is lying in the sense that a forger lies; each of them is accurate about one thing and silent about another.</p>
<p>That is why the hardware device with a screen remains the most effective single control, and why it is not sufficient. It removes the computer from the act of signing, which defeats the malware that redirects addresses, and it does not translate a contract call into a sentence about its consequences. The last mile of security in this market is a person reading a screen that was designed to be skimmed, and the industry has not solved that, which is the reason the fourth shape keeps working.</p>
<h2>Who is targeted, and what actually helps</h2>
<p>The targets are not selected by ignorance. They are selected by two properties that are easy to identify from outside: access to money, and anxiety about having missed something. Both are ordinary, and both are what the second step of every scheme is designed to work on. The professional participant who has spent a decade in the market and the person who opened their first account last month are both reachable, and the shapes are simply adjusted.</p>
<p>What helps is procedural rather than educational. A rule that large transfers leave after a delay. A rule that addresses are verified from a source the user opened. A rule that a phrase is never typed into anything connected to a network. And a rule that no decision is made within an hour of being asked, which is the only defence that works against a relationship that has been built over a month.</p>
<h2>The economics of the operators</h2>
<p>These schemes are a business, and understanding the business explains why they concentrate in this asset class. Three properties make the environment unusually favourable to an operator. Transfers are irreversible, so a successful step cannot be unwound by the victim&#8217;s bank. Settlement is global and permissionless, so a recipient in one country can be paid by an address in another without either party having an account anywhere. And the tools required to run a convincing front end are cheap, because the appearance of a trading platform is a matter of design rather than of infrastructure.</p>
<p>The organisational side has professionalised as well. The pattern reported most often by investigators is a compound of operations where some people run the initial contact, others staff the support conversations, and others handle the movement of funds through a chain of exchanges, brokers and over-the-counter desks. That division of labour is why the person a victim spoke to for a month often has no access to the money and no ability to return it.</p>
<p>The targets are selected by two signals that are visible from outside: available funds, and some anxiety about having missed an opportunity. Neither is a failure of intelligence, and the second is especially effective in an asset class whose public conversation is largely about things that have already gone up.</p>
<h2>What the industry changed, and what it still cannot fix</h2>
<p>The response to these schemes has been institutional rather than individual, and three of the changes are visible in any transaction. Deposit screening at regulated venues has improved to the point that moving stolen funds through a large exchange is materially harder than it was a few years ago, which pushes laundering toward brokers and over-the-counter desks. Wallet software now surfaces approvals, offers to revoke them, and warns about addresses that match those already in a user&#8217;s history.</p>
<p>A third change is specific to the structure of these assets: an issuer can freeze its own token on a given address, which is the only mechanism in the system capable of moving value back after a transfer. It reaches the assets that are still the ones that were taken, and it does nothing once they have been converted, which is the same asymmetry that governs recovery in every other case.</p>
<p>What cannot be fixed is the part that happens before any of those controls apply. A person who types a phrase into a website has transferred ownership, and a person who sends funds to a platform that does not exist has sent them to an address that will not return them, and no improvement in monitoring changes either outcome after the fact. That is why the useful interventions remain procedural and unglamorous: a delay before large transfers, verification of destinations through channels the user opened themselves, and a personal rule about never signing a request that cannot be explained in a sentence.</p>
<h2>Failure is not fraud, and the difference matters</h2>
<p>Two situations resemble the shapes above without being schemes, and confusing them produces bad judgement in both directions. The first is the project that fails honestly: a team raised money, built something, and the thing did not work, so the token fell and the product closed. The second is the ordinary loss: an asset was bought, the market fell, and the position is worth less than it was.</p>
<p>The distinguishing question is about intent and disclosure rather than about outcome. A failed project that published its code, its holdings and its changes of plan has done something different from one that moved funds to an address nobody can identify, even when the financial result for a holder is the same. And an asset that fell has done something different from one whose price was arranged by the party selling it.</p>
<p>The reason the distinction matters is practical. A person who cannot tell fraud from failure will treat every loss as a betrayal, which destroys the ability to evaluate anything. A person who treats every loss as market risk will not learn the signals that were available. The signals are in the structure rather than in the outcome: whether the rules were published, whether the funds were controlled by one party, and whether the people involved answered questions before the price moved rather than after.</p>
<h2>A catalogue, not a warning</h2>
<p>Six shapes, three irreversible steps, and one structural fact: the interface can show anything, and the ledger records only what was actually done. Every one of the schemes above ends with a payment, a permission or a disclosure, and every one of them begins with a period during which credibility was manufactured more cheaply than it could be verified.</p>
<p>The useful conclusion for a reader is not a list of names to avoid, since the names change every quarter. It is the shape of the trade: somebody is offering an outcome, on a timetable they set, in exchange for an action the reader cannot undo. Where those three conditions appear together, the offer is either a scam or a legitimate product the reader should understand before accepting &mdash; and in both cases, the correct next step is the same.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.newsbbvn.com/analysis/555.html/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>What Is a Blockchain Bridge? Four Designs, and Where the Trust Sits</title>
		<link>https://www.newsbbvn.com/blockchain/543.html</link>
					<comments>https://www.newsbbvn.com/blockchain/543.html#comments</comments>
		
		<dc:creator><![CDATA[bbnn-z]]></dc:creator>
		<pubDate>Sat, 03 Oct 2026 19:57:41 +0000</pubDate>
				<category><![CDATA[Blockchain]]></category>
		<category><![CDATA[Cross-Chain Bridges]]></category>
		<category><![CDATA[crypto]]></category>
		<category><![CDATA[Custody]]></category>
		<category><![CDATA[hacks]]></category>
		<category><![CDATA[security]]></category>
		<guid isPermaLink="false">https://www.newsbbvn.com/markets/543.html</guid>

					<description><![CDATA[Nothing moves between blockchains; a claim does, and a bridge is the mechanism that decides whether to believe the claim. Four designs differ in who is asked to vouch: a custodian holding locked assets, a set of signers, a contract verifying another chain's consensus, or nobody at all. The largest losses in this industry have been failures of that vouching, not of cryptography.]]></description>
										<content:encoded><![CDATA[<p>A bridge is not a piece of plumbing that joins two blockchains. Nothing moves between chains, because nothing can: each ledger records its own state and has no view of any other. What a bridge does is transport a claim. It observes an event on one chain, decides that the event happened, and then instructs the other chain to act as though it had. Everything interesting about bridges follows from the middle step, and the middle step is always a question about who is believed.</p>
<p>That is why this category produces the largest losses in the industry, and why the losses are found in a small number of shapes. The designs are variations on four ideas, each of which makes a different assumption about who has to be honest. Once the four are stated separately, most of the field&#8217;s complexity resolves into a single question asked four ways: what exactly is being trusted, and how many parties would have to collude to break it?</p>
<figure class="wp-block-image size-large"><img decoding="async" loading="lazy" src="https://www.newsbbvn.com/wp-content/uploads/2026/10/bridge-four-designs.png" alt="Table diagram comparing four ways to move value between ledgers by what they do, what they trust, and where each breaks" width="1657" height="769" /><figcaption>Four designs and the assumption each one makes. The first two insert a party between the user and the asset, and the last two pay for avoiding that in cost, delay or functionality.</figcaption></figure>
<h2>The problem: two ledgers that cannot see each other</h2>
<p>A blockchain is a machine that can validate its own history and nothing else. A node on one network does not read another network&#8217;s blocks, does not verify its signatures, and cannot be persuaded to accept a statement about another chain unless that statement is submitted and checked by rules the node already has. This isolation is a security property rather than an oversight: a chain whose validity depended on another chain&#8217;s state would inherit that chain&#8217;s failures as well.</p>
<p>So the transfer of value across chains is not a transfer at all. It is three separate operations: an asset is locked or burned on the source, a message describing the operation is delivered to the destination, and the destination acts on that message according to its own rules. The only hard part is the second step, because a message is just data and data can be forged, replayed, or misread. A bridge is, precisely, a mechanism for establishing that a particular message from another chain is real.</p>
<h2>Design one: lock the original and issue a representation</h2>
<p>The first design is the oldest and the easiest to explain. The user deposits the asset into a contract or a custodian on the source chain, which holds it, and a corresponding token is issued on the destination chain. Coming back reverses the process: the representative token is destroyed and the original is released.</p>
<p>The trust assumption is the entire business. Whoever holds the locked asset can release it at will, which means the security of every outstanding representative token is the security of that holding arrangement. When the arrangement is a single custodian, the bridge is a bank with a website. When it is a committee of validators or a multi-signature set, the bridge is as strong as the quorum rules and the key management of that set, which is where a series of large failures have come from.</p>
<p>The design&#8217;s advantage is that it works between chains with nothing in common. Its disadvantage is that the total value at risk grows with use, and the cost of attacking the bridge does not: a structure holding five billion dollars in locked assets is protected by the same dozen keys that protected it when it held fifty million.</p>
<h2>Design two: pools on both sides</h2>
<p>The second design avoids a single custodian by keeping a pool of liquidity on each side. A user who wants to move value pays into the pool on the source chain and takes an equivalent amount out of the pool on the destination, and the pools are rebalanced by traders who are paid to do so.</p>
<p>What is trusted here is less obvious and just as consequential. The pools have finite depth, so the price of a transfer depends on their state, and the price is usually computed from a feed rather than negotiated. That combination has produced a specific failure mode: if the feed can be moved within a single transaction, or if the depth is thinner than the size of the transfer, a user can drain one side against the other at a favourable rate, and the loss is socialised across the liquidity providers who funded the pools.</p>
<p>The design is capital-efficient for small transfers and structurally exposed to large ones, and it is also the design most dependent on the quality of the price it reads. The honest description is that it replaces custody risk with market-structure risk, which is a different risk rather than a smaller one.</p>
<h2>Design three: verify the other chain&#8217;s consensus</h2>
<p>The third design is the only one that tries to remove the middleman entirely. The destination chain runs verification logic for the source chain&#8217;s consensus, so that a state proof from the source can be checked against rules the destination already enforces. If the proof verifies, the message is real by construction, and no committee has to be trusted.</p>
<p>The assumption it removes is the largest one available: there is no custodian, no validator set with keys to steal, and no price feed to manipulate. What it substitutes is cost and complexity. Verifying another chain&#8217;s consensus means implementing its light protocol, tracking its validator set or its accumulated work, handling its finality rules, and updating all of that in code that must be correct forever.</p>
<p>Two consequences follow. Transfers are slower, because a proof cannot be verified until the source chain has finalised the event it describes. And the engineering surface is much larger, which means the failure mode shifts from a stolen key to a bug: a verification routine that accepts something it should not is as good as a signature that can be forged.</p>
<h2>Design four: swap or nothing happens</h2>
<p>The fourth design removes the message step altogether. Two parties on two chains agree to trade, and the exchange is arranged so that either both sides complete or neither does, with a time limit that lets each party recover its own asset if the other does not deliver.</p>
<p>Nothing is trusted beyond the two parties and the hashing rules, which makes this the most conservative mechanism available and also the least useful as a general service. It requires a counterparty who wants the opposite trade in matched size, at the same moment, and it produces no bridge in the usual sense: there is no liquidity sitting idle, no wrapped asset that can be used elsewhere, and no way to move value to a chain where nobody wants to trade back.</p>
<p>The design&#8217;s honest niche is large, occasional, bilateral movements where the parties can wait, and it is the reason the phrase &ldquo;trustless bridge&rdquo; should be read as a description of a mechanism with severe requirements rather than as a better version of the other three.</p>
<h2>Where the trust actually sits</h2>
<figure class="wp-block-image size-large"><img decoding="async" loading="lazy" src="https://www.newsbbvn.com/wp-content/uploads/2026/10/bridge-trust-step.png" alt="Diagram of one cross-chain transfer: the asset is locked, a message is emitted, the message is verified, and value is released on the destination" width="1611" height="699" /><figcaption>One transfer, four steps. Steps one, two and four are mechanical; step three is where every design makes its choice.</figcaption></figure>
<p>Laying the transfer out in steps makes the comparison mechanical. Locking is a transaction that either succeeds or does not. Emitting a message is a log entry with no discretion in it. Releasing value on the destination is another transaction. The only step with a judgement in it is verification, and every design above is a different answer to how the judgement is made: by a party holding the asset, by a set of parties signing, by a contract checking a proof, or by nobody because the two sides are the same transaction.</p>
<p>That is also why the marketing language around bridges is so unreliable. A service can describe itself as decentralised while running the first design with a committee of a dozen signers, and a service can describe itself as simple while implementing the third. The description that matters is not about decentralisation in general but about the specific party or parties whose honesty the verification step requires.</p>
<h2>The five attack surfaces</h2>
<p>Whatever the design, incidents concentrate in five places, and each is checkable in advance by somebody willing to read documentation.</p>
<p>The first is the size of the validating set: a bridge secured by one key is one compromised laptop away from total loss. The second is the signature threshold, which is the number of those validators that must collude, and which is often described as a fraction of a set that may itself be small. The third is the verification logic, where the failure is not a stolen key but a check that accepts an invalid input, including the classic case of a message being replayed twice. The fourth is the liquidity that stands behind the transfer, where thin depth combined with a readable price produces a profitable attack. And the fifth is administrative authority: contracts that can be upgraded or paused concentrate all four previous surfaces into whoever holds the upgrade key, which is the most common way a bridge that was technically fine became a bridge that was not.</p>
<h2>Why bridges carry the largest losses</h2>
<p>Four properties of the category explain the concentration of damage. The first is that a bridge holds assets belonging to many users at once, so a single compromise is not limited to the amounts involved in one transaction. The second is that the code is among the hardest to write and to audit in the field, because it has to reason about two different chains&#8217; rules at once and about the state of both while it does so.</p>
<p>The third is that the economic asymmetry favours the attacker: a defensive team has to be right about every path, while the attacker has to find one. The fourth is that bridges are a chokepoint, which means the payoff of an attack is proportional to how much traffic the industry routes through them rather than to how carefully any particular one was built. A bridge that becomes popular becomes a target in proportion, and popularity is not a security control.</p>
<h2>What has gone wrong, by category</h2>
<p>The recorded failures of the last several years fall into three groups, and the grouping is more instructive than any individual case. The largest group involved compromised signing keys or validator sets: attacks on the parties whose signatures authorised releases, producing losses in the hundreds of millions of dollars in several instances, including one case where the compromised set signed off on transfers worth more than six hundred million.</p>
<p>The second group involved flaws in the verification logic itself, in which a message was accepted that should not have been, or accepted more than once. The third group used the liquidity design against itself, exploiting a price that could be moved within a transaction or a pool that was thinner than the transfer being attempted.</p>
<p>A pattern runs across all three. In every case the mechanism did what its code said, and the question afterwards was why the code said that. The failures were not cryptographic: no signature scheme was broken and no hash function was reversed. They were all failures of design assumptions about who would behave.</p>
<h2>The trade-off nobody can remove</h2>
<p>Safety, cost and latency form the same triangle here as in every settlement system, and each design occupies a different corner. Verification by a committee of signers is fast and cheap and requires trusting the committee. Verification by proof is slow and expensive and requires trusting only consensus rules. Pools are cheap for small transfers and fragile for large ones. Atomic swaps are safe and slow and only work when both sides want the trade.</p>
<p>No design escapes the triangle, and the reason is structural: the property being bought is the absence of a trusted party, and that property has to be paid for somewhere &mdash; in computation, in time, or in the functionality that has to be given up. A bridge that advertises all three simultaneously is either describing a different mechanism than the one it runs, or it has moved the cost somewhere the user does not see.</p>
<h2>The canonical bridge and the third-party bridge</h2>
<p>One distinction deserves its own section because it changes what a user is trusting. A canonical bridge is the one operated by the network that needs it &mdash; the standard path between a base layer and a layer built on top of it. Its trust assumption usually reduces to the governance of that destination chain, which a user is already relying on by holding assets there at all.</p>
<p>A third-party bridge is a separate business: it connects chains that do not otherwise know each other, and it adds its own trust assumptions on top of both. Users are frequently unaware of which one they are using, because the interfaces look identical and the fees are comparable. The difference appears at the moment something goes wrong, when the recourse available depends entirely on which of the two arrangements was involved.</p>
<h2>What to check before using one</h2>
<p>Three questions cover the material risks and are answerable before a transfer. Who verifies, and how many are they? A bridge that publishes its validator set and its threshold is inviting scrutiny, and one that describes the set only in general terms is telling you something by the omission. What can the operators do unilaterally &mdash; upgrade the contracts, pause withdrawals, change the validator set? Each of those powers is a trust assumption that exists whether or not it is disclosed.</p>
<p>And where do the assets actually sit while in transit? For the first design this determines everything: if the locked assets are held by a contract with an upgrade key, then the security of the arrangement is the security of that key, and every other property of the bridge is decoration on top of it.</p>
<h2>The direction of travel</h2>
<p>Three developments are visible, and each is an attempt to reduce the amount of trust the third step requires. The first is standardisation of the message layer, so that verification logic is shared rather than reimplemented by every operator, on the theory that one heavily reviewed implementation is better than ten bespoke ones. The second is the pattern known as intents, in which a user states an outcome and a competing set of solvers delivers it, with the trust moving from a bridge to a market of parties who are paid to compete.</p>
<p>The third is redundancy as a design choice: routing value across several bridges at once so that a single failure is partial rather than total. That is an admission about the state of the art, and it is also the most honest one available. Until verification can be done cheaply and correctly on the destination chain, the practical answer is not to find a trustless bridge but to stop depending on any single one.</p>
<h2>What a wrapped asset actually is</h2>
<p>The representative token that a bridge issues is not a title deed. It is a liability of the bridge, recorded in a contract, redeemable for the original only by going back through the same mechanism. That distinction matters most in the scenario nobody wants to think about: if the locked assets are taken, the representative tokens are not backed by anything, and a holder who never touched the bridge discovers that the asset they were using was a claim on a mechanism rather than a claim on a coin.</p>
<p>Two consequences follow for anyone holding one. The first is that the credit quality of the wrapper is the credit quality of the bridge, so a token that trades at par on a normal day is trading at par because the mechanism is believed, not because the mechanism is riskless. The second is that multiple representatives of the same asset can exist at once, issued by different bridges with different designs, and they are not interchangeable: the price difference between two versions of the same coin is the market&#8217;s estimate of the difference in trust.</p>
<p>That price difference is the most useful signal a reader can watch. When two wrappers of one asset trade at different prices, the market is pricing a specific mechanism&#8217;s risk, and it does so before anything fails. A wrapper that trades persistently below its peers is telling you what somebody knows about the arrangement behind it.</p>
<h2>Why the industry keeps building them anyway</h2>
<p>The risks are well documented and the category keeps growing, and the reason is that the alternative is worse for the participants. Value is spread across dozens of networks, users want to hold one balance rather than a portfolio of chain-specific positions, and an application on one network cannot serve a user whose assets sit on another. A bridge is what makes an asset usable where it is not, which is a service rather than a convenience.</p>
<p>The incentives are also asymmetric in a way that explains the volume of construction. Whatever a bridge connects, the traffic that passes through it pays fees, and the team that operates the canonical route between a base layer and a network built on top of it holds a position that is difficult to displace. That combination of demand and rent explains why bridges are built faster than they are audited, and why the audits that matter are the ones conducted after a failure rather than before.</p>
<h2>Where bridge engineers disagree with each other</h2>
<p>The four designs are not ranked the same way by the people who build them, and the disagreement is instructive. The camp that favours proof verification argues that any arrangement requiring a set of parties to be honest is a temporary compromise whose failure is a matter of time, and that the cost and complexity of verification are the price of a property worth having. The camp that favours signed messages argues that proof verification has produced its own failures, that a verification routine which is subtly wrong is indistinguishable from a bridge with a forged signature, and that a well-audited committee with a published set of members is easier to reason about than a proof system nobody can review.</p>
<p>Both positions are defensible and they disagree about what a user is actually buying. The proof camp is buying the absence of a trusted party. The committee camp is buying inspectability, because a quorum of named entities can be evaluated, insured and, when necessary, held responsible in a way that a verification contract cannot. A reader can hold both ideas at once and ask a simpler question instead: which of the two risks does this particular bridge concentrate, and am I willing to carry it?</p>
<p>There is also a third position, held by a minority, that most bridges should not exist. Its argument is that the value of connecting two ledgers is smaller than the cost of the security machinery required to do it safely, and that the industry would be better served by users holding assets where they are rather than by constructing verification systems whose failures are measured in hundreds of millions of dollars. That view has not prevailed, and its persistence is a reasonable indication that the trade-off is genuinely contested.</p>
<h2>The middle step is the product</h2>
<p>A bridge is a mechanism for making one chain believe a fact about another, and everything else is the arrangement around that mechanism. The four designs differ in who is asked to vouch, and the largest losses in this industry have all been failures of that vouching rather than failures of cryptography.</p>
<p>Two sentences are worth keeping. The asset never moves between chains; a claim about it does, and the claim is only as good as the verification that admitted it. And the security of the arrangement is the security of the weakest party whose honesty the verification step requires, which is a fact that no amount of documentation can change and that every user can check in about five minutes if the operator is willing to say.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.newsbbvn.com/blockchain/543.html/feed</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>Where $388 Million Went: The Path Stolen Exchange Funds Actually Take</title>
		<link>https://www.newsbbvn.com/blockchain/513.html</link>
					<comments>https://www.newsbbvn.com/blockchain/513.html#respond</comments>
		
		<dc:creator><![CDATA[bbnn-z]]></dc:creator>
		<pubDate>Sat, 03 Oct 2026 18:29:30 +0000</pubDate>
				<category><![CDATA[Blockchain]]></category>
		<category><![CDATA[bitget]]></category>
		<category><![CDATA[Cross-Chain Bridges]]></category>
		<category><![CDATA[hacks]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[thorchain]]></category>
		<guid isPermaLink="false">https://www.newsbbvn.com/markets/513.html</guid>

					<description><![CDATA[A theft is one step; hiding it is five. Following roughly $388 million of stolen exchange funds through a split into twenty-three transactions, a cross-chain swap out of the stolen asset, a spread across four networks chosen for liquidity, cost, concealment and stablecoin depth, and an exit that is the only hop needing a willing human on the other side.]]></description>
										<content:encoded><![CDATA[<p>When a large theft is reported, two conversations start immediately and both are less useful than they appear. The first is about blame, and the second is about whether some protocol should have frozen the funds. Neither answers the question that a reader can actually learn from, which is how the money moved, what each hop cost the attacker, and which gates in the path were capable of closing and did not. The theft disclosed by an exchange in late September, involving roughly three hundred and eighty-eight million dollars, is unusually well documented on this last axis, because the analytics firm that traced it published the route.</p>
<p>What follows is that route as a sequence of five steps, with two things attached to each: what the step does for the person moving the money, and what it leaves behind for the person following it. The final sections deal with the gates, the attribution and the part of the story that never makes a headline, which is what happened to the customers.</p>
<figure class="wp-block-image size-large"><img decoding="async" loading="lazy" src="https://www.newsbbvn.com/wp-content/uploads/2026/10/stolen-funds-path.png" alt="Diagram of five steps in laundering stolen exchange funds: the transfer out, the split, the cross-chain swap, the spread across networks, and the exit into currency" width="1611" height="676" /><figcaption>The five steps. Only the first involves anything that an ordinary person would describe as breaking in; the rest is routine treasury work performed by somebody who does not want to be found.</figcaption></figure>
<h2>Step one: the transfer out, which is the only break-in</h2>
<p>The episode began with assets leaving wallets controlled by the exchange on 24 September, about three hundred and eighty-eight million dollars in total. That is the step the word &ldquo;hack&rdquo; describes, and it is also the step after which nothing is hidden: the movement of value on a public ledger creates a permanent record that anyone can read, and the first transaction of a theft is the beginning of the evidence, not the end of it.</p>
<p>The important consequence is a change in the attacker&rsquo;s problem. Before the transfer, the objective was access. Afterwards, the objective is disappearance, and disappearance in a system where every movement is recorded means changing what the assets look like rather than where they came from. Every remaining step in the sequence is an attempt to break the link between a specific quantity of value and the event that produced it.</p>
<h2>Step two: the split, and why twenty-three transactions</h2>
<p>The tracing published afterwards described twenty-three outgoing transactions within roughly three hours. A person new to this subject reads that as panic or as clumsiness; it is neither. Splitting a balance serves three purposes at once, and all of them are defensive.</p>
<p>The first is threshold management. Monitoring systems and compliance rules operate with size limits, and a quantity that moves in pieces may pass under several of them rather than over one. The second is channel testing: by sending value along different routes at the same time, the attacker discovers which routes still work before committing the whole amount to any single one. The third is concentration risk in reverse: if one route is blocked or seized, only the portion sent along it is lost, and the rest of the operation continues.</p>
<p>None of that requires specialised infrastructure. A large seller of any asset faces the same set of constraints and solves them the same way, which is why the split is the least distinctive part of the route and the part that most resembles ordinary activity.</p>
<h2>Step three: the swap that changes what the asset is</h2>
<p>The step that matters most technically is the third, in which one asset is fed into a permissionless cross-chain liquidity protocol and the value is withdrawn on another network in a different asset. The tracing described the remainder of the balance being routed this way, with value coming out in bitcoin.</p>
<p>Two things happen in that operation and only one of them is about geography. The obvious one is a move between networks, which lets the attacker leave the chain where the stolen asset was issued. The less obvious and more important one is a change of asset, because a holding&rsquo;s history is attached to the specific tokens that were taken. An issuer can freeze its own token on a specific address; it cannot freeze an unrelated asset that somebody else now holds, because as far as that asset&rsquo;s ledger is concerned, nothing improper happened on it.</p>
<p>Bitcoin is an efficient destination for that reason, and the reasons are economic rather than ideological. It has the deepest liquidity for large conversions, the widest over-the-counter market to absorb size without moving a public price, and no issuer with a switch over its supply. The operation is not money laundering in the classic sense of commingling funds to obscure a source; it is closer to changing a serial number by melting the metal and recasting it, and the tool that makes it easy was built to let ordinary users move value between networks cheaply.</p>
<h2>Step four: four networks, four different reasons</h2>
<figure class="wp-block-image size-large"><img decoding="async" loading="lazy" src="https://www.newsbbvn.com/wp-content/uploads/2026/10/stolen-funds-allocation.png" alt="Diagram showing the split of stolen exchange funds across a general-purpose chain, a payments ledger, a privacy-capable chain and a low-fee stablecoin network, with what each offered the sender" width="1587" height="723" /><figcaption>Where the value landed, and what each network offered. The distribution is deliberate: each destination is chosen for a property, not for storage.</figcaption></figure>
<p>The published split put roughly half on a general-purpose chain with the deepest liquidity, about forty percent on a payments-focused ledger whose native asset is cheap and fast to bridge, under eight percent on a chain whose transaction amounts can be hidden, and about two percent on the network with the densest market for dollar tokens. Read that distribution as a portfolio and each weight has a purpose.</p>
<p>The general-purpose chain is where the largest conversions can happen without disturbing a price. The payments ledger offers settlement speed and low cost, which matters when the objective is to keep moving. The privacy-capable chain offers concealment of amounts for the portion that needs it, although the transfers themselves remain visible. And the stablecoin network is useful because dollar tokens are the asset most easily exchanged for currency through venues and brokers that accept them without a banking relationship.</p>
<p>The pattern to note is that none of the four destinations is chosen to hold value. They are chosen for what each one can do to it, which is why the value keeps moving through the path rather than resting in it. Storage is the objective of an investor; a route is the objective here.</p>
<h2>Step five: the exit, which is the only step needing a counterparty</h2>
<p>The final step in any route is conversion into something spendable, and it is the only step that cannot be completed by software alone. A chain can move value between addresses; it cannot pay a salary, settle an invoice or buy a building. That requires a venue or a broker willing to take the asset and deliver currency, and a willing counterparty is exactly what a person trying to be invisible does not have.</p>
<p>That is why the last stage of every case looks the same and why it is where arrests and seizures concentrate. Everything upstream of it is a technical problem solved by code. The final hop is a human problem, and the humans on the other side of it are regulated, identifiable and increasingly automated in their screening. The published record of this case ends at the point where the funds were consolidated and beginning to be distributed, which is precisely the doorway.</p>
<h2>The four gates, and what each can actually do</h2>
<figure class="wp-block-image size-large"><img decoding="async" loading="lazy" src="https://www.newsbbvn.com/wp-content/uploads/2026/10/stolen-funds-gates.png" alt="Diagram comparing what a token issuer, a regulated venue, a permissionless exchange protocol and a chain&apos;s validators can each do about stolen funds" width="1654" height="699" /><figcaption>Four gates and their powers. The asymmetry between the two columns is the entire story of why recovery attempts stall.</figcaption></figure>
<p>A token issuer can freeze its own token on a given address, and that power is real: it works on a balance whether the holder agrees or not. Its limitation is scope. A freeze reaches only the liability that issuer created, which is why the change of asset in step three is the attacker&rsquo;s most valuable move &mdash; it steps out from under the only switch in the system that is designed to be pulled.</p>
<p>A regulated venue can refuse a deposit, can request information, and is obliged to report suspicious activity. That is the most consequential gate in practice, and it operates by attrition: it forces the person moving the funds to find a venue with weaker controls, which narrows the available routes with every refusal. A permissionless protocol has no such capability and does not want one; its inability to block a specific user is the same property that lets it serve a user whose government dislikes them. A chain&rsquo;s validators could censor or reorg, and have no obligation to, which makes that gate technically available and politically improbable.</p>
<p>The asymmetry produces the pattern of every large case: the swifter the response, the more value is caught at the first two gates, and the longer the delay, the more the funds have already passed into the layers that have no mechanism at all.</p>
<h2>Why the gate with no switch was built that way</h2>
<p>The refusal that drew attention in this case is worth understanding on its own terms. A permissionless cross-chain exchange declined to block addresses associated with the theft, explaining that blocking would require an authority the protocol does not have and was not designed to have. That statement is accurate and is also the honest description of a trade-off that every protocol in this category has made.</p>
<p>If such a protocol could block a specific address, it could block any address, and the set of reasons for blocking would be set by whoever controls the switch. The design choice to remove that capability is what allows the protocol to operate without permission, without identity checks and without jurisdiction. The cost of the choice appears in exactly this situation: an asset moving between networks through a mechanism that cannot distinguish a merchant from a thief.</p>
<p>Neither side of the argument is dissembling. The protocol&rsquo;s defenders are describing its architecture, and its critics are describing the consequence of that architecture. What is not available is a version of the same mechanism that keeps the permissionless property and gains a blocking power, because the second property is the first one applied to somebody.</p>
<h2>The trail that survives anyway</h2>
<p>Against the impression that a chain-hopping route makes funds untraceable, the evidence in this case runs the other way: the route was reconstructed from public data and published with the proportions and the intermediate steps. Three features of the record make that possible.</p>
<p>The first is that every transfer is permanent and timestamped, so a sequence can be ordered without asking anyone. The second is that the split at step two creates relationships: funds that move together, or rest in the same place at the same moment, or arrive at a pool within seconds of each other, cluster into groups that an automated analysis can assemble into a route. The third is that the exit is visible, because the venues that convert assets into currency keep records precisely so that the first two features can be used against their own customers when required.</p>
<p>A common misunderstanding belongs here. An unspent-output model &mdash; the design bitcoin uses &mdash; is not anonymous; it is pseudonymous, and the distinction is large. Amounts and destinations are public, and the only thing standing between a chain of transactions and a name is an identity check at some venue. Privacy features on other networks change what is visible in specific transactions, and they do not remove the fact that a hop between networks creates a link that has to be explained rather than erased.</p>
<h2>Attribution, and what it is worth</h2>
<p>The firm that traced the route attributed it to a state-linked group, and the total attributed to that actor over the course of the year passed a billion dollars. The exchange&rsquo;s chief executive publicly connected the incident to the same actor within hours, citing network-level evidence, which is a faster conclusion than most attribution work supports.</p>
<p>The technique behind such attributions is pattern recognition rather than proof: the reuse of infrastructure, the timing of activity, the choice of tooling, the habit of routing through a particular protocol, and in this case network identifiers consistent with a characteristic cluster. That is strong evidence in aggregate and is not the same as a signed confession. Its value is practical rather than forensic: it drives sanctions, it shapes how venues screen deposits, and it changes the political priority of an investigation.</p>
<p>The limit is worth stating because it is where expectations go wrong. Attribution does not recover assets, and it does not produce a defendant. It moves the problem from a technical puzzle to a diplomatic one, where the available instruments are sanctions and the willingness of third-country venues to cooperate, and it is the only path available once the funds have left the networks whose issuers have switches.</p>
<h2>What a hack costs after the hack</h2>
<p>The rest of the story belongs to the customers, and the sequence is instructive about what a venue actually sells. Withdrawals were restored asset by asset over about a week, beginning with bitcoin a few days after the incident, then ether, then the largest dollar token, with the remaining tokens, fiat and peer-to-peer services following into the next week.</p>
<p>In parallel, the venue reported that its protection fund had been restored above three hundred million dollars and published a reserve ratio of about one hundred and thirty-one percent across nineteen asset classes. Those two numbers are a solvency statement, and what holders actually needed was a liquidity statement. Being solvent while being unable to process withdrawals is the failure mode that has closed exchanges in the past, and the interval between the theft and the restoration of withdrawals is the metric that depositors feel, regardless of what the reserve ratio says.</p>
<p>The third-party losses in the same window are worth noting for scale. A separate exploit against an adapter used by a lending market drained a few hundred thousand dollars from two multisignature wallets, and several other incidents in the same fortnight involved compromised tooling rather than protocols. The category&rsquo;s loss record is not dominated by sophisticated attacks on cryptography; it is dominated by the operational security of the entities holding keys.</p>
<h2>The pattern across cases</h2>
<p>Compare this route with the one used by large thefts five years ago and the professionalisation is visible. The standard route then was a direct deposit to a venue with weak controls, followed by conversion, followed by an attempt to withdraw before anyone noticed. That route now fails almost immediately, because deposit screening improved and because venues learned to watch for the specific pattern.</p>
<p>The current route has three parts: a cross-chain swap into a different asset, a spread across networks chosen for specific properties, and an exit negotiated through brokers and over-the-counter desks rather than through retail deposit channels. Each part compensates for a defence that was added after the previous generation of cases, which is why the attribution rate stays roughly flat even as the loss amounts grow.</p>
<h2>What defenders can actually change</h2>
<p>Four levers are available and the first is the most powerful of them. Issuers can freeze their own liabilities, and in cases where the stolen asset is still the token that was stolen, that power recovers value while it is moving. Everything downstream of the swap falls outside its reach, which suggests where response time matters most: the first hours, before the second hop.</p>
<p>The second lever belongs to venues, and it is screening with a delay rather than screening alone. A deposit that is credited after a wait is a deposit that can still be reversed when the analysis catches up. The third belongs to the protocols, and taking it means giving up the property that makes them useful; that is a choice for their communities rather than a flaw to be patched. And the fourth is the least discussed and most important: reduce the number of places where a single key can move a large balance, through multi-party signing, threshold schemes and the separation of duties that ordinary treasury operations have used for a century.</p>
<p>The uncomfortable implication is that the layers doing the most to reduce this category of loss are the ones with the least interesting architecture. A multisignature policy is not a protocol upgrade, and an enforced delay between request and transfer is not a consensus mechanism, and both make the theft itself harder than any downstream measure can.</p>
<h2>Two things this case did not involve</h2>
<p>What is missing from the route is as informative as what is in it, and two absences are worth naming for anyone trying to place the right defences.</p>
<p>The first is a bug. Nothing in the published account describes a flaw in a contract that was exploited, a signature scheme that was broken, or a consensus rule that was violated. The assets left wallets controlled by an organisation because access to those wallets was obtained, which places the entire episode in the category of operational security rather than in the category of protocol security. That distinction determines who has to change behaviour after it: auditors reviewing code cannot find an access path, and a firm reviewing its key management can.</p>
<p>The second is a chain-level intervention. No reorganisation was attempted, no validator set was asked to censor, and no coordinated rollback was proposed. The networks behaved exactly as designed throughout, which means the recovery options available in this case were the ones available in every case: what an issuer can freeze, what a venue can refuse, and what an investigator can reconstruct. A theft that required a chain to do something unusual would be a different story with different politics.</p>
<p>Those two absences explain the shape of the response. When the failure is access rather than code, the remedies are procedural: multi-party signing, delays between request and transfer, segregation of duties, and the unglamorous review work that no product announcement describes. Every one of those measures is older than the industry and none of them requires a protocol change, which is why the losses in this category keep happening to organisations that have not adopted them.</p>
<h2>Three questions for the next report of this kind</h2>
<p>The value of following a route is that it converts a large number into three answerable questions. Which networks did the value pass through, and were any of them issuers with a switch over their own token? What asset did it become, and how many hops were required before it was no longer the thing that was stolen? And how long was the interval, which is the variable that decides whether any of the answers still matter by the time they are found.</p>
<p>A theft of this size is a failure of custody before it is anything else, and everything in the sequence after the first step is the consequence of that failure becoming public. The route described here is not a sophisticated exploit of cryptography; it is a set of ordinary operations performed in a deliberate order by somebody who understood which parts of the system have switches and which do not. That understanding is available to anyone who reads the same public data, which is the reason the trace exists at all and the reason the next case will follow a similar shape with different names.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.newsbbvn.com/blockchain/513.html/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>The Bitget Hack and the $387 Million Question: Should a Public Chain Freeze Stolen Funds?</title>
		<link>https://www.newsbbvn.com/analysis/485.html</link>
					<comments>https://www.newsbbvn.com/analysis/485.html#comments</comments>
		
		<dc:creator><![CDATA[bbnn-z]]></dc:creator>
		<pubDate>Fri, 02 Oct 2026 16:53:37 +0000</pubDate>
				<category><![CDATA[Analysis]]></category>
		<category><![CDATA[DeFi]]></category>
		<category><![CDATA[Exchange risk]]></category>
		<category><![CDATA[hacks]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[thorchain]]></category>
		<guid isPermaLink="false">https://www.newsbbvn.com/?p=485</guid>

					<description><![CDATA[Bitget lost about $387.5M on September 24, 2026. NEAR Intents blocked $50M and froze $503K; THORChain refused to act. The fight is not about hacking — it is about who enforces the rules on a permissionless chain.]]></description>
										<content:encoded><![CDATA[
<figure class="wp-block-image size-large"><img fetchpriority="high" decoding="async" width="1920" height="1280" src="https://www.newsbbvn.com/wp-content/uploads/2026/10/locks.jpg" alt="A chain-link fence covered with padlocks" class="wp-image-479" /><figcaption class="wp-element-caption">Approval to move, or approval to stop? Photo: MarkBuckawicki, CC0, via Wikimedia Commons.</figcaption></figure>



<p class="wp-block-paragraph">On September 24, 2026, attackers drained roughly $387.5 million from the crypto exchange Bitget. It was one of the larger exchange losses of the year &mdash; but the amount is not what turned it into the week&rsquo;s loudest argument. What turned it into an argument was the money that came back, and the question of who decides, when stolen assets move across a permissionless network, whether anyone can stop them at all.</p>



<p class="wp-block-paragraph">Two projects answered that question in opposite ways. <strong>THORChain</strong>, the decentralized cross-chain swap network that the attacker&rsquo;s funds are being routed through, refused to intervene. <strong>NEAR Intents</strong>, a competing cross-chain system, quietly blocked more than $50 million in attempted transfers and froze about $503,000 of the proceeds. Both published a rationale. The rationales do not fit together.</p>



<p class="wp-block-paragraph">The result is the cleanest test yet of a question the industry has deferred for years: on a public blockchain, is refusing to censor a stolen asset a principle, or an excuse?</p>



<h2 class="wp-block-heading">Key takeaways</h2>



<ul class="wp-block-list"><li>Bitget lost roughly $387.5 million on September 24, 2026 &mdash; not through stolen keys, but through forged withdrawal instructions written into its wallet system.</li><li>About $840,000, or 0.2% of the loss, was frozen: $318,000&ndash;$340,000 by Tether and Circle, and about $503,000 by NEAR Intents.</li><li>Stolen stablecoins were swapped into native tokens within 41 minutes and are being consolidated into Bitcoin, largely via THORChain.</li><li>THORChain refused to block attacker-linked addresses on the grounds that it is permissionless by design; NEAR Intents screened and blocked automatically.</li><li>The real dispute is not whether stolen funds should be spendable &mdash; everyone agrees they should not &mdash; but who should have the power to make that true, and under what rules.</li></ul>



<h2 class="wp-block-heading">What happened at Bitget</h2>



<p class="wp-block-paragraph">The attack was not a stolen key. Attackers wrote <strong>forged withdrawal instructions</strong> into Bitget&rsquo;s wallet system, reportedly through a zero-day in a third-party security product. Bitget says its private keys and cold wallets were never compromised. That distinction matters, because it tells you where the weakness sat: not in the cryptographic backing of the money, but in the software that decides which transactions to sign.</p>



<p class="wp-block-paragraph">What happened next was fast and mechanical. Within <strong>41 minutes</strong>, the stolen stablecoins were swapped into native tokens across multiple chains, and the funds began consolidating into Bitcoin &mdash; largely through THORChain, a network built specifically to move value between chains without a central operator. The speed is the point. By the time any centralized issuer could act, most of the money had already left the tokens that can be frozen.</p>



<p class="wp-block-paragraph">This is the modern template for a large exchange theft: take what can be moved fastest, convert it immediately into assets no one controls, and bridge it into the deepest, most liquid asset on the other side. Bitcoin is the exit because it has no issuer, no freeze function, and no compliance desk &mdash; and THORChain is the door because it has no gatekeeper either.</p>



<h2 class="wp-block-heading">The $840,000 that came back</h2>



<p class="wp-block-paragraph">Of a $387.5 million loss, roughly <strong>$840,000 &mdash; about 0.2% &mdash; was frozen</strong>. Tether and Circle froze between $318,000 and $340,000 of stablecoins, using the centralized control each issuer keeps over its token. NEAR Intents added about $503,000. Everything else kept moving.</p>



<p class="wp-block-paragraph">The ratio is the story. On a network where assets move without permission, the only recoverable money is the money that touches a system someone can switch off. Stablecoins have issuers; native tokens do not. Bitcoin has no switch at all. That is why the recovery rate on a cross-chain hack is not a measure of effort &mdash; it is a measure of how much of the stolen value happened to still be sitting in a form that a company controls.</p>



<figure class="wp-block-image size-large"><img decoding="async" width="1890" height="810" src="https://www.newsbbvn.com/wp-content/uploads/2026/10/chartC_bitget.png" alt="Timeline of the Bitget hack: about 387.5 million dollars stolen on September 24 2026, stablecoins swapped within 41 minutes, 503 thousand dollars frozen by NEAR SHIELD, and funds routed into bitcoin via THORChain" class="wp-image-480" /><figcaption class="wp-element-caption">Chart: BBVN Markets. Source: incident reporting and on-chain analysis, late September 2026.</figcaption></figure>



<h2 class="wp-block-heading">THORChain&rsquo;s answer: we can&rsquo;t, and we won&rsquo;t</h2>



<p class="wp-block-paragraph">Bitget CEO Gracy Chen publicly asked THORChain to refuse service to attacker-linked addresses, warning that &ldquo;the industry is watching.&rdquo; THORChain declined. Its position is that it is &ldquo;decentralized and permissionless like Bitcoin, Ethereum and BNB Chain,&rdquo; and that it has no function to screen individual addresses or transactions by policy. That is presented not as a limitation but as the design itself &mdash; a claim made more credible by the fact that THORChain revoked its admin keys before the 2025 Bybit hack, deliberately removing its own off-switch.</p>



<p class="wp-block-paragraph">Critics point to a contradiction. In May 2026, THORChain <strong>halted its chain</strong> after a vault exploit worth more than $10 million. If the network can pause for its own emergency, the argument goes, it can pause to stop laundering. THORChain&rsquo;s reply is that a halt is a liveness decision by validators &mdash; a pause the protocol allows &mdash; whereas address-level censorship is a different act entirely, one the protocol does not support. That distinction is technically real and, to a victim watching funds walk out the door, entirely academic.</p>



<p class="wp-block-paragraph">There is a deeper asymmetry here that both sides tend to skip. THORChain is not arguing it <em>cannot</em> build screening; it is arguing it <em>should not</em>. The engineering is not the hard part. The governance is: once you add a function that decides whose transfers to block, you have to answer who controls it, on what evidence, with what appeal, and how it behaves when a government asks for someone who is not a thief at all.</p>



<h2 class="wp-block-heading">NEAR Intents&rsquo; answer: screening, not surveillance</h2>



<p class="wp-block-paragraph">NEAR Intents took the other path. It deployed <strong>SHIELD</strong>, an automated risk layer that flagged and blocked more than $50 million in attempted transfers tied to the hack, freezing about $503,000 mid-execution. Only around $166,000 slipped through. It also waived Bitget&rsquo;s 5% recovery bounty, declining to profit from returning the money.</p>



<p class="wp-block-paragraph">Its general manager, Alex Shevchenko, framed the choice in property terms: &ldquo;Property rights are fundamental to functioning markets. A financial system where stealing an asset gives you an unrestricted right to monetize it isn&rsquo;t a freer system &mdash; it simply protects the thief.&rdquo;</p>



<p class="wp-block-paragraph">The design detail matters more than the slogan. SHIELD is <strong>automated and rule-based</strong>, not a human compliance desk making discretionary calls. That is deliberate. A system that applies published rules to every transaction is arguably more defensible &mdash; legally and politically &mdash; than one where an operator decides, case by case, whose funds to freeze. The first looks like a protocol property; the second looks like a bank deciding whether to honor a withdrawal.</p>



<h2 class="wp-block-heading">The legal fault line</h2>



<p class="wp-block-paragraph">Crypto lawyer Yuriy Brisov&rsquo;s read is that demonstrated control may create liability: if a system <em>can</em> stop a transfer and chooses not to, that choice can be scrutinized. On this view, automated, rule-based screening is far more defensible than human adjudication, precisely because it is predictable and even-handed &mdash; the same rule fires for the same inputs, every time.</p>



<p class="wp-block-paragraph">The libertarian counterpoint, from Dash&rsquo;s Jo&euml;l Valenzuela, is that if you can censor, you are no longer permissionless, and the ability itself &ldquo;opens Pandora&rsquo;s box&rdquo; &mdash; because the next request will not be for stolen funds, but for something far easier to justify and far harder to reverse. Bitwise Europe&rsquo;s Max Shannon split the difference: refusing to launder hack proceeds is a &ldquo;sound stance,&rdquo; and if THORChain will not do it, the laundering will simply migrate to THORChain and to every other venue that will not either.</p>



<p class="wp-block-paragraph">Strip away the labels and the disagreement narrows to one sentence. Everyone agrees stolen funds should not be spendable. They disagree about <em>who</em> should hold the power to make that true &mdash; and about whether building that power in the first place is worth the risk of it being used for something else later.</p>



<h2 class="wp-block-heading">Why this is not really about hacking</h2>



<p class="wp-block-paragraph">This is a debate about two architectures of a blockchain, and the hack is only the occasion.</p>



<ul class="wp-block-list"><li><strong>The bearer model.</strong> Whoever holds the key holds the asset. No third party can reverse a transfer. Recovery is limited to what victims can negotiate and what law enforcement can seize at the edges &mdash; an exchange deposit, a fiat off-ramp, a frozen stablecoin.</li><li><strong>The permissioned-in-practice model.</strong> Some operator &mdash; an issuer, a bridge, a venue &mdash; keeps the technical ability to screen and block, and uses it under a published policy. Transfers are still &ldquo;yours,&rdquo; but they pass through a system that can say no.</li></ul>



<p class="wp-block-paragraph">Stablecoins already live in the second model: every issuer can freeze, and did here. The question this week was whether the <em>first</em> model should quietly adopt the second&rsquo;s tools. NEAR Intents said yes, with rules. THORChain said no, on principle. Both answers are internally coherent, and both carry a cost: the first accepts a censor that must be governed; the second accepts a thief who cannot be stopped.</p>



<h2 class="wp-block-heading">The cross-chain blind spot</h2>



<p class="wp-block-paragraph">Cross-chain systems are where anti-money-laundering breaks down, and not by accident. On a single chain, a stolen asset is visible to everyone and spendable only by whoever holds the key; the one lever anyone has is a governance decision to freeze. When value crosses a bridge or a swap network, it passes through a component whose entire value proposition is that it does not ask who you are. The faster the bridge, the less time any counterparty has to react &mdash; and the 41-minute conversion window in the Bitget case is fast by design.</p>



<p class="wp-block-paragraph">That leaves a shrinking set of chokepoints. In practice, recovery now depends on three things: stablecoin issuers that can freeze, centralized exchanges that run know-your-customer checks on deposits, and the small number of cross-chain venues willing to screen. Everything else in the stack is built to be indifferent. The Bitget case is instructive precisely because it exercised all three chokepoints and still recovered 0.2%.</p>



<h2 class="wp-block-heading">What a rulebook would have to contain</h2>



<p class="wp-block-paragraph">NEAR Intents did not simply decide to be helpful; it implemented a policy. Anyone proposing that permissionless venues adopt screening has to answer five questions first:</p>



<ul class="wp-block-list"><li><strong>The rule set.</strong> What evidence triggers a block &mdash; a law-enforcement list, an on-chain attribution, a victim&rsquo;s assertion? Each carries a different error rate.</li><li><strong>The operator.</strong> Who maintains the rules: the protocol&rsquo;s validators, a foundation, or a third party? The answer determines how decentralized the network still is.</li><li><strong>The appeal.</strong> How does an address prove it was wrongly blocked? Without an appeal process, screening becomes a permanent and unaccountable ban.</li><li><strong>The scope creep.</strong> Today it is stolen funds. Tomorrow it is sanctioned entities, then politically exposed persons, then anyone a jurisdiction dislikes.</li><li><strong>The exit.</strong> Can users move to a venue that does not screen? If yes, screening routes around itself; if no, permissionlessness was always a story.</li></ul>



<p class="wp-block-paragraph">These are not rhetorical objections. They are the reason automated, published, uniformly applied screening is easier to defend than case-by-case judgment: it answers all five by construction, even if imperfectly. A human compliance desk answers none of them on the record.</p>



<h2 class="wp-block-heading">What to watch</h2>



<ol class="wp-block-list"><li><strong>Where the funds end up.</strong> If THORChain remains the last open door, laundering routes concentrate there &mdash; turning a philosophy into a single point of failure that regulators and victims will target next.</li><li><strong>Whether THORChain changes its policy.</strong> Any move to add an address-screening hook, even an opt-in one, would signal that even the most permissionless venues are shifting under pressure.</li><li><strong>Whether cross-chain screening standards appear.</strong> An industry standard &mdash; automated, published, and applied uniformly &mdash; would resolve the legal-defensibility problem without leaving each operator to decide for itself.</li></ol>



<h2 class="wp-block-heading">FAQ</h2>



<h3 class="wp-block-heading">Did the attacker steal Bitget&rsquo;s private keys?</h3>



<p class="wp-block-paragraph">No. Attackers wrote forged withdrawal instructions into Bitget&rsquo;s wallet system, reportedly through a vulnerability in a third-party security product. Bitget says private keys and cold wallets were not compromised.</p>



<h3 class="wp-block-heading">How much was actually recovered?</h3>



<p class="wp-block-paragraph">About $840,000 of roughly $387.5 million &mdash; around 0.2%. Tether and Circle froze between $318,000 and $340,000; NEAR Intents froze about $503,000.</p>



<h3 class="wp-block-heading">Why could stablecoins be frozen but not Bitcoin?</h3>



<p class="wp-block-paragraph">Stablecoins are issued by companies that retain a freeze function; the token is a claim on an issuer. Bitcoin has no issuer and no freeze function, so once stolen value is swapped into BTC, there is no switch to flip &mdash; only addresses to watch.</p>



<h3 class="wp-block-heading">What is THORChain&rsquo;s argument?</h3>



<p class="wp-block-paragraph">That it is permissionless by design and has no mechanism to screen individual addresses or transactions. Pausing for its own liveness emergency, it argues, is a different act from address-level censorship.</p>



<h3 class="wp-block-heading">What is NEAR Intents&rsquo; argument?</h3>



<p class="wp-block-paragraph">That property rights are foundational to a functioning market, and that automated, rule-based screening can stop laundering without giving a human operator discretion over whose funds to freeze.</p>



<h3 class="wp-block-heading">Does freezing funds set a precedent for censorship?</h3>



<p class="wp-block-paragraph">That is the core of the objection. Critics argue that any freeze capability, once built, will be requested for purposes beyond stolen funds &mdash; sanctions, political pressure, or simple regulatory caution. Defenders counter that the capability already exists at the stablecoin and exchange layer, and that the only real choice is whether it is governed by published rules or by whatever the loudest request happens to be.</p>



<h3 class="wp-block-heading">Is this a one-off?</h3>



<p class="wp-block-paragraph">No. As more value moves cross-chain, the question of who can freeze what will recur &mdash; and each incident becomes a precedent the next one cites. The 2025 Bybit hack already shaped THORChain&rsquo;s design decisions; the 2026 Bitget hack will shape the next round.</p>



<h2 class="wp-block-heading">Bottom line</h2>



<p class="wp-block-paragraph">The Bitget hack cost $387.5 million and returned about $840,000. The money is a rounding error; the fight is not. A permissionless network&rsquo;s strongest claim &mdash; that no one can stop your transaction &mdash; is also its weakest, because no one can stop a thief&rsquo;s either. NEAR Intents built a rulebook and enforced it automatically. THORChain refused to write one. The next hack will show which answer the market rewards &mdash; and which one regulators decide to test first.</p>



<h2 class="wp-block-heading">Sources</h2>



<ul class="wp-block-list"><li>Cointelegraph Magazine &mdash; <a href="https://cointelegraph.es/magazine/furious-debate-about-thorchain-vs-near-shows-idealism-has-limits" rel="nofollow noopener" target="_blank">The furious debate about THORChain vs. NEAR shows idealism has limits</a></li><li>Gate / FinanceFeeds &mdash; <a href="https://web.gate.it/zh/news/detail/thorchain-refuses-to-block-3875m-bitget-hack-funds-while-near-intents-24666857" rel="nofollow noopener" target="_blank">THORChain refuses to block $387.5M Bitget hack funds</a></li><li>Yahoo Tech &mdash; <a href="https://tech.yahoo.com/cybersecurity/articles/near-stopped-bitgets-hackers-without-191250541.html" rel="nofollow noopener" target="_blank">NEAR stopped Bitget&rsquo;s hackers without breaking privacy</a></li><li>BlockSec &mdash; <a href="https://blocksec.com/zh-hant/blog/bitget-hack-laundering-fund-tracing" rel="nofollow noopener" target="_blank">Bitget hack laundering path and attribution analysis</a></li><li>Cointelegraph &mdash; <a href="https://lcx.com/en/cryptonews/near-intents-says-it-blocked-50m-tied-to-bitget-hackers" rel="nofollow noopener" target="_blank">NEAR Intents says it blocked $50M tied to Bitget hackers</a></li></ul>

]]></content:encoded>
					
					<wfw:commentRss>https://www.newsbbvn.com/analysis/485.html/feed</wfw:commentRss>
			<slash:comments>1</slash:comments>
		
		
			</item>
		<item>
		<title>The Security Floor Didn&#8217;t Move. The Ceiling Became Your Job.</title>
		<link>https://www.newsbbvn.com/blockchain/191.html</link>
					<comments>https://www.newsbbvn.com/blockchain/191.html#respond</comments>
		
		<dc:creator><![CDATA[BBVN Research]]></dc:creator>
		<pubDate>Tue, 29 Sep 2026 02:11:22 +0000</pubDate>
				<category><![CDATA[Blockchain]]></category>
		<category><![CDATA[CCIP]]></category>
		<category><![CDATA[Chainlink]]></category>
		<category><![CDATA[Cross-Chain Bridges]]></category>
		<category><![CDATA[crypto]]></category>
		<category><![CDATA[Cybersecurity]]></category>
		<category><![CDATA[DeFi]]></category>
		<category><![CDATA[hacks]]></category>
		<category><![CDATA[kelpdao]]></category>
		<category><![CDATA[LayerZero]]></category>
		<category><![CDATA[security]]></category>
		<guid isPermaLink="false">https://www.newsbbvn.com/markets/191.html</guid>

					<description><![CDATA[Chainlink&#8217;s CCIP 2.0 hands integrators the dial for cross-chain security while retiring one of the two independent checks its default used to run. The floor held. The ceiling became the integrator&#8217;s job.]]></description>
										<content:encoded><![CDATA[<p>Chainlink&rsquo;s CCIP 2.0 does not make cross-chain transfers safer by default. It makes them safer only when the teams integrating it choose to do the work, and it hands those teams both the dial and the bill.</p>
<p>On Monday, 2026-09-28, Chainlink released CCIP 2.0, an upgrade to the Cross-Chain Interoperability Protocol it first shipped in <strong>2023</strong>. The release lets companies add their own security checks to cross-chain transfers on top of Chainlink&rsquo;s default verifier network of <strong>16</strong> independent node operators, which must reach a quorum on every transfer.</p>
<figure class="wp-block-image size-large"><img loading="eager" decoding="async" src="https://www.newsbbvn.com/wp-content/uploads/2026/09/suspension-bridge-night.jpg" alt="A suspension bridge lit at night over a river" width="1400" height="1025" /><figcaption>A bridge only works because both ends were designed together. Cross-chain messaging has the same property &mdash; and far less steel to inspect. <em>Photo: Derek Jensen (Tysto), public domain</em></figcaption></figure>
<h2>Cross-chain security has a lineage, and each generation hands the next one an unsolved hole</h2>
<p>Blockchains cannot communicate directly, so moving a token from one chain to another depends on a bridge. That technology relies on verifiers, which confirm that a transaction really happened on the first chain before funds are released on the second. If a verifier is fooled, an attacker can withdraw money that was never deposited.</p>
<p>That problem has a lineage, and the lineage is the clearest way to judge a design. The first generation used federated multisig bridges: a fixed set of signers held the keys and approved every transfer. It was cheap to build, but the signer set was the whole security model, and one wrong signature was final. The second generation answered with light clients, which let the destination chain verify the source chain&rsquo;s headers itself, removing the need to trust a signer set. Light clients were expensive to run, awkward across heterogeneous chains, and throttled by gas, so operators introduced external verifier networks: dedicated services that watched the source chain and signed attestations. That fixed the cost and the awkwardness, and it reintroduced trust in a set. The current generation is a market of pluggable verifiers, where an application can require several independent verification services at once. Every verifier-set generation shares the same weakness: a single wrong answer is final, and nothing on the destination chain can tell the difference.</p>
<p>April 2026 gave that weakness a price. Attackers allegedly linked to North Korea&rsquo;s Lazarus Group drained about <strong>$292 million</strong> in rsETH from Kelp DAO&rsquo;s bridge, which ran on Chainlink&rsquo;s rival LayerZero, after tricking the single verifier the setup relied on. LayerZero blamed Kelp for using one verifier instead of several, while Kelp said LayerZero staff had reviewed its setup and never objected. CoinGecko data showed nearly half of active LayerZero apps used the same one-verifier arrangement, and Kelp said it would move rsETH to Chainlink.</p>
<p>The honest lesson is not about a missing feature. The failure was a configuration choice, made by people who had a working default and turned it down, and the same pattern ran through that month&rsquo;s wider run of bridge and authorization failures, which we covered in our report on the <a href="https://www.newsbbvn.com/markets/72.html">April 2026 security cluster</a>. CCIP 2.0 arrives directly downstream of that month.</p>
<h2>What CCIP 2.0 actually changed</h2>
<p>The upgrade lets companies add their own security checks to cross-chain transfers on top of the default verifier network of 16 independent node operators, which must reach a quorum on every transfer. The release note lists five opt-in features: additive security through issuer, third-party, or institution-operated Cross-Chain Verifiers (CCVs); faster-than-finality (FTF) transfers; modular fee components; built-in compliance functions through the Chainlink Automated Compliance Engine (ACE); and permissionless execution, a custom executor, or No Exec. The Router contract, the single point of interface, is unchanged on all networks, and existing integrations keep working with no changes.</p>
<p>Two changes matter more than the feature list. First, the default stays the default: keep the default verifier and add CCVs as defense in depth, because additional CCVs are not a replacement for it. Second, Chainlink&rsquo;s Risk Management Network, a separate set of nodes that double-checked transactions and was promoted heavily, no longer plays that role; that independent check can now come from the optional verifiers instead. The consequence is that an application that changes nothing now relies on one verifier network where there used to be two, though that one network is 16 operators rather than a single verifier. Chainlink has not named any institution using the new verifiers yet, saying only that Aave and Maple have started adopting some of the upgrade&rsquo;s other features.</p>
<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" src="https://www.newsbbvn.com/wp-content/uploads/2026/09/chain-link-fence-closeup-night.jpg" alt="Chain links of a fence in close-up at night" width="1400" height="933" /><figcaption>Verification is additive by design: every added link carries load, and every added link can fail. <em>Photo: Sean DuBois, CC0</em></figcaption></figure>
<h2>If the default did not move, why does this release matter?</h2>
<p>Because the ownership of the decision moved. Chainlink&rsquo;s stated position is that users should not have to be cross-chain security infrastructure experts, and it told CoinDesk exactly that. The same release hands those same users a dial that requires precisely that expertise. Before adding any verifier, a team has to be able to answer, in writing, each of the following.</p>
<ol>
<li>Who operates this verifier, and under which jurisdiction, and what happens to my messages if that operator is compelled or disappears?</li>
<li>Does it provide the same reorg quarantine as the default Committee Verifier? The documentation states plainly that the default&rsquo;s reorg quarantine is specific to it and that third-party CCVs may not provide equivalent protection.</li>
<li>If the verifier stops responding, do my messages stall? The documentation warns that unresponsive verifiers can stall execution for all messages that require their attestation.</li>
<li>Is the verifier in the indexer&rsquo;s configuration? CCVs not known to the indexer&rsquo;s configuration are silently skipped, which can cause execution to stall for the messages that require their attestation.</li>
<li>Who pays for its maintenance, and at what rate, next year and the year after?</li>
</ol>
<p>I have seen too many teams add a dependency because it was available in a config file and then discover, six months later, that nobody on staff could describe who operated it or who to wake up when it stopped signing.</p>
<h2>The cost of a verifier you added yourself</h2>
<p>This is a trust boundary, not a feature. Chainlink&rsquo;s <a href="https://docs.chain.link/ccip/concepts/ccvs/trust-responsibility-model" rel="nofollow noopener" target="_blank">trust and responsibility model</a> puts the line plainly: operators of custom or third-party CCVs, outside the default Committee Verifier, own implementation quality, specification compliance, maintenance, and reliability, and neither Chainlink Labs nor the Chainlink Foundation is responsible for the development, maintenance, or operation of external CCV contracts or infrastructure. Conforming to the VerifierResult API spec and the verifyMessage interface is not optional either: failure to conform can cause stuck transactions, incorrect token accounting, or loss of funds. And because the design is permissionless, anyone can deploy a CCV, so the set of possible verifiers is unbounded while the set of audited ones is not.</p>
<table>
<thead>
<tr>
<th>Component</th>
<th>Provided by CCIP</th>
<th>Owned by the operator or integrator</th>
</tr>
</thead>
<tbody>
<tr>
<td>Default Committee Verifier</td>
<td>16 operators, quorum, onchain contracts, reorg quarantine</td>
<td>Risk assessment when using faster-than-finality</td>
</tr>
<tr>
<td>Third-party CCV such as CCTP or Lombard</td>
<td>Onchain interface enforcement, indexer integration</td>
<td>Attestation service uptime, API reliability, reorg policy</td>
</tr>
<tr>
<td>Custom CCV</td>
<td>Protocol interface spec, ramp caller validation</td>
<td>Full onchain and offchain implementation, maintenance, SLA</td>
</tr>
<tr>
<td>RMN curse flag</td>
<td>Onchain emergency stop contract</td>
<td>Deciding when to pull it and who is on call</td>
</tr>
</tbody>
</table>
<p>One detail matters. Each CCV uses a stable onchain resolver contract with versioned implementations behind it, and an immutable <strong>4-byte</strong> version tag acts as a domain separator, so attestation data from one verifier version cannot be replayed in another. That is good engineering, and it is also a promise about a component with no service-level agreement. The version tag protects the protocol from replay; it does not protect you from an operator who quietly stops responding.</p>
<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" src="https://www.newsbbvn.com/wp-content/uploads/2026/09/engineer-server-rack-data-center.jpg" alt="An engineer with a laptop working on a data center server rack" width="1400" height="930" /><figcaption>Running your own verifier is an operations job, not a checkbox: keys, hardware, uptime, and a person on call. <em>Photo: Derrick Coetzee, CC0</em></figcaption></figure>
<h2>Read the default before you touch the dial</h2>
<p>The dial has teeth in one place above all: faster-than-finality. Every layer defaults to full finality. FTF requires explicit opt-in at every layer that participates in the message path. The sender sets a non-finality mode in ExtraArgsV3; the token pool must configure an allowedFinalityConfig that permits it; each CCV must permit it; the executor must permit it; and for messages that call ccipReceive the receiver must permit it. If any layer rejects the requested mode, the send reverts or the message is recorded as FAILURE. Legacy V1 pools and receivers cannot opt in at all. On Ethereum, full finality takes two epochs, about <strong>12.8</strong> to 19 minutes.</p>
<p>Work through the concrete failure. A sender opts into a 2-block confirmation depth, roughly 24 seconds. A 3-block reorg then replaces those blocks. If attestation and execution already happened, the delivery stands, and the canonical fork produces a new message ID, because the message ID is keccak256 of the encoded message and the encoded payload commits to the per-lane message number, which can differ after a reorg. Two IDs mean two deliveries, and both can reach SUCCESS. The reorg quarantine in the default Committee Verifier narrows this window but does not close it: double execution remains possible when the chosen confirmation depth is less than or equal to the depth of the reorg and the pre-reorg message was already attested and executed before the reorg was detected. There is also a documented edge case apart from FTF: if a source chain&rsquo;s finalized checkpoint itself reorgs after messages were attested at full finality, recovery may require manual intervention for that chain.</p>
<blockquote>
<p>&ldquo;CCIP does not guarantee offchain verifier uptime, external API availability, or reorg-handling behavior for third-party CCVs. Operators and integrators are responsible for assessing those risks.&rdquo;</p>
<p><cite>Chainlink CCIP documentation, CCV Interfaces and Guarantees</cite></p></blockquote>
<p>The engineering rule is simple to state and hard to accept. If you cannot describe, in one paragraph, the corrective logic your application runs after a double execution, you are not ready to enable FTF. That logic has to name an idempotency key and a reconciliation job, because two message IDs means your application has to decide, on its own, that two deliveries are one payment.</p>
<h2>Additive security is additive work</h2>
<p>Adding verifiers reduces trust in any single verifier, and it adds a liveness dependency: every required CCV must produce a valid result before execution proceeds, so a verifier that is down blocks delivery. Security and liveness are not the same axis. The central judgment is this: the number of verifiers does not secure a bridge. What secures it is whether the failures of those verifiers are correlated with the thing you are defending against. Sixteen operators chosen by one vendor and two chosen by you are not the same claim, and neither is automatically better.</p>
<blockquote>
<p>&ldquo;Historically, legacy bridges have lost billions due to insecure infrastructure, while in-house builds are slow and expensive,&rdquo; Johann Eid, Chainlink Labs&rsquo; chief business officer, said in a statement.</p>
<p><cite>Johann Eid, Chainlink Labs chief business officer</cite></p></blockquote>
<p>Read that statement carefully. It is a real observation, and an argument about who carries the maintenance bill, not about cryptography. The same ecosystem that spent April absorbing someone else&rsquo;s single-verifier decision, as our <a href="https://www.newsbbvn.com/crypto/ethereum/163.html">analysis of restaking economics and the Kelp exploit</a> documented, now offers to hold part of that bill &mdash; while its own default went from two independent checks to one. CoinDesk&rsquo;s <a href="https://www.coindesk.com/business/2026/09/28/chainlink-updates-its-crypto-bridge-tech-months-after-a-usd292-million-hack-shook-the-industry" rel="nofollow noopener" target="_blank">coverage of the upgrade</a> is worth reading alongside the documentation.</p>
<p>It is not a cryptographic guarantee &mdash; it is a service contract, and the contract names you as the operator. A disclaimer notes that Chainlink does not hold or transfer any assets, and that the profile of a CCV varies depending on the verifier selected. Eighty percent of a system&rsquo;s lifetime cost is maintenance, so the only question that matters about a new verifier is who maintains it, and at what interest rate.</p>
<h2>What to write down before you ship</h2>
<p>A decision record, not a wish list. Before enabling any of this, the team should be able to produce five artifacts.</p>
<ol>
<li>The verifier set you actually require, written per lane, with the operator named for each required verifier.</li>
<li>The finality mode requested per lane, together with the reorg profile of each source chain that justifies that choice.</li>
<li>Your corrective logic for double execution, with the idempotency key or reconciliation job named explicitly.</li>
<li>The monitoring and on-call path for every verifier you added, including what happens when one is unresponsive.</li>
<li>The maintenance owner with a review date, because a verifier set rots the moment nobody owns it.</li>
</ol>
<p>Writing this down is the deliverable, not the code. The code is the easy part, and it is mostly configuration. The record is the part that survives the staff change, the reorg, and the operator who quietly stops signing. An architecture choice that needs more people to operate is a reasonable trade when those people are named, and a failure when they are not. The programmer is the author of the dial, and authorship carries accountability for what the dial does at three in the morning.</p>
<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" src="https://www.newsbbvn.com/wp-content/uploads/2026/09/old-padlock-wooden-door.jpg" alt="A rusty padlock securing a latch on a weathered wooden door" width="1400" height="934" /><figcaption>A lock is only as good as the last person who checked it. So is a verifier set. <em>Photo: Estormiz, CC0</em></figcaption></figure>
<p>What I do not know, stated plainly. The release is one day old at the time of writing, so there is no track record to read. Chainlink has named no institution using the new verifiers, and Aave and Maple have only adopted some of the upgrade&rsquo;s other features, which means the additive-security path is, so far, a design argument rather than an observed result. Whether sixteen operators under one quorum are stronger than two operators chosen by an integrator is not a settled fact either; it depends entirely on correlation, and nobody has published that correlation. The weaker default is a real change in posture for applications that do nothing, because one verifier network now stands where two stood before, even though that network is sixteen operators, not a single verifier.</p>
<p>The security floor did not move. The default is still the default, the Router still did not change, and existing integrations still work untouched. What moved is the ceiling, and the ceiling is now the integrator&rsquo;s job. A job that nobody writes down is a job nobody does, and on a bridge that is the whole of the risk.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.newsbbvn.com/blockchain/191.html/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>Crypto&#8217;s Security Bill Came Due This Week: Bitget, KelpDAO, Zano and Magic Eden</title>
		<link>https://www.newsbbvn.com/markets/72.html</link>
					<comments>https://www.newsbbvn.com/markets/72.html#respond</comments>
		
		<dc:creator><![CDATA[BBVN Research]]></dc:creator>
		<pubDate>Mon, 28 Sep 2026 02:17:18 +0000</pubDate>
				<category><![CDATA[Analysis]]></category>
		<category><![CDATA[Markets]]></category>
		<category><![CDATA[bitget]]></category>
		<category><![CDATA[crypto]]></category>
		<category><![CDATA[hacks]]></category>
		<category><![CDATA[kelpdao]]></category>
		<category><![CDATA[magic-eden]]></category>
		<category><![CDATA[market]]></category>
		<category><![CDATA[security]]></category>
		<category><![CDATA[thorchain]]></category>
		<category><![CDATA[zano]]></category>
		<guid isPermaLink="false">https://www.newsbbvn.com/?p=72</guid>

					<description><![CDATA[Four security failures in seven days - Bitget's 387.5M dollar wallet breach, KelpDAO's lawsuit against LayerZero, Magic Eden's rescued NFTs and Zano's month-long rollback - share one root cause: guarantees kept in processes instead of protocol invariants.]]></description>
										<content:encoded><![CDATA[<figure class="wp-block-image size-large"><img decoding="async" src="https://www.newsbbvn.com/wp-content/uploads/2026/09/crypto-exchange-data-center.jpg" alt="Data center corridor lined with server racks" width="1024" height="683" /><figcaption>Hot and warm wallets exist because settlement speed is a product feature. That uptime is also the attack surface. <em>Photo: jurvetson / Flickr (CC BY 2.0)</em></figcaption></figure>
<p><strong>Crypto&#8217;s security bill came due this week, and it arrived itemised.</strong> In seven days the industry booked a <strong>$387.5 million</strong> exchange breach, took a <strong>$292 million</strong> bridge failure to court, moved <strong>3,832 NFTs</strong> into protective custody, and — the most expensive admission of all — rolled a layer-1 blockchain back by an entire month. Four incidents, four teams, one structural failure repeated four times: <strong>the industry keeps its security promises in processes and configuration instead of protocol invariants.</strong></p>
<p>That is not a moral judgement, it is an engineering one. Nobody invented a new class of attack this week. Attackers walked through trust paths that were already there — an exchange&#8217;s signing backend, a single cross-chain verifier, a feature added to make integration easier, and an NFT approval granted years ago and never revoked.</p>
<p>Here is what happened, in order, followed by the only question worth asking of every &#8220;security upgrade&#8221; announced in the next month: does it remove trust from the system, or just move it somewhere less visible?</p>
<h2>September&#8217;s security ledger (Sept. 24–28, 2026)</h2>
<table>
<tbody>
<tr>
<th>When</th>
<th>Project</th>
<th>Reported loss</th>
<th>Where the failure lived</th>
</tr>
<tr>
<td>Sept. 24–25</td>
<td>Bitget</td>
<td>$387.5M (first reported at $351.6M)</td>
<td>The backend of the wallet service: forged transfer data fed into the authorization-signing flow</td>
</tr>
<tr>
<td>Sept. 25</td>
<td>KelpDAO v. LayerZero</td>
<td>$292M (exploit dated April 18)</td>
<td>A single LayerZero verifier path approved a forged cross-chain message</td>
</tr>
<tr>
<td>Sept. 25</td>
<td>Magic Eden</td>
<td>~$5.7M of NFTs exposed</td>
<td>Legacy approvals still live on old marketplace contracts</td>
</tr>
<tr>
<td>Sept. 28</td>
<td>Zano</td>
<td>~1 month of chain history invalidated</td>
<td>Gateway Addresses (Hard Fork 6) allowed unauthorized ZANO and fUSD issuance</td>
</tr>
<tr>
<td>Sept. 24–28</td>
<td>THORChain</td>
<td>$0 lost, reputation spent</td>
<td>Refusal to blacklist addresses linked to the Bitget hack</td>
</tr>
</tbody>
</table>
<p>One caveat before the detail: loss figures in live incidents are moving targets. Bitget&#8217;s own tally started at $351.6 million and was revised up to $387.5 million. KelpDAO&#8217;s $292 million is the value of 116,500 rsETH at the time of April&#8217;s exploit, not the value of the incident filed in court this week. Treat every number below as a snapshot, including ours.</p>
<h2>Bitget: the wallet that has to stay online</h2>
<p>Bitget disclosed &#8220;unauthorized transfers&#8221; affecting parts of its hot and warm wallet infrastructure on Sept. 24 and suspended withdrawals while it investigated. In a live Q&amp;A the following day, CEO Gracy Chen said attackers had compromised a backend system of the wallet service and used it to forge transfer information that was passed into the exchange&#8217;s authorization-signing process.</p>
<p>Her account is specific, and worth reading carefully: the attackers did not forge user withdrawal requests, and they did not obtain private keys to the cold, hot or warm wallets. If that holds, the lesson is not &#8220;Bitget had weak keys.&#8221; It is that <strong>a signature is only as trustworthy as the request pipeline that fills it in.</strong> The chain did exactly what it was told to do — which is the eternal problem with using a public ledger as your audit trail while trusting a private service to decide what the ledger gets told.</p>
<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" src="https://www.newsbbvn.com/wp-content/uploads/2026/09/wallet-signing-circuit-board.jpg" alt="Close-up of a circuit board with memory chips" width="1024" height="679" /><figcaption>&#8220;Unauthorized transfers&#8221; describe a forged signing path, not a stolen seed phrase. <em>Photo: Rawpixel (CC0)</em></figcaption></figure>
<p>Chen said preliminary findings matched IP addresses to VPN services used by a North Korean group, and that the exchange does not believe the breach was an inside job. Onchain researcher Specter traced part of the stolen XRP to an Ethereum address whose funding history overlaps a wallet previously tied to the AFX exploiter — a project whose own post-mortem pointed at TraderTraitor, a North Korea-linked group. That is pattern-matching, not proof, and Bitget framed it that way. But North Korea-linked theft reached an estimated $2.02 billion in 2025, including the roughly $1.5 billion Bybit hack, so the prior probability behind the claim is uncomfortably high.</p>
<p>Some funds have reportedly been recovered. The deeper issue is why the exposure existed at all. Hot and warm wallets exist because a withdrawal that takes thirty minutes is a lost customer. That is a business decision, and a defensible one — but it is a decision to place the security boundary inside an online service rather than at a cryptographic invariant. When that boundary fails, onchain immutability is not a defence. It is the weapon.</p>
<h2>THORChain: what an invariant actually costs</h2>
<p>The second-order fight is more instructive than the breach. Chen publicly called on THORChain — the protocol where much of the Bybit hack&#8217;s funds were swapped — to block the addresses tied to her exchange&#8217;s stolen funds: <em>&#8220;Decentralization is a design principle, not a shield for facilitating known stolen funds.&#8221;</em> THORChain declined.</p>
<p>Both sides are paying a real price, which is why this debate never resolves cleanly. Chen is asking a permissionless system to adopt the exact compliance primitives regulators have spent a decade demanding from exchanges. THORChain&#8217;s refusal preserves an invariant its users rely on — but it also means a sanctioned state actor can swap stolen assets through it, and &#8220;we don&#8217;t do blacklists&#8221; rings hollow when the system&#8217;s operators can pause the chain at will. They did exactly that in May, when THORChain itself was hacked for $10.7 million. The project says it retired its admin key back in February 2025, which raises an awkward question it has not fully answered: what, precisely, would it use to comply if it wanted to?</p>
<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" src="https://www.newsbbvn.com/wp-content/uploads/2026/09/cross-chain-bridge-cables.jpg" alt="Yellow Ethernet cables with RJ45 connectors" width="960" height="641" /><figcaption>Every bridge and swap desk is a join between systems — and the place where trust assumptions leak. <em>Photo: StockSnap (CC0)</em></figcaption></figure>
<p>That is the pattern worth remembering. A property that can be switched off by five people in a chat group is not an invariant; it is a configuration. Invariants are the things that stay true on the worst day, not the ones described in a blog post. Note what happened next: RUNE rose roughly 50% in a week. Being publicly accused of laundering is, in this market, a marketing event.</p>
<h2>KelpDAO v. LayerZero: when the guarantee lives in a document</h2>
<p>On Sept. 25, KelpDAO sued LayerZero and CEO Bryan Pellegrino over the April 18 exploit that drained 116,500 rsETH — about $292 million at the time — from Kelp&#8217;s LayerZero-powered bridge. Kelp&#8217;s position: LayerZero failed to disclose risks and, in writing, reviewed and endorsed the bridge&#8217;s deployment and configuration before the attack. Pellegrino&#8217;s substantive response was one word — &#8220;meritless&#8221; — and he says he will defend the case in Vancouver.</p>
<p>LayerZero&#8217;s final incident report describes a compromised internal node and a verifier that approved a forged cross-chain message. Its argument is that the loss was possible because Kelp&#8217;s bridge used a single LayerZero decentralized verifier network (DVN) as its only verification path, and that it had recommended running more than one. Kelp says that configuration was previously discussed and &#8220;confirmed as secure,&#8221; and has since announced it will migrate the rsETH bridge to Chainlink&#8217;s interoperability protocol.</p>
<p>Set aside who wins. The structural fact is that a multi-hundred-million-dollar security guarantee was, at the decisive moment, <strong>a document</strong>: a recommended configuration, a review, an endorsement. Nobody wrote the requirement into the protocol — &#8220;two independent verifiers must sign before value leaves&#8221; — which is the only place it would have been enforced automatically. Controls that live in reviews and emails are not controls. They are debts with a floating interest rate, and the interest is paid by whoever is holding the tokens when the forged message lands.</p>
<h2>Zano: the most honest expensive decision of the week</h2>
<p>Zano, a privacy-focused layer-1 launched in 2019, restarted its chain at block 3,833,000 — the block immediately before Hard Fork 6 — after a vulnerability in Gateway Addresses let unauthorized ZANO and Freedom Dollar (fUSD) tokens enter circulation. The rollback invalidates roughly a month of history: legitimate transactions from that window no longer exist on the recovered chain, and payments already settled on other blockchains cannot be reversed at all. Nodes, miners, stakers, exchanges and services all had to adopt the update, and the team says it will publish a reimbursement and claims process.</p>
<p>Trace the engineering, because it is a textbook sequence. Gateway Addresses were introduced to make life easier for bridges, exchanges and payment providers by handing them account-style balances instead of forcing them to scan for individual UTXOs. That is a first-order business feature — it lowers integration cost and it wins listings. It also moved the protocol&#8217;s trust model, quietly, in the direction of &#8220;one account can mint into the system if the logic is wrong.&#8221; When the logic was wrong, the only remaining remedy was the one tool that should never be needed: rewriting the chain.</p>
<p>Zano&#8217;s team is unusually blunt about the trade-off. &#8220;Restarting the chain from before Hard Fork 6 costs a month of history, and it costs trust, which we&#8217;ll have to earn back,&#8221; said head of marketing and growth Quinten van Welzen. &#8220;But it restores the supply everyone signed up for&#8230; We know it hurts. But not doing it would have hurt more.&#8221;</p>
<p>He is not wrong, and that is the uncomfortable part. Doing nothing meant unlimited dilution of an asset whose basic promise is a fixed supply — plus a signal to every future attacker that exploited coins keep their value. But be clear about what was decided: finality was treated as a configurable parameter, and the switch was flipped by the core team. That is not decentralisation failing. It is decentralisation that was never fully paid for, and the invoice arrived as a month of legitimate history.</p>
<h2>Magic Eden: approvals are a subscription you forgot you bought</h2>
<p>On Sept. 25, a single wallet moved 3,832 NFTs out of hundreds of wallets in transactions that appeared as sales on Magic Eden. Community member Cirrus flagged the activity publicly and told holders to revoke permissions; Yuga Labs&#8217; vice president of blockchain, 0xQuit, identified it as a whitehat rescue — the NFTs are safe and will be returned once they are no longer at risk. The Block reported that roughly $5.7 million of NFTs were exposed before the rescue.</p>
<p>There is no villain here, and that is the point. The exposure came from legacy approvals: permissions granted to old contracts that keep working long after the product, or the team behind it, has moved on. Nobody audits them. Nobody revokes them. They accumulate for years, and they are the least dramatic, most predictable line item in crypto&#8217;s security budget. The only cure is operational hygiene — revoking what you no longer use, exactly as you would remove a former employee&#8217;s access.</p>
<h2>The one idea pointing the other way</h2>
<p>Before leaving the SEC on Oct. 2, Commissioner Hester Peirce made the week&#8217;s most useful engineering argument: that hoarding identity documents online creates databases that get hacked, and that zero-knowledge proofs let a user prove eligibility without handing over a name, income or address. It is the same principle in reverse. Instead of trusting a company to hold your data safely, you verify without disclosing it.</p>
<p>That is what a real security improvement looks like: <strong>it removes data and trust from the path, rather than protecting them better inside the path.</strong> Keep that test in mind when you read the incident reports that will follow this week&#8217;s breaches — most will promise a stronger lock on a door that should not have existed.</p>
<figure class="wp-block-image size-large"><img loading="lazy" decoding="async" src="https://www.newsbbvn.com/wp-content/uploads/2026/09/defi-bridge-lawsuit-gavel.jpg" alt="Wooden gavel resting on a desk beside papers" width="1024" height="683" /><figcaption>KelpDAO is now asking a court to decide who owed the security guarantee. <em>Photo: Joe Gratz / Flickr (CC0)</em></figcaption></figure>
<h2>Why the market barely blinked</h2>
<p>Here is the number that should bother you more than any breach. Over the same stretch in which close to $680 million of value was stolen, invalidated or placed at risk, Bitcoin traded around $83,700–$84,200, up roughly 3.8% on the week. Ether sat near $2,660. Total market capitalisation held around $2.87 trillion, with Bitcoin dominance near 59%. Bitcoin ETFs notched a seven-session inflow streak, adding about $2.4 billion in a single week — their largest inflow since October, and enough to turn 2026 flows positive, according to The Block.</p>
<p>Read those two facts together. Institutional money is arriving through a wrapper that carries no exchange custody risk, while the users who supply spot exchange liquidity absorb the losses. The market is not saying that security does not matter. It is pricing these incidents as a recurring operating expense rather than a systemic risk — and as long as that pricing holds, the incentive to actually pay down the debt stays weak.</p>
<h2>A checklist for telling a fix from a new debt</h2>
<p>Every project involved this week will announce a hardening plan. Most will be defensible. Some will simply move trust somewhere less visible. Six questions separate the two:</p>
<ol>
<li><strong>Does it remove people and processes from the trust path, or add them?</strong> If the fix depends on more humans being careful, you have bought insurance, not architecture.</li>
<li><strong>Is the guarantee enforced by code or by policy?</strong> &#8220;Two independent verifiers must sign&#8221; is code. &#8220;We recommend two verifiers&#8221; is a wish.</li>
<li><strong>What is the defined failure mode, and who can trigger it?</strong> Zano can answer this precisely, which is more than most projects can. Its answer was &#8220;rewrite a month of history.&#8221;</li>
<li><strong>How many approvals stand between an attacker and the funds, and where is that threshold written?</strong> In a multisig or threshold-signing setup it is inspectable. Inside a backend service, it is a promise.</li>
<li><strong>Does it follow the architecture the largest operators already run</strong> — multi-verifier bridges, threshold signing, hardware key management — or a bespoke scheme only its authors understand?</li>
<li><strong>Can the improvement be measured?</strong> Loss per quarter, approvals revoked, verifiers that are actually independent. A security programme that cannot be quantified is marketing with a budget.</li>
</ol>
<h2>What to watch next</h2>
<ul>
<li><strong>KelpDAO v. LayerZero</strong> — a ruling on bridge responsibility would set the default for how integration risk is priced across DeFi.</li>
<li><strong>Bitget&#8217;s recovery and post-mortem</strong> — above all, whether the signing pipeline is rebuilt around hardware-enforced policy or merely re-tuned process. Withdrawals and the final loss figure still need to settle.</li>
<li><strong>Zano&#8217;s claims process</strong> — how a rollback compensates users whose valid transactions it erased is the real test of whether this was a rescue or a quiet transfer of loss.</li>
<li><strong>Multi-verifier defaults</strong> — LayerZero says it no longer acts as the sole required verifier, and Kelp has moved to Chainlink CCIP. Watch whether single-verifier configurations survive the next audit cycle at all.</li>
<li><strong>THORChain&#8217;s answer</strong> — if it cannot say what mechanism it would use to comply, the debate over whether it should is academic.</li>
</ul>
<h2>FAQ</h2>
<h3>How much did Bitget lose in the September 2026 hack?</h3>
<p>Bitget initially reported $351.6 million in unauthorized transfers, then revised the figure to $387.5 million as tracing continued. The exchange suspended withdrawals while investigating and says some funds have been recovered.</p>
<h3>Did Bitget lose private keys?</h3>
<p>No. CEO Gracy Chen said attackers compromised a backend system of the wallet service and forged transfer information that was passed into the authorization-signing process, without obtaining cold, hot or warm wallet private keys.</p>
<h3>Was North Korea responsible for the Bitget breach?</h3>
<p>That is preliminary, not proven. Bitget cited IP addresses matching VPN services linked to a North Korean group, and an independent onchain researcher reported funding histories overlapping an address tied to a North Korea-linked exploiter.</p>
<h3>Why did Zano roll back its blockchain?</h3>
<p>A vulnerability in Gateway Addresses let unauthorized ZANO and Freedom Dollar tokens into circulation, diluting holders of a fixed-supply asset. The team restarted the chain at the block before Hard Fork 6, which also invalidated roughly a month of legitimate transactions.</p>
<h3>What happened with Magic Eden&#8217;s NFTs?</h3>
<p>A whitehat operator moved 3,832 NFTs out of hundreds of wallets into protective custody after legacy approvals left them exposed. The NFTs are reported safe and will be returned to holders.</p>
<h3>Did KelpDAO&#8217;s lawsuit succeed?</h3>
<p>It was filed on Sept. 25, 2026 against LayerZero and CEO Bryan Pellegrino. Pellegrino has called the claim meritless and says he will defend it in Vancouver. No ruling has been issued.</p>
<hr />
<p><em><strong>Method note:</strong> This analysis applies the technical-debt framework of Chinese engineer Chen Hao (左耳朵耗子, 1976–2023), who argued that every architecture decision is a loan: trace what it replaced, name the interest, and quantify the benefit before calling it elegant. Market data are snapshots taken on Sept. 28, 2026 via CoinGecko.</em></p>
<p><em><strong>Disclaimer:</strong> This article is for informational purposes only and is not investment advice. Loss figures in active incidents change as investigations progress, and cryptocurrency markets are highly volatile. Always do your own research.</em></p>
<p>Track live prices, market rankings and the latest crypto news on <a href="https://www.newsbbvn.com/">BBVN Markets</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://www.newsbbvn.com/markets/72.html/feed</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
