Naval Ravikant and Dominic Williams Align on Push for On-Chain Governance

Naval Ravikant’s recent post on X has stirred interest across crypto circles, mainly because of how plainly he framed the issue. He argued that the habit of handing responsibility to “trusted” third parties has outlived its usefulness, describing it as a structural flaw that weakens any protocol that depends on it. His view was that governance should happen on-chain with privacy as a core feature, rather than through committees, multisigs or off-chain groups that operate on reputation.

Dominic Williams, founder of the Internet Computer, replied to say he agreed with that principle. He also stressed that achieving full autonomy in practice is far more demanding. According to him, a chain needs to be able to host heavy logic and large volumes of data natively before it can support complete automation. Williams pointed toward ICP’s governance system as an example of how these ideas work when built into the network itself. On ICP, proposals that are adopted do not wait for another group to carry them out. They are executed directly by the protocol.

The exchange arrives at a moment when many projects are reassessing how their internal decision-making works. Even platforms with large communities often fall back on multisig signers or influential off-chain groups to push through upgrades. Ravikant’s post challenges the idea that these arrangements are acceptable in systems that claim to be decentralised. His wording suggests frustration with the gap between the trustless ideals promoted by many networks and the real-world governance structures they use.

Williams added a technical layer to the discussion. He highlighted that full automation is not simply about voting on-chain. It requires the chain to be able to compute, store and execute complex actions without external help. This is where he says most networks are limited. Many chains treat governance as an off-chain coordination process that merely records votes on-chain. ICP takes a different route by embedding the operational logic into the network so that once a decision passes, the chain carries it out itself.

The interest around their comments shows how governance has become central to how users judge the credibility of a protocol. Faster block times and cheaper fees draw attention, but long-term trust often hinges on how decisions are made and who can influence them. Some developers say full automation reduces the risk of capture and keeps the rules predictable. Others warn that without thorough safeguards, automated systems can lock in errors that are hard to reverse.

Even with these cautionary views in the broader community, the point shared by Ravikant and Williams is straightforward. If decentralisation is the goal, the governance system must mirror that principle. Their comments highlight how much of the sector still operates with partial workarounds and how few networks have built the technical foundation needed for end-to-end automation.

While people may disagree on the ideal structure, the direction of travel is becoming harder to ignore. As more attention moves toward transparent and fully self-executing systems, projects that continue relying on manual intervention may face growing scrutiny from users who expect protocols to operate by their own rules rather than by the judgment of intermediaries.

Dear Reader,

Ledger Life is an independent platform dedicated to covering the Internet Computer (ICP) ecosystem and beyond. We focus on real stories, builder updates, project launches, and the quiet innovations that often get missed.

We’re not backed by sponsors. We rely on readers like you.

If you find value in what we publish—whether it’s deep dives into dApps, explainers on decentralised tech, or just keeping track of what’s moving in Web3—please consider making a donation. It helps us cover costs, stay consistent, and remain truly independent.

Your support goes a long way.

🧠 ICP Principal: ins6i-d53ug-zxmgh-qvum3-r3pvl-ufcvu-bdyon-ovzdy-d26k3-lgq2v-3qe

🧾 ICP Address: f8deb966878f8b83204b251d5d799e0345ea72b8e62e8cf9da8d8830e1b3b05f

🪙 BTC Wallet: bc1pp5kuez9r2atdmrp4jmu6fxersny4uhnaxyrxau4dg7365je8sy2q9zff6p

Every contribution helps keep the lights on, the stories flowing, and the crypto clutter out.

Thank you for reading, sharing, and being part of this experiment in decentralised media.
—Team Ledger Life

Naval Ravikant’s recent post on X has stirred interest across crypto circles, mainly because of how plainly he framed the issue. He argued that the habit of handing responsibility to “trusted” third parties has outlived its usefulness, describing it as a structural flaw that weakens any protocol that depends on it. His view was that governance should happen on-chain with privacy as a core feature, rather than through committees, multisigs or off-chain groups that operate on reputation.

Dominic Williams, founder of the Internet Computer, replied to say he agreed with that principle. He also stressed that achieving full autonomy in practice is far more demanding. According to him, a chain needs to be able to host heavy logic and large volumes of data natively before it can support complete automation. Williams pointed toward ICP’s governance system as an example of how these ideas work when built into the network itself. On ICP, proposals that are adopted do not wait for another group to carry them out. They are executed directly by the protocol.

The exchange arrives at a moment when many projects are reassessing how their internal decision-making works. Even platforms with large communities often fall back on multisig signers or influential off-chain groups to push through upgrades. Ravikant’s post challenges the idea that these arrangements are acceptable in systems that claim to be decentralised. His wording suggests frustration with the gap between the trustless ideals promoted by many networks and the real-world governance structures they use.

