Yan | swan.com

21K posts

Yan | swan.com banner
Yan | swan.com

Yan | swan.com

@skwp

co-founder & CTO @swan. Author Inventing Bitcoin. Shadowy Super Coder.

Chicago, IL Katılım Aralık 2006
3.4K Takip Edilen40.2K Takipçiler
Yan | swan.com
Yan | swan.com@skwp·
@larcho Yeah - definitely spec driven. Haven’t played with that one tho. We do a lot of compound engineering
English
1
0
0
13
Lars Klassen
Lars Klassen@larcho·
@skwp Spec driven development then, right? Have you seen OpenSpec from FissionAI?
English
1
0
0
22
Yan | swan.com
Yan | swan.com@skwp·
To avoid human driven systems, Netflix built Chaos Monkey to randomly wreak havoc on their infrastructure to ensure it was fully self healing. Today, Claude is the Chaos Monkey and software developers must create self-healing SDLC pipelines that can account for it.
English
1
1
5
614
Yan | swan.com
Yan | swan.com@skwp·
@larcho Meaning an AI driven pipeline that does the job that normally you’d have a bunch of humans doing. Architecture review, security review, QA, check for semantics, standards adherence, etc.
English
1
0
0
18
Lars Klassen
Lars Klassen@larcho·
@skwp What’s SDLC in this context? Spec driven development, AI tooling or something else?
English
1
0
0
20
Yan | swan.com
Yan | swan.com@skwp·
AI and Quantum are fundamentally the same type of problem: incredibly powerful engines that produce slop. The answer in both cases is multiple rounds of sophisticated error correction to harness the power.
English
2
0
2
598
Yan | swan.com retweetledi
Cory 🦢 Real Bitcoin @ Swan.com
Quantum Fear-Mongering and The Infinite Perils Trap Alex Thorn @intangiblecoins had a strong post on quantum and Bitcoin coming out of the Vegas discussions this week. I agree with most of it, and I think there’s a broader risk framework that explains why the emerging middle ground is the right one. The quantum debate keeps skipping the most important question. Not “is quantum a risk?” Of course it is. The question is what kind of risk it is. That distinction matters because of a fallacy that shows up in almost every tail-risk debate: The Infinite Perils Trap. If a risk sounds catastrophic enough, people start treating any non-zero probability as justification for emergency intervention. That sounds serious. It is often just sloppy. There are infinite potential perils. Quantum. AI. Asteroids. Engineered pandemics. State attacks. Supply chain attacks. Unknown unknowns. You cannot spend 50% of the attention budget on each one. At some point “prudence” becomes resource exhaustion. This is where Nassim Taleb’s systemic-risk filter is useful. The irony is that Taleb is often invoked to justify maximal precaution, but his framework also tells you when NOT to go all-in. The risks that justify extreme precaution are not merely the ones that sound scary. They are the ones that are connected and scalable. Connected means the threat spreads through the system. Scalable means a small failure can cascade into ruin for everyone. Pandemics qualify. Banking contagion qualifies. Highly levered financial systems qualify. A car crash does not. A restaurant failure does not. An airline bankruptcy usually does not. Different risk category, different response. Now apply that to quantum and Bitcoin. Quantum is not systemic. It is idiosyncratic. It fails on scalability. The attack surface is address-by-address. There is no magic “break Bitcoin” button. Cracking one exposed public key does not mechanically crack the next one. It does not trigger a cascade across the UTXO set. The attacker has to do the work for every address he wants to attack. Satoshi’s coins are the cleanest example. People talk about them as if they are one giant honeypot. They are not. They are spread across roughly 22,000 separate P2PK addresses, usually 50 BTC each. A long-range attack would have to go address by address. That is a very different risk profile from “one person can take Satoshi’s million coins.” Quantum also fails on connectivity. A successful crack of an old, long-cold address does not infect other addresses. It does not corrupt consensus. It does not rewrite the ledger. It does not change the 21 million cap. It does not cause other private keys to fall like dominos. The attacker gets access to specific vulnerable coins. That may be painful. It may be ugly. It may cause a violent repricing. But painful is not the same as systemic. This is also why the “giant honeypot” framing needs precision. The real concentrated targets are exchanges, ETFs, custodians, and other active entities. ETF holders themselves cannot rotate addresses, but the custodians controlling the actual coins can. Same with exchanges. Same with large active treasury holders. If the threat becomes real enough, those entities can move to post-quantum addresses. Satoshi’s coins are different because they are dormant. But even there, the risk is far more distributed than the panic narrative suggests. Roughly 22,000 addresses, not one vault. And this is where the fallacy matters. Once you misclassify an idiosyncratic risk as systemic, you start justifying interventions that create real systemic risk. Freeze Satoshi’s coins. Invalidate old addresses. Rush immature cryptography into consensus. Force a panic fork. Create gridlock around every other upgrade. Turn every theoretical threat into a political emergency. That is where the systemic risk actually lives. The intervention scales. The intervention connects. The intervention changes the property-rights model. Bitcoin can survive old coins moving. It cannot survive the normalization of “these coins make us nervous, therefore we can touch them.” That precedent would propagate everywhere. Lost coins. Dormant coins. Sanctioned coins. Coins from old hacks. Coins held by unpopular people. Coins held by political enemies. Coins that some future coalition decides are dangerous. That is connectivity. That is scalability. That is systemic. The cure becomes the contagion. This is why “don’t touch Satoshi’s coins” is not sentimental. It is the rigorous answer. Property rights are not downstream of convenience. They are the product. Bitcoin does not promise that every old cryptographic choice will remain optimal forever. It promises that valid coins remain valid coins, and that nobody gets to rewrite the rules because a future committee got scared. The market absorption point is secondary, but still important. Even in a nightmare scenario where very old coins moved, that is a market event, not a protocol death. Data from @Checkmatey and others shows Bitcoin absorbing 1M+ BTC of movement since October 2025 alone. A massive supply shock would hurt. It would not require us to violate property rights to survive. That is the point. None of this means “ignore quantum.” It means classify the threat properly. Working on post-quantum cryptography, testing schemes, compressing signatures, debating implementation paths, funding serious work, and having credible options on the shelf are all good things. The middle ground seems basically right: Do the work. Prepare contingencies to have on the shelf if needed. Do not rush the protocol. Do not touch Satoshi’s coins. Quantum is worth working on even if it remains a low-probability tail risk. But a low-probability tail risk is not a license to break Bitcoin’s deepest norms. That is the Infinite Perils Trap. If every scary non-zero risk becomes a protocol emergency, Bitcoin stops being conservative money and becomes a committee-managed anxiety machine. The right response is not complacency, it is proportionality. Quantum is a real research problem, but it is not a reason to freeze coins. Prepare seriously. Move slowly. Preserve the rules. Leave Satoshi’s coins alone.
English
14
33
115
22.3K
Yan | swan.com
Yan | swan.com@skwp·
We all know that government officials are bought and sold every day, but it's seldom been this much in the open and so openly disgusting. That to me signals that we are at a turning point of American society. Will we succumb to peak of empire nihilism or can we turn this ship around?
Steven Rattner@SteveRattner

