A nonprofit once handed back roughly $500 million and dissolved itself on purpose. Here is what that taught crypto about legal structure, onchain governance and who actually holds power.

In May 2021, a nonprofit gave away 84,000 governance tokens. At the time they were worth close to $500 million.

Then it shut itself down. On purpose.

That nonprofit was the Maker Foundation. The protocol it had been stewarding is known today as Sky Protocol.

And that single decision still frames a question every onchain project eventually has to answer out loud.

Who actually runs this thing?

There are three answers in circulation. A DAO. A foundation. A company. Most people treat them as competing options.

They are not. They are layers. And the protocols that hold up under pressure tend to use all three.

DAO vs Foundation vs Company: What Actually Separates Them

Short version first.

• A DAO is a decision-making system. Token holders vote, code executes. No registered office, no signature on a lease.
• A foundation is a legal entity with no owners. It can hold IP, sign contracts, publish reports and instruct a law firm. It is not supposed to control the protocol.
• A company is a legal entity with owners. Fast, familiar, easy to hire through. It also has a boss, which is exactly the problem.

The real dividing line is not ideology. It is far more boring than that.

Who can a court sue. Who can open an account. Who signs when a vendor asks for a signature.

A DAO, on its own, cannot sign anything. That gap is the entire story.

Why a Pure DAO Leaves Token Holders Legally Exposed

Here is the part most “what is a DAO” explainers skip.

If a group acts together for profit without registering an entity, most legal systems already have a default box waiting: general partnership, or unincorporated association.

In a general partnership, members are personally liable for the group’s debts.

That is not hypothetical anymore.

In CFTC v. Ooki DAO, a federal court in California accepted that a DAO could be sued in its own name as an unincorporated association made up of its token holders.

The regulator’s position was blunt: vote your governance tokens, and you are a member.

Members of a for-profit unincorporated association can be personally liable under partnership principles.

An earlier case, Sarcuni v. bZx DAO, noted that governance token holders could be treated as members of a general partnership under California law.

Read that twice if you hold governance tokens and vote with them.

This is why “we are just a DAO, we have no entity” stopped being a flex around 2023. Governance is not a shield. Governance without a legal wrapper is exposure.

The Crypto Foundation Structure Is a Legal Wrapper, Not a Boss

Foundations exist to absorb that exposure without becoming a boss. Three shapes dominate.

• Cayman foundation company. Ownerless. Run by a small board or council, with token holders named as beneficiaries. Common for large token ecosystems holding IP and contracts.
• Swiss foundation. Strong reputation, better banking access, higher running costs.
• Wyoming DUNA. A US nonprofit association purpose-built for DAOs, effective July 1, 2024. No mandatory board. Bylaws can point directly at onchain votes. Members are shielded from the association’s debts.

The catch is honest and worth saying out loud. A foundation fixes the paperwork problem by creating a small group of humans who hold a pen. That is a genuine centralization cost.

Which is why wording matters. The footer of skyeco.com reads:

“This website is managed by Sky Frontier Foundation (SFF). The SFF is an independent entity and does not have authority over Sky Protocol, its smart contracts, or governance decisions.”

That is a foundation publicly disclaiming control over the thing it supports. Not modesty. Architecture.

The Company Model Buys Speed and Cannot Shed Control

Companies are still everywhere in crypto, for good reason. You can hire. You can sign an engagement letter. You can buy insurance.

What you cannot do is make the control disappear.

Regulators have not drawn a neat line between “the DAO” and “the dev shop.”

In token enforcement actions, legal analysts note that agencies have named any company involved with the token, development companies included.

If your company holds admin keys, your decentralization story is a marketing asset, not a legal defense.

So the pattern that actually emerged is not DAO or foundation or company. It is:

• DAO for authority
• Foundation for legal capacity
• Independent companies for execution

Three layers, deliberately kept apart.

How Sky Ecosystem Splits Authority, Publishing and Execution

Sky Ecosystem is a clean worked example, because each layer is named differently on purpose.

• Sky Governance holds authority. Staked SKY activates voting power over risk parameters, collateral types, debt ceilings and protocol upgrades. Proposals move through forum review, then onchain voting, then execution. Once executed, a change cannot be reversed directly. It can only be challenged by passing a new proposal.
• Sky Frontier Foundation publishes. Reports, disclosures, formal positions. It does not set parameters.
• Sky Agents execute. Spark, Grove, Obex, Osero and others are independent capital allocators. They access USDS liquidity under governance-set risk parameters and deploy it. They are not subsidiaries.

The naming discipline is not pedantry. It is the difference between “Sky Governance voted to change the rate” and “the foundation changed the rate.” Only one of those is true, and only one survives a regulator reading it.

Scale check. Sky Protocol currently shows roughly $14.15B in Total Collateral backing about $11.48B in stablecoin supply.

Across the wider landscape, DeepDAO data put all DAO onchain treasuries above $26B combined in Q1 2026. This is not a governance thought experiment.

Where the Sky Savings Rate, sUSDS and USDS Fit In

Structure feels abstract until it touches yield. Here is exactly where it does.

• USDS is the base stablecoin. Independent allocators draw it against governance-approved collateral.
• Sky Agents deploy that liquidity into diversified strategies and pay for the access.
• Those payments accrue as protocol revenue.
• The Sky Savings Rate is funded from it. Variable, and set by Sky Governance rather than a pricing committee.
• sUSDS is how you hold it. Supply USDS, receive sUSDS, and the position accrues automatically. No lockups, no fees to exit.

So the governance question is a yield question.

If you hold sUSDS, the rate you receive is the output of a public process with a public record of who decided what and when.

You can read the forum thread. You can read the executed spell. You can check the dashboard.

Compare that to a rate that changed because an unnamed committee met on a Tuesday.

