GnosisDAO has approved GIP-153, giving Gnosis Chain a governance mandate to move toward becoming a ZK-proven Ethereum rollup rather than continuing only as an independent Layer 1 network.

The proposal passed with 123,158 GNO voting in favor, according to the Snapshot vote. The plan would transition Gnosis Chain into what the proposal describes as part of an Ethereum Economic Zone, with the chain settling on Ethereum and inheriting Ethereum’s security. Gas would remain paid in xDAI, and the target genesis window is late 2026 or early 2027.

That is a meaningful direction change.

Gnosis Chain has long occupied an unusual position in the Ethereum ecosystem. It is closely aligned with Ethereum values and tooling, but it has operated as its own chain. Moving toward a ZK-proven L2 model would bring it more directly into Ethereum’s rollup roadmap.

Still, this is a governance mandate, not immediate technical deployment.

TL;DR

• GnosisDAO approved GIP-153 to transition Gnosis Chain toward a ZK-proven Ethereum rollup.
• The proposal passed with 123,158 GNO voting in favor.
• Gas would remain paid in xDAI, with a target genesis in late 2026 or early 2027.

A Directional Vote, Not A Finished Migration

The most important detail is timing.

GIP-153 gives the project a clear direction, but it does not mean the technical migration has already happened. Rollup transitions require engineering, testing, sequencer and prover design, bridge considerations, user migration planning, security review, and ecosystem coordination.

That takes time.

The proposal’s late 2026 or early 2027 genesis target gives the market a broad window, not an overnight switch. Users should not assume that Gnosis Chain has already become an Ethereum rollup simply because the vote passed.

Governance has approved the direction. Implementation comes next.

Why Ethereum Settlement Matters

The appeal of settling on Ethereum is straightforward.

Ethereum remains the dominant security and settlement layer for rollups. Chains that settle to Ethereum can lean on its validator set, liquidity base, developer ecosystem, and institutional credibility. That is why many projects have chosen to become L2s rather than compete as standalone chains.

For Gnosis Chain, the move could strengthen its Ethereum alignment while preserving some of its existing user experience.

Keeping gas paid in xDAI is particularly important because it protects one of the chain’s most familiar features. Users would not suddenly need to rethink every basic transaction around ETH gas.

That balance — Ethereum security with Gnosis-specific UX — is likely the point.

Unlocking Staked GNO Adds Another Layer

The proposal also unlocks approximately 350,000 staked GNO.

That matters because governance changes can have token-economic effects as well as technical ones. Unlocking staked assets may improve flexibility, change incentives, or affect how participants think about GNO’s role in the future network structure.

The market will want to understand whether the transition makes GNO more governance-centered, more economically useful, or simply part of a broader ecosystem alignment.

That question will take time to answer.

For now, the vote shows that GnosisDAO wants the chain’s next phase to sit closer to Ethereum’s rollup economy.

Rollup Consolidation Keeps Moving

The broader story is that Ethereum’s scaling map continues to absorb more activity.

The L2 model has become the dominant way for Ethereum-aligned ecosystems to grow without forcing every transaction onto Ethereum mainnet. If Gnosis Chain follows through, it would add another established ecosystem to the rollup side of the market.

That could make sense strategically.

Instead of competing with Ethereum, Gnosis Chain can position itself as a specialized extension of Ethereum’s settlement layer. That may be more attractive to developers, users, and institutional partners who already trust Ethereum’s security model.

But it also means Gnosis will need to execute carefully. Rollup infrastructure is competitive, and users will judge the transition by reliability, fees, liquidity, tooling, and bridge safety.

What Comes Next

The next phase is execution.

GnosisDAO has approved the direction. Now the project needs technical design, implementation milestones, test environments, ecosystem communication, and final launch planning.

The vote is important because it clarifies intent. It does not settle every detail.

For Ethereum, the approval is another sign that its rollup-centered roadmap continues to pull in aligned ecosystems. For Gnosis Chain, it marks the beginning of a new chapter: one where the chain’s future is tied more tightly to Ethereum settlement.