Williams added a technical layer to the discussion. He highlighted that full automation is not simply about voting on-chain. It requires the chain to be able to compute, store and execute complex actions without external help. This is where he says most networks are limited. Many chains treat governance as an off-chain coordination process that merely records votes on-chain. ICP takes a different route by embedding the operational logic into the network so that once a decision passes, the chain carries it out itself.

The interest around their comments shows how governance has become central to how users judge the credibility of a protocol. Faster block times and cheaper fees draw attention, but long-term trust often hinges on how decisions are made and who can influence them. Some developers say full automation reduces the risk of capture and keeps the rules predictable. Others warn that without thorough safeguards, automated systems can lock in errors that are hard to reverse.

Even with these cautionary views in the broader community, the point shared by Ravikant and Williams is straightforward. If decentralisation is the goal, the governance system must mirror that principle. Their comments highlight how much of the sector still operates with partial workarounds and how few networks have built the technical foundation needed for end-to-end automation.

While people may disagree on the ideal structure, the direction of travel is becoming harder to ignore. As more attention moves toward transparent and fully self-executing systems, projects that continue relying on manual intervention may face growing scrutiny from users who expect protocols to operate by their own rules rather than by the judgment of intermediaries.

Dear Reader,

Ledger Life is an independent platform dedicated to covering the Internet Computer (ICP) ecosystem and beyond. We focus on real stories, builder updates, project launches, and the quiet innovations that often get missed.

We’re not backed by sponsors. We rely on readers like you.

If you find value in what we publish—whether it’s deep dives into dApps, explainers on decentralised tech, or just keeping track of what’s moving in Web3—please consider making a donation. It helps us cover costs, stay consistent, and remain truly independent.

Your support goes a long way.

🧠 ICP Principal: ins6i-d53ug-zxmgh-qvum3-r3pvl-ufcvu-bdyon-ovzdy-d26k3-lgq2v-3qe

🧾 ICP Address: f8deb966878f8b83204b251d5d799e0345ea72b8e62e8cf9da8d8830e1b3b05f

🪙 BTC Wallet: bc1pp5kuez9r2atdmrp4jmu6fxersny4uhnaxyrxau4dg7365je8sy2q9zff6p

Every contribution helps keep the lights on, the stories flowing, and the crypto clutter out.

Thank you for reading, sharing, and being part of this experiment in decentralised media.
—Team Ledger Life

Naval Ravikant’s recent post on X has stirred interest across crypto circles, mainly because of how plainly he framed the issue. He argued that the habit of handing responsibility to “trusted” third parties has outlived its usefulness, describing it as a structural flaw that weakens any protocol that depends on it. His view was that governance should happen on-chain with privacy as a core feature, rather than through committees, multisigs or off-chain groups that operate on reputation.

Dominic Williams, founder of the Internet Computer, replied to say he agreed with that principle. He also stressed that achieving full autonomy in practice is far more demanding. According to him, a chain needs to be able to host heavy logic and large volumes of data natively before it can support complete automation. Williams pointed toward ICP’s governance system as an example of how these ideas work when built into the network itself. On ICP, proposals that are adopted do not wait for another group to carry them out. They are executed directly by the protocol.

The exchange arrives at a moment when many projects are reassessing how their internal decision-making works. Even platforms with large communities often fall back on multisig signers or influential off-chain groups to push through upgrades. Ravikant’s post challenges the idea that these arrangements are acceptable in systems that claim to be decentralised. His wording suggests frustration with the gap between the trustless ideals promoted by many networks and the real-world governance structures they use.

Williams added a technical layer to the discussion. He highlighted that full automation is not simply about voting on-chain. It requires the chain to be able to compute, store and execute complex actions without external help. This is where he says most networks are limited. Many chains treat governance as an off-chain coordination process that merely records votes on-chain. ICP takes a different route by embedding the operational logic into the network so that once a decision passes, the chain carries it out itself.

The interest around their comments shows how governance has become central to how users judge the credibility of a protocol. Faster block times and cheaper fees draw attention, but long-term trust often hinges on how decisions are made and who can influence them. Some developers say full automation reduces the risk of capture and keeps the rules predictable. Others warn that without thorough safeguards, automated systems can lock in errors that are hard to reverse.

Even with these cautionary views in the broader community, the point shared by Ravikant and Williams is straightforward. If decentralisation is the goal, the governance system must mirror that principle. Their comments highlight how much of the sector still operates with partial workarounds and how few networks have built the technical foundation needed for end-to-end automation.

While people may disagree on the ideal structure, the direction of travel is becoming harder to ignore. As more attention moves toward transparent and fully self-executing systems, projects that continue relying on manual intervention may face growing scrutiny from users who expect protocols to operate by their own rules rather than by the judgment of intermediaries.