The 2026 Shift: DAO Legal Structures Are Coming Onshore

Two things moved the conversation recently.

First, the Uniswap Foundation proposed moving Uniswap Governance into a Wyoming DUNA, named DUNI. If adopted it becomes the largest DAO using the statute.

A coalition of crypto organizations then wrote to the US Treasury asking for federal recognition of the DUNA model.

Second, credit agencies started grading governance. When S&P Global assigned Sky Protocol a B- issuer credit rating, the first ever given to a DeFi protocol, it flagged governance concentration and low voter participation as risk factors. Not code quality. Governance.

That is the real trend. Governance design is now a credit input.

And the numbers deserve honesty. Most DAO proposals draw participation in the 5% to 15% range.

An OpenZeppelin governance review found that in 17 of 23 major DAOs, the top 10 delegates held enough voting power to pass a proposal on their own.

Decentralization on paper is not decentralization in practice.

So Which Structure Should a Protocol Actually Pick?

A rough decision frame.

• Public infrastructure with a global contributor base? Foundation plus DAO.
• Distributing revenue to holders? A nonprofit DUNA will not fit. Look at LLC structures.
• Pre-launch with a small team shipping fast? A company, plus a credible plan to reduce control.
• Already decentralized and worried about member liability? A DUNA or an offshore foundation, and stop delaying.

The one answer that is clearly wrong is doing nothing and hoping the word “decentralized” holds up in court. Ooki settled that argument.

The Question Nobody Has a Clean Answer To

Here is what I keep circling back to.

The Maker Foundation dissolved itself in 2021. Sky Frontier Foundation exists today and openly disclaims authority over the protocol.

Both were the right call at the time, which suggests these structures are not permanent identities at all. They are stages.

So, a question worth arguing about below.

If a foundation’s job is to eventually make itself unnecessary, how do you tell the difference between one genuinely winding down its influence and one quietly becoming the boss?

I have a view. I would rather hear yours first.

DAO vs Foundation vs Company: Three Ways to Run the Same Thing was originally published in Coinmonks on Medium, where people are continuing the conversation by highlighting and responding to this story.

Aave governance is considering an emergency Guardian powers proposal that would allow vulnerable lending pools to be frozen quickly during active security threats, without requiring immediate public write-ups.

It is a slightly uncomfortable proposal, and that is exactly why it matters.

On one hand, DeFi users want transparency. On the other hand, publishing too much detail during an active exploit can hand attackers a roadmap. Aave contributors are trying to solve that tension: how do you act fast enough to protect users without making governance feel opaque?

The proposal does not allow guardians to seize user funds or liquidate deposits. It is about emergency freeze powers.

For more details, visit the official Governance platform.

TL;DR

• Aave governance is discussing emergency Guardian freeze tools.
• The proposal would allow faster response during active exploit situations.
• It does not give guardians power to seize deposits.

Why Emergency Tools Matter In DeFi

DeFi moves fast when things go wrong.

A bug, oracle issue, bad debt event, or market manipulation attack can escalate in minutes. Waiting for a full public governance process is not always realistic when funds are at risk.

That is why many large protocols use emergency roles.

These roles are supposed to pause, freeze, or limit certain functions while the team or DAO investigates. The difficult part is designing those powers so they are strong enough to protect users, but narrow enough that they cannot be abused.

Aave’s proposal sits right in that design problem.

Transparency Versus Security

The public-notice question is the most interesting part.

In normal conditions, users should expect clear explanations. If a market is frozen, people want to know why. They want to understand whether their funds are safe and when normal operations may resume.

During an active exploit, though, immediate disclosure can be dangerous.

If the issue is not fully contained, a public write-up may expose technical details that help attackers move faster. That is the argument behind delaying some disclosures until the threat is under control.

It is not an easy trade-off.

Aave Has To Protect A Large System

Aave is one of DeFi’s core lending protocols.

That means its risk controls matter beyond one market. Aave deployments sit across multiple chains and assets, with users relying on the protocol for borrowing, lending, collateral management, and liquidity.

Emergency response is not a side issue.

It is part of the protocol’s safety design. If governance cannot respond quickly enough, users can suffer. If emergency powers are too broad, users may worry about centralization.

Finding the middle ground is the hard part.

What The Proposal Does Not Do

The proposal should not be exaggerated.

It does not mean Aave guardians can take user funds. It does not mean deposits can be seized. It does not mean liquidations can be manually forced outside protocol rules.

The proposal is about freezing vulnerable markets during emergencies.

That distinction is important because “emergency powers” can sound scarier than the actual mechanism.

The DeFi Governance Lesson

Aave’s discussion shows how mature DeFi protocols are thinking about crisis management.

Early DeFi loved pure automation. Over time, protocols learned that some emergency controls may be necessary, especially when billions of dollars are at stake. The question is how to make those controls accountable.

The best version of this proposal would protect users during live threats while preserving post-incident transparency.

That is the balance Aave governance now has to debate.

This article draws on Aave governance materials relating to the emergency Guardian powers proposal.

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

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

Ethereum Name Service has opened discussion around an ENSv2 migration proposal that would move domain registration and renewal resolution toward a Layer-2 registry model.

The idea is pretty straightforward: ENS works, but Ethereum mainnet fees can make everyday domain actions expensive. Moving more of that activity to Layer 2 could reduce costs while keeping links back to Ethereum’s security model.

This is still an early governance stage.

The proposal is a temp check, not a completed migration. It has not passed a full executable DAO vote, and users should not treat it as already implemented. But it is a meaningful direction for one of Ethereum’s most recognizable identity systems.

For more details, visit the official Discuss platform.

TL;DR