That could be powerful, but the hard part starts after the vote.

This article is based on GnosisDAO’s GIP-153 Snapshot vote and related governance materials.

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

This report is based on information released in disclosures at primary source documentation.

Luke Dashjr has been removed as a Bitcoin Improvement Proposal editor after a dispute around BIP-110, marking a rare governance flashpoint inside Bitcoin’s usually slow-moving technical process.

The change was merged through Pull Request 2248 in the bitcoin/bips repository, removing Dashjr from the editor list in BIP 3. The move followed controversy over BIP-110, a Reduced Data Temporary Softfork proposal that became tied to a stalled minority chain and accusations that standard review norms had been bypassed.

That does not mean Dashjr has been banned from Bitcoin development. It also does not mean Bitcoin itself was under serious threat.

It does show that even in Bitcoin, where governance is deliberately informal and conservative, process still matters.

For more details, visit the official Github platform.

TL;DR

• Luke Dashjr has been removed from the Bitcoin BIP editor list.
• The change followed controversy around BIP-110 and a stalled minority fork.
• This is a governance-process story, not a threat to Bitcoin mainnet.

Why BIP Editors Matter

Bitcoin Improvement Proposal editors do not control Bitcoin.

That is an important starting point. They do not decide what code runs on nodes. They do not force miners, exchanges, wallets, or users to adopt changes. They do not have unilateral authority over consensus.

Their role is more procedural.

BIP editors help manage proposals, formatting, numbering, status, and workflow inside the BIP repository. That sounds administrative, but in Bitcoin, process legitimacy is extremely important because there is no central foundation deciding the roadmap.

A proposal’s path through the BIP process can shape how seriously the wider community treats it.

That is why editor neutrality matters.

BIP-110 Became A Governance Flashpoint

BIP-110 was controversial because it dealt with data limits and anti-spam concerns, an area where Bitcoin users already disagree sharply.

Some users want stricter limits on certain kinds of data use. Others see those limits as censorship risk or as unnecessary interference with fee-market dynamics. The debate is not only technical. It touches Bitcoin’s identity: settlement network, data layer, censorship-resistant money, or all of the above.

When a proposal like BIP-110 becomes associated with a minority activation attempt and process disputes, the arguments escalate quickly.

Dashjr has long been a prominent Bitcoin developer and a strong voice on spam and data policy. That made the editor-role conflict even more sensitive.

The editor removal is therefore less about one document and more about whether the BIP process is seen as neutral.

The Minority Chain Did Not Threaten Bitcoin

The stalled minority chain is a useful piece of context, but it should not be overstated.

A breakaway chain with minimal hashpower does not become Bitcoin simply because it shares some history or branding. Bitcoin’s economic network is determined by users, nodes, miners, exchanges, wallets, merchants, and liquidity choosing which rules to recognize.

The main Bitcoin network continued operating normally.

The controversy showed rejection of one activation path, not weakness in Bitcoin’s core consensus. If anything, the episode underlines how hard it is to push rule changes without broad support.

That has always been one of Bitcoin’s defining features.

Bitcoin Governance Is Messy By Design

Bitcoin governance often looks chaotic from the outside.

There are no CEOs. There is no formal board. There is no official roadmap vote. Developers can propose. Users can reject. Miners can signal. Node operators can ignore. Exchanges can decide what they list. The process is social, technical, and economic all at once.

That messiness is intentional.

It makes Bitcoin hard to steer, but also hard to capture. Changes need overwhelming legitimacy because no single person can force the network to move.

The Dashjr removal shows that even process roles are subject to community pressure when trust breaks down.

What This Means Going Forward

The immediate effect is simple: Dashjr is no longer listed as a BIP editor.

The broader effect is that Bitcoin’s technical community will likely be more careful around conflicts of interest, editor discretion, and controversial soft-fork proposals. That does not mean anti-spam debates are over. They will continue because the underlying disagreement has not disappeared.

But future proposals may face even more scrutiny around process.