Foreign contributions to political campaigns are banned. Trump found a loophole—crypto—allowing him to rake in hundreds of millions from foreign regimes buying influence. My @Morning_Joe Chart.

English
0
0
3
773
Yan | swan.com
Yan | swan.com@skwp·
I will continue saying DeFi is incredibly unsafe right now. Get out of smart contracts immediately into bitcoin. Do not walk, run!
Blockaid@blockaid_

🚨 Blockaid's exploit detection system identified an on-going admin-key compromise exploit on @wasabi_protocol across Ethereum and Base. The Wasabi: Deployer EOA was used to grant ADMIN_ROLE to an attacker helper contract, which then UUPS-upgraded the perp vaults and LongPool to a malicious implementation that drained balances.

English
0
0
6
1.1K
Yan | swan.com
Yan | swan.com@skwp·
Why does it feel like everything is being hacked? LLMs are increasing the offense/defense asymmetry. Because they're probabilistic and non-deterministic machines. Every run finds a different subset of real bugs mixed with hallucinated ones. Attackers only need to find one exploit that works. Defensive LLM scans generate a new pile of maybe-bugs to triage in every run, and you can never be sure you got them all.
English
2
0
2
697
Yan | swan.com
Yan | swan.com@skwp·
We've had lightning since 2023, but we never released it. Most Swan clients are buying in size, not spending. It comes with support burden with minimal utility for our clients. We're focusing on long term wealth clients. I would rather see people set up non custodial wallets than build yet another custodial lightning thing.
English
0
0
2
31
TFTC
TFTC@TFTC21·
Tether Investments just proposed a series of mergers that would combine Twenty-One Capital (XXI), Strike, and Elektron Energy into a single publicly traded entity. Strike, founded by Jack Mallers, brings a profitable Bitcoin financial services platform available in 100+ countries. Elektron, led by Raphael Zagury, operates roughly 50 EH/s of Bitcoin mining capacity, approximately 5% of the global network, with all-in production costs below $60,000 per bitcoin. Elektron has mined over 5,500 BTC and runs cash-flow positive. Tether intends to vote its XXI shares in favor of both mergers and is recommending Zagury serve as President alongside Mallers. If completed, the combined company would integrate Bitcoin treasury, mining, financial services, lending, and capital markets into one public platform. Tether is calling it the "premier listed Bitcoin company in the world." Transaction terms and timelines are still being worked out.
TFTC tweet media
English
51
56
437
60.9K
Yan | swan.com
Yan | swan.com@skwp·
In the age of advanced exploits by LLMs, DeFi is *NOT SAFE* Stack Bitcoin, do not let your crypto sit inside smart contracts constructed from languages that are "Turing complete" like ETH and others. This was once a marketing point used by Vitalik to launch eth, but Bitcoin *wisely* chose a non-Turing complete language for its safety. Only Bitcoin is safe from this attack. Do your own research!
Ted@TedPillows

