Crypto Daily™
16.1k 投稿
Crypto Daily™
厳選トピック確認済＋報告
ユーザーをブロック
The leading Crypto News site that 'BRIDGES' the gap between companies. website➡️https://cryptodaily.co.uk/
Creator of the Year
0 フォロー
76.8K+ フォロワー
59.4K+ いいね
1 バッジ
投稿
翻訳参照
How Six Seven Club Turned Telegram Holders Into Distribution Instead of Exit LiquidityTelegram’s mini-app category spent much of the past year being written off. The last airdrop cycle left an array of apps whose token generation event immediately preceded their funeral, as it triggered a wave of selling pressure and saw their user base shrink within hours. By early 2026, a growing share of the crypto community on X had arrived at a consensus - the mini-app meta was dead.
Not users, but project participants
Six Seven Club, a Telegram-native community behind the $67 mini-app is one of the projects arguing that X’s verdict might have been premature. As evidence, the project is using its growth curve, attracting more than a million users in just two months—including daily active users above 150,000 and weekly active users surpassing 400,000.
As of today, the SIXSEVEN ($67) token is sitting at the summit of Dexscreener’s trending tab, with more trading volume than the next ten tokens combined.
According to data from Coingecko, $67 currently commands a market cap of more than $28 million. The token is omnichain, available for trade on both TON and BSC. However, it's not $67’s top trending position that’s the interesting bit. Anyone can buy virality for a few days. Rather, it’s how the Six Seven Club is experimenting with a different incentive structure in a market that had, until now, solely relied on the point-and-future airdrop structure.
Specifically, Six Seven Club is experimenting with turning incentive-driven users into participants by giving them an economic stake in the project, with the aim of making engagement more durable than in a traditional airdrop model.
Flipping the sequence
Six Seven Club began as a deliberate experiment rather than a reaction to market sentiment. When Pavel Durov laid out his seven steps for TON, the team read it differently than the rest of the market. Mini-apps weren’t exactly dead, just that the playbook used to build them. At the time, the team gave itself 67 days to prove mini-apps could work again.
Subsequently, the team at Six Seven Club built on lessons from prior experience running some of the largest Telegram mini-apps, some of which had reached tens of millions of users before their token economies collapsed. That experience led the team to identify what it sees as a key failure point in the previous cycle: airdrop day.
Users farm points for months in anticipation of a future distribution, with no financial stake in the product itself. When the airdrop lands, converting points to tokens all at once, the rational move for nearly everyone holding a fresh allocation is to sell immediately.
This isn’t failure pertaining to a single project but an incentive design problem. A points-based economy can ultimately incentivize users to leave, as points farmers become potential future sellers once the distribution arrives.
Six Seven’s approach inverts this flawed order. By launching the $67 token early and making it central to the community’s growth, the structure gives token holders a more direct financial incentive to remain engaged with the project.
A participant holding a token has an ongoing financial interest in the project's growth, which can create an incentive to talk about the project publicly, remain active in the community, use the product repeatedly, and refer others, since their own position benefits when the community expands.
A points farmer optimizing for a future claim has comparatively little reason to do any of that before cashing out.
The change in approach is also reflected in the project’s current numbers. Today, the $67 token community has more than 20,000 token holders, including a dedicated 10,000-person holder chat. The $67 token, introduced at a market cap of $2 million, has now expanded by over 16-times, with the holder base expanding rapidly alongside it.
Retention in low-switching-cost environment
Just owning a token doesn’t always necessarily mean sustained engagement. The Telegram mini-app users have quite a penchant for leaving for competing applications in seconds. A live token doesn’t magically fix a stagnant product. As a result, retention becomes particularly important to Six Seven’s model.
Notably, Six Seven attributes much of its user retention to its product cadence. The project’s product suite consists of a chat-based earning feature (Chat2Earn), a tap-based clicker revived as a nostalgic nod to the previous cycle (Tap2Earn), a competitive profile-scoring mechanic (Mog2Earn), structured referral campaigns, and large-scale reward events distributing both the $67 token and GRAM to participants.
Rather than treating product cadence purely as a marketing exercise, Six Seven uses it as part of its community-retention strategy. That makes retention particularly important in a market category with near-zero switching costs. The approach also reflects the team’s previous experience building Telegram mini-apps.
What comes next
Skepticism toward the mini-app category remains high across the market, and Six Seven has taken its share of it. Rather than responding to that noise directly, the team has kept token distribution ongoing and let the rewards structure speak for itself. To date, the project has already distributed more than $50,000 in rewards from its vault.
As for what’s ahead, Six Seven plans to distribute the remaining $67 supply through regular events. This is a stark departure from the usual single large unlocks that tend to reproduce the exact sell-pressure dynamics that have annihilated prior-cycle projects. Six Seven is also eyeing listings based on liquidity depth, instead of chasing exchange-brand visibility.
Whether a live-token, ownership-first model outperforms the points-farming structure over a longer horizon remains to be tested at scale. However, what Six Seven’s growth curve demonstrates is that a mini-app can still scale massively, provided the underlying token stops functioning as an exit for the community and starts functioning as a reason to stay.
Disclaimer: This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.
How Six Seven Club Turned Telegram Holders Into Distribution Instead of Exit Liquidity
Telegram’s mini-app category spent much of the past year being written off. The last airdrop cycle left an array of apps whose token generation event immediately preceded their funeral, as it triggered a wave of selling pressure and saw their user base shrink within hours. By early 2026, a growing share of the crypto community on X had arrived at a consensus - the mini-app meta was dead.
Not users, but project participants
Six Seven Club, a Telegram-native community behind the $67 mini-app is one of the projects arguing that X’s verdict might have been premature. As evidence, the project is using its growth curve, attracting more than a million users in just two months—including daily active users above 150,000 and weekly active users surpassing 400,000.
As of today, the SIXSEVEN ($67) token is sitting at the summit of Dexscreener’s trending tab, with more trading volume than the next ten tokens combined.
According to data from Coingecko, $67 currently commands a market cap of more than $28 million. The token is omnichain, available for trade on both TON and BSC. However, it's not $67’s top trending position that’s the interesting bit. Anyone can buy virality for a few days. Rather, it’s how the Six Seven Club is experimenting with a different incentive structure in a market that had, until now, solely relied on the point-and-future airdrop structure.
Specifically, Six Seven Club is experimenting with turning incentive-driven users into participants by giving them an economic stake in the project, with the aim of making engagement more durable than in a traditional airdrop model.
Flipping the sequence
Six Seven Club began as a deliberate experiment rather than a reaction to market sentiment. When Pavel Durov laid out his seven steps for TON, the team read it differently than the rest of the market. Mini-apps weren’t exactly dead, just that the playbook used to build them. At the time, the team gave itself 67 days to prove mini-apps could work again.
Subsequently, the team at Six Seven Club built on lessons from prior experience running some of the largest Telegram mini-apps, some of which had reached tens of millions of users before their token economies collapsed. That experience led the team to identify what it sees as a key failure point in the previous cycle: airdrop day.
Users farm points for months in anticipation of a future distribution, with no financial stake in the product itself. When the airdrop lands, converting points to tokens all at once, the rational move for nearly everyone holding a fresh allocation is to sell immediately.
This isn’t failure pertaining to a single project but an incentive design problem. A points-based economy can ultimately incentivize users to leave, as points farmers become potential future sellers once the distribution arrives.
Six Seven’s approach inverts this flawed order. By launching the $67 token early and making it central to the community’s growth, the structure gives token holders a more direct financial incentive to remain engaged with the project.
A participant holding a token has an ongoing financial interest in the project's growth, which can create an incentive to talk about the project publicly, remain active in the community, use the product repeatedly, and refer others, since their own position benefits when the community expands.
A points farmer optimizing for a future claim has comparatively little reason to do any of that before cashing out.
The change in approach is also reflected in the project’s current numbers. Today, the $67 token community has more than 20,000 token holders, including a dedicated 10,000-person holder chat. The $67 token, introduced at a market cap of $2 million, has now expanded by over 16-times, with the holder base expanding rapidly alongside it.
Retention in low-switching-cost environment
Just owning a token doesn’t always necessarily mean sustained engagement. The Telegram mini-app users have quite a penchant for leaving for competing applications in seconds. A live token doesn’t magically fix a stagnant product. As a result, retention becomes particularly important to Six Seven’s model.
Notably, Six Seven attributes much of its user retention to its product cadence. The project’s product suite consists of a chat-based earning feature (Chat2Earn), a tap-based clicker revived as a nostalgic nod to the previous cycle (Tap2Earn), a competitive profile-scoring mechanic (Mog2Earn), structured referral campaigns, and large-scale reward events distributing both the $67 token and GRAM to participants.
Rather than treating product cadence purely as a marketing exercise, Six Seven uses it as part of its community-retention strategy. That makes retention particularly important in a market category with near-zero switching costs. The approach also reflects the team’s previous experience building Telegram mini-apps.
What comes next
Skepticism toward the mini-app category remains high across the market, and Six Seven has taken its share of it. Rather than responding to that noise directly, the team has kept token distribution ongoing and let the rewards structure speak for itself. To date, the project has already distributed more than $50,000 in rewards from its vault.
As for what’s ahead, Six Seven plans to distribute the remaining $67 supply through regular events. This is a stark departure from the usual single large unlocks that tend to reproduce the exact sell-pressure dynamics that have annihilated prior-cycle projects. Six Seven is also eyeing listings based on liquidity depth, instead of chasing exchange-brand visibility.
Whether a live-token, ownership-first model outperforms the points-farming structure over a longer horizon remains to be tested at scale. However, what Six Seven’s growth curve demonstrates is that a mini-app can still scale massively, provided the underlying token stops functioning as an exit for the community and starts functioning as a reason to stay.
Disclaimer: This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.
Not users, but project participants
Six Seven Club, a Telegram-native community behind the $67 mini-app is one of the projects arguing that X’s verdict might have been premature. As evidence, the project is using its growth curve, attracting more than a million users in just two months—including daily active users above 150,000 and weekly active users surpassing 400,000.
As of today, the SIXSEVEN ($67) token is sitting at the summit of Dexscreener’s trending tab, with more trading volume than the next ten tokens combined.
According to data from Coingecko, $67 currently commands a market cap of more than $28 million. The token is omnichain, available for trade on both TON and BSC. However, it's not $67’s top trending position that’s the interesting bit. Anyone can buy virality for a few days. Rather, it’s how the Six Seven Club is experimenting with a different incentive structure in a market that had, until now, solely relied on the point-and-future airdrop structure.
Specifically, Six Seven Club is experimenting with turning incentive-driven users into participants by giving them an economic stake in the project, with the aim of making engagement more durable than in a traditional airdrop model.
Flipping the sequence
Six Seven Club began as a deliberate experiment rather than a reaction to market sentiment. When Pavel Durov laid out his seven steps for TON, the team read it differently than the rest of the market. Mini-apps weren’t exactly dead, just that the playbook used to build them. At the time, the team gave itself 67 days to prove mini-apps could work again.
Subsequently, the team at Six Seven Club built on lessons from prior experience running some of the largest Telegram mini-apps, some of which had reached tens of millions of users before their token economies collapsed. That experience led the team to identify what it sees as a key failure point in the previous cycle: airdrop day.
Users farm points for months in anticipation of a future distribution, with no financial stake in the product itself. When the airdrop lands, converting points to tokens all at once, the rational move for nearly everyone holding a fresh allocation is to sell immediately.
This isn’t failure pertaining to a single project but an incentive design problem. A points-based economy can ultimately incentivize users to leave, as points farmers become potential future sellers once the distribution arrives.
Six Seven’s approach inverts this flawed order. By launching the $67 token early and making it central to the community’s growth, the structure gives token holders a more direct financial incentive to remain engaged with the project.
A participant holding a token has an ongoing financial interest in the project's growth, which can create an incentive to talk about the project publicly, remain active in the community, use the product repeatedly, and refer others, since their own position benefits when the community expands.
A points farmer optimizing for a future claim has comparatively little reason to do any of that before cashing out.
The change in approach is also reflected in the project’s current numbers. Today, the $67 token community has more than 20,000 token holders, including a dedicated 10,000-person holder chat. The $67 token, introduced at a market cap of $2 million, has now expanded by over 16-times, with the holder base expanding rapidly alongside it.
Retention in low-switching-cost environment
Just owning a token doesn’t always necessarily mean sustained engagement. The Telegram mini-app users have quite a penchant for leaving for competing applications in seconds. A live token doesn’t magically fix a stagnant product. As a result, retention becomes particularly important to Six Seven’s model.
Notably, Six Seven attributes much of its user retention to its product cadence. The project’s product suite consists of a chat-based earning feature (Chat2Earn), a tap-based clicker revived as a nostalgic nod to the previous cycle (Tap2Earn), a competitive profile-scoring mechanic (Mog2Earn), structured referral campaigns, and large-scale reward events distributing both the $67 token and GRAM to participants.
Rather than treating product cadence purely as a marketing exercise, Six Seven uses it as part of its community-retention strategy. That makes retention particularly important in a market category with near-zero switching costs. The approach also reflects the team’s previous experience building Telegram mini-apps.
What comes next
Skepticism toward the mini-app category remains high across the market, and Six Seven has taken its share of it. Rather than responding to that noise directly, the team has kept token distribution ongoing and let the rewards structure speak for itself. To date, the project has already distributed more than $50,000 in rewards from its vault.
As for what’s ahead, Six Seven plans to distribute the remaining $67 supply through regular events. This is a stark departure from the usual single large unlocks that tend to reproduce the exact sell-pressure dynamics that have annihilated prior-cycle projects. Six Seven is also eyeing listings based on liquidity depth, instead of chasing exchange-brand visibility.
Whether a live-token, ownership-first model outperforms the points-farming structure over a longer horizon remains to be tested at scale. However, what Six Seven’s growth curve demonstrates is that a mini-app can still scale massively, provided the underlying token stops functioning as an exit for the community and starts functioning as a reason to stay.
Disclaimer: This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.
122
翻訳参照
Solana Cuts Inflation Faster After Historic Governance Vote PassesSolana validators passed SGP-0002 on August 28, approving a faster disinflation schedule after the measure received 67.001% support, narrowly clearing the 66.67% supermajority threshold, according to Solana Compass. The result commits the network to a schedule designed to reach its existing 1.5% terminal inflation rate materially sooner.
The vote approved the parameter change set out in SIMD-0550, which doubles Solana's annual disinflation rate from 15% to 30%. The proposal estimates that the revised path will result in approximately 18.9 million fewer SOL emissions over six years than the previous schedule.
SGP-0002 clears the two-thirds threshold by a narrow margin
The final margin was exceptionally tight. Support exceeded the required two-thirds threshold by 0.331 percentage points, based on the reported 67.001% result.
Participation was approximately 60.7%, with about 67% voting in favour, 25.16% against and 7.84% abstaining, CoinDesk reported. Those figures show that the proposal drew substantial opposition even as it achieved the supermajority needed to pass.
30% annual disinflation brings Solana to 1.5% in 2.8 years
Under the approved change, Solana’s annual disinflation rate rises from 15% to 30%, while the terminal inflation rate remains 1.5%. The change therefore affects how quickly the network reaches that endpoint.
The SIMD-0550 proposal estimates that Solana will reach the 1.5% rate in roughly 2.8 years, compared with 5.7 years under the prior schedule—a reduction of about 2.9 years.
SIMD-0550 projects 18.9 million fewer SOL emissions over six years
The most concrete supply implication in the proposal is its six-year issuance estimate. SIMD-0550 projects approximately 18.9 million fewer SOL emissions over that period relative to the current schedule.
The figure is a comparison with the old emissions path, rather than a statement that Solana will stop issuing SOL. Issuance would continue while declining more quickly toward the unchanged 1.5% terminal rate.
Disclaimer: This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.
Solana Cuts Inflation Faster After Historic Governance Vote Passes
Solana validators passed SGP-0002 on August 28, approving a faster disinflation schedule after the measure received 67.001% support, narrowly clearing the 66.67% supermajority threshold, according to Solana Compass. The result commits the network to a schedule designed to reach its existing 1.5% terminal inflation rate materially sooner.
The vote approved the parameter change set out in SIMD-0550, which doubles Solana's annual disinflation rate from 15% to 30%. The proposal estimates that the revised path will result in approximately 18.9 million fewer SOL emissions over six years than the previous schedule.
SGP-0002 clears the two-thirds threshold by a narrow margin
The final margin was exceptionally tight. Support exceeded the required two-thirds threshold by 0.331 percentage points, based on the reported 67.001% result.
Participation was approximately 60.7%, with about 67% voting in favour, 25.16% against and 7.84% abstaining, CoinDesk reported. Those figures show that the proposal drew substantial opposition even as it achieved the supermajority needed to pass.
30% annual disinflation brings Solana to 1.5% in 2.8 years
Under the approved change, Solana’s annual disinflation rate rises from 15% to 30%, while the terminal inflation rate remains 1.5%. The change therefore affects how quickly the network reaches that endpoint.
The SIMD-0550 proposal estimates that Solana will reach the 1.5% rate in roughly 2.8 years, compared with 5.7 years under the prior schedule—a reduction of about 2.9 years.
SIMD-0550 projects 18.9 million fewer SOL emissions over six years
The most concrete supply implication in the proposal is its six-year issuance estimate. SIMD-0550 projects approximately 18.9 million fewer SOL emissions over that period relative to the current schedule.
The figure is a comparison with the old emissions path, rather than a statement that Solana will stop issuing SOL. Issuance would continue while declining more quickly toward the unchanged 1.5% terminal rate.
Disclaimer: This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.
The vote approved the parameter change set out in SIMD-0550, which doubles Solana's annual disinflation rate from 15% to 30%. The proposal estimates that the revised path will result in approximately 18.9 million fewer SOL emissions over six years than the previous schedule.
SGP-0002 clears the two-thirds threshold by a narrow margin
The final margin was exceptionally tight. Support exceeded the required two-thirds threshold by 0.331 percentage points, based on the reported 67.001% result.
Participation was approximately 60.7%, with about 67% voting in favour, 25.16% against and 7.84% abstaining, CoinDesk reported. Those figures show that the proposal drew substantial opposition even as it achieved the supermajority needed to pass.
30% annual disinflation brings Solana to 1.5% in 2.8 years
Under the approved change, Solana’s annual disinflation rate rises from 15% to 30%, while the terminal inflation rate remains 1.5%. The change therefore affects how quickly the network reaches that endpoint.
The SIMD-0550 proposal estimates that Solana will reach the 1.5% rate in roughly 2.8 years, compared with 5.7 years under the prior schedule—a reduction of about 2.9 years.
SIMD-0550 projects 18.9 million fewer SOL emissions over six years
The most concrete supply implication in the proposal is its six-year issuance estimate. SIMD-0550 projects approximately 18.9 million fewer SOL emissions over that period relative to the current schedule.
The figure is a comparison with the old emissions path, rather than a statement that Solana will stop issuing SOL. Issuance would continue while declining more quickly toward the unchanged 1.5% terminal rate.
Disclaimer: This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.
118
翻訳参照
When Should a Blockchain Halt? Fogo Reopens the Decentralization Trade-OffFogo said its blockchain was operating normally. It nevertheless halted mainnet.
In an August 29 compromise involving the Fogo Foundation, an attacker received about 400 million FOGO tokens—4% of the 10 billion-token genesis supply and more than 10% of reported circulating supply, according to The Block. The scale made the incident a mainnet liquidity problem.
Validators paused the chain and upgraded the network to prevent further movement of the assets, but initially disclosed no restart time or technical implementation details. The response showed why technical liveness and economic safety can diverge: ordinary transaction processing may be unacceptable even when a chain could otherwise remain live.
A Foundation compromise became a mainnet liquidity emergency
Fogo’s initial statement located the breach outside the blockchain itself. The Foundation said it had alerted exchanges, law enforcement and forensic specialists, but did not disclose the attack vector or the affected addresses. Those omissions limit what can be concluded about the immediate cause and whether protocol-level weaknesses played any role.
They do not eliminate the operational problem created by the tokens. A holder controlling more than a tenth of reported circulating supply is not simply another account moving through a functioning ledger. The prospect of the tokens being transferred, sold or otherwise distributed can become a threat to market order and to the credibility of the network’s launch economics, irrespective of whether consensus is processing blocks correctly.
Stopping a chain is an unusually direct form of containment because it interrupts all on-chain activity, not merely the suspected attacker’s transactions. Yet it is also a response available to a network whose validators can coordinate quickly enough to make a pause meaningful. Fogo’s decision suggests that, in an emergency involving a large compromised allocation, preserving permissionless continuity did not take precedence over trying to contain the assets.
That is not necessarily evidence of a mismatch between Fogo’s operations and its design. It is more accurately read as a consequence of the trade-off the project has made explicit: a narrower, managed validator system can act decisively when the economic threat lies beyond the narrow question of whether the protocol is still producing valid blocks.
Fogo’s curated validators make intervention part of the security model
Fogo’s architecture does not present validator participation as wholly open-ended. Its documentation describes a curated validator set in which approval sits alongside stake and performance requirements. It also gives the social layer authority to remove validators deemed underperforming or abusive.
That is a significant governance choice. A social layer with validator-removal power necessarily has a role in defining the active security perimeter of the chain. Coordination among that group during a crisis is therefore not an improvised override of a purely permissionless system; it is consistent with an architecture that makes operational judgment part of network security.
The advantage is visible in the response to a fast-moving incident. A validator set that is known, approved and subject to performance oversight can potentially align on an upgrade or a halt more readily than a diffuse global population of independent operators. The same arrangement can also make accountability more legible: there is a defined group expected to keep the network operating and respond when it does not.
But the authority that makes containment feasible also changes what decentralization means in practice. The relevant question is not whether validators are geographically or institutionally separate in some abstract sense. It is whether the people and entities able to operate the network can take coordinated action that changes the experience of every user. On Fogo, the answer appears to be yes.
For users, this is not a semantic dispute. During the pause, the practical property of the chain was not uninterrupted settlement but managed interruption. That may be an acceptable security posture for participants who value coordinated remediation. It is a different proposition from the expectation that a blockchain should continue processing transactions regardless of a Foundation’s compromised holdings.
Low-latency consensus concentrates responsibility in one active zone
Fogo’s performance model helps explain why the operational layer is so central. The protocol markets 40-millisecond block times and roughly 1.3-second finality. Its documentation, however, says that validators in inactive zones do not propose blocks, vote on forks or earn consensus rewards during inactive epochs.
Mainnet documentation listed a single active APAC zone with seven validators. Inactive-zone validators remain connected and can participate in other epochs, but the set actively carrying consensus at a given moment is materially narrower than a globally active validator network.
This is not an incidental implementation detail. Fogo concentrates active consensus responsibility to reduce latency, then rotates geographic zones over time. The design puts the validators closest to the active operating zone at the center of block production and fork choice. It is a purposeful exchange: less globally simultaneous participation in return for the speed associated with local coordination.
The halt therefore should not be assessed in isolation from the performance promise. A system optimized for very low-latency agreement among a limited active group has also built the conditions for swift operational alignment. That does not establish that the seven active validators alone decided or implemented the August response; Fogo initially gave no such technical account. It does show that concentrated active responsibility is embedded in the same model that supports its latency claims.
There is a broader distinction here between validator count and effective control. A network may have validators connected across zones, but its day-to-day decentralization is shaped by who can propose blocks, vote on forks and participate in the live consensus process at a given time. Fogo’s own documentation makes clear that those functions are not continuously shared by all connected validators.
That arrangement can be attractive for applications where execution speed is a central requirement. It also places more weight on the governance, competence and resilience of the currently active set. When a crisis requires a judgment call, the system has fewer active participants through whom that judgment must travel.
Fallback consensus preserves safety, not necessarily economic continuity
Fogo’s protocol includes a different response for a different class of failure. Its whitepaper describes a fallback from ultra-low-latency local consensus to slower global consensus when local-zone operation is degraded. The stated aim is to preserve continuity and safety even if the local mode is impaired.
That mechanism is important, but it should not be confused with the August halt. Fallback consensus addresses an operational deterioration in the network’s consensus environment. A discretionary pause after compromised tokens arrive in an attacker’s possession addresses economic containment. One is a planned continuity mechanism; the other is an intervention based on the consequences of allowing otherwise valid transactions to proceed.
The distinction exposes a limit of technical resilience. A protocol can be engineered to remain safe through connectivity or locality problems, yet still be halted because network operators conclude that continued liveness would worsen a market event. Global fallback can preserve the ability to agree on blocks; it cannot itself resolve who should bear the consequences of a Foundation compromise or whether a large token allocation should remain mobile.
Fogo has already encountered a liveness risk particular to its locality-based architecture. During a testnet incident on August 13, 2025, the network halted at slot 287,501,008 in a zone transition. Its post-mortem attributed the failure to an edge case involving the final leader in one zone and the first validator in the next.
That episode does not demonstrate a flaw in the response to the Foundation compromise, and testnet failures are not equivalent to a mainnet security incident. It does show that rotating locality creates failure modes of its own. The protocol’s global fallback is designed for degraded conditions, but the earlier transition outage illustrates why preserving liveness across zones is not merely a theoretical challenge.
Fogo’s latest pause adds a separate test. The network now has to show not only that it can recover from technical disruption, but also that a curated validator model can contain an economic emergency without leaving users uncertain about the rules, scope and duration of intervention. Its first announcement offered no restart timetable, while the earlier zone-transition outage remains a reminder that speed-oriented consensus still has to earn continuity at the boundaries between its operating modes.
Disclaimer: This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.
When Should a Blockchain Halt? Fogo Reopens the Decentralization Trade-Off
Fogo said its blockchain was operating normally. It nevertheless halted mainnet.
In an August 29 compromise involving the Fogo Foundation, an attacker received about 400 million FOGO tokens—4% of the 10 billion-token genesis supply and more than 10% of reported circulating supply, according to The Block. The scale made the incident a mainnet liquidity problem.
Validators paused the chain and upgraded the network to prevent further movement of the assets, but initially disclosed no restart time or technical implementation details. The response showed why technical liveness and economic safety can diverge: ordinary transaction processing may be unacceptable even when a chain could otherwise remain live.
A Foundation compromise became a mainnet liquidity emergency
Fogo’s initial statement located the breach outside the blockchain itself. The Foundation said it had alerted exchanges, law enforcement and forensic specialists, but did not disclose the attack vector or the affected addresses. Those omissions limit what can be concluded about the immediate cause and whether protocol-level weaknesses played any role.
They do not eliminate the operational problem created by the tokens. A holder controlling more than a tenth of reported circulating supply is not simply another account moving through a functioning ledger. The prospect of the tokens being transferred, sold or otherwise distributed can become a threat to market order and to the credibility of the network’s launch economics, irrespective of whether consensus is processing blocks correctly.
Stopping a chain is an unusually direct form of containment because it interrupts all on-chain activity, not merely the suspected attacker’s transactions. Yet it is also a response available to a network whose validators can coordinate quickly enough to make a pause meaningful. Fogo’s decision suggests that, in an emergency involving a large compromised allocation, preserving permissionless continuity did not take precedence over trying to contain the assets.
That is not necessarily evidence of a mismatch between Fogo’s operations and its design. It is more accurately read as a consequence of the trade-off the project has made explicit: a narrower, managed validator system can act decisively when the economic threat lies beyond the narrow question of whether the protocol is still producing valid blocks.
Fogo’s curated validators make intervention part of the security model
Fogo’s architecture does not present validator participation as wholly open-ended. Its documentation describes a curated validator set in which approval sits alongside stake and performance requirements. It also gives the social layer authority to remove validators deemed underperforming or abusive.
That is a significant governance choice. A social layer with validator-removal power necessarily has a role in defining the active security perimeter of the chain. Coordination among that group during a crisis is therefore not an improvised override of a purely permissionless system; it is consistent with an architecture that makes operational judgment part of network security.
The advantage is visible in the response to a fast-moving incident. A validator set that is known, approved and subject to performance oversight can potentially align on an upgrade or a halt more readily than a diffuse global population of independent operators. The same arrangement can also make accountability more legible: there is a defined group expected to keep the network operating and respond when it does not.
But the authority that makes containment feasible also changes what decentralization means in practice. The relevant question is not whether validators are geographically or institutionally separate in some abstract sense. It is whether the people and entities able to operate the network can take coordinated action that changes the experience of every user. On Fogo, the answer appears to be yes.
For users, this is not a semantic dispute. During the pause, the practical property of the chain was not uninterrupted settlement but managed interruption. That may be an acceptable security posture for participants who value coordinated remediation. It is a different proposition from the expectation that a blockchain should continue processing transactions regardless of a Foundation’s compromised holdings.
Low-latency consensus concentrates responsibility in one active zone
Fogo’s performance model helps explain why the operational layer is so central. The protocol markets 40-millisecond block times and roughly 1.3-second finality. Its documentation, however, says that validators in inactive zones do not propose blocks, vote on forks or earn consensus rewards during inactive epochs.
Mainnet documentation listed a single active APAC zone with seven validators. Inactive-zone validators remain connected and can participate in other epochs, but the set actively carrying consensus at a given moment is materially narrower than a globally active validator network.
This is not an incidental implementation detail. Fogo concentrates active consensus responsibility to reduce latency, then rotates geographic zones over time. The design puts the validators closest to the active operating zone at the center of block production and fork choice. It is a purposeful exchange: less globally simultaneous participation in return for the speed associated with local coordination.
The halt therefore should not be assessed in isolation from the performance promise. A system optimized for very low-latency agreement among a limited active group has also built the conditions for swift operational alignment. That does not establish that the seven active validators alone decided or implemented the August response; Fogo initially gave no such technical account. It does show that concentrated active responsibility is embedded in the same model that supports its latency claims.
There is a broader distinction here between validator count and effective control. A network may have validators connected across zones, but its day-to-day decentralization is shaped by who can propose blocks, vote on forks and participate in the live consensus process at a given time. Fogo’s own documentation makes clear that those functions are not continuously shared by all connected validators.
That arrangement can be attractive for applications where execution speed is a central requirement. It also places more weight on the governance, competence and resilience of the currently active set. When a crisis requires a judgment call, the system has fewer active participants through whom that judgment must travel.
Fallback consensus preserves safety, not necessarily economic continuity
Fogo’s protocol includes a different response for a different class of failure. Its whitepaper describes a fallback from ultra-low-latency local consensus to slower global consensus when local-zone operation is degraded. The stated aim is to preserve continuity and safety even if the local mode is impaired.
That mechanism is important, but it should not be confused with the August halt. Fallback consensus addresses an operational deterioration in the network’s consensus environment. A discretionary pause after compromised tokens arrive in an attacker’s possession addresses economic containment. One is a planned continuity mechanism; the other is an intervention based on the consequences of allowing otherwise valid transactions to proceed.
The distinction exposes a limit of technical resilience. A protocol can be engineered to remain safe through connectivity or locality problems, yet still be halted because network operators conclude that continued liveness would worsen a market event. Global fallback can preserve the ability to agree on blocks; it cannot itself resolve who should bear the consequences of a Foundation compromise or whether a large token allocation should remain mobile.
Fogo has already encountered a liveness risk particular to its locality-based architecture. During a testnet incident on August 13, 2025, the network halted at slot 287,501,008 in a zone transition. Its post-mortem attributed the failure to an edge case involving the final leader in one zone and the first validator in the next.
That episode does not demonstrate a flaw in the response to the Foundation compromise, and testnet failures are not equivalent to a mainnet security incident. It does show that rotating locality creates failure modes of its own. The protocol’s global fallback is designed for degraded conditions, but the earlier transition outage illustrates why preserving liveness across zones is not merely a theoretical challenge.
Fogo’s latest pause adds a separate test. The network now has to show not only that it can recover from technical disruption, but also that a curated validator model can contain an economic emergency without leaving users uncertain about the rules, scope and duration of intervention. Its first announcement offered no restart timetable, while the earlier zone-transition outage remains a reminder that speed-oriented consensus still has to earn continuity at the boundaries between its operating modes.
Disclaimer: This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.
In an August 29 compromise involving the Fogo Foundation, an attacker received about 400 million FOGO tokens—4% of the 10 billion-token genesis supply and more than 10% of reported circulating supply, according to The Block. The scale made the incident a mainnet liquidity problem.
Validators paused the chain and upgraded the network to prevent further movement of the assets, but initially disclosed no restart time or technical implementation details. The response showed why technical liveness and economic safety can diverge: ordinary transaction processing may be unacceptable even when a chain could otherwise remain live.
A Foundation compromise became a mainnet liquidity emergency
Fogo’s initial statement located the breach outside the blockchain itself. The Foundation said it had alerted exchanges, law enforcement and forensic specialists, but did not disclose the attack vector or the affected addresses. Those omissions limit what can be concluded about the immediate cause and whether protocol-level weaknesses played any role.
They do not eliminate the operational problem created by the tokens. A holder controlling more than a tenth of reported circulating supply is not simply another account moving through a functioning ledger. The prospect of the tokens being transferred, sold or otherwise distributed can become a threat to market order and to the credibility of the network’s launch economics, irrespective of whether consensus is processing blocks correctly.
Stopping a chain is an unusually direct form of containment because it interrupts all on-chain activity, not merely the suspected attacker’s transactions. Yet it is also a response available to a network whose validators can coordinate quickly enough to make a pause meaningful. Fogo’s decision suggests that, in an emergency involving a large compromised allocation, preserving permissionless continuity did not take precedence over trying to contain the assets.
That is not necessarily evidence of a mismatch between Fogo’s operations and its design. It is more accurately read as a consequence of the trade-off the project has made explicit: a narrower, managed validator system can act decisively when the economic threat lies beyond the narrow question of whether the protocol is still producing valid blocks.
Fogo’s curated validators make intervention part of the security model
Fogo’s architecture does not present validator participation as wholly open-ended. Its documentation describes a curated validator set in which approval sits alongside stake and performance requirements. It also gives the social layer authority to remove validators deemed underperforming or abusive.
That is a significant governance choice. A social layer with validator-removal power necessarily has a role in defining the active security perimeter of the chain. Coordination among that group during a crisis is therefore not an improvised override of a purely permissionless system; it is consistent with an architecture that makes operational judgment part of network security.
The advantage is visible in the response to a fast-moving incident. A validator set that is known, approved and subject to performance oversight can potentially align on an upgrade or a halt more readily than a diffuse global population of independent operators. The same arrangement can also make accountability more legible: there is a defined group expected to keep the network operating and respond when it does not.
But the authority that makes containment feasible also changes what decentralization means in practice. The relevant question is not whether validators are geographically or institutionally separate in some abstract sense. It is whether the people and entities able to operate the network can take coordinated action that changes the experience of every user. On Fogo, the answer appears to be yes.
For users, this is not a semantic dispute. During the pause, the practical property of the chain was not uninterrupted settlement but managed interruption. That may be an acceptable security posture for participants who value coordinated remediation. It is a different proposition from the expectation that a blockchain should continue processing transactions regardless of a Foundation’s compromised holdings.
Low-latency consensus concentrates responsibility in one active zone
Fogo’s performance model helps explain why the operational layer is so central. The protocol markets 40-millisecond block times and roughly 1.3-second finality. Its documentation, however, says that validators in inactive zones do not propose blocks, vote on forks or earn consensus rewards during inactive epochs.
Mainnet documentation listed a single active APAC zone with seven validators. Inactive-zone validators remain connected and can participate in other epochs, but the set actively carrying consensus at a given moment is materially narrower than a globally active validator network.
This is not an incidental implementation detail. Fogo concentrates active consensus responsibility to reduce latency, then rotates geographic zones over time. The design puts the validators closest to the active operating zone at the center of block production and fork choice. It is a purposeful exchange: less globally simultaneous participation in return for the speed associated with local coordination.
The halt therefore should not be assessed in isolation from the performance promise. A system optimized for very low-latency agreement among a limited active group has also built the conditions for swift operational alignment. That does not establish that the seven active validators alone decided or implemented the August response; Fogo initially gave no such technical account. It does show that concentrated active responsibility is embedded in the same model that supports its latency claims.
There is a broader distinction here between validator count and effective control. A network may have validators connected across zones, but its day-to-day decentralization is shaped by who can propose blocks, vote on forks and participate in the live consensus process at a given time. Fogo’s own documentation makes clear that those functions are not continuously shared by all connected validators.
That arrangement can be attractive for applications where execution speed is a central requirement. It also places more weight on the governance, competence and resilience of the currently active set. When a crisis requires a judgment call, the system has fewer active participants through whom that judgment must travel.
Fallback consensus preserves safety, not necessarily economic continuity
Fogo’s protocol includes a different response for a different class of failure. Its whitepaper describes a fallback from ultra-low-latency local consensus to slower global consensus when local-zone operation is degraded. The stated aim is to preserve continuity and safety even if the local mode is impaired.
That mechanism is important, but it should not be confused with the August halt. Fallback consensus addresses an operational deterioration in the network’s consensus environment. A discretionary pause after compromised tokens arrive in an attacker’s possession addresses economic containment. One is a planned continuity mechanism; the other is an intervention based on the consequences of allowing otherwise valid transactions to proceed.
The distinction exposes a limit of technical resilience. A protocol can be engineered to remain safe through connectivity or locality problems, yet still be halted because network operators conclude that continued liveness would worsen a market event. Global fallback can preserve the ability to agree on blocks; it cannot itself resolve who should bear the consequences of a Foundation compromise or whether a large token allocation should remain mobile.
Fogo has already encountered a liveness risk particular to its locality-based architecture. During a testnet incident on August 13, 2025, the network halted at slot 287,501,008 in a zone transition. Its post-mortem attributed the failure to an edge case involving the final leader in one zone and the first validator in the next.
That episode does not demonstrate a flaw in the response to the Foundation compromise, and testnet failures are not equivalent to a mainnet security incident. It does show that rotating locality creates failure modes of its own. The protocol’s global fallback is designed for degraded conditions, but the earlier transition outage illustrates why preserving liveness across zones is not merely a theoretical challenge.
Fogo’s latest pause adds a separate test. The network now has to show not only that it can recover from technical disruption, but also that a curated validator model can contain an economic emergency without leaving users uncertain about the rules, scope and duration of intervention. Its first announcement offered no restart timetable, while the earlier zone-transition outage remains a reminder that speed-oriented consensus still has to earn continuity at the boundaries between its operating modes.
Disclaimer: This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.
275
SBI、東南アジア向け投資2億7000万ドルでアジャイブに20%出資SBIホールディングスは8月28日、子会社を通じて、インドネシア拠点のアジャイブ・グループに戦略的投資を行ったと発表した。この取引により約20%の持分を確保し、アジャイブは持分法適用の関連会社となった。
アジャイブは投資額が2億7000万ドルに達し、2019年以来の累積資金調達額が5億ドル超に引き上がったと述べた。
SBIは、アジャイブを、従来の金融商品とデジタル資産にまたがるマルチアセット・プラットフォームだと説明した。同社によれば、この提携は、東南アジアを中心としたデジタル資産インフラと取引所ネットワークの開発に向けた取り組みの一環だという。
SBI、東南アジア向け投資2億7000万ドルでアジャイブに20%出資
SBIホールディングスは8月28日、子会社を通じて、インドネシア拠点のアジャイブ・グループに戦略的投資を行ったと発表した。この取引により約20%の持分を確保し、アジャイブは持分法適用の関連会社となった。
アジャイブは投資額が2億7000万ドルに達し、2019年以来の累積資金調達額が5億ドル超に引き上がったと述べた。
SBIは、アジャイブを、従来の金融商品とデジタル資産にまたがるマルチアセット・プラットフォームだと説明した。同社によれば、この提携は、東南アジアを中心としたデジタル資産インフラと取引所ネットワークの開発に向けた取り組みの一環だという。
アジャイブは投資額が2億7000万ドルに達し、2019年以来の累積資金調達額が5億ドル超に引き上がったと述べた。
SBIは、アジャイブを、従来の金融商品とデジタル資産にまたがるマルチアセット・プラットフォームだと説明した。同社によれば、この提携は、東南アジアを中心としたデジタル資産インフラと取引所ネットワークの開発に向けた取り組みの一環だという。
76
アクティブアドレスとホルダー：トークン化市場における採用を読み解くアクティブアドレスは、選定した期間において成功した取引に参加したブロックチェーンのアドレス数で、通常は送信者または受信者として関与します。保有者（ホルダー）は、特定のトークンについて残高がゼロでないアドレスを数えます。前者は時間の経過における観測された活動の指標であり、後者はある資産を保持し続けているアドレスのスナップショットです。
どちらの図も「人数（people count）」を表しているわけではありません。参加者は複数のウォレットを利用できる一方で、取引所・カストディアン・プロトコル上の1つのアドレスは、多くの顧客、資産、または機能に相当し得ます。したがって重要なのは、「採用（adoption）の」数としてどの指標が“唯一の”値なのかではなく、他のオンチェーン証拠と併せて読むことで、それぞれが参加と所有について何を示しているのかです。
アクティブアドレスとホルダー：トークン化市場における採用を読み解く
アクティブアドレスは、選定した期間において成功した取引に参加したブロックチェーンのアドレス数で、通常は送信者または受信者として関与します。保有者（ホルダー）は、特定のトークンについて残高がゼロでないアドレスを数えます。前者は時間の経過における観測された活動の指標であり、後者はある資産を保持し続けているアドレスのスナップショットです。
どちらの図も「人数（people count）」を表しているわけではありません。参加者は複数のウォレットを利用できる一方で、取引所・カストディアン・プロトコル上の1つのアドレスは、多くの顧客、資産、または機能に相当し得ます。したがって重要なのは、「採用（adoption）の」数としてどの指標が“唯一の”値なのかではなく、他のオンチェーン証拠と併せて読むことで、それぞれが参加と所有について何を示しているのかです。
どちらの図も「人数（people count）」を表しているわけではありません。参加者は複数のウォレットを利用できる一方で、取引所・カストディアン・プロトコル上の1つのアドレスは、多くの顧客、資産、または機能に相当し得ます。したがって重要なのは、「採用（adoption）の」数としてどの指標が“唯一の”値なのかではなく、他のオンチェーン証拠と併せて読むことで、それぞれが参加と所有について何を示しているのかです。
40
トークン化株式の移転量はマーケットバリュー（時価）とどう違うかトークン化株式の移転量は、所定の期間においてどれだけの価値が移動したかを示します。一方、時価総額（マーケット・バリュー）は、特定の時点で流通しているトークン化された資産の価値、または場合によっては期間平均の価値を指します。前者はフロー（流量）です。後者はストック（残高）です。数値が似ていることはあっても、同じ質問に答えるものではなく、代替として用いるべきではありません。
その違いは、発行体、プラットフォーム、または市場参加者が、比較的小さい（あるいは大きい）資産価値と並んで、大きなオンチェーンの取引活動（活動量）の数値を報告している場合に重要になります。移転総量が高い場合は、同じトークンをめぐる頻繁な所有権の変更、償還、またはその他の移動が反映されている可能性があります。逆に、移転活動が低いのに時価総額が大きい場合は、保有者がポジションを維持していることを示しているかもしれません。
トークン化株式の移転量はマーケットバリュー（時価）とどう違うか
トークン化株式の移転量は、所定の期間においてどれだけの価値が移動したかを示します。一方、時価総額（マーケット・バリュー）は、特定の時点で流通しているトークン化された資産の価値、または場合によっては期間平均の価値を指します。前者はフロー（流量）です。後者はストック（残高）です。数値が似ていることはあっても、同じ質問に答えるものではなく、代替として用いるべきではありません。
その違いは、発行体、プラットフォーム、または市場参加者が、比較的小さい（あるいは大きい）資産価値と並んで、大きなオンチェーンの取引活動（活動量）の数値を報告している場合に重要になります。移転総量が高い場合は、同じトークンをめぐる頻繁な所有権の変更、償還、またはその他の移動が反映されている可能性があります。逆に、移転活動が低いのに時価総額が大きい場合は、保有者がポジションを維持していることを示しているかもしれません。
その違いは、発行体、プラットフォーム、または市場参加者が、比較的小さい（あるいは大きい）資産価値と並んで、大きなオンチェーンの取引活動（活動量）の数値を報告している場合に重要になります。移転総量が高い場合は、同じトークンをめぐる頻繁な所有権の変更、償還、またはその他の移動が反映されている可能性があります。逆に、移転活動が低いのに時価総額が大きい場合は、保有者がポジションを維持していることを示しているかもしれません。
64
翻訳参照
Why a Patched Blockchain Vulnerability Can Still Matter to Token HoldersThe Cosmos EVM incident shows why closing an exploit route is not the same as restoring holders’ prior economic position. Attackers exchanged about $2.87 million of stolen assets on decentralised exchanges and sold an estimated $2.85 million through centralised exchanges, according to the Cosmos Security post-mortem.
By the time the affected software was patched, those transactions could not be reversed and the token’s prior liquidity conditions could not be restored. A patch may therefore succeed technically while holders still face sell-side flow, pooled-staking losses, exposure beyond realised theft, or the burden of moving to a replacement environment. That distinction does not establish that every exploit causes a measurable price move or that this patch failed.
Cosmos EVM’s flaw released vested tokens rather than minting new ones
The Cosmos EVM vulnerability affected production chains running versions below v0.6.2 or v0.7.2. It arose from inconsistent token-balance accounting between Cosmos EVM and the Cosmos SDK, allowing attackers to extract legitimate tokens from vesting accounts without increasing total token supply.
That last point matters. A supply-creation bug and an accounting exploit involving restricted, already-issued tokens are not the same event. No additional units need to be minted for holders to confront an effective change in the assets available for sale. Tokens subject to vesting are, by design, not meant to have the same immediate market availability as unrestricted balances. If they can be extracted and traded early, the relevant economic change is in accessible supply, not necessarily headline supply.
The post-mortem identified six affected networks. Its estimates of roughly $2.87 million exchanged on DEXs and $2.85 million sold through CEXs put a concrete scale on the route from an accounting discrepancy to market activity. For token holders, the concern is less whether the protocol’s maximum or total supply fields changed than whether assets that should have remained constrained became available to counterparties across trading venues.
It also explains why “no new tokens were minted” can be an incomplete reassurance. The phrase correctly describes one limit of the incident. It does not establish that the timing of circulation was unchanged, that victims were made whole, or that liquidity was unaffected by assets released from accounts intended to vest over time.
Public disclosure turned patch deployment into a race across six networks
A fix in a repository does not protect every production chain using the affected code. Each operator must identify its exposure and deploy a protected version; across six networks, practical protection depended on that execution as well as on corrected code.
The Cosmos post-mortem says a public pull request disclosed the vulnerability and a detailed exploitation path before the first known incident, although maintainers had prepared a fix. The disclosure left affected production chains facing a deployment task after the route had become visible.
For holders, “patched” can therefore describe four distinct events: discovery of the flaw, availability of corrected software, deployment by affected chains, and containment of already-extracted assets. Those events can occur at different times, and a patch announcement alone does not establish which chains deployed the fix, whether funds were extracted, whether attackers converted proceeds, or whether realized losses and subsequent market sales were addressed.
A patched exploit can leave holders with losses, diluted staking pools or migration work
SubQuery Network reported that five transactions drained 382,433,441 SQT tokens, worth approximately $134,000 at the time, from pooled staking balances, 272 individual staker and delegator wallets, deployment boosters and the treasury. The project said it restored contract addresses and added onlyOwner controls, according to its incident report. The fix addressed the disclosed access-control weakness, but the listed pooled balances and participant wallets remained among the sources drained.
The incident illustrates why residual costs may not appear as an immediately tradeable balance. Delegators can be exposed through shared contracts and pools, and treasury stakeholders through resources intended for development or operations, so the consequences can be distributed across collective infrastructure.
Zilliqa reported 6,772 exposed accounts, but said 51 were known to have been drained, involving 683,130,969.66 ZIL in proven theft. It decided to retire the legacy environment and require migration to Zilliqa EVM, according to its incident status page. Holders who were not drained may still face access, compatibility and user-action burdens during that transition.
Rapid containment does not establish that the security surface is closed
The speed of a response remains important. Hyperbridge said an attacker forged a proof using an out-of-bounds leaf and drained its Token Gateway. The gateway was paused within hours, and a permanent patch was deployed in under 72 hours.
The containment steps addressed the specific route used in the incident, but the same Hyperbridge post-mortem said follow-up audits identified 14 additional vulnerabilities, including one critical issue. Those findings do not establish that the issues were exploited; they do show why a successful response to one observed attack should not automatically be read as a complete assessment of the surrounding security surface.
For token holders, that difference affects how they interpret recovery narratives. A paused gateway can halt a drain. A permanent patch can remove the identified weakness. Subsequent audit findings may nevertheless require further upgrades, governance decisions or operational changes before confidence in the wider system can be reassessed.
There is no single holder-impact metric that captures this. An exploit’s direct loss, the market treatment of extracted assets, the dependence of stakers on pooled contracts, and the quality of post-incident review all describe different parts of the exposure. A narrow technical question—was the bug fixed?—therefore cannot carry the whole economic analysis.
Bug bounties price the value of prevention against residual holder costs
The value of finding a flaw before exploitation is clearest when set against the costs that cannot be cleanly patched afterwards. Ethereum’s bug-bounty programme covers execution- and consensus-layer client bugs, including specification non-compliance, denial-of-service vulnerabilities and issues capable of causing irreparable consensus splits. It offers rewards of up to $1 million.
That ceiling does not place a universal price on every blockchain vulnerability. It does indicate the economic importance Ethereum assigns to reporting severe defects before they can cause irreversible disruption. A bounty payment is comparatively contained: it can avoid stolen assets entering DEX or CEX markets, pooled stakes being drained, or users being required to move from a retired environment.
The Cosmos case supplies the most direct comparison. Once assets extracted from vesting accounts had been exchanged or sold, a corrected release could prevent repetition of the accounting exploit but could not unwind the reported trading activity. The same basic asymmetry applies to the SubQuery and Zilliqa examples: controls can be added and environments can be retired, but the remedial work begins after holders, delegates, treasuries or users have already absorbed some form of risk.
Security spending is therefore not only about preventing a protocol from going offline. It is also an attempt to preserve the conditions around a token that code changes cannot recreate after the fact: scheduled restrictions on assets, custody integrity, stable participation arrangements and the ability for holders to remain in an ecosystem without a forced recovery process.
Ethereum’s bug-bounty programme frames that preventive logic explicitly through rewards of up to $1 million. The Cosmos post-mortem shows the other side of the equation: even where total supply does not increase, assets released from vesting accounts can still be exchanged and sold before the patch has finished doing its work.
Disclaimer: This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.
Why a Patched Blockchain Vulnerability Can Still Matter to Token Holders
The Cosmos EVM incident shows why closing an exploit route is not the same as restoring holders’ prior economic position. Attackers exchanged about $2.87 million of stolen assets on decentralised exchanges and sold an estimated $2.85 million through centralised exchanges, according to the Cosmos Security post-mortem.
By the time the affected software was patched, those transactions could not be reversed and the token’s prior liquidity conditions could not be restored. A patch may therefore succeed technically while holders still face sell-side flow, pooled-staking losses, exposure beyond realised theft, or the burden of moving to a replacement environment. That distinction does not establish that every exploit causes a measurable price move or that this patch failed.
Cosmos EVM’s flaw released vested tokens rather than minting new ones
The Cosmos EVM vulnerability affected production chains running versions below v0.6.2 or v0.7.2. It arose from inconsistent token-balance accounting between Cosmos EVM and the Cosmos SDK, allowing attackers to extract legitimate tokens from vesting accounts without increasing total token supply.
That last point matters. A supply-creation bug and an accounting exploit involving restricted, already-issued tokens are not the same event. No additional units need to be minted for holders to confront an effective change in the assets available for sale. Tokens subject to vesting are, by design, not meant to have the same immediate market availability as unrestricted balances. If they can be extracted and traded early, the relevant economic change is in accessible supply, not necessarily headline supply.
The post-mortem identified six affected networks. Its estimates of roughly $2.87 million exchanged on DEXs and $2.85 million sold through CEXs put a concrete scale on the route from an accounting discrepancy to market activity. For token holders, the concern is less whether the protocol’s maximum or total supply fields changed than whether assets that should have remained constrained became available to counterparties across trading venues.
It also explains why “no new tokens were minted” can be an incomplete reassurance. The phrase correctly describes one limit of the incident. It does not establish that the timing of circulation was unchanged, that victims were made whole, or that liquidity was unaffected by assets released from accounts intended to vest over time.
Public disclosure turned patch deployment into a race across six networks
A fix in a repository does not protect every production chain using the affected code. Each operator must identify its exposure and deploy a protected version; across six networks, practical protection depended on that execution as well as on corrected code.
The Cosmos post-mortem says a public pull request disclosed the vulnerability and a detailed exploitation path before the first known incident, although maintainers had prepared a fix. The disclosure left affected production chains facing a deployment task after the route had become visible.
For holders, “patched” can therefore describe four distinct events: discovery of the flaw, availability of corrected software, deployment by affected chains, and containment of already-extracted assets. Those events can occur at different times, and a patch announcement alone does not establish which chains deployed the fix, whether funds were extracted, whether attackers converted proceeds, or whether realized losses and subsequent market sales were addressed.
A patched exploit can leave holders with losses, diluted staking pools or migration work
SubQuery Network reported that five transactions drained 382,433,441 SQT tokens, worth approximately $134,000 at the time, from pooled staking balances, 272 individual staker and delegator wallets, deployment boosters and the treasury. The project said it restored contract addresses and added onlyOwner controls, according to its incident report. The fix addressed the disclosed access-control weakness, but the listed pooled balances and participant wallets remained among the sources drained.
The incident illustrates why residual costs may not appear as an immediately tradeable balance. Delegators can be exposed through shared contracts and pools, and treasury stakeholders through resources intended for development or operations, so the consequences can be distributed across collective infrastructure.
Zilliqa reported 6,772 exposed accounts, but said 51 were known to have been drained, involving 683,130,969.66 ZIL in proven theft. It decided to retire the legacy environment and require migration to Zilliqa EVM, according to its incident status page. Holders who were not drained may still face access, compatibility and user-action burdens during that transition.
Rapid containment does not establish that the security surface is closed
The speed of a response remains important. Hyperbridge said an attacker forged a proof using an out-of-bounds leaf and drained its Token Gateway. The gateway was paused within hours, and a permanent patch was deployed in under 72 hours.
The containment steps addressed the specific route used in the incident, but the same Hyperbridge post-mortem said follow-up audits identified 14 additional vulnerabilities, including one critical issue. Those findings do not establish that the issues were exploited; they do show why a successful response to one observed attack should not automatically be read as a complete assessment of the surrounding security surface.
For token holders, that difference affects how they interpret recovery narratives. A paused gateway can halt a drain. A permanent patch can remove the identified weakness. Subsequent audit findings may nevertheless require further upgrades, governance decisions or operational changes before confidence in the wider system can be reassessed.
There is no single holder-impact metric that captures this. An exploit’s direct loss, the market treatment of extracted assets, the dependence of stakers on pooled contracts, and the quality of post-incident review all describe different parts of the exposure. A narrow technical question—was the bug fixed?—therefore cannot carry the whole economic analysis.
Bug bounties price the value of prevention against residual holder costs
The value of finding a flaw before exploitation is clearest when set against the costs that cannot be cleanly patched afterwards. Ethereum’s bug-bounty programme covers execution- and consensus-layer client bugs, including specification non-compliance, denial-of-service vulnerabilities and issues capable of causing irreparable consensus splits. It offers rewards of up to $1 million.
That ceiling does not place a universal price on every blockchain vulnerability. It does indicate the economic importance Ethereum assigns to reporting severe defects before they can cause irreversible disruption. A bounty payment is comparatively contained: it can avoid stolen assets entering DEX or CEX markets, pooled stakes being drained, or users being required to move from a retired environment.
The Cosmos case supplies the most direct comparison. Once assets extracted from vesting accounts had been exchanged or sold, a corrected release could prevent repetition of the accounting exploit but could not unwind the reported trading activity. The same basic asymmetry applies to the SubQuery and Zilliqa examples: controls can be added and environments can be retired, but the remedial work begins after holders, delegates, treasuries or users have already absorbed some form of risk.
Security spending is therefore not only about preventing a protocol from going offline. It is also an attempt to preserve the conditions around a token that code changes cannot recreate after the fact: scheduled restrictions on assets, custody integrity, stable participation arrangements and the ability for holders to remain in an ecosystem without a forced recovery process.
Ethereum’s bug-bounty programme frames that preventive logic explicitly through rewards of up to $1 million. The Cosmos post-mortem shows the other side of the equation: even where total supply does not increase, assets released from vesting accounts can still be exchanged and sold before the patch has finished doing its work.
Disclaimer: This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.
By the time the affected software was patched, those transactions could not be reversed and the token’s prior liquidity conditions could not be restored. A patch may therefore succeed technically while holders still face sell-side flow, pooled-staking losses, exposure beyond realised theft, or the burden of moving to a replacement environment. That distinction does not establish that every exploit causes a measurable price move or that this patch failed.
Cosmos EVM’s flaw released vested tokens rather than minting new ones
The Cosmos EVM vulnerability affected production chains running versions below v0.6.2 or v0.7.2. It arose from inconsistent token-balance accounting between Cosmos EVM and the Cosmos SDK, allowing attackers to extract legitimate tokens from vesting accounts without increasing total token supply.
That last point matters. A supply-creation bug and an accounting exploit involving restricted, already-issued tokens are not the same event. No additional units need to be minted for holders to confront an effective change in the assets available for sale. Tokens subject to vesting are, by design, not meant to have the same immediate market availability as unrestricted balances. If they can be extracted and traded early, the relevant economic change is in accessible supply, not necessarily headline supply.
The post-mortem identified six affected networks. Its estimates of roughly $2.87 million exchanged on DEXs and $2.85 million sold through CEXs put a concrete scale on the route from an accounting discrepancy to market activity. For token holders, the concern is less whether the protocol’s maximum or total supply fields changed than whether assets that should have remained constrained became available to counterparties across trading venues.
It also explains why “no new tokens were minted” can be an incomplete reassurance. The phrase correctly describes one limit of the incident. It does not establish that the timing of circulation was unchanged, that victims were made whole, or that liquidity was unaffected by assets released from accounts intended to vest over time.
Public disclosure turned patch deployment into a race across six networks
A fix in a repository does not protect every production chain using the affected code. Each operator must identify its exposure and deploy a protected version; across six networks, practical protection depended on that execution as well as on corrected code.
The Cosmos post-mortem says a public pull request disclosed the vulnerability and a detailed exploitation path before the first known incident, although maintainers had prepared a fix. The disclosure left affected production chains facing a deployment task after the route had become visible.
For holders, “patched” can therefore describe four distinct events: discovery of the flaw, availability of corrected software, deployment by affected chains, and containment of already-extracted assets. Those events can occur at different times, and a patch announcement alone does not establish which chains deployed the fix, whether funds were extracted, whether attackers converted proceeds, or whether realized losses and subsequent market sales were addressed.
A patched exploit can leave holders with losses, diluted staking pools or migration work
SubQuery Network reported that five transactions drained 382,433,441 SQT tokens, worth approximately $134,000 at the time, from pooled staking balances, 272 individual staker and delegator wallets, deployment boosters and the treasury. The project said it restored contract addresses and added onlyOwner controls, according to its incident report. The fix addressed the disclosed access-control weakness, but the listed pooled balances and participant wallets remained among the sources drained.
The incident illustrates why residual costs may not appear as an immediately tradeable balance. Delegators can be exposed through shared contracts and pools, and treasury stakeholders through resources intended for development or operations, so the consequences can be distributed across collective infrastructure.
Zilliqa reported 6,772 exposed accounts, but said 51 were known to have been drained, involving 683,130,969.66 ZIL in proven theft. It decided to retire the legacy environment and require migration to Zilliqa EVM, according to its incident status page. Holders who were not drained may still face access, compatibility and user-action burdens during that transition.
Rapid containment does not establish that the security surface is closed
The speed of a response remains important. Hyperbridge said an attacker forged a proof using an out-of-bounds leaf and drained its Token Gateway. The gateway was paused within hours, and a permanent patch was deployed in under 72 hours.
The containment steps addressed the specific route used in the incident, but the same Hyperbridge post-mortem said follow-up audits identified 14 additional vulnerabilities, including one critical issue. Those findings do not establish that the issues were exploited; they do show why a successful response to one observed attack should not automatically be read as a complete assessment of the surrounding security surface.
For token holders, that difference affects how they interpret recovery narratives. A paused gateway can halt a drain. A permanent patch can remove the identified weakness. Subsequent audit findings may nevertheless require further upgrades, governance decisions or operational changes before confidence in the wider system can be reassessed.
There is no single holder-impact metric that captures this. An exploit’s direct loss, the market treatment of extracted assets, the dependence of stakers on pooled contracts, and the quality of post-incident review all describe different parts of the exposure. A narrow technical question—was the bug fixed?—therefore cannot carry the whole economic analysis.
Bug bounties price the value of prevention against residual holder costs
The value of finding a flaw before exploitation is clearest when set against the costs that cannot be cleanly patched afterwards. Ethereum’s bug-bounty programme covers execution- and consensus-layer client bugs, including specification non-compliance, denial-of-service vulnerabilities and issues capable of causing irreparable consensus splits. It offers rewards of up to $1 million.
That ceiling does not place a universal price on every blockchain vulnerability. It does indicate the economic importance Ethereum assigns to reporting severe defects before they can cause irreversible disruption. A bounty payment is comparatively contained: it can avoid stolen assets entering DEX or CEX markets, pooled stakes being drained, or users being required to move from a retired environment.
The Cosmos case supplies the most direct comparison. Once assets extracted from vesting accounts had been exchanged or sold, a corrected release could prevent repetition of the accounting exploit but could not unwind the reported trading activity. The same basic asymmetry applies to the SubQuery and Zilliqa examples: controls can be added and environments can be retired, but the remedial work begins after holders, delegates, treasuries or users have already absorbed some form of risk.
Security spending is therefore not only about preventing a protocol from going offline. It is also an attempt to preserve the conditions around a token that code changes cannot recreate after the fact: scheduled restrictions on assets, custody integrity, stable participation arrangements and the ability for holders to remain in an ecosystem without a forced recovery process.
Ethereum’s bug-bounty programme frames that preventive logic explicitly through rewards of up to $1 million. The Cosmos post-mortem shows the other side of the equation: even where total supply does not increase, assets released from vesting accounts can still be exchanged and sold before the patch has finished doing its work.
Disclaimer: This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.
1
252
Validator Resource Exhaustion: ブロックチェーン停止の背後にある静かなリスクバリデータのリソース枯渇とは、ブロックチェーンのバリデータが、コンセンサス作業を期限内に完了するために必要な計算能力、メモリ、ストレージ、OS（オペレーティングシステム）能力、またはネットワークスループットが足りなくなった状態を指します。ノードは稼働していて到達可能であっても、アテステーション、投票、またはブロック提案に必要な情報を検証・保存・伝播するには遅れすぎている可能性があります。
この違いは重要です。明確なクラッシュは判別しやすい一方で、生きているのに遅れているノードは、静かに最初にライブネス（稼働性）を失ってしまうことがあります。ストレージが遅い、または帯域が制約されているとチェーンの最新位置（チェーン先端）より遅れてしまい、さらに伝播が遅れると、Ethereum.orgのノードに関するガイダンスによれば、遅延したり見逃したアテステーションや提案につながる可能性があります。規模が大きくなると、十分に多くの遅れた参加者がいることで、ネットワークが次に合意された状態へ収束するのが難しくなることがあります。
Validator Resource Exhaustion: ブロックチェーン停止の背後にある静かなリスク
バリデータのリソース枯渇とは、ブロックチェーンのバリデータが、コンセンサス作業を期限内に完了するために必要な計算能力、メモリ、ストレージ、OS（オペレーティングシステム）能力、またはネットワークスループットが足りなくなった状態を指します。ノードは稼働していて到達可能であっても、アテステーション、投票、またはブロック提案に必要な情報を検証・保存・伝播するには遅れすぎている可能性があります。
この違いは重要です。明確なクラッシュは判別しやすい一方で、生きているのに遅れているノードは、静かに最初にライブネス（稼働性）を失ってしまうことがあります。ストレージが遅い、または帯域が制約されているとチェーンの最新位置（チェーン先端）より遅れてしまい、さらに伝播が遅れると、Ethereum.orgのノードに関するガイダンスによれば、遅延したり見逃したアテステーションや提案につながる可能性があります。規模が大きくなると、十分に多くの遅れた参加者がいることで、ネットワークが次に合意された状態へ収束するのが難しくなることがあります。
この違いは重要です。明確なクラッシュは判別しやすい一方で、生きているのに遅れているノードは、静かに最初にライブネス（稼働性）を失ってしまうことがあります。ストレージが遅い、または帯域が制約されているとチェーンの最新位置（チェーン先端）より遅れてしまい、さらに伝播が遅れると、Ethereum.orgのノードに関するガイダンスによれば、遅延したり見逃したアテステーションや提案につながる可能性があります。規模が大きくなると、十分に多くの遅れた参加者がいることで、ネットワークが次に合意された状態へ収束するのが難しくなることがあります。
47
確認済み
カリシのインサイダー取引事件、17万2000ドルのCFTC制裁で決着米国商品先物取引委員会（CFTC）は8月28日、ホワイトハウスの元技術顧問でテレプロンプターの運用担当だったガブリエル・ペレスに対し、17万2539.02ドルの支払いを命じ、ドナルド・トランプ大統領の演説に連動したカリシ（Kalshi）契約に関する取引を理由に、3年間の取引を禁じた。
支払いの内訳は、没収された利益10万7539.02ドルと、6万5000ドルの民事上の金銭的制裁金であると、CFTCの発表によるものです。この命令は、同委員会がペレスに対して行っていた措置を解決するもので、ペレスは発言に関する機密の素材にアクセスした後、実際に話されることになる語句やフレーズに紐づいた契約での取引を行っていました。
カリシのインサイダー取引事件、17万2000ドルのCFTC制裁で決着
米国商品先物取引委員会（CFTC）は8月28日、ホワイトハウスの元技術顧問でテレプロンプターの運用担当だったガブリエル・ペレスに対し、17万2539.02ドルの支払いを命じ、ドナルド・トランプ大統領の演説に連動したカリシ（Kalshi）契約に関する取引を理由に、3年間の取引を禁じた。
支払いの内訳は、没収された利益10万7539.02ドルと、6万5000ドルの民事上の金銭的制裁金であると、CFTCの発表によるものです。この命令は、同委員会がペレスに対して行っていた措置を解決するもので、ペレスは発言に関する機密の素材にアクセスした後、実際に話されることになる語句やフレーズに紐づいた契約での取引を行っていました。
支払いの内訳は、没収された利益10万7539.02ドルと、6万5000ドルの民事上の金銭的制裁金であると、CFTCの発表によるものです。この命令は、同委員会がペレスに対して行っていた措置を解決するもので、ペレスは発言に関する機密の素材にアクセスした後、実際に話されることになる語句やフレーズに紐づいた契約での取引を行っていました。
2
123
StellarのRWA価値、2026年に360%上昇し約40億ドルに接近ステラのトークン化された実世界資産（RWA）価値は、8月29日時点で39.96億ドルに到達した。昨年末の8億6880万ドルから2026年にかけて約360%上昇したという。今回の数値はネットワークが40億ドルの節目をわずかに下回っていることを示しており、その後は今年中に報告された10億ドル規模のRWA達成が急速に続いた流れを反映している。
この合計は、CointelegraphがDune AnalyticsとStellarのデータとして引用したものに基づく。これはステラのネットワーク上でのトークン化された実世界資産を測るものであり、ステーブルコインの送金活動や、より広範なステラの利用状況を示す指標ではない。
StellarのRWA価値、2026年に360%上昇し約40億ドルに接近
ステラのトークン化された実世界資産（RWA）価値は、8月29日時点で39.96億ドルに到達した。昨年末の8億6880万ドルから2026年にかけて約360%上昇したという。今回の数値はネットワークが40億ドルの節目をわずかに下回っていることを示しており、その後は今年中に報告された10億ドル規模のRWA達成が急速に続いた流れを反映している。
この合計は、CointelegraphがDune AnalyticsとStellarのデータとして引用したものに基づく。これはステラのネットワーク上でのトークン化された実世界資産を測るものであり、ステーブルコインの送金活動や、より広範なステラの利用状況を示す指標ではない。
この合計は、CointelegraphがDune AnalyticsとStellarのデータとして引用したものに基づく。これはステラのネットワーク上でのトークン化された実世界資産を測るものであり、ステーブルコインの送金活動や、より広範なステラの利用状況を示す指標ではない。
140
グローバル株式ファンド、流入13週連続の後に58.7Bドル失う2026年8月26日に終了した週で、世界株式ファンドは58.7億ドルの資金流出（引き出し）を記録し、13週間にわたる資金流入に終止符を打った。ロイターのデータ（Investing.com掲載）によると、これは2026年5月20日以来初めての週次の流出であり、3か月超に及ぶ継続的な買い支えの後に転換が起きた点で注目に値する。
今回の大きな資金流出は、株式からの一様な後退を意味するものではなかった。同じ報告週において、資金フローは地域によって大きく分かれ、テクノロジーおよび貴金属ファンドは引き続き新たな資金を集めた。
グローバル株式ファンド、流入13週連続の後に58.7Bドル失う
2026年8月26日に終了した週で、世界株式ファンドは58.7億ドルの資金流出（引き出し）を記録し、13週間にわたる資金流入に終止符を打った。ロイターのデータ（Investing.com掲載）によると、これは2026年5月20日以来初めての週次の流出であり、3か月超に及ぶ継続的な買い支えの後に転換が起きた点で注目に値する。
今回の大きな資金流出は、株式からの一様な後退を意味するものではなかった。同じ報告週において、資金フローは地域によって大きく分かれ、テクノロジーおよび貴金属ファンドは引き続き新たな資金を集めた。
今回の大きな資金流出は、株式からの一様な後退を意味するものではなかった。同じ報告週において、資金フローは地域によって大きく分かれ、テクノロジーおよび貴金属ファンドは引き続き新たな資金を集めた。
1
105
ゴールドおよび貴金属ファンドが42.1億ドルを集める、6カ月ぶりの高水準LSEG Lipperのデータによると、ゴールドおよびその他の貴金属ファンドは、2026年8月26日までの週に純流入が42.1億ドルとなり、6カ月ぶりの高水準を記録した。同期間に投資家は、世界の株式ファンドから58.7億ドルを引き揚げており、5月20日以来の初めての週次流出で、13週間に及ぶ資金流入の連続が終了した。これらの数字は異なるファンド区分を対象としているため、それ自体では、株式から流出した資金が直接的に貴金属へ振り向けられたことを示すものではない。
データ・スナップショット
ゴールドおよびその他の貴金属ファンドへの純流入（期間：直近、4.21十億ドル—6カ月ぶり高水準、週次：8月26日まで、2026-08-26、Reuters via Investing.com）—グローバル株式ファンドからの純流出（5.87十億ドル—5月20日以来の初めての週次流出、週次：8月26日まで、2026-08-26、Reuters via Investing.com）—米国株式ファンドからの純売上（22.33十億ドル——8月26日までの週、2026-08-26、Reuters via Investing.com）—テクノロジーファンドへの流入（3.2十億ドル——8月26日までの週、2026-08-26、Reuters via Investing.com）—メタル・鉱業ファンドへの流入（489百万ドル——8月26日までの週、2026-08-26、Reuters via Investing.com）—エネルギーファンドからの流出（313百万ドル—2週連続の週次流出、週次：8月26日まで、2026-08-26、Reuters via Investing.com）
ゴールドおよび貴金属ファンドが42.1億ドルを集める、6カ月ぶりの高水準
LSEG Lipperのデータによると、ゴールドおよびその他の貴金属ファンドは、2026年8月26日までの週に純流入が42.1億ドルとなり、6カ月ぶりの高水準を記録した。同期間に投資家は、世界の株式ファンドから58.7億ドルを引き揚げており、5月20日以来の初めての週次流出で、13週間に及ぶ資金流入の連続が終了した。これらの数字は異なるファンド区分を対象としているため、それ自体では、株式から流出した資金が直接的に貴金属へ振り向けられたことを示すものではない。
データ・スナップショット
ゴールドおよびその他の貴金属ファンドへの純流入（期間：直近、4.21十億ドル—6カ月ぶり高水準、週次：8月26日まで、2026-08-26、Reuters via Investing.com）—グローバル株式ファンドからの純流出（5.87十億ドル—5月20日以来の初めての週次流出、週次：8月26日まで、2026-08-26、Reuters via Investing.com）—米国株式ファンドからの純売上（22.33十億ドル——8月26日までの週、2026-08-26、Reuters via Investing.com）—テクノロジーファンドへの流入（3.2十億ドル——8月26日までの週、2026-08-26、Reuters via Investing.com）—メタル・鉱業ファンドへの流入（489百万ドル——8月26日までの週、2026-08-26、Reuters via Investing.com）—エネルギーファンドからの流出（313百万ドル—2週連続の週次流出、週次：8月26日まで、2026-08-26、Reuters via Investing.com）
データ・スナップショット
ゴールドおよびその他の貴金属ファンドへの純流入（期間：直近、4.21十億ドル—6カ月ぶり高水準、週次：8月26日まで、2026-08-26、Reuters via Investing.com）—グローバル株式ファンドからの純流出（5.87十億ドル—5月20日以来の初めての週次流出、週次：8月26日まで、2026-08-26、Reuters via Investing.com）—米国株式ファンドからの純売上（22.33十億ドル——8月26日までの週、2026-08-26、Reuters via Investing.com）—テクノロジーファンドへの流入（3.2十億ドル——8月26日までの週、2026-08-26、Reuters via Investing.com）—メタル・鉱業ファンドへの流入（489百万ドル——8月26日までの週、2026-08-26、Reuters via Investing.com）—エネルギーファンドからの流出（313百万ドル—2週連続の週次流出、週次：8月26日まで、2026-08-26、Reuters via Investing.com）
1
1
263
$5.7Mの6チェーン攻撃を引き起こしたCosmos EVMのバグは、あまりに早い段階で無害と判断されていたCosmos Labsは、4月に同社のバグバウンティ・プログラムを通じて報告された重大なCosmos EVMの脆弱性について、生産ネットワークへの影響がないと誤って判断されたと述べた。攻撃者は2026年8月20日から8月25日までの間に6つのチェーンでこの脆弱性を悪用した。
この活動は分散型取引所を通じて約287万ドル移動し、さらに中央集権型取引所を通じて約285万ドル移動したと、Cosmos Securityの事後検証投稿で明らかにされた。
この事件は、最初の報告と、最初に判明した攻撃の直前に影響を受けたブランチへリリースが到達するまでの数カ月にわたるギャップを明らかにした。Cosmos Labsは、初期テストで生産チェーンが安全だと分かったためサイレント・パッチの手順を用いたと説明した。リリースには、脆弱性に特化した告知は含まれていなかった。
$5.7Mの6チェーン攻撃を引き起こしたCosmos EVMのバグは、あまりに早い段階で無害と判断されていた
Cosmos Labsは、4月に同社のバグバウンティ・プログラムを通じて報告された重大なCosmos EVMの脆弱性について、生産ネットワークへの影響がないと誤って判断されたと述べた。攻撃者は2026年8月20日から8月25日までの間に6つのチェーンでこの脆弱性を悪用した。
この活動は分散型取引所を通じて約287万ドル移動し、さらに中央集権型取引所を通じて約285万ドル移動したと、Cosmos Securityの事後検証投稿で明らかにされた。
この事件は、最初の報告と、最初に判明した攻撃の直前に影響を受けたブランチへリリースが到達するまでの数カ月にわたるギャップを明らかにした。Cosmos Labsは、初期テストで生産チェーンが安全だと分かったためサイレント・パッチの手順を用いたと説明した。リリースには、脆弱性に特化した告知は含まれていなかった。
この活動は分散型取引所を通じて約287万ドル移動し、さらに中央集権型取引所を通じて約285万ドル移動したと、Cosmos Securityの事後検証投稿で明らかにされた。
この事件は、最初の報告と、最初に判明した攻撃の直前に影響を受けたブランチへリリースが到達するまでの数カ月にわたるギャップを明らかにした。Cosmos Labsは、初期テストで生産チェーンが安全だと分かったためサイレント・パッチの手順を用いたと説明した。リリースには、脆弱性に特化した告知は含まれていなかった。
616
カリフォルニア、政治家向けのミームコイン禁止を知事ガビン・ニューサムに送付カリフォルニア州上院は、8月26日にデジタル・アセット：ミームコイン法案であるAB 2409を賛成40、反対0で可決し、さらに下院が上院修正案に賛成78、反対0で同意して同法案を知事ガビン・ニューサムに送付した。投票結果は、両院での全会一致の承認を経た後、知事に先んじて公職者および特定の公務員がミームコインを発行することを禁じる提案を盛り込むものだった。
AB 2409はカリフォルニア州の両院を通過
立法上の対応は、法案の公式履歴として記録されており、同日付で上院の承認と下院の同意が示されている。これらの投票の後、AB 2409は“engrossing（校正・再整理）”および“enrolling（最終本作成）”の段階に入った。この段階は州の記録に反映された立法手続きの工程である。
カリフォルニア、政治家向けのミームコイン禁止を知事ガビン・ニューサムに送付
カリフォルニア州上院は、8月26日にデジタル・アセット：ミームコイン法案であるAB 2409を賛成40、反対0で可決し、さらに下院が上院修正案に賛成78、反対0で同意して同法案を知事ガビン・ニューサムに送付した。投票結果は、両院での全会一致の承認を経た後、知事に先んじて公職者および特定の公務員がミームコインを発行することを禁じる提案を盛り込むものだった。
AB 2409はカリフォルニア州の両院を通過
立法上の対応は、法案の公式履歴として記録されており、同日付で上院の承認と下院の同意が示されている。これらの投票の後、AB 2409は“engrossing（校正・再整理）”および“enrolling（最終本作成）”の段階に入った。この段階は州の記録に反映された立法手続きの工程である。
AB 2409はカリフォルニア州の両院を通過
立法上の対応は、法案の公式履歴として記録されており、同日付で上院の承認と下院の同意が示されている。これらの投票の後、AB 2409は“engrossing（校正・再整理）”および“enrolling（最終本作成）”の段階に入った。この段階は州の記録に反映された立法手続きの工程である。
169
翻訳参照
Tokenized Stock Transfers Jump 415% to $29.5B in 30 DaysMonthly tokenized stock transfer volume climbed more than 415% over the past 30 days to $29.5 billion, according to RWA.xyz data reported by Cointelegraph. The reading is notable because it marks a far sharper increase in transfers than in the total value of tokenized stocks distributed onchain over the same period.
Transfer volume records the value moving through tokenized stock instruments, while distributed value measures the value of the outstanding stock tokens held onchain. They therefore describe different parts of the market: one measures activity during a period, and the other measures the size of the onchain asset base at a point in time.
Data Snapshot
MetricCurrentPreviousChangePeriodAs ofSourceMonthly tokenized stock transfer volume$29.5 billion—more than 415%past 30 days2026-08-29CointelegraphMonthly active addressesaround 1.3 million—more than 209%past 30 days2026-08-29CointelegraphTokenized stock holders2.36 million—167%past 30 days2026-08-29CointelegraphTotal value of tokenized stocks distributed onchain$2.54 billion$344 million1.45% over the past 30 days; roughly 637% from a year ago30 days and one year2026-08-29Cointelegraph
Active addresses and holders expanded alongside transfer volume
Monthly active addresses rose more than 209% to around 1.3 million over the same 30-day period. That expansion accompanied the jump in transfer volume, showing that the rise in activity coincided with a substantially larger number of addresses active in tokenized stocks.
The number of tokenized stock holders also climbed 167% to 2.36 million. Holder counts and active-address figures are separate measures, but both moved higher over the period covered by the data.
Monthly transfer volume reached $29.5 billion, alongside around 1.3 million active addresses and 2.36 million holders. Those combined readings show that growth extended across usage measures rather than being confined to the dollar value of transfers alone.
$29.5 billion in transfers versus $2.54 billion distributed onchain
The total value of tokenized stocks distributed onchain rose 1.45% over 30 days to $2.54 billion. That modest 30-day movement stands in contrast to the more than 415% increase in monthly transfer volume, indicating that transactions accelerated much more quickly than the value of tokenized stock assets outstanding onchain.
The gap between the $29.5 billion in transfers and the $2.54 billion in distributed value reflects two different measures, not competing estimates. Transfers during the month need not increase the total value of tokens distributed onchain, just as new issuance or changes in the value of existing holdings can affect distributed value without matching transfer activity.
On a longer comparison, distributed onchain value was up roughly 637% from $344 million a year ago. The annual increase shows that the onchain tokenized stock base has expanded considerably, even as its latest 30-day gain of 1.45% was much smaller than the change in transfer volume.
The data therefore separate two developments: a $2.54 billion onchain stock-token base following growth from $344 million a year ago, and a recent period in which transfers rose more than 415% to $29.5 billion. Monitoring whether distributed value begins to move more rapidly would help distinguish a sustained expansion of outstanding onchain assets from a period dominated by higher turnover.
Disclaimer: This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.
Tokenized Stock Transfers Jump 415% to $29.5B in 30 Days
Monthly tokenized stock transfer volume climbed more than 415% over the past 30 days to $29.5 billion, according to RWA.xyz data reported by Cointelegraph. The reading is notable because it marks a far sharper increase in transfers than in the total value of tokenized stocks distributed onchain over the same period.
Transfer volume records the value moving through tokenized stock instruments, while distributed value measures the value of the outstanding stock tokens held onchain. They therefore describe different parts of the market: one measures activity during a period, and the other measures the size of the onchain asset base at a point in time.
Data Snapshot
MetricCurrentPreviousChangePeriodAs ofSourceMonthly tokenized stock transfer volume$29.5 billion—more than 415%past 30 days2026-08-29CointelegraphMonthly active addressesaround 1.3 million—more than 209%past 30 days2026-08-29CointelegraphTokenized stock holders2.36 million—167%past 30 days2026-08-29CointelegraphTotal value of tokenized stocks distributed onchain$2.54 billion$344 million1.45% over the past 30 days; roughly 637% from a year ago30 days and one year2026-08-29Cointelegraph
Active addresses and holders expanded alongside transfer volume
Monthly active addresses rose more than 209% to around 1.3 million over the same 30-day period. That expansion accompanied the jump in transfer volume, showing that the rise in activity coincided with a substantially larger number of addresses active in tokenized stocks.
The number of tokenized stock holders also climbed 167% to 2.36 million. Holder counts and active-address figures are separate measures, but both moved higher over the period covered by the data.
Monthly transfer volume reached $29.5 billion, alongside around 1.3 million active addresses and 2.36 million holders. Those combined readings show that growth extended across usage measures rather than being confined to the dollar value of transfers alone.
$29.5 billion in transfers versus $2.54 billion distributed onchain
The total value of tokenized stocks distributed onchain rose 1.45% over 30 days to $2.54 billion. That modest 30-day movement stands in contrast to the more than 415% increase in monthly transfer volume, indicating that transactions accelerated much more quickly than the value of tokenized stock assets outstanding onchain.
The gap between the $29.5 billion in transfers and the $2.54 billion in distributed value reflects two different measures, not competing estimates. Transfers during the month need not increase the total value of tokens distributed onchain, just as new issuance or changes in the value of existing holdings can affect distributed value without matching transfer activity.
On a longer comparison, distributed onchain value was up roughly 637% from $344 million a year ago. The annual increase shows that the onchain tokenized stock base has expanded considerably, even as its latest 30-day gain of 1.45% was much smaller than the change in transfer volume.
The data therefore separate two developments: a $2.54 billion onchain stock-token base following growth from $344 million a year ago, and a recent period in which transfers rose more than 415% to $29.5 billion. Monitoring whether distributed value begins to move more rapidly would help distinguish a sustained expansion of outstanding onchain assets from a period dominated by higher turnover.
Disclaimer: This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.
Transfer volume records the value moving through tokenized stock instruments, while distributed value measures the value of the outstanding stock tokens held onchain. They therefore describe different parts of the market: one measures activity during a period, and the other measures the size of the onchain asset base at a point in time.
Data Snapshot
MetricCurrentPreviousChangePeriodAs ofSourceMonthly tokenized stock transfer volume$29.5 billion—more than 415%past 30 days2026-08-29CointelegraphMonthly active addressesaround 1.3 million—more than 209%past 30 days2026-08-29CointelegraphTokenized stock holders2.36 million—167%past 30 days2026-08-29CointelegraphTotal value of tokenized stocks distributed onchain$2.54 billion$344 million1.45% over the past 30 days; roughly 637% from a year ago30 days and one year2026-08-29Cointelegraph
Active addresses and holders expanded alongside transfer volume
Monthly active addresses rose more than 209% to around 1.3 million over the same 30-day period. That expansion accompanied the jump in transfer volume, showing that the rise in activity coincided with a substantially larger number of addresses active in tokenized stocks.
The number of tokenized stock holders also climbed 167% to 2.36 million. Holder counts and active-address figures are separate measures, but both moved higher over the period covered by the data.
Monthly transfer volume reached $29.5 billion, alongside around 1.3 million active addresses and 2.36 million holders. Those combined readings show that growth extended across usage measures rather than being confined to the dollar value of transfers alone.
$29.5 billion in transfers versus $2.54 billion distributed onchain
The total value of tokenized stocks distributed onchain rose 1.45% over 30 days to $2.54 billion. That modest 30-day movement stands in contrast to the more than 415% increase in monthly transfer volume, indicating that transactions accelerated much more quickly than the value of tokenized stock assets outstanding onchain.
The gap between the $29.5 billion in transfers and the $2.54 billion in distributed value reflects two different measures, not competing estimates. Transfers during the month need not increase the total value of tokens distributed onchain, just as new issuance or changes in the value of existing holdings can affect distributed value without matching transfer activity.
On a longer comparison, distributed onchain value was up roughly 637% from $344 million a year ago. The annual increase shows that the onchain tokenized stock base has expanded considerably, even as its latest 30-day gain of 1.45% was much smaller than the change in transfer volume.
The data therefore separate two developments: a $2.54 billion onchain stock-token base following growth from $344 million a year ago, and a recent period in which transfers rose more than 415% to $29.5 billion. Monitoring whether distributed value begins to move more rapidly would help distinguish a sustained expansion of outstanding onchain assets from a period dominated by higher turnover.
Disclaimer: This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.
266
4億FOGOトークンの不正流出を受けフォーゴがメインネットを停止フォーゴは、報じられたトークンの不正流出を受けて8月29日にメインネットを一時停止した。これにより、不正な活動に結びついた資産のさらなる移動を防ぐことを意図していると説明した。最新の更新（UTC 16:29に投稿）で、ネットワークはバリデーターが当該活動に関連するアドレスを制限するためにチェーンをアップグレードすると述べた。
メインネットはバリデーターのアドレス制限のために停止
フォーゴは停止は一時的であり、バリデーターが当該活動に関連するアドレスを制限するアップグレードを実施すると述べた。
4億FOGOトークンの不正流出を受けフォーゴがメインネットを停止
フォーゴは、報じられたトークンの不正流出を受けて8月29日にメインネットを一時停止した。これにより、不正な活動に結びついた資産のさらなる移動を防ぐことを意図していると説明した。最新の更新（UTC 16:29に投稿）で、ネットワークはバリデーターが当該活動に関連するアドレスを制限するためにチェーンをアップグレードすると述べた。
メインネットはバリデーターのアドレス制限のために停止
フォーゴは停止は一時的であり、バリデーターが当該活動に関連するアドレスを制限するアップグレードを実施すると述べた。
メインネットはバリデーターのアドレス制限のために停止
フォーゴは停止は一時的であり、バリデーターが当該活動に関連するアドレスを制限するアップグレードを実施すると述べた。
326
MarvellのGoogle AI提携は1200億ドルの見出しと、2029年の売上課題を抱えるマーベルのグーグルとの拡大した関係に付されている金額は、1200億ドルです。これは、単純な読み取りを誘うほどの大きさです。つまり、半導体サプライヤーが、人工知能インフラにおける最大級の支出者の一社から、将来の販売見込みという非常に大きなまとまりを確保したということです。
それは開示された契約書の記載内容とは異なります。この図は、グーグルが時間の経過とともにエクイティ・ワラントの大部分を得るために必要となる売上水準であり、明示された購入コミットメントや開示されたバックログの数値ではありません。この区別が重要なのは、マーベルが、両者の関係から得られるより意味のある貢献は会計年度2029年になってから開始する見通しだと述べているためです。
MarvellのGoogle AI提携は1200億ドルの見出しと、2029年の売上課題を抱える
マーベルのグーグルとの拡大した関係に付されている金額は、1200億ドルです。これは、単純な読み取りを誘うほどの大きさです。つまり、半導体サプライヤーが、人工知能インフラにおける最大級の支出者の一社から、将来の販売見込みという非常に大きなまとまりを確保したということです。
それは開示された契約書の記載内容とは異なります。この図は、グーグルが時間の経過とともにエクイティ・ワラントの大部分を得るために必要となる売上水準であり、明示された購入コミットメントや開示されたバックログの数値ではありません。この区別が重要なのは、マーベルが、両者の関係から得られるより意味のある貢献は会計年度2029年になってから開始する見通しだと述べているためです。
それは開示された契約書の記載内容とは異なります。この図は、グーグルが時間の経過とともにエクイティ・ワラントの大部分を得るために必要となる売上水準であり、明示された購入コミットメントや開示されたバックログの数値ではありません。この区別が重要なのは、マーベルが、両者の関係から得られるより意味のある貢献は会計年度2029年になってから開始する見通しだと述べているためです。
279
MoonwellのMAMOエクスプロイト、Baseで約870万ドルを流出Moonwellの8月28日付の事後報告書では、Base上のMAMO市場でのインシデントに関連して、残存する借り手義務は約913.1万ドルとしていた。プロトコルによると、最終的に成功した借入の32秒後に清算が開始されており、これは前日のエクスプロイトによって総額約1,103万ドルの借入が可能になったことに続くものだ。
Moonwellは、未履行の借り手義務を913.1万ドルと見積もった
Base上のMAMO市場でのインシデント後、Moonwellは、清算が開始される時点で借り手義務が約913.1万ドル残っていたと見積もった。
MoonwellのMAMOエクスプロイト、Baseで約870万ドルを流出
Moonwellの8月28日付の事後報告書では、Base上のMAMO市場でのインシデントに関連して、残存する借り手義務は約913.1万ドルとしていた。プロトコルによると、最終的に成功した借入の32秒後に清算が開始されており、これは前日のエクスプロイトによって総額約1,103万ドルの借入が可能になったことに続くものだ。
Moonwellは、未履行の借り手義務を913.1万ドルと見積もった
Base上のMAMO市場でのインシデント後、Moonwellは、清算が開始される時点で借り手義務が約913.1万ドル残っていたと見積もった。
Moonwellは、未履行の借り手義務を913.1万ドルと見積もった
Base上のMAMO市場でのインシデント後、Moonwellは、清算が開始される時点で借り手義務が約913.1万ドル残っていたと見積もった。
283
HMRC：2024-25年に暗号資産の利益で100万ポンド超を報告したのは240人HMRCによると、2024年から2025年の税年度に暗号資産キャピタルゲインとして、1人あたり100万ポンド超をそれぞれ報告したのは240人で、合計で7億1,700万ポンドを申告した。これらは、課税対象となる暗号資産キャピタルゲインを対象にした、英国で初めての公式統計である。これは、確定申告（Self Assessment）の申告書に専用の暗号資産セクションが導入されたことに続くものだ。
高額層は、同期間にキャピタルゲイン税（Capital Gains Tax）の対象となる暗号資産の処分を行った17,600人の中に含まれている。彼らが報告した利益は、課税対象となる暗号資産取引のうち上位層を、非常に明確に把握できる一方で、より広いデータは、英国の暗号資産保有者全員や取引活動すべてではなく、より広い範囲の納税者を捉えている。
HMRC：2024-25年に暗号資産の利益で100万ポンド超を報告したのは240人
HMRCによると、2024年から2025年の税年度に暗号資産キャピタルゲインとして、1人あたり100万ポンド超をそれぞれ報告したのは240人で、合計で7億1,700万ポンドを申告した。これらは、課税対象となる暗号資産キャピタルゲインを対象にした、英国で初めての公式統計である。これは、確定申告（Self Assessment）の申告書に専用の暗号資産セクションが導入されたことに続くものだ。
高額層は、同期間にキャピタルゲイン税（Capital Gains Tax）の対象となる暗号資産の処分を行った17,600人の中に含まれている。彼らが報告した利益は、課税対象となる暗号資産取引のうち上位層を、非常に明確に把握できる一方で、より広いデータは、英国の暗号資産保有者全員や取引活動すべてではなく、より広い範囲の納税者を捉えている。
高額層は、同期間にキャピタルゲイン税（Capital Gains Tax）の対象となる暗号資産の処分を行った17,600人の中に含まれている。彼らが報告した利益は、課税対象となる暗号資産取引のうち上位層を、非常に明確に把握できる一方で、より広いデータは、英国の暗号資産保有者全員や取引活動すべてではなく、より広い範囲の納税者を捉えている。
127
BitGoはNYDIGのトレーディング部門を4,250万ドル＋アーンアウトで買収BitGoは2026年8月27日にNYDIGの機関投資家向けトレーディング事業および関連資産の買収を完了し、現金と株式の組み合わせで総額4,250万ドルを前払いしました。この取引には、収益マイルストーンに連動する最大1,500万ドルの条件付き現金支払いも含まれており、最終的な対価は取得した事業の業績に左右されます。
同社の米国証券取引委員会（SEC）への提出書類によれば、前払いのパッケージは現金700万ドルと、BitGoの株式約3,550万ドルで構成されています。BitGoは、8月27日の発表で当該取引が完了していたと述べました。
BitGoはNYDIGのトレーディング部門を4,250万ドル＋アーンアウトで買収
BitGoは2026年8月27日にNYDIGの機関投資家向けトレーディング事業および関連資産の買収を完了し、現金と株式の組み合わせで総額4,250万ドルを前払いしました。この取引には、収益マイルストーンに連動する最大1,500万ドルの条件付き現金支払いも含まれており、最終的な対価は取得した事業の業績に左右されます。
同社の米国証券取引委員会（SEC）への提出書類によれば、前払いのパッケージは現金700万ドルと、BitGoの株式約3,550万ドルで構成されています。BitGoは、8月27日の発表で当該取引が完了していたと述べました。
同社の米国証券取引委員会（SEC）への提出書類によれば、前払いのパッケージは現金700万ドルと、BitGoの株式約3,550万ドルで構成されています。BitGoは、8月27日の発表で当該取引が完了していたと述べました。
133
ログインして、さらにコンテンツを読む
厳選トピックで世界の暗号資産トレーダーの仲間入り
⚡️ 暗号資産に関する最新かつ有益な情報が見つかります。
💬 世界最大の暗号資産取引所から信頼されています。
👍 認証を受けたクリエイターから、有益なインサイトを得られます。
メール / 電話番号
トレンドトピック
SKHynixStudiesJapanMemoryChipVenture
閲覧回数 1,612
111人が討論中
#SKHynixStudiesJapanMemoryChipVenture SK ヒュニックスの「数十億ドル規模の工場」選定基準は、ただ「良い電力と良い水」だけ 💧⚡
8月31日、仙台。SKグループ会長チェ・テウォンは、SKハイニックスが日本（可能性として宮城県）での共同ベンチャー型メモリーチップ工場について検討していると確認した。投資額は数兆ウォンに達する可能性がある。パートナー名は明かされていない。候補地も確定していない。資本額も決まっていない。スケジュールの提示もない。実際に何を探しているのかを問われると、チェの答えは全文で「日本中を見ています。良い電力と良い水がある場所なら、どこでも。」だった。率直すぎるほど正直か、あるいは記者が集まる場で会長がこれまでにした中で最も役に立たない答えかのどちらかだ。😂
これは、私たちが数か月追ってきたパターンに当てはまる理由 🧠
SKハイニックスは先週、インディアナ州で40億ドルのパッケージング工場に着工したばかりだ。さらに別途、5,400億ウォン（約390億ドル）を投資して韓国国内の生産能力を拡張している。そこへ今度は日本も会話に加わってきた。私たちが見てきたのと同じ会社だ。過去最高を更新したADRのデビュー、KOSPIのサーキットブレーカーによる過酷な急落を生き延びたこと、そして中国のCXMTによるメモリ生産の拡大が1四半期で719%に達し、しぼられる局面も。拡張をあちこちで同時に進める——それがどうやら実際の戦略らしい。💎
本当に興味深い「関係性」の角度 🎯
SKハイニックスはすでに、日本のNANDフラッシュメーカーであるキオクシアに対して重要な間接出資を持っており、CEOのクァク・ノウジョンは、より深い協力に向けた協議が進行中だと明言している。チェはさらに踏み込み、両国の労働力が縮小していることを踏まえ、韓国と日本が「経済圏を形成する」ことを求めた。💡
率直な現実チェック 🎭
これは実現可能性調査であって、大規模な突破口ではない。確定しているのは、今後10年の終わりまで世界のメモリーチップ供給がタイトに推移する見通しだ、という点だけだ。今のところ容量増強を進めている企業は、皆その前提に賭けている。🚀
$BTC
Philboom
·いいね：0件
·閲覧回数 14
WTICrudeBreaksAbove$85
閲覧回数 1,153
53人が討論中
BrentRisesAbove$90
閲覧回数 7,224
115人が討論中