That may feel slow and frustrating. It is also how Bitcoin preserves credibility.

Bitcoin governance is not clean, but it is resilient. The network rejected the disputed path, the BIP repository changed its editor list, and the main chain kept moving.

That is Bitcoin governance in practice.

This article is based on the merged Bitcoin BIPs repository change removing Luke Dashjr from the BIP editor list.

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

This report is based on information released by Github. at Github

ENS Labs has revised a governance proposal after delegate criticism over treasury control, choosing to keep the DAO’s primary operational wallet custody in place rather than moving broader control to the Foundation.

According to the validated notes, the revised plan scraps the more contentious transfer of the DAO’s operational wallet, which includes ETH and stablecoins. The DAO retains custody, while only the $65 million Endowment Safe is set to transition to the Foundation, subject to a timelock and Security Council cancellation rights.

The DAO’s 54.6 million ENS tokens remain with tokenholders, while the Foundation would receive a 1 million ENS grant vesting over multiple years.

This is not the flashiest governance story, but it is an important one. ENS is trying to balance professional execution with decentralized control, and the delegate pushback shows that the community is still willing to draw lines around treasury authority.

For more details, visit the official Discuss platform.

TL;DR

• ENS Labs revised a treasury-control proposal after delegate criticism.
• The DAO retains custody of its primary operational wallet.
• The $65 million Endowment Safe can move to the Foundation, with timelock and Security Council safeguards.

Why Treasury Control Gets Sensitive Fast

DAO treasury debates can become emotional because they sit at the heart of governance legitimacy.

A DAO may want a foundation or operating company to move faster, manage resources professionally, sign contracts, pay vendors, hire staff, and handle legal responsibilities. Those are real needs. Pure tokenholder voting can be slow and awkward for day-to-day operations.

But if too much treasury control moves away from the DAO, delegates may worry that governance becomes symbolic.

That is the tension ENS Labs ran into.

The revised proposal appears to acknowledge that professional management has value, but that primary operational wallet custody is too sensitive to move without broader comfort.

That is a reasonable governance compromise.

The Endowment Safe Is A Different Question

The $65 million Endowment Safe is still expected to transition to the Foundation under the revised plan, according to the validation notes.

That makes sense as a narrower operational change.

An endowment can be managed with a long-term mandate, specific oversight, and defined controls. Moving an endowment safe is different from moving the DAO’s primary operating wallet, especially if the transfer comes with a timelock and cancellation rights.

The Security Council safeguard is important because it gives the DAO a way to respond if a governance action is considered malicious or dangerous during the execution window.

That does not eliminate all risk, but it reduces the fear that control shifts permanently without recourse.

The ENS Token Treasury Remains With Holders

The DAO’s 54.6 million ENS tokens remaining with tokenholders is another key point.

Governance tokens are not just assets on a balance sheet. They represent voting power and long-term control over the protocol’s direction. Moving them into a more centralized structure would have created a much larger governance debate.

The revised structure avoids that.

Instead, the Foundation receives a 1 million ENS grant that vests over multiple years. That gives the Foundation resources, but it does not move the full token treasury out of DAO control.

For delegates, that kind of vesting structure can feel more accountable. It gives an operating entity funding while maintaining a timeline and limiting immediate control.

Delegate Pushback Worked As Designed

The healthiest part of this story may be that pushback changed the proposal.

DAO governance often gets criticized for being performative. Proposals appear, delegates comment, and outcomes sometimes seem predetermined. When feedback actually changes the structure, it shows governance is doing something useful.

ENS delegates raised concerns, and ENS Labs revised the plan.

That is how a serious DAO should function. Not every criticism needs to win, but major treasury changes should be tested hard before approval.

This is especially true for a protocol like ENS, which provides core naming infrastructure across Ethereum and the broader crypto ecosystem. Its governance model needs to maintain trust among tokenholders, builders, users, and institutions.

Professionalization Without Capture

The broader ENS debate is really about professionalization.