• ENS is discussing an ENSv2 migration toward a Layer-2 registry.
• The proposal aims to reduce registration and renewal costs.
• It is an early governance discussion, not an implemented migration.

Why ENS Needs Lower Costs

ENS is one of Ethereum’s simplest consumer products.

Instead of using long wallet addresses, users can register readable names. That makes wallets easier to share, payments easier to understand, and identity easier to build across apps.

The problem is cost.

When Ethereum mainnet fees rise, simple actions like registering, renewing, or managing names can become annoying or expensive. That limits how broadly ENS can be used, especially for smaller users.

A Layer-2 registry model could help by moving more routine activity onto cheaper infrastructure.

Keeping Ethereum Security In The Picture

The challenge is not just moving to L2.

ENS has to preserve the trust assumptions that made it valuable in the first place. Users want lower fees, but they also want confidence that names remain secure, durable, and connected to Ethereum’s settlement layer.

That is why the proposal matters.

It is trying to find a balance between cheaper user actions and strong security proofs. If that balance works, ENS could become easier to use without losing the trust that comes from being rooted in Ethereum.

Governance Comes First

ENS is governed by a DAO, so major changes need community discussion and approval.

The current proposal is still in the early discussion phase. That means delegates, users, developers, and service providers can debate trade-offs before anything becomes final.

That process may feel slow, but it is important.

Name infrastructure is sensitive. If ENS changes how registration and resolution work, the ecosystem needs time to understand the implications.

Cost Savings Need Careful Wording

The proposal aims to reduce gas costs sharply, but cost-saving claims need to be tied to the final design.

Layer 2s can make transactions much cheaper, but actual savings depend on implementation, network fees, bridging assumptions, proof systems, and how users interact with the new registry.

So the right view is that ENSv2 could significantly reduce costs if adopted and implemented successfully.

It is not a guarantee today.

The Bigger Ethereum Identity Story

ENS has remained one of Ethereum’s most recognizable non-financial protocols.

It is not just about speculation. It is about identity, payments, wallets, websites, and user experience. If ENS can make names cheaper and easier to manage, it could become more useful across the Ethereum ecosystem.

That is why the L2 migration proposal matters.

It shows ENS trying to adapt to where Ethereum is going: a world where mainnet anchors security, while more user activity happens on Layer 2.

The proposal is early, but the direction makes sense.

This article draws on ENS governance materials relating to the ENSv2 Layer-2 registry migration 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

Arbitrum DAO has approved a governance proposal for ecosystem incentive programs, giving the community another chance to direct treasury resources toward growth.

The vote matters because DAO funding is one of the main ways Layer-2 networks try to keep builders, users, and liquidity engaged. Incentives can help bootstrap activity, but they also need discipline. Spend too little, and promising projects may leave for better-supported ecosystems. Spend too freely, and the treasury can disappear without lasting results.

That balance is exactly why governance decisions like this matter.

For more details, visit the official Snapshot platform.

TL;DR

• Arbitrum DAO approved an ecosystem incentive proposal.
• The vote supports community-directed funding for growth programs.
• Approval does not mean all funds are instantly spent; distribution can still be staged.

Why Incentives Matter For Arbitrum

Layer-2 networks compete hard for attention.

Developers can choose between Arbitrum, Base, Optimism, Polygon, zkSync, Starknet, and others. Liquidity can move quickly. Users often follow rewards, apps, and trading opportunities.

In that environment, incentives are a tool.

They can encourage protocols to launch, deepen liquidity, attract users, and test new markets. For Arbitrum, a well-designed incentive program can help strengthen the ecosystem without relying only on organic growth.

But incentives are not magic.

They work best when they support apps that can survive after rewards slow down.

DAO Governance Is The Real Story

The important part is not just the funding.

It is the governance process. Arbitrum’s DAO gives token holders and delegates a role in deciding how ecosystem resources are used. That makes funding decisions more transparent, but also more political.

Different stakeholders may disagree on where incentives should go.

Some may want DeFi liquidity. Others may want gaming, infrastructure, grants, developer tools, or regional growth. A proposal approval shows where the DAO landed this time, but it also adds to the wider debate over treasury management.

Approval Is Not The Same As Instant Spending

This is where the wording needs care.

A governance approval does not necessarily mean every token is immediately distributed. Programs can involve staged allocations, milestones, oversight, reporting requirements, or follow-up processes.

That distinction matters because DAO headlines often make funding sound simpler than it is.

The balanced read is that Arbitrum DAO has approved the direction of an ecosystem incentive program. The real test comes in execution.

Incentives Need Measurable Results

The market has become more skeptical of token incentives.

In the last cycle, many ecosystems paid heavily for temporary activity. Users arrived for rewards, farmed the incentives, and left when the program ended. That kind of growth looks good on a dashboard until it disappears.

Arbitrum’s challenge is to fund activity that sticks.

That means looking at retention, liquidity depth, developer output, protocol revenue, user activity, and whether funded projects continue growing without constant subsidies.

What This Means For ARB

For ARB holders, governance activity can be a double-edged signal.

On one hand, a busy DAO can support ecosystem growth and make the token more relevant. On the other hand, treasury spending must be handled carefully, because poor allocation can weaken confidence.

The approval shows Arbitrum is still actively using governance to compete.

Now the community will need to prove that the incentives lead to something durable.

That is the real story: not just passing the vote, but making the spending matter.

This article draws on Arbitrum DAO Snapshot governance materials.

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

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

BNB Smart Chain is preparing to activate its Pasteur hard fork on mainnet on August 25 at 02:30 UTC.

The upgrade introduces several network changes, including BEP-682 for bridge verification, BEP-695 for validator governance, and BEP-675 for block processing capacity. Node operators are required to update their software client to version 1.7.7 and remove the EnableBAL setting.

The timing matters.

