Bruce21b ⓥ (@bruce21b) header
Bruce21b ⓥ (@bruce21b) profile picture

The Wolf of Crypto

Joined July 2009
Photo by Bruce21b ⓥ (@bruce21b)Photo by Bruce21b ⓥ (@bruce21b)Photo by Bruce21b ⓥ (@bruce21b)Photo by Bruce21b ⓥ (@bruce21b)Photo by Bruce21b ⓥ (@bruce21b)Photo by Bruce21b ⓥ (@bruce21b)Photo by Bruce21b ⓥ (@bruce21b)Photo by Bruce21b ⓥ (@bruce21b)Photo by Bruce21b ⓥ (@bruce21b)Photo by Bruce21b ⓥ (@bruce21b)
We are aware of and closely following the situation at Binance and have offered our support. I've just wrapped a call with our custody team and we see no indications of any suspicious activity at @coinbase. Let's all breath and work this together.
11
13
2
139
10,367
Bruce21b ⓥ retweeted
Coinbase is safe and secure. We’re actively monitoring the Binance situation, and have reached out to their team to offer our support.
811
1,014
168
16,526
1,075,683
Bruce21b ⓥ retweeted
NEAR is here.
Near has landed on Gemini near:native is now available to trade, with deposits and withdrawals enabled → exchange.gemini.com/buy/NEAR
14
28
3
256
16,186
Bruce21b ⓥ retweeted
Market of markets. That is why NEAR Intents is at Solana Breakpoint, building with Solana apps instead of against them.
1
10
78
1,573
Bruce21b ⓥ retweeted
After a week of the ICP patent drama, here is what I see. DFINITY started two lines the same week in 2021: a sealed patent application, and a public CC BY paper with the same method. For three years the public line was the only one anyone could see. NEAR built on it and cited it. Then DFINITY switched to the sealed line and asked for money. The product they built on the same patent holds about 240 BTC today. The dates, all public and linkable. Sep 30, 2021: DFINITY files a patent application on re-randomized presignatures. Applications are sealed until published, nobody outside the company can read them. Oct 5, 2021: five days later, the same two people, Jens Groth and Victor Shoup, DFINITY's cryptographers and the named inventors on the patent, put the same method on eprint under CC BY. Free for anyone to use, attribution only. Nov 13, 2023: a NEAR engineer opens a public ticket. He describes a known attack on ECDSA with derived keys and presignatures, and proposes the defense from Groth and Shoup's paper, citing it by name: "one technique proposed in [GroSho22] is to re-randomize presignatures". Merged in December. This is how cryptography is supposed to work: you do not invent your own, you take a published, peer-reviewed construction and say where it came from. The code running today still carries the comment "inspired by [GS21]" with a link to the paper, and the Trail of Bits audit describes it the same way. Nov 28, 2024: the application becomes public for the first time. Three years after filing, a year after NEAR cited the paper. Jul 28, 2026: patent granted. Sep 25, 2026: NEAR makes online presign the default, a path where the presignature is computed after the request and there is nothing stored to re-randomize. The PR description is about protocol safety, no patents mentioned. Oct 2026: DFINITY's founder calls it theft and asks for license fees back to the first day of use. Bottom line: two paths opened the same week. NEAR took the public one for three years and said so at every step. DFINITY waited until the sealed one was granted, then came for the readers of the public one.
35
21
5
91
6,257
Bruce21b ⓥ retweeted
Context for everyone else. Dom says NEAR took a signing method from DFINITY "without referencing them", knew about unpublished patent applications, and points at a 2024 PR as proof of a cover-up. Dom, you did not look. The source is named in three places. near/mpc_old issue #352, Nov 13, 2023: a NEAR engineer wrote up the attack, the fix, and the author: "one technique proposed in [GroSho22] is to re-randomize presignatures". The code that shipped has a comment "inspired by [GS21]" with a link to your paper. The Trail of Bits audit describes it the same way. Your application became public on Nov 28, 2024. The ticket is a year older. The paper has been on eprint under CC BY since 2021, published by your own people for anyone to read. So the facts are: public ticket, public credit, public code, a year before anyone outside DFINITY could see a claim. That is the opposite of hiding. You asked NEAR for "proper credits and references". They were there before you asked. Read the repo before accusing the people who wrote it.
Replying to @Trisor876
Firstly, there were two patents on the algorithm they took, one was issued *beginning* of this year. We want license fees at the least. Sorry to those that liked my previous post, I reworded this to be more precise. If they knew about the patent applications, then license fees could be recoverable from the beginning of their use of the proprietary tech (~2+ years) not from earlier this year. There are some things that point in that direction in my view, e.g. 1) GitHub posts like this, note what's in the quotes, which I read like pre-emptive non-infringement positioning github.com/near/mpc_old/pull… (the algo of course re-uses the invention with a minor tweak that make it less secure), and 2) they had hired a senior DFINITY engineering manager in April 2022, who I feel would have known full well about DFINITY efforts to patent major works. We need that Google doc referenced by that GitHub pull request; NEAR if you're reading this, deleting evidence won't be helpful, maybe you'd like to voluntarily share this. Secondly, it looks to us like their Confidential Key Derivation is basically derived from the vetKeys paper, and maybe they looked at our Rust implementation too. That wasn't patented, but completely wrong to go around passing off hard and substantial work by very serious cryptographers as your own, and also completely ridiculous. I'm sure Ilia is a more serious guy than that. We are not anti-NEAR, but this is obviously too much and has to be addressed. Note as well that passing off a competitor's academic work as your own to gain an advantage also transgresses various other laws around the world. But anyway, if this is what has happened, I'm sure Ilia, as a supporter of open source, will want proper credits and references to be added, and for their CKD article to explain where the math came from. We're busy but will be contacting them, first to try and resolve this amicably. Meanwhile, they also need to think hard about who they choose as friends. Some of the people that came after us for them are absolutely freaky and the worst web3 has to offer. Notably, we've heard no denial, nor apology.
28
12
6
106
8,796
Bruce21b ⓥ retweeted
Gemini: NEAR is live, deposits and withdrawals enabled. Gemini is the exchange that bet on Zcash before it was fashionable. Shielded ZEC withdrawals since 2020, the only major US exchange that offers them. Last month they rebuilt their Zcash node in Rust for the November upgrade that cuts block time from 75 to 25 seconds. The Winklevoss twins filed for a ZEC ETF. NEAR Intents is the main rail for ZEC outside its own chain: ZEC on Solana, ZEC in confidential swaps, and this week near(.)com's Universal Send, where you pay from USDC and the other side receives ZEC privately. So the step after listing NEAR: let users move ZEC in and out of Gemini from any chain, shielded on the Zcash side, through Intents. One integration instead of a node on every chain. Gemini has the fiat exit and the compliance, Intents has the routes. For clarity: nobody announced this, the pieces are just lying next to each other now.
1
9
1
85
1,994
Bruce21b ⓥ retweeted
$NEAR is now listed on @Gemini.
Near has landed on Gemini near:native is now available to trade, with deposits and withdrawals enabled → exchange.gemini.com/buy/NEAR
43
170
11
1,234
116,971
Bruce21b ⓥ retweeted
Replying to @dominic_w
I know some of you are scrolling this thread looking for my reply. Enjoy, this one is for you. > "Key enabling component is stolen DFINITY tech." The threshold ECDSA protocol in near/mpc is Cait-Sith by Lúcás Meier, an open-source MIT library, triples-based, not DFINITY's design. The repo is public, go read it. > "8 servers, nobody can get more info." The MPC network is 17 operators, threshold 11 of 17, names public: Bitwise, HashKey Cloud, Nansen, NEAR One, HOT, Aurora, Everstake, Luganodes, Stakin and more. It is in SVRN's SEC filing. His number is from a blog post dated May. > "The algorithm NEAR took." Additive key derivation is BIP32, Bitcoin, 2012. Presignatures predate DFINITY. The one thing from DFINITY is a fix from a paper Groth and Shoup put on eprint in 2021 and presented at Eurocrypt 2022. The paper's own abstract says these techniques were "used widely throughout the cryptocurrency space" before it. Citing a Eurocrypt paper is called research. Calling a published paper "proprietary, licensed for ICP only" is called marketing. There is no patent, I looked. > "Emergency downgrade from our algorithms." The PR he links was merged on September 25, a month before his thread. The issue behind it, from September 2, says the reason in plain words: three precomputation phases are hard to maintain, "a simpler system is better for trust and maintainability." It is a Cait-Sith variant with online presign. No DFINITY, no lawyers, no emergency. > "Two engineers mining the ICP repo." The GitHub link he gives is a NEP discussion about execution context in the runtime. Nothing to do with cryptography. > The fired employee story. No facts, just a grudge. I will leave it. So the summary: an open MIT library, a Bitcoin standard from 2012, and a public Eurocrypt paper. If that is theft, every wallet on earth owes DFINITY a check.
9
11
4
77
2,907
Bruce21b ⓥ retweeted
NEAR published the Chain Signatures update: 17 independent operators inside a TEE with proof checked on-chain. Great for NEAR. And it quietly makes OutLayer a lot stronger, so a few words on why. Trust in an AI agent has two floors. The lower floor is the key: who holds it, who can see it. The upper floor is behavior: what the agent did with the key, under whose rules, and can you check. NEAR just closed the lower floor. The key is split across 17 operators, each operator's piece lives inside encrypted hardware, and the chain verifies what code those machines run. Nobody holds the whole key. Not an operator, not NEAR, and you do not have to take anyone's word for it. OutLayer is the upper floor, and it sits directly on that key. The agent's wallet secret is derived by that same MPC network for an OutLayer enclave that proved its code on-chain. Nobody at OutLayer can read it. Then everything the agent does happens inside its own enclave, with its own proof: the policy you wrote, the limits, the confirmation step, the connector that places an order on Hyperliquid or Polymarket or pays an invoice through Mercury. The agent gets buttons, not keys. Put together: a key nobody holds, rules only the owner can change, and a proof for every run. Until this update one link in that chain was a promise, the MPC operators' servers. Now it is hardware and on-chain proof, all the way down. The one place that still trusts OutLayer is cross-chain swaps and withdrawals, which our coordinator assembles. In practice it means this: you can hand an agent real money and real accounts, and every action it takes comes with a proof that no one, not the agent, not OutLayer, not NEAR, could have faked. NEAR built the foundation. OutLayer built the floor you actually live on.
NEAR just moved its Chain Signatures network, the MPC that signs for 35+ chains, fully inside Intel TDX enclaves, with proofs checked on-chain. For OutLayer this is not news to retweet. It is the ground floor of our own building getting poured in concrete. Why it matters to us. Every OutLayer agent wallet starts from a secret that NEAR's MPC network derives for an OutLayer enclave. Nobody at OutLayer holds a wallet key. The agent's code never touches it either. The agent gets buttons, not keys. Until now there was one place in that story you had to take on trust: the MPC nodes themselves, 17 operators running on their own servers. Today those nodes run inside the same kind of encrypted hardware our keystore does, and anyone can check it on-chain. So the whole path is now proven, not promised: > 17 operators, 11 needed to sign, every node in TDX, verified on-chain > the wallet's secret is derived for an OutLayer keystore build the chain has approved; the code is open source, anyone can rebuild it and compare > every agent run executes in TDX and comes back with its own proof What NEAR cannot do, and OutLayer does: decide what the agent is allowed to do with that key. Spending limits, allowed venues, owner confirmation for the actions you mark sensitive, a refusal for anything outside the policy, and connectors to Hyperliquid, Polymarket, Mercury, Gmail and GitHub, all running inside the same proven enclave. NEAR made the key trustworthy. OutLayer makes the agent's actions trustworthy. Not a whitepaper. Running on mainnet, on top of the most decentralized MPC network NEAR knows of.
3
8
70
4,717
Bruce21b ⓥ retweeted
$NEAR quietly green while everyone argues about AI earnings instead $5.12 and nobody in the replies even noticed
69
2
84
5,477
Bruce21b ⓥ retweeted
Dom, respectfully - you are full of shit and a complete LARP. Tearing down others doesn't help your situation at ICP. Let's go through some facts about the "Internet Computer", an completely unoriginal and uninspiring name swiped from Ethereum's world computer: - 3,870 daily active users (lol, lmfao really) - spent millions of dollars on terrible conference marketing to get exit liquidity in 2021-2022 - down 99.9% from all time highs - company makes ZERO revenue - team max extracted and contributed negative value to the industry - the transactions on the network are clearly wash traded/bot volume and one claude prompt will get you there You've contributed practically nothing to the industry yet got rich as f*ck, funny how that works. To be clear, and concise: $ICP is a total shitcoin, has zero reason to exist, and this post reeks of desperation & pure jealousy. Envy is a major sin, and you should celebrate the successes of others, rather than try to tear them down. This industry is far too small to not grow the pie. Ask any ZK, privacy, or developer about NEAR's TEEs and confidential tech and they will tell you the same thing: it's not perfect, but it's pretty damn good for onchain privacy in 2026. Meanwhile, ICP is still paying the worst KOLs in the industry to promote while you dump on side wallets and OTC. Rant over. Don't fuck with NEAR.
This is craazy. I asked one of our PhD engineers to look into NEAR *Confidential* Intents wondering how they designed their system. Unredacted, word-for-word, this was his answer 😱😱😱 "Everything I found out about the privacy claims and confidential intents is so bad that it seems almost comical and I cannot believe what I am seeing. Apparently they run a completely separate instance of the protocol, which is called FAR (as an opposite to NEAR), and that has a permissioned operator set. The entire confidentiality claim seems to rest upon the fact that it is a permissioned chain and the nodes are trusted to keep things private, there doesn't seem to be any deep technology behind it and it also does not seem to be open source. The entities running the nodes are also not publicly known. I almost feel weird writing this because it is so absurdly bad that it feels like ... I don't know ... a simulation? I know the usual level of overpromising in Web3 but this is so many levels beyond believable that it still feels unreal."
193
51
30
627
78,433
Bruce21b ⓥ retweeted
Hard to believe, but the hottest market on earth, AI compute, has no real exchange. Deals are OTC, by phone and PDF, like oil in 1983. It cannot go on an order book: GPUs are heterogeneous like oil, an H100 on InfiniBand in Virginia is not an H100 in Jakarta, and perishable like electricity, an idle hour at 3am is gone forever. Nothing with both properties has ever traded cleanly. So H200 hours cost what they did at launch and the whole market clears over Signal. This is a NEAR Intents shaped problem. You cannot post an order for a thing with no standard grade, but you can post a need: a thousand GPUs of roughly this shape, this region, these weeks. Solvers who have it, or can stitch it from five clouds, come back with a price. The biggest market without an exchange will get one, and it will look like near:native Intents, not Nasdaq.
7
9
2
103
3,727
Bruce21b ⓥ retweeted
$NEAR Holders, this proposal strengthens NEAR’s tokenomics. HSP-029 ramps annual issuance from 2.5% → 1.6% over 24 months cutting ~11.8M tokens over 2 years and ~66M over 6. Lower inflation. Higher scarcity. Stronger long-term value accrual. Vote now: houseofstake.org/proposals/2…
1/3 HSP-029: Establish a 24-Month Issuance Ramp to a 1.6% Target Rate of NEAR Token Emissions — Vote now! This proposal aims to gradually reduce $NEAR's annual token issuance from 2.5% to 1.6% over 24 months, helping reduce token dilution and strengthen long-term tokenomics.
2
7
1
48
1,910
Bruce21b ⓥ retweeted
Huge
for crypto to win, we need the best ecosystems working together NEAR is how trillions
2
17
1
331
5,434
the bear case on $NEAR keeps changing. first it was "no users". then "no narrative". then "nobody uses intents". then "intents generates little revenue". when bears have to rewrite the thesis every year, the bull case usually didn't need to.
7
11
1
148
5,445