Crypto protocols often begin as communities and then discover they need operating structures. Foundations, labs teams, service providers, and working groups emerge because someone has to do the work.

The danger is that operational efficiency can drift into centralization.

The revised ENS proposal tries to avoid that by keeping the DAO’s core treasury control intact while still giving the Foundation a clearer role around the endowment and long-term operations.

That may not satisfy everyone. Some will want more decentralization. Others will want faster execution. But the compromise is a sign that ENS governance is maturing.

A DAO does not need to choose between chaos and central control. It can build guardrails, delegate responsibilities, and still preserve the community’s authority over the assets that matter most.

This article is based on ENS governance materials related to the revised Foundation treasury proposal.

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

This report is based on information released by Discuss. at Discuss

Uniswap governance has activated a protocol fee switch on v4 liquidity pools, pushing protocol revenue higher and directing collected fees toward UNI buy-and-burn mechanics rather than direct distributions to tokenholders.

The validated notes point to Uniswap Governance Proposal 100 passing with about 46.6 million votes in favor and roughly 1.27 million opposed. The mechanism collects around one-sixth of swap fees into TokenJar contracts, which are then used to buy and burn UNI.

Daily protocol revenue has reportedly risen to about $325,000 from a prior run rate near $114,000. The activation spans seven networks: Ethereum, Arbitrum, Base, BNB Chain, Polygon, OP Mainnet, and Robinhood Chain.

That is a meaningful governance shift, but the nuance matters. UNI holders are not receiving fee checks. The mechanism is about token burn and protocol value capture.

For more details, visit the official Governance platform.

TL;DR

• Uniswap governance has activated a v4 protocol fee switch.
• Fees flow into TokenJar contracts to buy and burn UNI.
• The mechanism boosts protocol revenue, but does not directly distribute fees to UNI holders.

Why The Fee Switch Has Always Mattered

The Uniswap fee switch has been one of DeFi’s longest-running governance debates.

Uniswap is one of the most important decentralized exchanges in crypto, but for years the core question around UNI has been awkward: how does the token capture value from the protocol’s activity?

Liquidity providers earned fees. Traders used the product. The protocol became essential infrastructure. But UNI governance had to move carefully around any mechanism that would redirect fees, affect LP incentives, or create legal and market-structure concerns.

That is why this activation matters.

It shows Uniswap governance moving from theory into a more active value-capture model, at least for v4 pools and within the defined structure.

This is not a casual parameter change. It is part of the long debate over whether DeFi tokens can represent more than governance rights.

Burn Is Different From Distribution

The most important distinction is burn versus distribution.

If fees were paid directly to UNI holders, that would create one kind of economic and regulatory conversation. A buy-and-burn mechanism creates another. In this setup, collected protocol fees are used to buy UNI and remove it from circulation.

That can support token economics by reducing supply, but it is not the same as paying holders income.

Markets often blur those lines, especially when fee-switch headlines appear. But readers should be precise. UNI holders are not being handed swap fees. The mechanism routes value through buybacks and burns.

That may still matter a lot for UNI’s market narrative, but it works differently from dividends or staking rewards.

LPs Still Need To Watch The Details

Fee switches always raise the same concern: what happens to liquidity providers?

If a protocol takes too much from swap fees, LP returns could decline, and liquidity may move elsewhere. If the take is too small, protocol revenue may not be meaningful. The balance is delicate.

The validated notes say LP yields are not reduced by this fee because the fees are additive to swap fees, but the market will still watch how liquidity responds over time.

DeFi liquidity is mercenary when incentives weaken. If LPs feel they are worse off, they can move capital to other pools, other DEXs, or other chains.

Uniswap’s strength is its brand, routing, integrations, and liquidity depth. But fee design still matters because DEX competition remains intense.

v4 Makes The Timing More Interesting

Uniswap v4 is designed to be more flexible than earlier versions, especially through hooks and more customizable pool logic.

That makes the fee switch more interesting because governance is not just turning on an old idea. It is doing so inside a newer architecture where pool design, fee behavior, and execution paths can become more varied.

