demand increases or decreases. In Bitcoin, this can lead to periods of higher transaction fees when there’s greater demand for its limited blockspace.

In Bitcoin, we have two advantages that gold does not have. First, making Bitcoin transactions that can be viewed in alternative ways does not affect the market for Bitcoin itself. Unlike gold, very little Bitcoin is allocated to these uses. Second, in Bitcoin, we have a protocol that is already designed to minimize cost to the validation network from such other interpretations. Bitcoin limits both the size of blocks and the number of signatures that can be used in transactions. These are the greatest costs to validating nodes, and the protocol limits on them have been in place since the very early days of Bitcoin, precisely to prevent abuse by any high-frequency or high-volume use of the ledger. These limits have already spurred innovations such as the Lightning Network, Ark, Spark, Cashu, and many more. Even the boom in demand for blockspace caused by these “non-monetary” ledger entries (yes, that does sound ridiculous) has increased the use of these scaling solutions, which require fewer entries on the main ledger.

With the justification for BIP110 thus explored, and hopefully shown to be woefully lacking, let’s look at the proposed change itself. BIP110 restricts the size of locking scripts, restricts the number of alternative scripts in taproot, makes the taproot annex invalid, removes all upgradable witness and tapscript versions, removes all tapscript upgradable opcodes, and makes OP_IF and OP_NOTIF invalid in tapscript. All of these restrictions apply to UTXOs created during the 52414 blocks (approximately 1 year) after its activation. BIP110 also proposes a miner readiness signaling threshold of 55% instead of the threshold used in prior miner signaled softforks of 90% or more. If 55% of blocks do not signal readiness before block 961632, nodes enforcing BIP110 will treat blocks not signaling readiness as invalid to force the change to lock in by block 963648 and activate by block 965664.

BIP110 would be the most sweeping restriction of Bitcoin script since Satoshi’s well-known deactivation of many opcodes in response to a critical vulnerability (CVE-2010-5137) back in 2010. It proposes miner signaled activation with an unprecedentedly low threshold and node-forced activation after less than 9 months from the date the BIP was assigned a number. It does all of this because (as discussed above) other people are viewing certain ledger entries in ways which the BIP110 supporters do not approve of. Worse yet, the folks who use such disapproved ledger entries have already updated their software to continue making such entries even if BIP110 were to become Bitcoin’s consensus rule set. This was, of course, a predictable outcome (many of us explicitly predicted it) because it is fundamentally impossible to restrict how other people use external software to analyze entries on an open-access public ledger.

In summary, BIP110 is a proposal to do something impossible (limit how users of an open access ledger use that ledger) in response to a problem that is already fully addressed through Bitcoin’s existing protocol limits. It proposes to do this impossible thing on an irresponsibly short activation timeline, with incredibly limited code review, and regardless of whether the change reaches any type of ecosystem consensus. Fortunately, Bitcoin is not such a delicate flower of a system that such a foolhardy attempt at modifying it will succeed. Not only have miners soundly rejected BIP110, but other voices throughout the developer, investor, influencer, and corporate landscape have spoken out against the changes.  In August, this particular attack against Bitcoin’s consensus rules will have made Bitcoin stronger through its failure, and the network will continue its steady rhythm of tick-tock, next block.

This post The Bitcoin Softfork That Tried to Police “Junk Data” — And Why It’s Already Failing first appear[...]

ed on Bitcoin Magazine and is written by Brandon Black.

NewsBTC Timelock Account Recovery Gives Ethereum Smart Accounts A Safer Backup Route

Timelock Account Recovery Gives Ethereum Smart Accounts A Safer Backup Route is a useful reminder that crypto coverage is not only about token prices. Sometimes the more important story is the infrastructure, regulation, security, or product layer sitting underneath the market noise.

The immediate point is straightforward: a new Ethereum Magicians proposal outlines timelock-based smart account recovery. That gives readers something concrete to work with, rather than another vague sentiment update. TL;DR

* A new Ethereum Magicians proposal outlines timelock-based smart account recovery.
* The design aims to reduce trust in guardians by adding delay and cancellation windows.
* The idea could make ERC-4337 wallets safer for ordinary users if it matures. Why This Matters Now