At the time of the source materials, the upgrade was scheduled but not yet completed. It should not be described as already live until the activation has occurred.

TL;DR

• BNB Smart Chain’s Pasteur hard fork is scheduled for August 25 at 02:30 UTC.
• The upgrade includes BEP-682, BEP-695, and BEP-675.
• Node operators need to update to client version 1.7.7.

Why Pasteur Matters

BNB Chain is one of the largest smart contract ecosystems by user activity.

That means hard forks are operationally important. Validators, node operators, exchanges, wallets, developers, and infrastructure providers need to coordinate around the upgrade to avoid service disruptions.

Pasteur introduces changes across bridge verification, validator governance, and block processing.

Those are not cosmetic upgrades. They touch infrastructure areas that affect security, performance, and network operations.

Bridge Verification Gets Attention

BEP-682 focuses on bridge verification.

Bridge security remains one of the biggest issues in crypto. Cross-chain infrastructure has historically been a major attack surface, and ecosystems have had to improve how they verify and secure bridge-related activity.

A proposal focused on bridge verification fits that broader trend.

BNB Chain is trying to strengthen the infrastructure around cross-chain movement, which is essential for a network with wide DeFi and exchange-connected usage.

Validator Governance Also Changes

BEP-695 introduces validator governance changes.

Validator governance determines how network operators participate in decisions and how the chain evolves operationally. Changes in this area can affect decentralization, upgrade coordination, and long-term network control.

For users, validator governance may feel distant.

But it shapes the network’s resilience. A chain with poor validator coordination can struggle during upgrades, security events, or performance stress.

That is why BEP-695 belongs in the upgrade conversation.

Block Processing Capacity Is The Performance Piece

BEP-675 targets block processing capacity.

This is the kind of change users may eventually feel through throughput, reliability, or network responsiveness. BNB Chain handles high transaction activity, so processing capacity remains a practical concern.

Performance upgrades can help the ecosystem support more applications, more users, and more transaction types.

But the impact should be judged after activation, not before.

Node Operators Have Work To Do

The operator instructions are clear.

Nodes need to update to version 1.7.7 and remove the EnableBAL setting. Upgrade coordination is one of the most important parts of a hard fork. If too many operators fail to update, networks can face instability or temporary disruption.

That is why scheduled hard forks are communicated in advance.

The market should watch whether activation proceeds smoothly on August 25.

What Comes Next

The next milestone is mainnet activation.

If Pasteur goes live without problems, BNB Chain will have completed another infrastructure upgrade across bridge, governance, and processing layers. If issues emerge, developers and validators may need to respond quickly.

For now, the story is preparation.

BNB Smart Chain has a scheduled hard fork, clear operator requirements, and several meaningful BEPs bundled into the upgrade.

This article is based on BNB Chain materials regarding the Pasteur hard fork.

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.

Solana validators have begun voting on SGP-0003, a governance proposal that would restructure parts of the network’s fee model and potentially increase daily SOL burns.

The vote opened on August 23 and runs through Epoch 1023, which is expected to conclude on August 27. The proposal introduces a variable, resource-based transaction fee that would be burned in full, replacing the current flat-fee model for the affected resources.

If approved, the change is projected to increase daily SOL burns from roughly 650 SOL to between 7,500 and 9,000 SOL.

That is a major token-economics proposal, but it is not active yet.

The vote is ongoing. SOL has not become deflationary because of the proposal, and the network’s supply dynamics have not yet changed.

TL;DR

• Solana validators are voting on SGP-0003.
• The proposal would introduce a fully burned resource-based fee.
• Projected daily burns could rise from about 650 SOL to 7,500–9,000 SOL if approved.

Why Fee Burns Matter

Solana is known for speed and low transaction costs.

But high activity does not automatically mean strong token capture. Investors and validators often debate how network usage should feed into SOL’s long-term economics.

Fee burning is one way to connect activity with supply dynamics.

If more fees are burned when more resources are consumed, the network creates a clearer link between usage and token scarcity. That does not guarantee price appreciation, but it can make the economic model easier to understand.

That is why SGP-0003 is getting attention.

Resource-Based Fees Could Change Incentives

A resource-based fee model is more flexible than a flat-fee structure.

Different transactions can place different demands on the network. A variable fee model can better reflect the cost of consuming specific resources. Burning those fees in full then removes that amount of SOL from circulation.

The design aims to make heavy usage more economically meaningful.

But there are trade-offs. Validators, users, developers, and applications all care about fee predictability. Solana’s low-cost user experience has been part of its appeal, so any fee redesign must avoid undermining that advantage.

Validator Voting Is The Key Step

The proposal is now in the hands of validators.

That matters because Solana governance depends on validator participation and network coordination. A proposal can look attractive on paper, but it still needs support from those responsible for running the network.

If SGP-0003 passes, attention will move to implementation.

If it fails, Solana’s fee and supply debate will continue in another form.

Either way, the vote shows that token economics are becoming a more active governance topic for the network.

Do Not Call SOL Deflationary Yet

The projection of 7,500 to 9,000 SOL burned per day is eye-catching.

But it is conditional. It depends on approval, implementation, network usage, and how the fee mechanism works under real conditions. It should not be described as an existing burn rate.

Nor should it be used to claim SOL is already deflationary.

A network’s supply profile depends on issuance, burns, staking dynamics, and activity. Fee burning is one part of the equation.

What Comes Next

The voting window through August 27 will decide whether SGP-0003 moves forward.

If validators approve it, Solana’s community will watch how quickly the change can be implemented and whether real burn levels match projections. If not, the proposal may be revised or replaced.

For now, Solana is having the kind of economic debate mature networks eventually face.

The chain has proven it can handle activity. Now validators are deciding how that activity should affect SOL’s supply mechanics.