The activation across multiple networks also reflects where Uniswap is now.

It is no longer just an Ethereum mainnet DEX. It is a multi-chain liquidity system spanning major Layer 2s and newer environments. Applying protocol revenue mechanics across those networks gives governance a broader base to work with.

That also makes reporting harder, because revenue, liquidity, volume, and user behavior can differ widely from chain to chain.

A Real Test For UNI Economics

The bigger question is whether this changes how investors think about UNI.

For years, UNI has traded partly on Uniswap’s importance and partly on the possibility of future value capture. Now, with buy-and-burn mechanics activated for v4 pools, the market has something more concrete to measure.

Does protocol revenue continue rising?

Does liquidity stay healthy?

Do burns become meaningful relative to supply?

Does governance expand the mechanism over time?

Do users or LPs change behavior?

Those are the questions that matter more than the first-day revenue figure.

Uniswap remains one of DeFi’s most important protocols. The fee switch activation gives UNI a clearer economic story, but it also creates a new standard for governance execution.

The token now has a more visible value-capture mechanism. The next test is whether that mechanism can scale without harming the liquidity that made Uniswap important in the first place.

This article is based on Uniswap governance materials and related protocol revenue data.

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

This report is based on information released by Governance. at Governance

Reference: Aave Governance

Aave Picks Chainlink CCIP As Default Standard For Cross-Chain sGHO

Aave governance has moved to make Chainlink CCIP the default standard for cross-chain sGHO transfers, reinforcing the role of security-focused infrastructure in DeFi’s next phase.

The Aave governance proposal focuses on launching sGHO cross-chain and using Chainlink’s Cross-Chain Interoperability Protocol as the default option. The wider Delivery Infrastructure, known as a.DI, still uses a multi-bridge architecture for redundancy, but CCIP is positioned as the standard route for this specific cross-chain flow.

That distinction matters.

DeFi has spent years learning that bridges are one of the most sensitive parts of the stack. Cross-chain systems can unlock liquidity and improve user experience, but they also introduce risk. Aave’s decision shows that major protocols are increasingly treating cross-chain communication as a security decision, not just a convenience feature.

TL;DR

• Aave governance has selected Chainlink CCIP as the default standard for cross-chain sGHO.
• The proposal sits inside Aave’s broader a.DI cross-chain infrastructure.
• The move highlights DeFi’s growing focus on secure cross-chain messaging.

Why Cross-Chain Infrastructure Matters For Aave

Aave is one of DeFi’s most important lending protocols.

As DeFi spreads across multiple networks, Aave needs infrastructure that can move information and value safely between chains. That is especially important for GHO and sGHO, where liquidity, accounting, governance, and risk controls have to remain consistent across environments.

Cross-chain expansion is useful, but it is also dangerous if handled poorly.

Many of crypto’s largest exploits have involved bridges or cross-chain infrastructure. The reason is simple: bridges often sit between different consensus systems, custody models, liquidity pools, and message-passing mechanisms. If something goes wrong, the losses can be large and fast.

For a protocol like Aave, the bridge standard is therefore not a minor technical choice.

It affects user trust, governance execution, stablecoin liquidity, and the way the protocol expands beyond one network.

Why Chainlink CCIP Was Chosen

Chainlink has positioned CCIP as a security-first cross-chain messaging and transfer standard.

The pitch is that major protocols need more than a basic bridge. They need risk controls, decentralized oracle infrastructure, and a model that can support large-scale cross-chain communication without relying on a single fragile route.

Aave’s proposal reflects that direction.

Using CCIP as the default route for sGHO suggests Aave wants a standard that can support cross-chain expansion while reducing operational risk. At the same time, the validation materials make clear that the broader a.DI system remains multi-bridge. That means CCIP is not the only infrastructure in the architecture, and alternative bridges are not simply being switched off.

That is the right nuance.

In complex DeFi systems, redundancy matters. A default route can provide consistency, while a multi-bridge design can help avoid dependence on one provider.