The timing matters because Ethereum is already part of a wider conversation across the market. Traders want to know whether the development changes liquidity or risk. Builders want to know whether it changes what can be deployed. Compliance teams want to know whether it changes how platforms operate.

In that sense, the story is bigger than one headline. It sits inside the ongoing shift from speculative crypto cycles toward more practical questions: who can use these systems, how safe are they, and whether the underlying incentives actually work.

The best way to read it is with discipline. It is not a guarantee of immediate upside, and it should not be treated as one. But it does add a fresh data point to the way the market is thinking about Ethereum. The Ethereum Angle

For Ethereum, the important part is the specific mechanism. If this is a security issue, the risk sits in dependencies and user protection. If it is a listing or product launch, the question is access and liquidity. If it is a governance or research proposal, the question is whether the idea can survive implementation.

That is where this update becomes useful. It is not just a label attached to a trend. It gives readers a way to understand what might actually change if the development gains traction.

Crypto has a habit of turning every announcement into a broad market claim. This one deserves a narrower read. The value is in seeing how it affects the users, developers, institutions, or traders closest to the issue. The Risk Side

There is also a caution attached. Source material can confirm that a development exists, but it cannot prove that adoption will follow. A proposal still needs support. A product still needs users. A chart still needs confirmation. A compliance tool still needs integration.

That is why the responsible reading is not to oversell the story. The stronger takeaway is that this adds to a pattern. The crypto market is steadily becoming more professional, more technical, and more sensitive to real operational details.

Readers should also watch for follow-up signals. That could mean developer feedback, exchange support, regulatory response, wallet adoption, liquidity data, or simply whether market participants continue reacting after the first headline fades. What Comes Next

The next stage will decide whether this remains a narrow update or becomes part of a larger market theme. In crypto, that difference matters. Plenty of stories look important for a few hours and then disappear. The ones that last usually show up again through usage, liquidity, enforcement, governance, or developer adoption.

For now, this gives the market another piece of information to weigh. It is specific enough to be useful, but still early enough that readers should keep the caveats in view.

That makes it worth covering without pretending it settles anything. The story is a signal, not a final verdict.

This report is based on information from ethereum-magicians.org.

This article was written by the News Desk and edited by Samuel Rae.

NewsBTC Injective SDK Compromise Puts Wallet Private Keys Back In The Security Spotlight

Injective SDK Compromise Puts Wallet Private Keys Back In The Security Spotlight is a useful reminder that crypto coverage is not only about token prices. Sometimes the more important story is the infrastructure, regulation, security, or product layer sitting underneath the market noise.

The immediate point is straightforward: slowMist warned that a compromised Injective SDK package may steal wallet private keys. That gives readers something concrete to work with, rather than another vague sentiment update. TL;DR

* SlowMist warned that a compromised Injective SDK package may steal wallet private keys.
* The issue highlights the danger of malicious software dependencies in crypto apps.
* Developers are being urged to verify packages before shipping wallet-facing code. Why This Matters Now

The timing matters because Injective is already part of a wider conversation across the market. Traders want to know whether the development changes liquidity or risk. Builders want to know whether it changes what can be deployed. Compliance teams want to know whether it changes how platforms operate.

In that sense, the story is bigger than one headline. It sits inside the ongoing shift from speculative crypto cycles toward more practical questions: who can use these systems, how safe are they, and whether the underlying incentives actually work.

The best way to read it is with discipline. It is not a guarantee of immediate upside, and it should not be treated as one. But it does add a fresh data point to the way the market is thinking about Injective. The Injective Angle

For Injective, the important part is the specific mechanism. If this is a security issue, the risk sits in dependencies and user protection. If it is a listing or product launch, the question is access and liquidity. If it is a governance or research proposal, the question is whether the idea can survive implementation.

That is where this update becomes useful. It is not just a label attached to a trend. It gives readers a way to understand what might actually change if the development gains traction.

