The Neutral Information Thesis

Web3 has a trust problem. Not the kind everyone talks about, such as smart contract exploits, rug pulls, or regulatory uncertainty. The trust problem runs deeper: we can trust on-chain data about transactions BUT we can’t trust the information and data layers available about the projects behind those transactions OR trust the algorithms/AI that describe what’s happening on-chain.

This isn't obvious yet. The ecosystem still runs on vibes, X threads, and whoever shouts loudest. But as Web3 matures. As real institutions allocate real capital. As regulators demand real answers. As builders need real data to make decisions… this information crisis will compound. And when it does, the question becomes “who do you trust to tell you what's actually happening?” and “are you actually getting the information you are looking for?”

The answer matters more than most people realize. Because the wrong answer doesn't just slow Web3 down. It holds us back from realizing the full potential and possibilities of Web3.

The Unrecognized Challenge: Process Determines Trust

Web3 data is fragmented. It's scattered across block explorers, Discord servers, X accounts, and GitHub repos. The common assumption on how to solve the fragmentation problem: Just aggregate it all in one place, and like magic that solves the problem.

That's wrong. Or rather, it misses the complexity of the problem.

Aggregation without neutral processes creates a new bottleneck. A centralized source of truth that operates on (intentional or structural) bias doesn’t create a sustainable solution - it creates a long term liability. It trades one problem for a worse one because it gives a false sense of security and kicks the can down the road.

The real problem isn't that information is hard to find. The real problem is that most sources of information lack transparent procedures for how they handle that information. They don't have published policies on conflicts and disclose how they operate. They may not explain the methodology behind their data. They may not follow consistent processes. Every decision becomes opaque. And that opacity breeds distrust.

This isn't always malice (see Hanlon’s Razor). Often it's just the absence of structure. But the result is the same: ecosystem participants can't verify whether the data they're seeing reflects reality or reflects someone's agenda. Keep in mind that we are not talking about transactions written in a blockchain. We’re talking about all the other critical data that brings context to those transactions written on-chain.

Why Neutrality Isn't Optional

Throughout my time working on open licensing and open information, I've seen how the absence of neutral processes poisons information systems. Not dramatically, but slowly, through accumulated bias and selective omission.

The lesson is simple: data infrastructure must operate on neutral principles, or it becomes a weapon.