GHO Needs Stronger Distribution

The GHO stablecoin has always needed distribution to grow.

A stablecoin’s success depends on more than minting. It needs liquidity, integrations, cross-chain availability, lending demand, and confidence in how it is managed. Making sGHO easier to move across networks can help expand its utility.

That is where CCIP can matter.

If users and protocols can move sGHO more safely between chains, Aave can support broader GHO adoption without forcing activity to remain concentrated in one environment. That can improve liquidity and make GHO more useful across DeFi.

But the stablecoin market is competitive.

USDC, USDT, DAI, and newer stablecoin models already dominate much of the liquidity conversation. GHO needs clear advantages to gain share. Cross-chain accessibility is one part of that, but not the whole story.

Aave still has to build demand for GHO itself.

DeFi Is Becoming More Infrastructure-Led

The proposal also shows where DeFi is heading.

Early DeFi growth was often about yield, liquidity mining, and fast deployments. The next phase is more infrastructure-heavy. Protocols need safer cross-chain communication, more formal risk controls, better governance execution, and deeper integrations between networks.

That is a more mature market.

It may not produce the same kind of retail excitement as meme-token speculation, but it is the work required for DeFi to support larger amounts of capital.

Aave choosing CCIP as the default standard for sGHO is part of that shift. It shows that leading protocols are thinking carefully about how to expand without repeating the bridge failures of earlier cycles.

For Chainlink, the decision strengthens CCIP’s role as a core infrastructure product. For Aave, it gives sGHO a clearer cross-chain path. For DeFi users, it may eventually mean a smoother experience moving between networks.

The important point is not that every bridge problem is now solved. It is that major protocols are becoming more selective about the infrastructure they trust.

This article is based on the Aave governance forum and Chainlink CCIP materials.

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

This report is based on information released by Aave Governance. at Aave Governance

View original post on X

Michael Saylor Opposes Bitcoin BIP-110 Over Censorship Concerns

Michael Saylor has come out against Bitcoin’s BIP-110 proposal, warning that the planned soft fork could introduce censorship risks into the network.

The debate centres on whether Bitcoin should restrict certain forms of non-monetary data storage, including activity linked to Ordinals and similar uses. Supporters of tighter limits argue that Bitcoin block space should remain focused on monetary transactions. Critics argue that protocol-level restrictions could set a dangerous precedent by deciding which types of data are acceptable.

Saylor’s intervention matters because he is one of the most visible corporate Bitcoin advocates in the world. When the MicroStrategy chairman weighs into a technical governance debate, the discussion moves beyond developer circles and reaches a wider market audience.

This is not just about one proposal. It is about what Bitcoin should be allowed to carry, who gets to decide, and whether efforts to reduce spam could accidentally weaken Bitcoin’s neutrality.

TL;DR

• Michael Saylor has opposed Bitcoin’s BIP-110 proposal.
• BIP-110 seeks to limit arbitrary data storage on Bitcoin.
• Critics argue the proposal could create censorship risk and set a problematic precedent.

https://x.com/saylor/status/2078754106030649740

What BIP-110 Is Trying To Do

BIP-110, also known as the Reduced Data Temporary Softfork, is aimed at limiting non-monetary data stored on Bitcoin.

The proposal is connected to a long-running argument inside the Bitcoin community. Some users believe block space should be preserved primarily for financial transactions. Others believe Bitcoin’s rules should remain neutral, even when certain uses are unpopular or expensive.

Ordinals pushed that debate into the open. By using Bitcoin block space for inscriptions and other data-heavy activity, Ordinals created new demand for block space but also frustrated users who saw higher fees and congestion.

BIP-110 is one proposed response.

The proposal attempts to restrict arbitrary data while using miner signaling as the activation route. One of the most controversial details is the proposed 55% activation threshold, which is far lower than the traditional 95% supermajority standard often associated with major Bitcoin soft fork activation.

That lower threshold is part of why critics are uneasy.