Crypto has a habit of turning every announcement into a broad market claim. This one deserves a narrower read. The value is in seeing how it affects the users, developers, institutions, or traders closest to the issue. The Risk Side

There is also a caution attached. Source material can confirm that a development exists, but it cannot prove that adoption will follow. A proposal still needs support. A product still needs users. A chart still needs confirmation. A compliance tool still needs integration.

That is why the responsible reading is not to oversell the story. The stronger takeaway is that this adds to a pattern. The crypto market is steadily becoming more professional, more technical, and more sensitive to real operational details.

Readers should also watch for follow-up signals. That could mean developer feedback, exchange support, regulatory response, wallet adoption, liquidity data, or simply whether market participants continue reacting after the first headline fades. What Comes Next

The next stage will decide whether this remains a narrow update or becomes part of a larger market theme. In crypto, that difference matters. Plenty of stories look important for a few hours and then disappear. The ones that last usually show up again through usage, liquidity, enforcement, governance, or developer adoption.

For now, this gives the market another piece of information to weigh. It is specific enough to be useful, but still early enough that readers should keep the caveats in view.

That makes it worth covering without pretending it settles anything. The story is a signal, not a final verdict.

This report is based on information from slowmist.medium.com.

This article was written by the News Desk and edited by Samuel Rae.

NewsBTC
Ethereum Foundation Clear Signing Push Targets Crypto’s Blind Approval Problem

Ethereum Foundation Clear Signing Push Targets Crypto’s Blind Approval Problem is a useful reminder that crypto coverage is not only about token prices. Sometimes the more important story is the infrastructure, regulation, security, or product layer sitting underneath the market noise.

The immediate point is straightforward: the Ethereum Foundation outlined work around safer clear signing standards. That gives readers something concrete to work with, rather than another vague sentiment update. TL;DR

* The Ethereum Foundation outlined work around safer clear signing standards.
* The goal is to reduce blind approvals when users interact with complex dApps.
* Better signing clarity could help wallets reduce one of crypto’s most common user-side risks. Why This Matters Now

The timing matters because Ethereum is already part of a wider conversation across the market. Traders want to know whether the development changes liquidity or risk. Builders want to know whether it changes what can be deployed. Compliance teams want to know whether it changes how platforms operate.

In that sense, the story is bigger than one headline. It sits inside the ongoing shift from speculative crypto cycles toward more practical questions: who can use these systems, how safe are they, and whether the underlying incentives actually work.

The best way to read it is with discipline. It is not a guarantee of immediate upside, and it should not be treated as one. But it does add a fresh data point to the way the market is thinking about Ethereum. The Ethereum Angle

For Ethereum, the important part is the specific mechanism. If this is a security issue, the risk sits in dependencies and user protection. If it is a listing or product launch, the question is access and liquidity. If it is a governance or research proposal, the question is whether the idea can survive implementation.

That is where this update becomes useful. It is not just a label attached to a trend. It gives readers a way to understand what might actually change if the development gains traction.

Crypto has a habit of turning every announcement into a broad market claim. This one deserves a narrower read. The value is in seeing how it affects the users, developers, institutions, or traders closest to the issue. The Risk Side

There is also a caution attached. Source material can confirm that a development exists, but it cannot prove that adoption will follow. A proposal still needs support. A product still needs users. A chart still needs confirmation. A compliance tool still needs integration.

That is why the responsible reading is not to oversell the story. The stronger takeaway is that this adds to a pattern. The crypto market is steadily becoming more professional, more technical, and more sensitive to real operational details.

Readers should also watch for follow-up signals. That could mean developer feedback, exchange support, regulatory response, wallet adoption, liquidity data, or simply whether market participants continue reacting after the first headline fades. What Comes Next

The next stage will decide whether this remains a narrow update or becomes part of a larger market theme. In crypto, that difference matters. Plenty of stories look important for a few hours and then disappear. The ones that last usually show up again through usage, liquidity, enforcement, governance, or developer adoption.

For now, this gives the market another piece of information to weigh. It is specific enough to be useful, but still early enough that readers should keep the caveats in view.