This article is based on Solana governance materials related to SGP-0003.

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.

Optimism governance has approved the reallocation of 546.9 million OP tokens from user airdrop reserves into a Strategic Ecosystem Fund managed by the Optimism Foundation.

The tokens are valued at roughly $49 million, according to the validated governance trail. The proposal passed with support from core development delegate Test in Prod and shifts capital toward strategic partnerships and ecosystem incentives.

That is a major governance decision.

But it should be framed precisely. Optimism has not necessarily terminated all user reward initiatives. The vote reallocates a large pool of tokens away from generalized future airdrops and toward a more targeted ecosystem strategy.

TL;DR

• Optimism approved moving 546.9 million OP into a Strategic Ecosystem Fund.
• The tokens were previously tied to user airdrop reserves.
• The move shifts incentives toward strategic partnerships and ecosystem growth.

Why The Reallocation Matters

Airdrops have been one of the defining features of crypto growth.

They reward users, bootstrap communities, and distribute governance tokens. But they can also attract short-term farming, low-quality activity, and users who leave once rewards stop.

Optimism now appears to be adjusting that balance.

By moving a large amount of OP into a Strategic Ecosystem Fund, governance is signaling that targeted partnerships and ecosystem investments may deliver more value than broad user distributions.

That is a meaningful shift in incentive philosophy.

The Foundation Gets More Strategic Firepower

A Foundation-managed fund gives Optimism more direct resources to support growth.

Those resources can be used for partnerships, integrations, developer incentives, institutional relationships, infrastructure, and ecosystem programs. In theory, this can help Optimism compete more effectively against other L2 ecosystems.

But it also centralizes more decision-making.

Token holders may support that if the fund produces measurable growth. They may criticize it if spending becomes opaque or if community users feel excluded from future rewards.

That is the governance trade-off.

Airdrops Are Losing Some Shine

The broader market has become more skeptical of airdrops.

Early airdrops created loyal communities and strong narratives. Later airdrops often became heavily farmed. Users created wallets, performed minimal activity, claimed tokens, and sold quickly.

That made airdrops less efficient as long-term growth tools.

Optimism’s move reflects that changing environment. Instead of distributing tokens broadly and hoping usage sticks, the ecosystem is shifting some resources toward strategic deployment.

The question is whether that produces better retention.

Do Not Overstate The End Of Rewards

The vote should not be described as Optimism killing all user rewards.

The governance action affects a large reserve allocation, but it does not prove every user incentive program is gone forever. Ecosystems can still use targeted grants, liquidity incentives, developer programs, quests, or other reward mechanisms.

The clean framing is that Optimism is moving a major token pool away from future generalized airdrops and into a Foundation-run strategic fund.

That is already significant enough.

What Comes Next

The next test is execution.

How will the Strategic Ecosystem Fund allocate capital? Which partners or programs receive support? How transparent will reporting be? Will the shift drive measurable usage, developer activity, TVL, revenue, or Superchain adoption?

Those are the metrics that will decide whether the move looks smart.

For now, Optimism governance has made a clear choice: fewer broad airdrop reserves, more strategic ecosystem capital.

That may be the direction more mature crypto networks take as incentive programs become more professional and less purely community-distribution driven.

This article is based on Optimism governance materials related to the Strategic Ecosystem Fund proposal.

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.

Solana validators are moving toward a vote on a governance package designed to reduce SOL issuance pressure through resource-based fee burning and faster inflation reduction.

The package includes SGP-0003, combining SIMD-0553 and SIMD-0550. SIMD-0553 introduces a resource-fee burn mechanism, while SIMD-0550 would accelerate Solana’s inflation reduction path toward a 1.5% terminal rate by 2029.

The validator vote is scheduled to open on August 23.

That makes this a proposal story, not a completed supply change.

SOL has not suddenly become deflationary. Supply has not already been materially reduced. But the proposals show that Solana’s community is actively debating token economics as the network matures.

TL;DR

• Solana governance is preparing to vote on supply-related proposals.
• SIMD-0553 targets resource-fee burns.
• SIMD-0550 would accelerate inflation reduction toward a 1.5% terminal rate by 2029.

Why Token Economics Matter

Solana’s performance story is well known.

The network is fast, cheap, and heavily used. But high throughput does not automatically translate into strong token economics. Investors also care about issuance, burns, validator incentives, fee capture, and long-term supply dynamics.

That is why these proposals matter.

If Solana can reduce inflation pressure while keeping validators properly incentivized, SOL’s economic model may look stronger to long-term holders.

The hard part is getting the balance right.

Fee Burning Ties Usage To Supply

A resource-based fee burn can help connect network usage to token economics.

In simple terms, if more network resources are consumed, more fees can be burned under the proposed model. That may create a clearer relationship between activity and supply pressure.

This is important because Solana has often been criticized for high usage but relatively modest fee burn compared with the amount of activity it processes.

A better burn mechanism could improve that narrative.

But design details matter. Fee markets need to protect users, validators, and network stability. Burning too much or too little can create different problems.

Faster Disinflation Is A Bigger Policy Choice

Accelerating inflation reduction is more direct.

SIMD-0550 would move Solana toward its terminal inflation rate faster, aiming for 1.5% by 2029. That may appeal to investors who want lower issuance, but it also affects validator economics and staking incentives.

Networks need validators to remain economically motivated.

If issuance falls too quickly, validator rewards may need to be supported by fees or other incentives. If it falls too slowly, holders may worry about dilution.

This is the central trade-off in proof-of-stake economics.

Vote First, Impact Later

The scheduled vote is the next milestone.

Even if validators support the package, implementation and actual economic effects will take time. Markets often react to proposals before they change fundamentals, but the real impact depends on adoption, deployment, network usage, and fee generation.