If Bitcoin’s rules can be changed with a relatively narrow majority of miner signaling, opponents worry that the network could become more vulnerable to political, commercial, or social pressure over time.

Why Saylor’s Objection Matters

Saylor’s position is important because he has built his public reputation around Bitcoin as neutral, durable monetary infrastructure.

His criticism is not only about Ordinals. It is about whether Bitcoin should start filtering certain kinds of transactions at the protocol level. Once that door opens, the next debate becomes harder: who decides what counts as spam, abuse, or unacceptable data?

That is where censorship concerns enter the picture.

Bitcoin’s value proposition depends heavily on predictability and neutrality. Users may disagree about how the network should be used, but the protocol itself is supposed to enforce rules without caring who is transacting or why.

A rule designed to reduce unwanted data may seem harmless to some users. But to others, it creates a slippery slope. If one category of data can be restricted because enough people dislike it, future changes could target other categories.

That is why the debate has become sharper than a normal technical disagreement.

The Ordinals Fight Is Still Really About Bitcoin’s Identity

The Ordinals debate has always been bigger than JPEGs, inscriptions, or meme activity.

It asks whether Bitcoin is only money, or whether the protocol should remain open to any valid transaction that follows consensus rules. Purists argue that arbitrary data dilutes Bitcoin’s mission and makes monetary use more expensive. Neutrality advocates argue that filtering use cases damages Bitcoin’s permissionless design.

Both sides have a point.

High fees can hurt ordinary users. Spam can make the network harder to use. But protocol-level filtering is not a small fix. It changes the balance between open validation and social preference.

Bitcoin has survived partly because rule changes are difficult. That slowness frustrates people, but it also protects the network from fast-moving political or commercial pressure.

BIP-110 now sits inside that tension.

Activation Is Not Guaranteed

It is important not to overstate where this stands.

BIP-110 is not guaranteed to activate. Community support remains divided, and miner signaling would still have to reach the required threshold. Bitcoin’s governance process is deliberately difficult, and controversial proposals often fail to gain enough momentum.

That is part of the point.

For many Bitcoin supporters, the resistance to quick protocol changes is a feature, not a flaw. It means proposals must survive public scrutiny, technical review, and broad social consensus before becoming part of the network’s rules.

Saylor’s opposition adds weight to the anti-BIP-110 side of the debate, but it does not settle the issue. Developers, miners, node operators, businesses, and users will all continue to shape the outcome.

For now, the story is less about immediate activation and more about Bitcoin’s governance culture.

The network is again being forced to decide how it balances efficiency, neutrality, block space demand, and resistance to censorship. That is a hard debate, but it is also the kind of debate Bitcoin was designed to survive.

This article is based on Michael Saylor’s public statement and the BIP-110 GitHub repository.

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

This report is based on publicly available market and on-chain data. at X

Uniswap founder Hayden Adams has proposed expanding protocol fees across Uniswap v4 and several network deployments, putting one of DeFi’s longest-running governance debates back at the centre of the market.

Protocol fees are a sensitive topic for Uniswap because the exchange is one of DeFi’s most important pieces of infrastructure. It processes huge volumes, sits across multiple chains, and remains a core liquidity venue for tokens. But for years, the question has been whether that usage should translate into direct economic value for the protocol and UNI governance.

The new proposal, published through Uniswap governance, targets protocol-level fee activation across multiple deployments, including v4 pools and the newly launched Robinhood Chain.

For UNI holders and DeFi users, this is not just a technical governance item. It goes to the heart of how DeFi protocols should capture value.

Reference: Uniswap Governance Forum

TL;DR

• Hayden Adams has proposed expanding Uniswap protocol fees across several network deployments.
• The proposal includes v4 pools and Robinhood Chain activity.
• The debate matters because it could reshape how Uniswap captures value from its own trading infrastructure.

Why Protocol Fees Matter For Uniswap

Uniswap is widely used, but usage and token value have not always moved together.

That has been one of the biggest debates around UNI. The protocol is critical to DeFi, but the token has often struggled with the question of direct value capture. Governance rights matter, but investors also want to know whether protocol activity can translate into a stronger economic model.