That makes it worth covering without pretending it settles anything. The story is a signal, not a final verdict.

The key is not to confuse coverage with certainty. Ethereum stories can move quickly, especially when they touch security, regulatio[...]

n, listings, infrastructure, or price levels. The useful approach is to track the next confirming detail rather than assume the first update carries the whole market story. That is how traders avoid chasing noise and how readers separate a genuine development from another passing headline.

This report is based on information from blog.ethereum.org.

This article was written by the News Desk and edited by Samuel Rae.

NewsBTC
Ethereum Governance Debate Turns To Who Really Controls Voting Power

Ethereum Governance Debate Turns To Who Really Controls Voting Power is a useful reminder that crypto coverage is not only about token prices. Sometimes the more important story is the infrastructure, regulation, security, or product layer sitting underneath the market noise.

The immediate point is straightforward: ethereum researchers are discussing how voting authority can become hard to track. That gives readers something concrete to work with, rather than another vague sentiment update. TL;DR

* Ethereum researchers are discussing how voting authority can become hard to track.
* The debate has implications for liquid staking protocols and DAO governance.
* Greater visibility into delegation could become a key decentralization safeguard. Why This Matters Now

The timing matters because Ethereum is already part of a wider conversation across the market. Traders want to know whether the development changes liquidity or risk. Builders want to know whether it changes what can be deployed. Compliance teams want to know whether it changes how platforms operate.

In that sense, the story is bigger than one headline. It sits inside the ongoing shift from speculative crypto cycles toward more practical questions: who can use these systems, how safe are they, and whether the underlying incentives actually work.

The best way to read it is with discipline. It is not a guarantee of immediate upside, and it should not be treated as one. But it does add a fresh data point to the way the market is thinking about Ethereum. The Ethereum Angle

For Ethereum, the important part is the specific mechanism. If this is a security issue, the risk sits in dependencies and user protection. If it is a listing or product launch, the question is access and liquidity. If it is a governance or research proposal, the question is whether the idea can survive implementation.

That is where this update becomes useful. It is not just a label attached to a trend. It gives readers a way to understand what might actually change if the development gains traction.

Crypto has a habit of turning every announcement into a broad market claim. This one deserves a narrower read. The value is in seeing how it affects the users, developers, institutions, or traders closest to the issue. The Risk Side

There is also a caution attached. Source material can confirm that a development exists, but it cannot prove that adoption will follow. A proposal still needs support. A product still needs users. A chart still needs confirmation. A compliance tool still needs integration.

That is why the responsible reading is not to oversell the story. The stronger takeaway is that this adds to a pattern. The crypto market is steadily becoming more professional, more technical, and more sensitive to real operational details.

Readers should also watch for follow-up signals. That could mean developer feedback, exchange support, regulatory response, wallet adoption, liquidity data, or simply whether market participants continue reacting after the first headline fades. What Comes Next

The next stage will decide whether this remains a narrow update or becomes part of a larger market theme. In crypto, that difference matters. Plenty of stories look important for a few hours and then disappear. The ones that last usually show up again through usage, liquidity, enforcement, governance, or developer adoption.

For now, this gives the market another piece of information to weigh. It is specific enough to be useful, but still early enough that readers should keep the caveats in view.

That makes it worth covering without pretending it settles anything. The story is a signal, not a final verdict.

The key is not to confuse coverage with certainty. Ethereum stories can move quickly, especially when they touch security, regulation, listings, infras[...]

tructure, or price levels. The useful approach is to track the next confirming detail rather than assume the first update carries the whole market story. That is how traders avoid chasing noise and how readers separate a genuine development from another passing headline.

This report is based on information from ethresear.ch.

This article was written by the News Desk and edited by Samuel Rae.

NewsBTC
Chainalysis Adds Automatic Stablecoin Support As Compliance Teams Face Token Sprawl

Chainalysis Adds Automatic Stablecoin Support As Compliance Teams Face Token Sprawl is a useful reminder that crypto coverage is not only about token prices. Sometimes the more important story is the infrastructure, regulation, security, or product layer sitting underneath the market noise.