That means traders should be careful with immediate supply claims.

The proposals are important because they show Solana governance addressing long-term economics. They do not instantly change circulating supply overnight.

What Comes Next

The validator vote opening on August 23 will show how much support exists for the package.

If the proposals pass, attention will shift to implementation timing and measurable effects on issuance and burn activity. If they fail or are revised, the token-economic debate will continue.

Either way, Solana’s governance conversation is becoming more sophisticated.

The network is no longer only selling speed. It is also trying to refine how usage, fees, inflation, and supply interact.

That is the kind of debate mature chains eventually need to have.

This article is based on Solana governance materials and forum discussions around SGP-0003, SIMD-0553, and SIMD-0550.

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.

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

Aave governance is reviewing a request for final comment that would wind down six lower-adoption V3 markets and offboard dozens of reserves, as the lending protocol looks to reduce operational complexity and focus on more productive deployments.

The validated notes say the LlamaRisk proposal targets Aave V3 markets on Sonic, Scroll, zkSync, Metis, Soneium, and Aptos. It also proposes offboarding 50 low-use reserves and 21 matured Pendle Principal Tokens.

The affected markets reportedly hold $98.1 million in deposits and $15.6 million in debt, representing less than 1% of Aave deposits. They generated less than $5,000 quarterly, failing to cover oracle and monitoring costs.

That is the key point.

This is not just about usage. It is about whether maintaining small deployments is worth the operational risk and cost.

For more details, visit the official Governance platform.

TL;DR

• Aave governance is reviewing an ARFC to wind down six V3 markets.
• The proposal affects Sonic, Scroll, zkSync, Metis, Soneium, and Aptos.
• It is a governance recommendation under discussion, not a completed shutdown.

DeFi Expansion Has A Maintenance Cost

During growth phases, DeFi protocols expand aggressively.

They deploy on new chains, add reserves, support new assets, integrate partner ecosystems, and chase users wherever liquidity appears. That can be smart when the goal is reach. But every deployment adds maintenance.

A lending market needs risk monitoring, oracle support, parameter updates, liquidity oversight, liquidation infrastructure, governance attention, and emergency response capability.

If a market is barely used, those costs may outweigh the benefit.

Aave’s proposed cleanup reflects a more mature phase of DeFi. The protocol is not simply asking where it can deploy next. It is asking where it should remain deployed.

That is a healthier question.

Small Markets Can Create Big Risk

A low-adoption market may sound harmless, but it can still create risk.

Thin liquidity can make liquidations harder. Low revenue can fail to justify oracle or monitoring expenses. Smaller markets may receive less attention from risk teams and governance participants. Exotic reserves can create unexpected parameter problems.

If something breaks, the protocol’s brand still takes the hit.

That is why offboarding low-use reserves can make sense even if the headline deposit amount is not huge.

Aave is one of DeFi’s most important lending protocols. Its risk posture matters because users treat it as core infrastructure. Carrying too many small, low-revenue deployments can make the system harder to manage.

The Numbers Explain The Proposal

The reported figures are useful because they show the economic mismatch.

$98.1 million in deposits and $15.6 million in debt may sound meaningful in isolation, but if that is less than 1% of Aave deposits and generates under $5,000 per quarter, the case for continued support becomes weaker.

Protocols need to prioritize.

Oracle costs, engineering time, governance bandwidth, monitoring tools, and risk analysis all have limits. If resources are tied up supporting low-productivity markets, they are not being used to strengthen the core.

This is not necessarily negative for the affected chains. It may simply mean Aave’s deployment did not reach the scale needed to justify ongoing support.

Users Need A Clear Wind-Down Path

The user experience is the most important part of any market closure.

Borrowers need time to repay or migrate. Depositors need clear instructions. Liquidation risk needs to be controlled. Governance needs to avoid abrupt changes that trap users or create unnecessary losses.

That is why the ARFC process matters.

A recommendation under discussion gives the community time to review the plan before final execution. It also gives affected users advance notice.

The worst version of a market wind-down is sudden and confusing. The better version is gradual, transparent, and parameterized.

Aave’s governance process is designed to support the second version.

Aave Is Choosing Focus Over Footprint

The broader message is that DeFi protocols may be entering an era of focus.

More chains does not always mean more value. More assets does not always mean better markets. More deployments can create complexity that eventually needs to be cleaned up.

For Aave, focusing on larger, more productive markets could strengthen the protocol over time.

It may disappoint users on smaller deployments, but it can make the overall system easier to secure and manage.

The proposal is still under discussion, so it should not be framed as final. But the direction is clear: Aave is reviewing where its lending markets actually justify the cost of support.

That kind of discipline is what mature DeFi governance looks like.

This article is based on Aave governance and LlamaRisk materials related to the proposed V3 market wind-down.

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

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

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

BonkDAO’s treasury has reportedly been drained of approximately $20 million after a malicious governance vote passed through Realms, creating one of the clearest recent examples of DAO governance risk on Solana.

The exploit did not involve a failure of the Solana blockchain itself. Instead, the validated materials point to a governance attack that used voter weight mechanics to pass a proposal and move treasury assets.

That distinction matters.

Smart contract exploits often get the attention, but governance attacks can be just as damaging. If an attacker can manipulate voting power, proposal rules, or treasury permissions, the outcome can look perfectly valid on-chain while still being malicious in substance.

For Solana DAOs, the incident is a warning that governance design needs the same level of scrutiny as code security.

TL;DR

• BonkDAO treasury assets were drained after a malicious Realms governance proposal.
• The reported loss was about $20 million.
• The incident reflects DAO governance risk, not a Solana base-layer failure.

Governance Can Be An Attack Surface

DAOs often focus on decentralization, participation, and community control.

