⚠️ DOM (ICP) CLAIMS IP THEFT: DFINITY VS NEAR INTENTS
@dominic_w from dfinity/icp just published a long piece claiming near intents is running on stolen proprietary dfinity tech, that a fired former employee helped them do it, and more
🔍 let's fact-check and understand it ↓
he frames it as IP theft with legal implications, points to a 2022 paper on ecdsa with additive key derivation and presignatures, and says near is now trying to emergency-downgrade away from "our algorithm."
if this is actual IP theft of proprietary tech licensed only for the internet computer, the normal place to handle it is court, not an x article.
i asked this very question to him as an article comment:
> "if this is a case of IP theft, shouldn't you be handling it legally in the court, rather in an X article?"
dom hasn't answered yet.
courts exist for this. discovery, expert comparison of code, damages, etc. posting the accusation publicly first, with strong language, does something different.
a few things stand out in how it's written.
the core privacy claim comes from an anonymous "phd engineer" who apparently looked into near confidential intents and concluded everything was "so bad that it seems almost comical."
no name. no credentials. no published notes.
the quote does a lot of work: it delivers the attack while creating distance if someone later asks for the real analysis.
near's own docs already describe far as a permissioned private fork with a small validator set and no public networking. confidentiality there rests on isolation + authenticated access + operator trust, not client-side zk. that design trade-off (ux, speed, selective disclosure) has been public for a while. treating documented architecture as a shocking discovery requires the audience not to check the source (or to take this audience--the icp community--for fools)
on the threshold ecdsa side, the paper he cites is a public security analysis by groth and shoup (dfinity) of techniques that already existed in various forms, including bip32-style additive key derivation.
near's production mpc stack is built primarily on the open-source cait-sith library, with public github, audits, and an operator set that has grown and is now listed with named parties.
the github prs he links read as engineering work on online-presign variants and rollout compatibility, not a clear "emergency downgrade from the dfinity algorithm," as dom claims. mapping them that way is a wording choice.
the language is overloaded on purpose: "stolen," "saboteur," "craazy," "colossal harm," "emergency downgrade," "legal implications." these words turn a technical and potential legal dispute into a moral one before the evidence is examined in detail. they stick better than the qualifications. they also make later softening easier while the strong framing remains.
this looks like intentional rethorics tactics.
this pattern is familiar. the same style shows up in many posts on X from questionable entities. the framing generates confusion, attacks one project while implicitly favoring another, and works as click/rage bait.
here the strong conclusion comes first; the public counter-evidence (docs, github, operator lists, the paper being a published analysis) comes later or not at all.
this too looks intentional.
none of this means near has zero trade-offs. the private shard is permissioned. people should understand the trust assumptions. i've posted about that several times myself.
threshold signing designs have different decentralization and security properties depending on operator set size, key distribution method, and upgradeability. those are real topics.
what the piece does is package public and contested points inside anonymous attribution and maximal language so the audience feels the conclusion before checking the sources. that is useful for narrative competition. it is weaker for establishing what really happened and if IP theft really happened.
this looks intentional.
accuracy matters more than the temperature. the docs, the papers, and the github activity are all public. read them with an open mind and critical thinking. DO YOUR OWN RESEARCH, as we used to say in the good old days of cypherpunk crypto development.
i'm doing mine and will share any new findings i might encounter