Data indicates that the NEAR Foundation has seated Mert Mumtaz — co-founder and CEO of Helius, the largest remote procedure call (RPC) provider on Solana — on its Foundation Council. Three facts were made public. The appointee's identity. His corporate affiliation. The Council's stated mandate to oversee the Foundation and its most consequential decisions. Three facts were withheld. The term of appointment. The compensation structure. Any conflict-of-interest recusal policy governing a sitting executive of a competing Layer-1's infrastructure vendor. The announcement circulated in ecosystem press, not financial press. That distribution choice is itself a data point. It signals how the event's authors expect it to be classified: as ecosystem movement, not as a governance action with measurable consequences. Assumption is the adversary of verification, and the assumption here — that a personnel announcement carries no analytical weight — is precisely the assumption I intend to dismantle.
Context first. NEAR Protocol is a Layer-1 blockchain that has, over the past several cycles, repositioned its public narrative around chain abstraction and intent-based execution. The thesis is straightforward: users should not need to know which chain settles their transaction. NEAR markets itself as the coordination layer above fragmented liquidity. The NEAR Foundation is the entity that stewards the protocol's treasury, grants, and strategic direction. It operates, according to publicly available information, under a Swiss foundation (Stiftung) structure — a legal form that separates control from ownership and vests supervisory authority in a council rather than shareholders. That council is the body in question.
Helius occupies a different position in the stack. It is an RPC and developer-tooling provider on Solana. RPC nodes are the interface layer through which applications read and write to a chain. If a chain is a database, RPC providers are the query engine. Helius became one of the dominant providers in the Solana ecosystem, and its CEO, Mert Mumtaz, became a high-visibility figure in public technical discourse — a voice with measurable reach across developer communities.
So the structural picture is this. A governance body that supervises one Layer-1 has added a decision-maker whose day job is operating critical infrastructure on a rival Layer-1. The two chains compete for the same finite pool of developers, users, and capital. There are dozens of Layer-1 and Layer-2 networks now drawing from the same small user base; this is not expansion, it is the slicing of already-scarce liquidity into fragments. When two of those fragments begin exchanging governance personnel, the analytical question is not whether it is friendly. The question is what mechanism prevents the resulting decisions from being structurally biased.
Let me state the governance mechanics precisely, because imprecision here is where most commentary fails. A foundation council is not an advisory board. It is the supervisory organ. In the Stiftung model, the council holds authority over the foundation's purpose, its asset deployment, and its most significant commitments. When a source states that the Council oversees the Foundation and its most important decisions, the operative word is "most important." That is not a ceremonial seat. It is a seat with veto-adjacent influence over treasury allocation, grant priorities, and partnership direction.
Now consider the appointee's dual role. Mumtaz is a fiduciary of Helius, a commercial entity whose revenue depends on the health of the Solana developer ecosystem. He is simultaneously a decision-maker inside a governance body whose decisions shape the competitive standing of NEAR. These two interests are not merely adjacent. They intersect at the exact points where Layer-1 competition is decided: developer acquisition, infrastructure standards, and cross-chain interoperability design. This is the textbook definition of a conflict of interest — a situation in which a decision-maker's secondary interest has the potential to influence a primary obligation, regardless of whether any improper act occurs.
The absence of a disclosed recusal policy is the finding that matters. Based on my audit experience, I have learned that governance risk is rarely located in the disclosed act. It is located in the undisclosed mechanism. When I reviewed the custodial infrastructure supporting a proposed Bitcoin ETF in 2024, the failing was not the existence of multi-signature cold storage. The failing was that the signature thresholds did not meet the rigor the applicable regulatory standard required, and no document explained how the gap would be closed. The custodian had a policy. It simply had not been verified against the standard. Here, no policy has been disclosed at all. There is nothing to verify.
I want to be precise about what I am and am not claiming. I am not claiming that Mumtaz will act against NEAR's interests. I have no evidence of intent, and intent is not the analytical unit. Assumption is the adversary of verification, and the assumption that a dual fiduciary will naturally compartmentalize his obligations is unverified. Governance design exists precisely to remove reliance on individual virtue. A recusal framework, a disclosure schedule, an independent ethics review — these are the mechanisms that convert a soft expectation of good behavior into a hard, auditable structure. None of them appear in the disclosed record.
The regulatory lens sharpens this. Under Swiss foundation law, council members owe duties of loyalty and care to the foundation's purpose. Those duties are not suspended by external commercial affiliations. And a growing body of regulatory frameworks — from securities regulators to corporate governance codes — treats undisclosed conflicts as a compliance deficiency independent of outcome. In my work with Indian institutional clients, I have watched SEBI's disclosure expectations tighten around exactly this kind of structural entanglement. The principle is portable: a decision-maker with a material external interest must either disclose and recuse, or document why the interest is immaterial. Neither disclosure nor documentation is present here.
Now let me apply the Howey-adjacent discipline, not because a council seat triggers securities law, but because the same evidentiary standard applies. Does the appointment change the token's economic properties? No. Does it alter supply, emission, or value capture? No. Does it create a direct regulatory obligation such as KYC or AML? No. The honest answer to each is that the appointment is governance-only and produces no direct regulatory event. But the absence of a direct event is not the absence of risk. The risk is prospective. If NEAR later adopts Helius-style infrastructure, or if Helius later integrates NEAR tooling, the appointment becomes the documented origin point of a relationship that was never disclosed as a relationship. That is when a governance soft spot becomes a compliance finding.
Let me address the statistical dimension, because this is where the bulls and the bears both err. The information density of this event is close to zero. We have three disclosed facts. From three facts, one cannot compute a price impact, a TVL shift, or a developer migration. Anyone who claims this move is bullish or bearish for NEAR is performing narrative arithmetic on an empty dataset. The correct posture is to record the event, define the falsifiable signals that would confirm or refute its significance, and wait. Assumption is the adversary of verification. The signal set is concrete: does NEAR publish a conflict-of-interest policy? Does Mumtaz's voting record on competitive proposals show a measurable lean? Does a second external, non-ecosystem figure join the Council within twelve months? Does any joint NEAR–Helius infrastructure product appear?
These are testable. The claim that this is "Solana and NEAR aligning" is not testable, because no institutional alignment was announced. A person joining a council is not the same as two ecosystems forming a partnership. The distinction between individual affiliation and institutional commitment is not pedantry. It is the difference between a narrative and a contract. Markets price contracts with terms. They price narratives with sentiment, and sentiment reverses.
I have seen this exact category error before. In 2021, I analyzed a Mumbai-based generative art collection whose minting script was alleged to distribute rare traits randomly. It did not. The script was statistically weighted toward early buyers, and a Python breakdown of the trait frequencies proved it. The project's floor price fell roughly 40% once collectors engaged the raw distribution rather than the marketing language around it. The lesson was not that the project was fraudulent in a legal sense. The lesson was that a community had accepted a claim — randomness — that had never been verified, and the unverified claim was the entire basis of value. The same discipline applies here. A community is being invited to accept that a cross-ecosystem appointment is benign. That claim has not been verified, and there is no mechanism on record that would verify it.
Let me now examine the contrarian position, because a teardown that ignores the strongest counterargument is not analysis — it is theater. The bulls have a real point, and it deserves a fair hearing. Cross-ecosystem governance mobility is genuinely novel, and novelty is not automatically risk. There is a coherent case that importing an operator from a high-performance infrastructure ecosystem injects external competence into NEAR's governance — exactly the kind of outside perspective that prevents insular, self-referential decision-making. Solana's developer tooling matured under real load; that experience is portable. If Mumtaz's presence raises NEAR's infrastructure standards, the net effect could be strongly positive.
The bulls also have a structural argument that cuts against my conflict-of-interest framing. Layer-1 competition is frequently overstated. The chains are not zero-sum in the way maximalists claim; developers often work across multiple ecosystems, and interoperability — NEAR's own stated direction — requires exactly this kind of cross-chain familiarity. On that reading, the appointment is not a conflict to be managed but a bridge to be built. And the most honest point of all: without disclosure of the actual decision record, I cannot demonstrate that any bias has occurred or will occur. My critique is about structural exposure, not observed behavior. I should say so plainly. The bulls are right that a missing policy is not the same as a broken policy. My response is that a missing policy is precisely what makes the policy unverifiable — and unverifiable governance is the failure mode, not the exception.
The opportunity is real and narrow. The next twelve to twenty-four months will determine whether this was a symbolic diversification or the first documented instance of a competitive-interest entanglement inside a Layer-1 foundation. The tracking signals are few and unambiguous. Watch for a published recusal framework. Watch for the composition of subsequent council appointments — one external figure is an event, two is a pattern. Watch for any commercial interface between NEAR and Helius, because that is the point at which a governance soft spot hardens into a disclosed relationship with obligations. And watch whether the Foundation itself treats this appointment as material enough to document. The ledger remembers everything. A foundation that declines to record a conflict is not neutral. It is choosing which record to keep. That choice — not the appointment itself — is the finding I will be tracking.