The immediate point is straightforward: chainalysis added automatic token support for stablecoin monitoring. That gives readers something concrete to work with, rather than another vague sentiment update. TL;DR

* Chainalysis added automatic token support for stablecoin monitoring.
* The tool is aimed at faster compliance coverage for newly launched stablecoins.
* The update reflects how quickly the stablecoin market is fragmenting across issuers and chains. Why This Matters Now

The timing matters because Chainalysis is already part of a wider conversation across the market. Traders want to know whether the development changes liquidity or risk. Builders want to know whether it changes what can be deployed. Compliance teams want to know whether it changes how platforms operate.

In that sense, the story is bigger than one headline. It sits inside the ongoing shift from speculative crypto cycles toward more practical questions: who can use these systems, how safe are they, and whether the underlying incentives actually work.

The best way to read it is with discipline. It is not a guarantee of immediate upside, and it should not be treated as one. But it does add a fresh data point to the way the market is thinking about Stablecoins. The Stablecoins Angle

For Stablecoins, the important part is the specific mechanism. If this is a security issue, the risk sits in dependencies and user protection. If it is a listing or product launch, the question is access and liquidity. If it is a governance or research proposal, the question is whether the idea can survive implementation.

That is where this update becomes useful. It is not just a label attached to a trend. It gives readers a way to understand what might actually change if the development gains traction.

Crypto has a habit of turning every announcement into a broad market claim. This one deserves a narrower read. The value is in seeing how it affects the users, developers, institutions, or traders closest to the issue. The Risk Side

There is also a caution attached. Source material can confirm that a development exists, but it cannot prove that adoption will follow. A proposal still needs support. A product still needs users. A chart still needs confirmation. A compliance tool still needs integration.

That is why the responsible reading is not to oversell the story. The stronger takeaway is that this adds to a pattern. The crypto market is steadily becoming more professional, more technical, and more sensitive to real operational details.

Readers should also watch for follow-up signals. That could mean developer feedback, exchange support, regulatory response, wallet adoption, liquidity data, or simply whether market participants continue reacting after the first headline fades. What Comes Next

The next stage will decide whether this remains a narrow update or becomes part of a larger market theme. In crypto, that difference matters. Plenty of stories look important for a few hours and then disappear. The ones that last usually show up again through usage, liquidity, enforcement, governance, or developer adoption.

For now, this gives the market another piece of information to weigh. It is specific enough to be useful, but still early enough that readers should keep the caveats in view.

That makes it worth covering without pretending it settles anything. The story is a signal, not a final verdict.

The key is not to confuse coverage with certainty. Stablecoins stories can move quickly, especially when they touch secu[...]

rity, regulation, listings, infrastructure, or price levels. The useful approach is to track the next confirming detail rather than assume the first update carries the whole market story. That is how traders avoid chasing noise and how readers separate a genuine development from another passing headline.

This report is based on information from chainalysis.com.

This article was written by the News Desk and edited by Samuel Rae.

NewsBTC
Starknet Memory Protocol Draft Puts User-Owned AI Data On The Crypto Agenda

Starknet Memory Protocol Draft Puts User-Owned AI Data On The Crypto Agenda is a useful reminder that crypto coverage is not only about token prices. Sometimes the more important story is the infrastructure, regulation, security, or product layer sitting underneath the market noise.

The immediate point is straightforward: a Starknet community draft proposes a user-owned memory protocol for AI agents. That gives readers something concrete to work with, rather than another vague sentiment update. TL;DR

* A Starknet community draft proposes a user-owned memory protocol for AI agents.
* The design uses scoped, temporary, auditable access through capability tokens.
* It reflects a growing push to make AI-agent data control more user-owned. Why This Matters Now

The timing matters because Starknet is already part of a wider conversation across the market. Traders want to know whether the development changes liquidity or risk. Builders want to know whether it changes what can be deployed. Compliance teams want to know whether it changes how platforms operate.

In that sense, the story is bigger than one headline. It sits inside the ongoing shift from speculative crypto cycles toward more practical questions: who can use these systems, how safe are they, and whether the underlying incentives actually work.