Dear Reader,

Ledger Life is an independent platform dedicated to covering the Internet Computer (ICP) ecosystem and beyond. We focus on real stories, builder updates, project launches, and the quiet innovations that often get missed.

We’re not backed by sponsors. We rely on readers like you.

If you find value in what we publish—whether it’s deep dives into dApps, explainers on decentralised tech, or just keeping track of what’s moving in Web3—please consider making a donation. It helps us cover costs, stay consistent, and remain truly independent.

Your support goes a long way.

🧠 ICP Principal: ins6i-d53ug-zxmgh-qvum3-r3pvl-ufcvu-bdyon-ovzdy-d26k3-lgq2v-3qe

🧾 ICP Address: f8deb966878f8b83204b251d5d799e0345ea72b8e62e8cf9da8d8830e1b3b05f

🪙 BTC Wallet: bc1pp5kuez9r2atdmrp4jmu6fxersny4uhnaxyrxau4dg7365je8sy2q9zff6p

Every contribution helps keep the lights on, the stories flowing, and the crypto clutter out.

Thank you for reading, sharing, and being part of this experiment in decentralised media.
—Team Ledger Life

Naval Ravikant’s recent post on X has stirred interest across crypto circles, mainly because of how plainly he framed the issue. He argued that the habit of handing responsibility to “trusted” third parties has outlived its usefulness, describing it as a structural flaw that weakens any protocol that depends on it. His view was that governance should happen on-chain with privacy as a core feature, rather than through committees, multisigs or off-chain groups that operate on reputation.

Dominic Williams, founder of the Internet Computer, replied to say he agreed with that principle. He also stressed that achieving full autonomy in practice is far more demanding. According to him, a chain needs to be able to host heavy logic and large volumes of data natively before it can support complete automation. Williams pointed toward ICP’s governance system as an example of how these ideas work when built into the network itself. On ICP, proposals that are adopted do not wait for another group to carry them out. They are executed directly by the protocol.

The exchange arrives at a moment when many projects are reassessing how their internal decision-making works. Even platforms with large communities often fall back on multisig signers or influential off-chain groups to push through upgrades. Ravikant’s post challenges the idea that these arrangements are acceptable in systems that claim to be decentralised. His wording suggests frustration with the gap between the trustless ideals promoted by many networks and the real-world governance structures they use.

Williams added a technical layer to the discussion. He highlighted that full automation is not simply about voting on-chain. It requires the chain to be able to compute, store and execute complex actions without external help. This is where he says most networks are limited. Many chains treat governance as an off-chain coordination process that merely records votes on-chain. ICP takes a different route by embedding the operational logic into the network so that once a decision passes, the chain carries it out itself.

The interest around their comments shows how governance has become central to how users judge the credibility of a protocol. Faster block times and cheaper fees draw attention, but long-term trust often hinges on how decisions are made and who can influence them. Some developers say full automation reduces the risk of capture and keeps the rules predictable. Others warn that without thorough safeguards, automated systems can lock in errors that are hard to reverse.

Even with these cautionary views in the broader community, the point shared by Ravikant and Williams is straightforward. If decentralisation is the goal, the governance system must mirror that principle. Their comments highlight how much of the sector still operates with partial workarounds and how few networks have built the technical foundation needed for end-to-end automation.

While people may disagree on the ideal structure, the direction of travel is becoming harder to ignore. As more attention moves toward transparent and fully self-executing systems, projects that continue relying on manual intervention may face growing scrutiny from users who expect protocols to operate by their own rules rather than by the judgment of intermediaries.

Dear Reader,

Ledger Life is an independent platform dedicated to covering the Internet Computer (ICP) ecosystem and beyond. We focus on real stories, builder updates, project launches, and the quiet innovations that often get missed.

We’re not backed by sponsors. We rely on readers like you.

If you find value in what we publish—whether it’s deep dives into dApps, explainers on decentralised tech, or just keeping track of what’s moving in Web3—please consider making a donation. It helps us cover costs, stay consistent, and remain truly independent.

Your support goes a long way.

🧠 ICP Principal: ins6i-d53ug-zxmgh-qvum3-r3pvl-ufcvu-bdyon-ovzdy-d26k3-lgq2v-3qe

🧾 ICP Address: f8deb966878f8b83204b251d5d799e0345ea72b8e62e8cf9da8d8830e1b3b05f

🪙 BTC Wallet: bc1pp5kuez9r2atdmrp4jmu6fxersny4uhnaxyrxau4dg7365je8sy2q9zff6p

Every contribution helps keep the lights on, the stories flowing, and the crypto clutter out.

Thank you for reading, sharing, and being part of this experiment in decentralised media.
—Team Ledger Life