
a former shitcoiner. 𤢠my shitcoin PoW: tried building @SmokeDotMoney | read my cross-chain thoughts on Substack
Future
Joined August 2022
- Tweets2.1K
- Following762
- Followers996
- Likes33.4K
Pinned Tweet
Smoke is Shutting Down
Yep. Itās been several months since I stopped working on Smoke. I thought Iād get back into it naturally if it pulled me back, but I donāt think I want to anymore. A few weeks ago the domain quietly expired, and that was proof enough. Time to take it behind the barn once and for all.
What Happened?Ā
I think this was the fate shared by many companies that were trying to solve the cross-chain problem. Many of them ran out of juice to continue solving this problem that became less pressing than other problems. The biggest lesson for me was that I got the timing wrong. I was late to the party and the pie didnāt get as big as we all predicted. I needed a lot of pieces to click into place for Smoke to work. Let me unpack this in a few sections.
- Why did I start working on this problem?
- What were the biggest hurdles?
- And what made me finally pull the plug?Ā
The Motivation to Start
When I started working on this problem, innovative apps were still being built on the periphery. Although I wasnāt big on Blast, I thought it would succeed. I even took Fantasy Top as one of the main examples in my pitch. My belief was that we would see an explosion of chains with thousands of apps built on hundreds of chains. I believed that the scaling problem was the only bottleneck; since we had solved it via the modular architecture, weād see all these apps being built on many different chains, and we needed something like @SmokeDotMoney to connect them in the best way possible.
Smoke is still one of the best solutions to this problem, with a few caveats (Smoke required a change in user behaviour), but the problem isnāt the biggest one anymore. I thought we were right to build all these chains with custom execution, custom sequencing, custom consensus layers, etc. All of this was probably just marketing by the modular mafia. Maybe all the apps could fit into a single chain like Solana or Arbitrum because there aren't many apps anyway.
Does that mean weāll never see hundreds of chains? I donāt know. But right now it doesnāt seem like we have demand for hundreds of chains.
Another reason I started working on this problem was probably that I was not brave enough to leave the cross-chain space I was an expert in. In hindsight, I shouldnāt have been so scared of switching fields, especially now that AI makes it so easy to learn so many new things in such a short period of time. It is a fast learnerās world right now.
These were the reasons why I started working on the problem. But what are the challenges I faced?
The Biggest Hurdles
Iād say the biggest hurdle was the lack of conviction: should I really keep spending my valuable time on a problem that might become more relevant sometime in the future, something Iām not even certain about? Itās a good practice to work on problems that might become big, but I lacked the conviction that this one would.
Other hurdles included the absence of a clear path to distribution. Smoke required a significant change in user behaviour, similar to how the resource-lock-based chain-abstraction solutions that were making noise last year. Account Abstraction companies struggled for similar reasons, adoption stalled because the product demanded too significant a change in user (and wallet) behaviour.
Finally, there was a shortage of people willing to rally behind the idea. I continue to believe this design is the most effective way to solve the problem, but this isnāt a school competition where the academically perfect solution wins. Itās a market that only accepts the solution good enough to satisfy ease of use, timing, and incumbency advantages.
The Nail in the Coffin
What made everything so clear was Unichain reaching only $15 M in TVL months after launch. Enough to convince me that an MEV-focused rollup built by two highly reputable teams still couldnāt pull users or builders to a new chain. Uniswap was already there; people could deploy tokens and migrate existing apps from other EVM chains to take advantage of Rollup Boost, its advanced MEV-mitigation system. Yet no one seemed to care.
Solana stole the spotlight. Most builders I could see, possibly just riding hype the way the modular mafia once hyped āhundreds of chainsā, are now shipping on Solana. If Solana can scale to hundreds of apps, do we still need hundreds of chains? And do people still care about the decentralization and security Ethereum offers? It doesnāt look like it. The Ethereum Foundation now says it wants L1 to become a āgigagasā chain. What that means for L2s and other rollups is anyoneās guess. The one certainty is that nothing here is certain, should be expected from frontier tech like web3. That, perhaps, is where I was wrong too.
We will still have a need for interop between major L1s like Ethereum, Solana, Hyperliquid, and a few L2s like Base, Arbitrum, etc. But I doubt weāll see thousands of chains. Thatās why I was building Smoke. To seamlessly connect hundreds of chains.Ā
A lot of you found me when I was complaining about LayerZero and Hyperlaneās multisig setups for cross-chain security, maybe they were right. Maybe multisigs are enough. Nobody cares about security in the space. Thatās not wrong, thatās just the reality.Ā
Whatās next for me?Ā
Iām exploring another small project right now. Will keep you all updated. In the meantime, if you are working on something, Iād love to take look at it and learn more about why youāre solving that problem.Ā
I really appreciate everyone who supported me during my Smoke arc. Thank you all for connecting me to people, giving me feedback, and keeping me motivated. You will be remembered and I owe all of you. Hit me up. Anytime.
sand retweeted
Replying to @lex_node
You donāt fully grasp how much of your life is tracked until youāre sitting in a courtroom, watching federal prosecutors use your digital history against you, down to your most harmless Google searches. Your entire life becomes an open book, and even your most innocent actions can be twisted into something sinister.
They get to tell the most damning version of your story. To tell yours in your own words, you have to take the stand.
After this incident Iām sure 80% of all Bitcoiners canāt read the block explorer š«
Even some OG Bitcoiners misread @mempool in the last couple of days.
sand retweeted
I fully accept what happened yesterday. It is sad, I will admit that. But it also feels like a catharsis.
BIP-148 is celebrated as Bitcoin Independence Day, because it proved that ordinary users, running nodes in their homes, could force the most powerful mining cartels and corporations in the industry to back down. The users had no hashrate, no exchanges, no lobbyists. They had conviction and they had nodes, and that was enough.
BIP-110 ran the same play with the same conviction, a reasoning that was shared by all bitcoiners five years ago (Bitcoin is money and not a grift database), and node support at levels at least comparable to 2017. This time the miners and the corporate layer simply refused to follow. They extended their spam-friendly chain and moved on like nothing happened.
Remember yesterday as Bitcoin Dependence Day.
What changed between 2017 and 2026?
Not the users. They showed up with the same fire.
What changed is everything that grew in the years between. ETFs. Treasury companies. Custodians holding millions of coins for people who will never touch a node. Hashrate concentrated into a handful of pools building templates for the whole world. Capture of the governance of the reference implementation resulting in stark philosophical pivot.
Those already celebrating Bitcoin Dependence Day are not simply cheering an outcome they won. They are treating evidence that miners and the corporate layer now control Bitcoin as if it were a grand cypherpunk victory, while ridiculing the people who fought for decentralization and for Bitcoin as money.
In my opinion, and in my heart, legacy Bitcoin is not what I signed up for. Captured. Centralized. Led by suits.
No longer about freedom, sovereignty, or the mission of separating money from state.
No longer about the things that made me a ride or die bitcoiner for many years.
The fire that originally drew me to Bitcoin is still alive in the node runners who supported BIP-110. I will follow it where it goes.
As for legacy Bitcoin, I have no interest in it anymore as a freedom project. In my mind, it is now a stock.
sand retweeted
Podcasters who read coldcard ads for years now framing their disclosure efforts as some kind of public service ā I swear, you couldnāt even make this stuff up.
Pi is the best agent harness and more importantly framework we have right now.
The stats are stunning:
- highest cache hit rate
- lowest latency
- highest performance
- smallest bundle
- cleanest code
- cheapest cache + tiny system prompt over months adds up
Try it
Replying to @composio
Median time per task (clock time, run start to finish):
- Pi Agent: 161.7s
- Hermes Agent: 179.5s
- Codex: 236.2s
- OpenCode: 271.1s
- Kimi Code: 297.1s
- Claude Code: 347.6s
Codex placed third, so it fared better on speed. Pi's lead fits its minimal design.
sand retweeted
A zero day related to master private key generation placed at a top tier HWW vendor or other custodian will be almost indistinguishable from a protocol breech, even for even savvy observers. This is a massively under appreciated vulnerability.
It takes me more than 2 days to sync my node. 1 day to sync until 2022
i.e., for 14 years of blocks and 1 whole day to sync remaining 4 years. Iāve tried multiple times.
This is why BIP-110 and this new direction we are going in is very important.
sand retweeted
Replying to @adam3us
I've been thinking about how I would respond to this as I was mowing my lawn, because yes, I'm that kind of guy who doesn't have a stake in a billion dollar company and who doesn't get invited to private islands, the kind of guy who mows his own lawn and just does what he thinks is right in the world. You are as guilty of what I'm describing as anyone, dismissing @hodlonaut's articles as pulp and tabloid material instead of contending with the very real issues that they raise. I began and lead a FOSS project that has continued to build a useful savings tool for bitcoiners, including bitcoiners in some of the most difficult and hardest to reach parts of the world, and I've tried to steer the project to build in a way we think is in the true spirit of bitcoin. And I can confirm that portions of the grant space are captured by corporate interests and treat certain projects like shit -- I have experienced this personally and repeatedly. SeedSigner invented SeedQR and popularized the stateless approach that gave Jade a second wind after it's PIN server approach didn't resonate with bitcoiners. After I pointed this out Blockstream cut us a $2k novelty check, and we continued to get shot down by most grant orgs, save the HRF. I looked up to you so fucking hard when you did that episode of Lets Talk Bitcoin in '14 or '15, talking about sidechains and network upgrades. You were the original cypherpunk who initially overlooked bitcoin but circled back to help advance the movement after seeing the value. The truth between core and knots is somewhere in the middle. Core has a ton of eyeballs and really smart people working on it, but blowing up the op_return from 80 bytes to whatever crazy number it is was a mistake and any rational person can see that. The reasonable thing to do would be to figure out how to walk that back instead of digging into the false dichotomy this whole thing has begun. But what do I know, I'm just a 80-IQ chump nym watching you and all of the other luminaries being primarily more worried about conference junkets and lining your own pockets.
sand retweeted
ATTENTION. IN ONE MONTH, THE BITCOIN NETWORK WILL START REJECTING BLOCKS THAT DO NOT SIGNAL READINESS FOR BIP-110, A SOFTFORK TO REJECT THE ARBITRARY DATA STORAGE USE CASE, THEREBY REAFFIRMING THAT BITCOIN IS MONEY.
(1/)
Iām in favor of BIP-110. Letās keep all the spammers away!
I donāt know if any Bitcoiners are following me or if my stand matters but I still wanted to speak out. Bitcoin is too important and Core has been changing it by making it more and more vulnerable.
sand retweeted
I feel for the ZEC holders who got rekt. Truly.
Itās true that in life very few people are actually looking out for you. But whatās often understated is that thereās a massive difference between normal self-interest and people who seem to lack any moral framework at all, people who treat harming or extracting from others as if itās the backbone of their entire life philosophy.
With ZEC, everything from the people around the project since inception to the ones promoting it of late pointed to something darker than self-interest: a total absence of honor, restraint, and moral consequence.
Thereās a difference between realizing youāre in this alone and nobody is looking out for you, and realizing some people will actively destroy you if it means they can make more money or achieve their goals.
Tell you what, unfollow all crypto VCs. They are literally anti-signal.
And unfollow, block and report crypto VCs spinning narratives about their bags. š
There's a lot of confusion about the recently patched Zcash bug. Here's how to actually understand it.
If the bug had been exploited before the patch (very unlikely it was), it would have looked like the shielded pool getting drained. Whoever minted the counterfeit shielded ZEC would want to sell fast, before anyone else found the same bug. And remember, the market for ZEC is almost entirely transparent ZEC, not shielded. You can't dump freshly minted shielded ZEC on Binance or Coinbase without unshielding it first.
The losers in that scenario are shielded holders who sit still. The transparent portion of Zcash is fully visible, so it's trivial to enforce that transparent ZEC never exceeds max supply. If you try to unshield more than the cap, you'll get stopped at the door.
So if you hold transparent ZEC (anyone trading, on an exchange, or doing price discovery on ZEC) there's no marginal effect on you. The loss falls entirely on shielded holders.
The team's next step is a new turnstile and a fresh shielded pool in the coming upgrade, which will confirm the shielded pool was not inflated. Think of it as taking headcount at the end of the field trip--that will make sure no extra kids snuck onto the bus.
But while AI found this bug, AI will also deliver the fix for the whole category: formal verification. I'm very bullish on this as the path to harden all software across the industry. Formally verified cryptography can't have implementation bugs by construction.
Right now AI is surfacing vulnerabilities across all our software--browsers, OSes, and blockchains are no exception. We're in the awkward adolescence where every wart is getting magnified and put on full display. But formally verified software is the only path forward for mission-critical software, and Zcash has put it front and center on their roadmap to deliver.
Privacy is too important not to.
(Dragonfly holds $ZEC and continues to. I'm personally an investor in ZODL.)
sand retweeted
btw this isnāt the first time a bug like this was discovered in zcash. last time it was disclosed after being a year+ in the wild and everyone lost faith and zcash went to zero for 7 years, until they found a new generation of buyers who doesnāt know the history (thatās you)






