Those values matter, but governance systems can also become attack surfaces. A treasury controlled by token voting or delegated voting is only as safe as the rules governing proposals, quorum, voter weight, timelocks, and execution permissions.

If those rules are weak, attackers may not need to hack the contract directly.

They can use the governance process itself.

That appears to be the concern in the BonkDAO incident. A malicious proposal passed through governance mechanics and resulted in treasury funds being moved. From a technical point of view, the action may have followed the system’s rules. From a governance point of view, it was destructive.

That is what makes DAO attacks difficult.

They blur the line between exploit and illegitimate governance action.

Why Realms Matters

Realms is widely used in the Solana ecosystem for DAO governance.

It gives projects tools to manage proposals, voting, treasuries, and community decision-making. That makes it important infrastructure, but also means incidents involving Realms-based DAOs get wide attention.

The BonkDAO drain does not mean Realms itself failed as a platform. The validated materials point to voter weight and proposal mechanics inside the DAO setup. But the incident will likely push other Solana DAOs to review their configurations.

That review should include quorum thresholds, voting periods, treasury execution limits, emergency pause powers, and how voting weight is calculated.

The lesson is simple: governance defaults are not enough.

A DAO with a valuable treasury needs defensive design. It needs enough decentralization to be legitimate, but enough safeguards to prevent hostile capture.

BONK’s Community Faces A Trust Test

BONK has become one of Solana’s most recognizable meme assets, and BonkDAO has played an important role in its ecosystem identity.

A major treasury drain therefore creates a trust problem.

Community members will want to know how the vote passed, whether funds can be recovered, whether any accounts or delegates were compromised, and what reforms will prevent a repeat. Traders will focus on whether the incident affects liquidity, incentives, and confidence around the wider BONK ecosystem.

The response matters as much as the exploit.

If the team and community provide clear transaction details, governance analysis, and a credible recovery or reform plan, confidence may recover. If the response is vague or slow, the damage can spread beyond the treasury loss.

Meme ecosystems depend heavily on community trust. A governance exploit cuts directly into that trust.

Solana Itself Is Not The Issue

The incident should not be framed as a Solana blockchain failure.

Solana processed the transactions. The problem was governance design and treasury control inside a DAO. That distinction is important because base-layer performance is different from application-level or governance-level risk.

Every major ecosystem faces this issue.

Ethereum DAOs can suffer governance attacks. BNB Chain projects can mismanage treasury permissions. Arbitrum and Optimism protocols can pass flawed proposals. Solana is not unique in that sense.

What matters is whether ecosystem projects learn quickly.

The BonkDAO incident could push more Solana DAOs to strengthen safeguards, add timelocks, review voter-weight rules, improve proposal review, and create emergency procedures.

That would be a constructive outcome from a painful event.

For now, the takeaway is clear: DAO governance is not just politics. It is security infrastructure. If treasury rules can be exploited, community assets are at risk even when the underlying blockchain works exactly as designed.

This article is based on BONK’s public statement, Solscan, and Realms proposal data.

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

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

Reference: GitHub

Cardano Van Rossem Hard Fork Moves Mainnet To Protocol Version 11

Cardano has activated the Van Rossem hard fork on mainnet, moving the network to Protocol Version 11 and marking another step in its push toward fully on-chain governance.

The upgrade went live at Epoch 644 on July 18, according to the validated release details. It requires node operators to run Cardano Node v11.0.1 or later and represents one of the most important governance milestones in Cardano’s recent history.

The key point is not just that Cardano upgraded. Networks upgrade all the time. What makes Van Rossem notable is that it was enacted through Cardano’s on-chain governance framework, rather than being handled purely through a traditional core-development process.

That makes the hard fork a test of Cardano’s Voltaire-era promise: can a major blockchain coordinate technical upgrades through formal decentralized governance without losing stability?

TL;DR

• Cardano has activated the Van Rossem hard fork on mainnet.
• The upgrade moves the network to Protocol Version 11.
• It is described as Cardano’s first hard fork fully enacted through on-chain governance.

Why Van Rossem Matters

Cardano has always taken a slower, more formal approach than many rival layer-1 networks.

That has earned it both supporters and critics. Supporters argue that Cardano’s research-heavy process makes the network more resilient. Critics argue that it slows execution and leaves the ecosystem behind faster-moving competitors.

The Van Rossem hard fork sits right inside that debate.

A mainnet protocol upgrade is not just a technical release. It requires exchanges, stake pool operators, infrastructure providers, wallets, developers, and users to align around the new version. If coordination breaks down, the network can suffer from delays, compatibility problems, or fragmentation.

Cardano’s claim is that its governance system can manage this kind of process more transparently and more formally.

By moving to Protocol Version 11 through on-chain governance, Cardano is trying to show that decision-making can be decentralized without becoming chaotic. That is the real test.

Governance Is Becoming More Than A Narrative

Crypto governance often sounds abstract until it touches the protocol itself.

Token votes, committees, proposals, and community discussions are one thing. A hard fork is another. When governance leads to a network-level upgrade, the stakes become real.

That is why this milestone matters for ADA holders and Cardano builders.

If governance works, it can give the ecosystem a clearer route for upgrades and long-term coordination. If governance becomes slow, political, or difficult to execute, critics will argue that the process is adding friction.

Cardano’s model depends on proving that formal governance can support technical progress.

Van Rossem is therefore not just about today’s code. It is about whether future upgrades can move through the system with enough legitimacy and speed.

What The Upgrade Does — And Does Not Do

The hard fork moves Cardano to Protocol Version 11, but traders should be careful not to treat it as an instant performance catalyst.

The validated materials point to Van Rossem as laying groundwork for later upgrades, including work connected to Ouroboros Leios and the Dijkstra era. That means the upgrade is more structural than immediately user-facing.