Protocol fees are one possible answer.

If activated, a portion of trading fees can be routed to protocol-controlled mechanisms rather than flowing only to liquidity providers. That can create a clearer link between exchange activity and the protocol’s treasury, buyback/burn mechanics, or other governance-directed uses.

The details matter. Fee rates, affected pools, chain selection, and how collections are handled can all change how traders, liquidity providers, and token holders respond.

For Uniswap, the challenge is balancing value capture with liquidity competitiveness. If fees are too aggressive, liquidity may migrate. If fees are too light, token holders may see little impact.

Multi-Chain DeFi Makes The Debate Harder

Uniswap is no longer just an Ethereum mainnet protocol.

It exists across multiple networks, and v4 is designed to make liquidity architecture more flexible. That multi-chain footprint creates opportunity, but it also makes governance more complicated.

Different chains have different users, fee environments, liquidity profiles, and competitive pressures. A fee model that works on Ethereum may not work the same way on Base, Arbitrum, Optimism, BNB Chain, Robinhood Chain, or Polygon.

That is why this proposal matters. It is not only about turning on a switch. It is about deciding how Uniswap should operate as a cross-chain liquidity protocol.

The governance materials note that fee collections would be routed into TokenJars and claimed for burning through UNI bridging to mainnet. That kind of structure shows how much DeFi governance has evolved. Fee activation now involves not just a governance vote, but cross-chain accounting, collection mechanisms, and execution details.

The more networks Uniswap supports, the more important those mechanics become.

What UNI Holders Will Be Watching

UNI holders will likely focus on whether the proposal creates a clearer path for token value.

That does not mean the market will instantly reprice UNI. Governance proposals can take time, and implementation matters more than the headline. But the direction is important. If Uniswap can show a credible method for turning protocol volume into economic value, the token’s investment case becomes easier to explain.

Liquidity providers will be watching from another angle.

They want to know whether protocol fees reduce their share of trading economics and whether any fee changes make certain pools less attractive. DeFi liquidity is mobile. If LPs believe another venue offers better returns, they can move.

Users care about execution quality. If fee activation damages liquidity or worsens pricing, traders may notice. If the change is small enough to preserve competitiveness, users may barely feel it.

That is the balance Uniswap governance has to strike.

DeFi Is Moving From Growth To Value Capture

The proposal also says something bigger about DeFi’s maturity.

Early DeFi was mostly about growth: liquidity, volume, users, integrations, and TVL. Mature protocols eventually face a different question: how does that activity support long-term economics?

Uniswap is one of the clearest examples because it is both widely used and heavily scrutinised. If a protocol of its size cannot find a sustainable value-capture model, investors will keep asking difficult questions about governance tokens across the sector.

That is why this debate reaches beyond Uniswap.

Other DeFi protocols are watching the same issue. They need to reward users, keep liquidity, satisfy governance, and avoid creating regulatory problems. Protocol fees sit right at the intersection of those pressures.

For now, the proposal gives the market a fresh reason to pay attention to UNI governance. It may not settle the value-capture debate immediately, but it moves the discussion into a more concrete phase.

If approved and implemented cleanly, it could become one of the more important DeFi governance developments of the year.

This article is based on the Uniswap governance forum.

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

This report is based on information released by Uniswap Governance Forum. at Uniswap Governance Forum

NEAR Governance Vote To Scrap Gas Rebates Puts Developer Incentives Under Review 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: nEAR governance voted to scrap developer gas rebates. That gives readers something concrete to work with, rather than another vague sentiment update.

TL;DR

• NEAR governance voted to scrap developer gas rebates.
• The change affects developers who relied on protocol gas distributions.
• It raises a broader question about how chains should reward app builders.

Why This Matters Now

The timing matters because NEAR 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 NEAR.

The NEAR Angle

For NEAR, 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. NEAR stories can move quickly, especially when they touch security, 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 thedefiant.io.

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

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, 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 ethresear.ch.

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