People ask why it’s a bad day for DeFi? Kelp DAO just lost $293M in the largest hack of 2026. But zoom out: $600M+ stolen in 2 weeks. 10+ protocols compromised. AI is lowering the barrier for attackers. Biggest hacks: Kelp (bridge exploit → Aave impact) Drift ($285M, AI social engineering) Rhea ($18M, oracle manipulation) Security isn’t keeping up.

English
1
0
3
1.1K
Yan | swan.com
Yan | swan.com@skwp·
Stay safe out there. Stacking Bitcoin is the safest way to avoid getting ruined by insider trading, hacks, rugs, and other “DeFi” staples.
Dark Web Informer@DarkWebInformer

‼️ Polymarket, the decentralized prediction market platform, has allegedly been breached, with 300,000+ records and an exploit kit leaked on a popular cybercrime forum. The actor states Polymarket has no bug bounty program and was not notified. ⠀ ‣ Threat Actor: xorcat ‣ Category: Data Leak / Exploit Kit ‣ Victim: Polymarket ‣ Industry: Cryptocurrency / Prediction Markets ⠀ The actor states the data was pulled via undocumented API endpoints, pagination bypass, and CORS misconfiguration on Polymarket's Gamma and CLOB APIs. The pack also includes working POCs for multiple CVEs and an auto-dump script. Date of extraction: 2026-04-27. ⠀ What's in it: ⠀ ▪️ 300,000+ total records ▪️ ~750 MB extracted / ~8.3 MB compressed JSONs ▪️ 10,000 unique user profiles with full PII (name, pseudonym, bio, profile image, proxy wallet, base address) ▪️ 4,111 comments with attached profile objects ▪️ 1,000 report records containing 58 unique ETH addresses + admin_auth_addr indicator ▪️ 48,536 gamma markets with full metadata, condition IDs, token IDs ▪️ 250,000+ active CLOB markets with FPMM addresses ▪️ 292+ events with submitter/resolver ETH addresses and internal usernames ▪️ 100 reward configurations with USDC contract addresses and daily rates ▪️ 9,000 follower profiles with names, pseudonyms, proxy wallets ▪️ Internal user IDs exposed in createdBy/updatedBy fields ⠀ Vulnerabilities included (POCs in ZIP): ⠀ ▪️ CVE-2025-62718: Axios NO_PROXY Bypass (CVSS 9.9, SSRF to internal services) ▪️ CORS Misconfiguration on CLOB API (wildcard origin + credentials=true) ▪️ CVE-2024-51479: Next.js Middleware Auth Bypass (CVSS 7.5) ▪️ CLOB Pagination Validation Bypass (limit=999999 accepted, no rate limiting) ▪️ Unauthenticated /comments/{id} endpoint (brute-forceable, leaks full profiles) ▪️ Unauthenticated /reports endpoint (leaks user activity + admin indicator) ▪️ Unauthenticated /v1/data/followers/{address} (full social graph enumeration) ⠀ Pack contents: ⠀ ▪️ All dumped JSONs (markets, events, profiles, comments, reports, rewards, series) ▪️ 5 working POCs (CORS exploit, Axios SSRF, Next.js bypass, pagination DoS, WebSocket exploit) ▪️ Auto-dump script (continuously pulls fresh data until endpoints are patched) ▪️ Full redteam report with MITRE ATT&CK mapping ▪️ Additional 350MB data dump

