
DFINITY founder accuses NEAR of allegedly stealing the threshold signature algorithm and questions the degree of decentralization of its MPC network.
Author: TechFlow
TechFlow Guide: An academic patent dispute surrounding underlying chain abstraction technology has erupted publicly. DFINITY Foundation founder Dominic Williams published an article alleging that NEAR Protocol improperly used its threshold ECDSA algorithm.
Meanwhile, Williams questioned the decentralization level of nodes on the NEAR network and cited codebase records to point out technical vulnerabilities. Currently, these statements are unilateral allegations with no public response from NEAR yet, sparking widespread industry scrutiny over the commercial boundaries of open-source cryptography.
Academic Outputs and Departing Employees: The Full Story of Threshold Signature Algorithm Infringement Allegations
In decentralized account abstraction, threshold signatures serve as the core foundation for cross-chain asset allocation. Williams stated in his declaration that NEAR's chain abstraction components directly reused the core algorithm published in DFINITY's 2022 academic paper.
According to his introduction, this threshold ECDSA algorithm features highly optimized mathematical efficiency, boosting distributed node signing speed up to three times that of conventional schemes. In intent routing where second-level confirmation is emphasized, this speed advantage directly impacts user experience.
The dispute centers on technical licensing. Williams emphasized that commercial licensing for this algorithm is strictly confined within the Internet Computer ecosystem and does not extend to external competing networks.
Regarding personnel appointments, Williams accused NEAR of hiring a former employee who was terminated by DFINITY in 2021 to lead signature R&D. This development escalated the matter from academic discussion into a serious legal dispute involving non-compete restrictions and intellectual property rights.
Williams stated that DFINITY does not oppose technology sharing. If NEAR had proactively sought formal cooperation and acknowledged the academic source beforehand, the team would have been willing to reach a licensing agreement under a fair framework; direct transplantation breached the baseline of mutual trust within the ecosystem.
Questions on Node Count and Architectural Downgrades: 8 Servers and the 3-Round Signature Dispute
Beyond the patent algorithm allegations, Williams also challenged the degree of decentralization underlying NEAR's chain abstraction. He publicly pointed out that NEAR's multi-party computation (MPC) network is deployed on only 8 servers, casting doubt on its overall fault tolerance capability.
For comparison, Williams emphasized that the Internet Computer's threshold signature network consists of approximately 50 independent node entities globally. This scaled subnet architecture features strict Byzantine fault tolerance mechanisms, sufficient to maintain stable consensus during node failures.
On the engineering implementation side, Williams cited public records from the NEAR official codebase. He listed pull requests (PR #4503) and issue discussions (Issue #4324) in the MPC repository, pointing directly to the technical dilemmas it faces.
Records show that NEAR's engineering team is attempting to shift from a 1-round communication signature scheme to a longer-duration 3-round signature scheme. Williams believes this engineering change reflects that the original implementation encountered security vulnerabilities or deadlocks, forcing them to compromise on efficiency and downgrade.
Heating Competition in the Chain Abstraction Track: The Game Between Open Academic Boundaries and Infrastructure Foundations
This incident reflects the fierce positioning battle among public chains in the realm of chain abstraction and cross-chain intents. As the multi-chain landscape continues to fragment, whoever provides faster and more secure underlying cross-chain signatures will hold the dominant position for a unified on-chain entry point.
In blockchain development contexts, the boundary between academic papers and open-source code has long been blurred. Some teams are accustomed to treating published papers as a public knowledge base, but when proprietary commercial licensing is involved, academic papers do not equate to liability-free open-source licenses.
It should be clarified that the allegation details currently disclosed on social media stem entirely from DFINITY's unilateral statements. NEAR has not yet issued a formal announcement or provided clarification on intellectual property matters, and adjustments to the codebase await independent assessment by professional security institutions.
As the competition for cross-chain intents intensifies, infrastructure sector competition is evolving from mere technical exchange into a more rigorous stage of compliance review and patent validation. This signature dispute will inevitably bring profound insights to the industry regarding standardized technical citation and team non-compete management.