It should not be described as a sudden speed boost or a complete scaling transformation.

For users, the near-term impact may be subtle. For developers and infrastructure operators, the upgrade is more important because it updates the base layer that future improvements will depend on.

That is often how serious blockchain upgrades work. The market wants obvious before-and-after changes, but protocol development usually happens in layers.

Van Rossem is one of those layers.

ADA Market Impact Depends On Follow-Through

For ADA, the hard fork gives the market a concrete governance milestone, but price impact will depend on what follows.

Cardano needs developer activity, DeFi growth, liquidity, user adoption, and stronger application demand to turn governance progress into market momentum. A hard fork can help the long-term story, but it does not solve every adoption question on its own.

Still, it gives Cardano supporters something specific to point to.

The network has now moved a major upgrade through its governance process. If future upgrades build on that successfully, Cardano’s decentralization-first identity becomes more credible.

The risk is that the market sees the event as procedural rather than catalytic. That is fair. Protocol upgrades only matter to traders when they translate into clearer growth, better performance, or stronger ecosystem activity.

For now, Van Rossem is best understood as a governance and infrastructure milestone.

It shows Cardano continuing to build its future around formal decentralized decision-making. The next step is proving that this model can also deliver faster, more visible ecosystem progress.

This article is based on Intersect Cardano Node release materials.

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

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

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.

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

Cardano is preparing to hand over core infrastructure responsibilities to independent ecosystem teams, marking a significant step in the network’s long-running shift toward decentralized governance.

The transition is expected to begin in August, with responsibilities moving away from Input Output Global and toward independent teams under Intersect oversight. According to the available project materials, the affected components include the Haskell node, Plutus smart contract platform, Daedalus wallet, and Hydra scaling tools.

That is not a small operational change.

Cardano has always placed governance and decentralization near the centre of its identity. The Voltaire era is meant to push that further by giving the community and ecosystem institutions more responsibility over the network’s future. But decentralization is not just a slogan. It has to work in practice.

This handover will test whether Cardano can distribute critical development responsibilities without losing coordination, quality, or momentum.

Reference: Intersect MBO

TL;DR

• Cardano core infrastructure responsibilities are set to begin moving to independent teams in August.
• The handover includes major components such as the node, Plutus, Daedalus, and Hydra tools.
• The transition is a major test of Cardano’s Voltaire-era governance model.

Decentralization Has To Become Operational

Many crypto projects describe themselves as decentralized, but core development often remains concentrated.

That is not always a bad thing in the early stages. Networks need direction, funding, engineering discipline, and accountability. But over time, a project that wants to be genuinely decentralized has to reduce dependence on a single founding company or core team.

Cardano has been moving toward that model for years.

The planned infrastructure handover matters because it shifts decentralization from governance theory into operational reality. It is one thing for token holders to vote or for a community to debate proposals. It is another thing to manage the core codebase, wallet infrastructure, smart contract tooling, and scaling components that developers and users rely on.

That is where the real test begins.

If independent teams can maintain and improve the infrastructure effectively, Cardano’s decentralization claims become stronger. If the process becomes fragmented or slow, critics will argue that the network is sacrificing execution speed for governance ideals.

Why Intersect’s Role Matters

Intersect is expected to sit at the centre of the coordination process.

That matters because decentralized development still needs structure. Someone has to coordinate teams, manage priorities, communicate with the community, and help ensure that critical work does not fall through the cracks.

The goal is not to replace one central operator with another. The goal is to create a more accountable ecosystem structure where responsibilities are distributed but still coordinated.

That is difficult.

Open-source ecosystems can be powerful, but they can also become messy. Different teams may disagree on priorities. Funding decisions can become political. Technical standards need consistency. Security reviews and release processes need discipline.

For Cardano, the handover is therefore not only about who controls the code. It is about whether the ecosystem can mature into a structure that is decentralized without becoming disorganized.

That balance is hard, but it is exactly what Voltaire is supposed to prove.

Market Impact Depends On Execution

For ADA traders, governance milestones can be difficult to price.

A successful handover could strengthen the long-term Cardano narrative. It would show that the network is becoming less dependent on IOG and more capable of sustaining itself through distributed teams and community institutions.

But the market may wait for evidence.

Traders usually want to see whether governance changes lead to more development activity, better tooling, stronger DeFi growth, more builders, or clearer ecosystem momentum. A handover by itself may be positive, but the market will judge what happens next.

That is especially true in a competitive layer-1 environment.

Ethereum, Solana, and other networks are constantly fighting for developers, liquidity, users, and institutional attention. Cardano’s governance-first approach gives it a distinct identity, but it must still produce visible progress.

The August transition could become an important step in that direction if it makes development more resilient and community-led.

The risk is that responsibilities become spread across too many groups without enough speed or accountability. That would reinforce the criticism that Cardano is thoughtful but slow.

Cardano’s Next Phase Is About Proof

Cardano’s long-term supporters will see this handover as part of the network growing up.

That reading is fair. A blockchain that wants to last for decades cannot depend forever on one founding development company. It needs institutions, processes, and independent teams that can keep the network moving.

But the next phase has to prove itself.

Users need reliable infrastructure. Developers need tools that improve. The market needs evidence that governance does not slow delivery. Intersect and the independent teams will now have to show that decentralization can be practical, not just philosophical.

That is the significance of the handover.

It is not a short-term hype event. It is a structural milestone for how Cardano wants to be run. If it works, the network’s governance model becomes more credible. If it struggles, the market will question whether decentralization has made execution harder.

For now, Cardano is entering an important test of its own design.

This article is based on Intersect and Input Output Global materials.

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

This report is based on information released by Intersect MBO. at Intersect MBO

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