A dispute over chain abstraction infrastructure has broken into the open after DFINITY Foundation founder Dominic Williams accused NEAR Protocol of improperly using DFINITY’s threshold ECDSA algorithm and raised doubts about the decentralization of NEAR’s multiparty computation, or MPC, network.
So far, the details in circulation come from Williams’ public statements. NEAR has not released a formal response or publicly addressed the intellectual property claims.
Threshold signature dispute moves into public view
In decentralized account abstraction, threshold signatures are a core piece of infrastructure for coordinating assets across chains. Williams said NEAR’s chain abstraction component directly reused the core algorithm disclosed by DFINITY in a 2022 academic paper.
According to Williams, the threshold ECDSA design was highly optimized from a mathematical efficiency standpoint, allowing distributed nodes to sign about three times faster than conventional approaches. In routing systems built around near-instant confirmation, he said, that speed difference has a direct effect on user experience.
The central disagreement, in his telling, is not whether the research was published, but how commercial rights were defined. Williams said commercial authorization for the algorithm was strictly limited to the Internet Computer ecosystem and was not extended to outside competing networks.
Claims extend beyond research into IP and staffing
Williams also tied the matter to personnel decisions. He alleged that NEAR hired a former DFINITY employee who had been dismissed in 2021 and put that person in charge of signature-related development, turning what might have remained an academic dispute into a more serious conflict involving intellectual property and non-compete concerns.
At the same time, Williams said DFINITY was not opposed to sharing the technology itself. He argued that if NEAR had sought a formal partnership in advance and properly cited the academic source, the team would have been willing to discuss a licensing arrangement under what he described as a fair framework. In his account, a direct port crossed a line of trust between ecosystems.
Williams questions the scale of NEAR’s MPC network
Separate from the patent and licensing allegations, Williams challenged the architecture behind NEAR’s chain abstraction stack. He said NEAR’s MPC network runs on only eight servers and suggested that its fault tolerance is open to question.
As a comparison, Williams said the Internet Computer threshold signature network is made up of about 50 independent node entities around the world. He described that subnet structure as having strict Byzantine fault tolerance and said it can maintain stable consensus even when nodes fail.
Repository references cited as evidence of technical strain
On the engineering side, Williams pointed to public records in NEAR’s official code repositories, specifically PR #4503 and Issue #4324 tied to the MPC codebase.
He said NEAR engineers were trying to move from a one-round communication signing scheme to a slower three-round design. Williams argued that the shift suggests the original implementation ran into either security vulnerabilities or deadlock problems, forcing a tradeoff on efficiency.
That interpretation, though, also comes from Williams alone. The exact reason for the code changes, and whether they in fact reflect a security issue, has not been publicly explained by NEAR or independently assessed by a security firm in the material available so far.
Chain abstraction rivalry sharpens focus on licensing boundaries
The episode also reflects intensifying competition among public blockchain networks in chain abstraction and cross-chain intent infrastructure. As the multi-chain market keeps fragmenting, the ability to offer faster and safer cross-chain signing at the base layer is becoming a more contested part of infrastructure strategy.
Within blockchain development, the line between academic publication and open-source software has long been blurry. Some teams treat published papers as part of a shared body of knowledge, but where proprietary commercial rights are involved, publication does not automatically amount to an open-source license.
At this stage, the allegations disclosed on social platforms come from DFINITY’s side only. NEAR has not responded publicly, and the meaning of the repository changes still needs further review. As competition around cross-chain intents heats up, infrastructure disputes are moving beyond technical exchange and into stricter questions of compliance and patent ownership.