Consider that the entire promise of Web3 is disintermediation. We’ve built systems where code, not institutions, enforces rules. But all of that falls apart if the information layer (the thing that tells you what's actually happening beyond the on-chain transaction data) operates without transparent, consistent processes.

You can't have trustless systems built on top of opaque information. It doesn’t stack properly.

Neutrality isn't a marketing position. It's a structural requirement. If Web3 is going to deliver on its premise - if it's going to create genuinely open, permissionless, verifiable systems - then the intelligence layer supporting those systems must operate on equally transparent principles.

What Neutrality Actually Means

Neutrality doesn't mean detachment. You can't build ecosystem intelligence while pretending you're not part of the ecosystem.

At The Grid, we participate in the token economy. We use crypto payment rails. We receive grants and investment via tokens. We hold tokens in our treasury. Our team members hold tokens and participate in the broader Web3 economy. We're not observers standing outside the system. We're participants within it.

This raises an obvious question: if you're participating, how can you be neutral?

The answer is procedural neutrality. We are building systems and following processes designed to eliminate bias, regardless of outcomes. It's not about what you hold or where your funding comes from. It's about whether your processes are transparent, consistent, and designed to surface truth rather than favor particular results.

Our neutrality policy lays this out explicitly. We center our work around:

• Procedural neutrality: We follow consistent principles in how we review sources of ecosystem data. Internal procedures ensure accuracy and eliminate bias.

• Outcome neutrality: We don't favor particular results. We focus on the process of review and validation, not on engineering outcomes.

• Transparency: We disclose our participation in the token economy. We publish our coverage policies. We explain our methodology.

• Awareness of potential bias: We actively work to identify and reduce bias in our collection and validation processes.

• Accepting feedback: We welcome challenges to our data and our methods.

This is fundamentally different from platforms that operate without disclosed conflicts, without consistent processes, or without mechanisms for accountability. The difference isn't what we hold. The difference is whether we're transparent about it and how our processes are designed to prevent that from distorting outcomes.

The Observer’s Paradox

The act of measuring a system changes the system. This is the Observer's Paradox in social science, the Heisenberg Uncertainty Principle in physics. You can't step outside the system to observe it without becoming part of what you're observing. That means you can never be sure if your observations changed what you are observing. 

Some people conclude from this that neutrality is impossible. If participation inevitably influences outcomes, why even try?

That's the wrong conclusion. That’s giving up. The fact that perfect detachment is impossible is exactly why procedural neutrality matters. Since we can't eliminate our influence entirely, we must build transparent processes that account for our observability. We must disclose our participation. We must follow consistent principles regardless of our own interests. We must create accountability mechanisms that catch bias when it creeps in.

The Observer’s Paradox isn't a bug. It's a design constraint. It tells us what kind of neutrality is actually achievable: not the neutrality of detachment, but the neutrality of process.

A referee in sports influences the game. Every call affects momentum, strategy, and outcome. The conclusion though is not that referees are useless. We instead conclude that referees must follow clear rules, make consistent calls, and operate transparently. The best referees aren't the ones you don't notice. They're the ones you trust to apply the rules fairly.

That's the kind of neutrality we all require for ecosystem intelligence. Not the impossible neutrality of the uninvolved observer, but the achievable neutrality of the transparent participant following consistent principles.

We actually do hope to influence the overall adoption of blockchain technologies. We are transparent that we believe in blockchain technologies and want to see their use grow in society. We believe that in order to accelerate adoption, the industry needs accurate and comprehensive data that brings additional context to what’s happening on-chain. We built our company around that thesis, and as part of building this service, we're designing processes that prevent that mission from distorting the accuracy of the data itself.

The question isn't whether we're part of the system. The question is whether our processes are designed to produce accurate data regardless of what we'd prefer that data to show. Would you even want to use an ecosystem data provider that didn’t use the very technology that it maps?

No Pay to Play: A Procedural Safeguard

One of the most important procedural safeguards in our neutrality framework is this: projects don't pay for guaranteed outcomes.

The commercial pressure to compromise data quality can be high, and so this is a fundamental part of how we are building.

Here's how it often works in other parts of the blockchain market today: a project pays a platform for "premium listing" or "featured placement" or "guaranteed coverage." The payment doesn't explicitly buy favorable data, but it creates pressure and it does explicitly buy exposure. But when this is your business model, you become reluctant to publish data that makes them look bad because it directly impacts your income stream. You start to rationalize. You find reasons to emphasize their strengths and downplay their weaknesses. The bias creeps in slowly.

We've eliminated that pressure structurally. Projects can claim their profiles at The Grid. They can submit data directly about themselves. But they don't pay us to guarantee the results of those updates. We don't sell “fast lane verification” or "featured status" that would create commercial incentives to favor certain projects.

We’re not being altruistic - we have designed our infrastructure to achieve a specific result. If our revenue depends on projects paying for favorable treatment, then our data quality will degrade over time. The commercial model and the data mission would be in direct conflict. Eventually, one has to win, and in commercial conflicts, money usually wins.

By removing that structural conflict, we protect data quality. We build our business model on providing accurate, comprehensive ecosystem intelligence, and not on selling favorable coverage to individual projects, or alternatively being very slow for anyone that doesn’t pay and charging for people to get into the “fast lane” for actual service.

This combines with our other procedural safeguards: consistent review processes, disclosed conflicts, transparent methodology, and accountability mechanisms. They self-reinforce and together create a system where the structure protects the data quality.

What Neutrality Enables

Procedural neutrality isn't just about avoiding corruption. It's about unlocking capabilities that opaque platforms can't deliver.

When you operate on transparent, consistent principles, you can:

• Compare ecosystems honestly. You can really see what’s being built in an ecosystem, instead of just simply looking at TVL.

• Track the full competitive landscape. You can map every protocol, every product, every relationship and not worry that undisclosed conflicts skew coverage or that hidden decisions favor certain projects.

• Serve regulators and institutions. When governments and traditional finance start demanding unbiased data about Web3, they won't trust sources with hidden conflicts or hidden processes. They'll need infrastructure with transparent operations.

• Become essential. Truly neutral platforms don't compete with ecosystems. They support all of them. That makes you data infrastructure, not a vendor. Infrastructure that ecosystems can build on.

• Build network effects. When projects trust your processes, they'll contribute data directly. That creates a flywheel: better data attracts more participation, which improves data quality, which attracts more trust. But this only works if the underlying processes are credible.

This is the path from "nice to have" to "can't operate without." But it only works if the neutrality is real and structural, not cosmetic...

The Difference Between Participation and Conflict

There's a critical distinction that needs to be made explicit: participating in the token economy is not the same as having structural conflicts of interest.

Holding tokens as part of treasury management doesn’t create a conflict if you build processes designed to prevent treasury management from influencing coverage. Receiving grants isn't a conflict if those grants don't create pressure to favor particular outcomes. Using crypto payment rails isn't a conflict. It's just operating in the ecosystem you serve.

The conflict arises when:

• Your business model depends on a particular narrative (ecosystem) winning

• Your funding structure creates pressure to favor certain projects over others

• You lack transparent processes for handling potential bias

• You operate without disclosed conflicts or accountability mechanisms

The difference is structure. Do you have procedures that eliminate bias? Do you disclose your participation? Do you follow consistent processes regardless of who's involved? Or do you operate in the shadows, with undisclosed interests and opaque decision-making?

That's the line. Not whether you participate, but whether your participation is transparent and whether your processes are designed to prevent it from distorting truth.

Why Now?

Web3 is at an inflection point. The experimentation phase is ending. The infrastructure phase is beginning. We're moving from "can this even work?" to "how do we make this work at scale?"

That transition demands better information. Ecosystem leaders need to understand what's being built, where resources should flow, and which projects actually deliver. Investors need reliable data, not narratives. Regulators need verifiable facts. Builders need to know where they fit in the landscape. None of that works with hidden sources operating on undisclosed conflicts.

The longer we wait to build neutral infrastructure with transparent processes and disclosed conflicts, the more entrenched the opaque sources become. The more the ecosystem learns to distrust the data layer entirely. The more we recreate the exact centralized, biased gatekeepers that Web3 was supposed to replace.

Neutrality isn't a luxury. It's the foundation. And foundations need to be laid before you build on top.

The Long Game

Building procedurally neutral data infrastructure is harder than operating in the shadows. It means disclosing your conflicts. It means building accountability mechanisms. It means following consistent processes even when they produce inconvenient results.

But it's the only model that survives contact with reality.

Because five years from now, when Web3 has integrated into everyday business and when institutions depend on this infrastructure, the platforms that matter won't be the ones that grew fastest. They'll be the ones people trust.

And trust, in information systems, comes from transparency. From processes that eliminate bias. From platforms that disclose their participation and follow consistent principles regardless of outcomes.

The neutral infrastructure thesis is simple: if you want to build something essential, build transparent processes. If you want to be trusted, disclose your conflicts and follow procedures designed to eliminate bias. If you want to be infrastructure, act like infrastructure, boring, reliable, procedurally sound. Like a utility grid, which is the origin of our name. It just works, and you trust it.

Web3 promised to remove trusted third parties. But that promise only works if the information layer doesn't become the new trusted third party operating in the shadows.

Neutrality isn't optional. It's the whole point.