The best way to read it is with discipline. It is not a guarantee of immediate upside, and it should not be treated as one. But it does add a fresh data point to the way the market is thinking about Starknet. The Starknet Angle

For Starknet, the important part is the specific mechanism. If this is a security issue, the risk sits in dependencies and user protection. If it is a listing or product launch, the question is access and liquidity. If it is a governance or research proposal, the question is whether the idea can survive implementation.

That is where this update becomes useful. It is not just a label attached to a trend. It gives readers a way to understand what might actually change if the development gains traction.

Crypto has a habit of turning every announcement into a broad market claim. This one deserves a narrower read. The value is in seeing how it affects the users, developers, institutions, or traders closest to the issue. The Risk Side

There is also a caution attached. Source material can confirm that a development exists, but it cannot prove that adoption will follow. A proposal still needs support. A product still needs users. A chart still needs confirmation. A compliance tool still needs integration.

That is why the responsible reading is not to oversell the story. The stronger takeaway is that this adds to a pattern. The crypto market is steadily becoming more professional, more technical, and more sensitive to real operational details.

Readers should also watch for follow-up signals. That could mean developer feedback, exchange support, regulatory response, wallet adoption, liquidity data, or simply whether market participants continue reacting after the first headline fades. What Comes Next

The next stage will decide whether this remains a narrow update or becomes part of a larger market theme. In crypto, that difference matters. Plenty of stories look important for a few hours and then disappear. The ones that last usually show up again through usage, liquidity, enforcement, governance, or developer adoption.

For now, this gives the market another piece of information to weigh. It is specific enough to be useful, but still early enough that readers should keep the caveats in view.

That makes it worth covering without pretending it settles anything. The story is a signal, not a final verdict.

This report is based on information from community.starknet.io.

This article was written by the News Desk and edited by Samuel Rae.

Decrypt
UK to Defer Capital Gains Tax on DeFi Lending, Liquidity Pool Deposits

Moving crypto into a lending protocol or liquidity pool won’t count as a taxable disposal, deferring the charge until a real cash-out.

Decrypt
Bitcoin Ticks Up to $64K Following Largest Inflation Slowdown in Six Years

Consumer prices cooled more than expected in June, yet geopolitical tensions continue to cast a shadow over crypto prices

Decrypt
DeepMind CEO Says AGI Will Be Bigger Than Electricity or Fire

Demis Hassabis says artificial general intelligence is only a few years away and proposes a new U.S. standards body to test frontier AI models before release.

CoinDesk
U.S., UK move to align rules for tokenized finance across world's largest financial markets

The joint roadmap aims to reduce regulatory friction for tokenized assets while strengthening ties between the world's two largest financial centers.

CoinDesk
Wikipedia blackout could hurt how AI engines like ChatGPT understand crypto

Wikipedia observes guidelines on crypto coverage that date back many years and may now be outdated, according to the report.

CoinDesk
Mizuho downgrades Circle to underperform, cuts price target to $50 on Open USD threat

The Japanese investment bank said Open USD's yield pass-through model could pressure Circle's margins by shifting more reserve income to distributors.

CoinDesk
The Clarity Act isn't a ticket to sanctions evasion, actually

The bill, as currently drafted, has the power to stop sanctions evasion at scale, argues Ari Redbord, global head of policy at TRM Labs.

CoinDesk
Binance bets on becoming a crypto 'super app' as stablecoins reshape growth

Shunyet Jan, Binance’s head of spot trading and derivatives, said the exchange is focusing more on payments and financial services than on trading alone as it drives the next phase of its expansion.

CoinDesk
Some U.S. Senate Democrats come out against Clarity Act, calling it a 'corrupt' bill

Certain Democrats are taking an increasingly rigorous stand against the crypto market structure bill, which needs a significant number from their party to pass.

CoinDesk
U.S. CFTC moves to stop Kalshi from canceling trades as ordered by Michigan court

The federal derivatives regulator, which oversees trading at Kalshi, argued it was inappropriate for Michigan to "bully" the firm into reversing trades.