English
0
0
2
1.8K
Yan | swan.com
Yan | swan.com@skwp·
A company lost its entire production infrastructure to an AI agent doing an "oopsie" on their Railway setup. Here's a few tips to prevent that: 1. No prod credentials on dev machines. Production deployments run through CI only. Nothing on laptops that can touch prod, no matter what the agent does. 2. If you do have such access due to early stage development products, etc, use a biometric gate on infrastructure commands. If you have sensitive tools, ask the agent to wrap them in pre-tool-use hooks with TouchID. It's just a few lines of code. Every time Claude wants to terraform, you have to scan your fingerprint. Trust but bioverify. And never give the agent the keys.
English
1
0
9
1K
Daniel Batten
Daniel Batten@DSBatten·
At the end of 2023 I met the person who ran GreenpeaceUSA's campaign against Bitcoin. I expected it to be tense. But it wasn't. He told me he'd read almost all of my responses to the posts they'd made on Twitter. "I wish we'd engaged with you and people like you from the outset," he said. Two months later he left Greenpeace. A few months after that they ended the campaign entirely. It was the most well-funded, yet the worst result in their history. I keep coming back to that phrase. "People like you." Not me, but a whole group: Troy Cross, Margot Paez, Elliot David, Susie Violet Ward and many others. We were working independently, with no budget and no coordination. We just shared data and conviction. It is a great story of a decentralized response beating a multi-million dollar centralized campaign, by a combination of having the truth behind us, and expressing that truth in such a way that reasonable people could see. That recipe has two parts, and it's like giving a glass of water to someone dying of thirst. The first part is truth, there must be water in the glass. The second part is the container, how you hold and deliver that truth matters just as much. You can have perfect data and still lose people if the glass doesn't reach them, or if the energy behind it makes them flinch instead of drink. We won because the data was right AND because enough people delivered it with the kind of energy that made opponents think rather than react. And this recipe, we can use again and again throughout Bitcoin's adoption journey, and each time a Bitcoiner builds a new Bitcoin project that involves outreach to non-Bitcoiners.
English
50
122
909
79.1K
Yan | swan.com
Yan | swan.com@skwp·
This is DeFi
Sweep@0xSweep

Curve's founder pulled $100 MILLION out of his own token to buy two Australian mansions and left holders with a token that dumped 98% In 2023 Curve Finance founder Michael Egorov took out $100 million in stablecoin loans across Aave, Frax, Inverse, Abracadabra and other protocols His collateral was 427 million CRV, which was 47% of the circulating supply of his own token Lookonchain traced $31 million in stablecoins flowing from Egorov to Bitfinex in April 2023 One month later his wife bought a $41 million mansion in Melbourne, right next door to the $18 million home they had purchased the year before That's $59 million in Australian real estate funded by loans against the token his own community was holding In July 2023 Curve was hacked for $70 million through a Vyper bug, CRV crashed and his positions almost got liquidated A liquidation would have created tens of millions in bad debt across Aave, Frax and other protocols and triggered a DeFi wide catastrophe To avoid this Egorov sold 106 million CRV in OTC deals at $0.40 per token, well below the market price, to a roster that included Justin Sun, convicted felon Michael Patryn, Jeffrey Huang, DWF Labs and several anonymous wallets He raised $42 million in stablecoins from these deals while community holders watched CRV dump In April 2024 he had to do it again, selling another 159 million CRV in OTC to 33 different buyers for $63 million In June 2024 CRV crashed 24% in 3 hours and he got fully liquidated for $140 million across 5 protocols The liquidation created $10 million of bad debt that the community had to absorb Ethereum developer Eric Conner did the math: "He got 100 million in stables out of a 140 million CRV position. He just transferred the rektage to the community instead" Egorov's response was that he was "committed to building Curve more than ever" thanks to veTokenomics, meaning he locked his remaining CRV to keep control of governance CRV is down 98% from its all time high and Egorov still owns the two mansions and the protocol When the founder of your protocol uses your bag as collateral for his mansion, you're not an investor You're his ATM

English
0
0
5
1.8K
Yan | swan.com
Yan | swan.com@skwp·
Bitcoin’s vastly superior proof of work difficulty ensures that individuals looking for security and longevity choose it over other crypto networks.
Alex Shevchenko 🇺🇦@AlexAuroraDev

10h ago @litecoin experienced a coordinated attack on the chain that resulted in 13 blocks reorg that took more than 3h to generate. During this time attackers were performing double spend attacks on multiple cross-chain swapping protocols. We are investigating the situation.

English
0
1
11
1.6K
Yan | swan.com retweetledi
Swan
Swan@Swan·
.@ben_mckenzie went on @jonstewart's @weeklyshowpod last week and made a series of claims about Bitcoin and crypto. @LynAldenContact responded to them in a video on the Swan YouTube channel. 🧵 Here's a thread with some clips of Lyn's takes...
Swan tweet media
English
17
50
403
58K