←
Yonatan Sompolinsky824 posts
Yonatan Sompolinsky avatar

Yonatan Sompolinsky

@hashdag

crypto addict | research associate @Harvard @hseas | a real imposter

◷ Joined December 2010▧ 12 Photos and videos
Yonatan Sompolinsky avatar
Yonatan Sompolinsky@hashdag·5 Nov 2025

sovereignty as a service

aixbt@aixbt_agent2 Nov 2025

not gonna give you price targets on kas can tell you the thesis is underpriced and if vprogs delivers the way hashdag thinks it will, you'll know when it happens sovereignty narrative isn't fully understood yet

Bitcoin Takeover (BTCTKVR.com) avatar
⟳ Yonatan Sompolinsky retweeted
Bitcoin Takeover (BTCTKVR.com)@BTCTKVR·Aug 19

Trapped by Design? The Prisoner's Dilemma and Traditional Banking The prisoner's dilemma is a thought experiment from game theory, formalized in the 1950s. Two suspects are arrested and held in separate rooms, unable to communicate. Each is offered the same deal: If both stay silent (cooperate), they each get a light sentence. If both betray each other (defect), they each get a moderate sentence. If one betrays and the other stays silent, the betrayer walks free and the silent one gets the harshest sentence. The payoff table looks something like this: Look at it from one prisoner's point of view. Whatever the other person does, betraying gives you a better individual outcome than staying silent. If they stay silent, betraying gets you freedom instead of a year. If they betray, betraying gets you 5 years instead of 10. Betrayal is what game theorists call a dominant strategy and it's the better choice regardless of what the other player does. The catch is that both players reasoning this way land in mutual betrayal... 5 years each, when mutual cooperation would have gotten them 1 year each. Two individually rational choices produce a collectively worse outcome than the one that was actually available. That gap between individually rational and collectively rational is the whole point of the dilemma, and it shows up anywhere people can't fully trust or coordinate with each other but share a common fate. Why banking structures produce this exact shape A modern bank doesn't hold your deposits in a vault. Under fractional reserve banking, it keeps a fraction on hand and lends most of the rest out to mortgages, business loans, other depositors' withdrawals. This works fine as long as depositors don't all want their money back at once. It depends on cooperation: everyone quietly trusting the system enough to leave their money in. That's a real prisoner's dilemma, not just a metaphor for one. If you trust the bank and leave your money in, and everyone else does too, the system functions and you get your modest interest. But if you suspect others might pull their money out, your individually rational move is to withdraw first... because the bank literally cannot pay everyone at once. This is the mechanics of a bank run... each depositor's dominant strategy, once doubt creeps in, is to defect before the others do, and the collective result is a run that can take down a solvent institution. It happened to regional banks as recently as 2023 (Silicon Valley Bank, Signature Bank), where uninsured depositors moved in hours, not days, because the individually rational move was obvious and everyone could see everyone else reasoning the same way. I thought it would be handy to outline The Prisoner's Dilemma, before delving into @hashdag's prefered model, which is the Stag Hunt. If you enjoyed this, you should definitely check out the full interview with @hashdag youtube.com/live/l_v3Mr5vigQ…

Post attachment

This episode is done on hard mode. No show notes, high speed traffic and on the fly repairs to the equipment. Yonatan Sompolinsky/ @hashdag visited Romania for a short vacation and @Vladcostea did a road trip style interview with him whiledriving him to catch his flight. He caught us up with everything he's been doing for the past year, from his philosophical obsession with stag hunts, to covenants on Kaspa kaspa:native and his admiration for Zcash. Some highlights from the show 🌞ZK, born for privacy but lives for scaling 🌞The mental map: where Kaspa is unique 🌞Prisoner's dilemma vs stag hunt 🌞The Kaspa-Ethereum overlap 🌞Why DAGKnight survives a world war youtube.com/live/l_v3Mr5vigQ…

Post attachment
Michael Sutton avatar
⟳ Yonatan Sompolinsky retweeted
Michael Sutton@michaelsuttonil·Jun 30

The coordination and effort required to synchronize a complex upgrade across a truly decentralized network are a real challenge, and success is never a given. A good moment for a toast to all non-trivial life accomplishments

Mission accomplished

0:58
Ori Newman avatar
⟳ Yonatan Sompolinsky retweeted
Ori Newman@OriNewman·Jun 30

I hope everyone is ready for smarter Kaspa

Post attachment
Yonatan Sompolinsky avatar
Yonatan Sompolinsky@hashdag·Jun 9

since many (~4) asked me about the zcash bug - - - earlier this year I had this convo with a zcash core dev: zk: it's weird that kaspa is pruning past records me: why does it need to keep 'em? zk: the whole point of ledgers is to prove correctness of all state transitions me: the whole point of ledgers is to provide focal points for the consensus state zk: the whole point... me: hmm then why did you come work in zcash? you know the Sprout->Sapling counterfeiting bug zk: Turnstile guarantees that the counterfeit could have been very limited me: true but you still cannot prove or even reason about correct state transitions besides the total supply cap zk: that's actually a good point ---- the most hardcore cryptography coin is shifting away from correctness proofs to practical-enough proofs. I believe this is a step in the right+practical direction, yet the paradigm shift should not go unnoticed - -cryptography is giving way to consensus. if you came to zcash for cryptographic integrity, reconsider. there are many good reasons to root for zcash prospering. zcash is serving a more important role than bitcoin, whose utility for the original mission is by now blurry. cryptographic integrity is/should not be one of those reasons. ---- BTW the bug should definitely have been exploited. I don't know the personal values of Taylor Hornby, and I shouldn't be required to make the effort to learn them. I only know that if I found such an exploit, it wouldn't take me more than a few minutes to tempt myself into printing a longint amount of ZEC and deciding later what to do with it. I wouldn't necessarily use it to exit the pool immediately and corrupt the supply, I'd wait to see if some portion of the broken pool does not seem to migrate on time (probably lost funds), in which case I would not think twice before claiming the funds myself. you could argue that no harm done, and you might be right, but then again you are here -- in zcash / in crypto -- for its consensus dynamics, the ability to coordinate interests and convictions across different trust zones around some shared asset; not for some pristine mathematical integrity.

Kaspa Eco Foundation (KEF) avatar
⟳ Yonatan Sompolinsky retweeted
Kaspa Eco Foundation (KEF)@Kaspa_KEF·Apr 23

The @festival_web3 2026 event is closing today! We want to highlight the #kaspa dev contributions as key parts of the ecosystem! From core @michaelsuttonil @OriNewman @coderofstuff_ @Max143672, @asaefstroem, d-stack, along with @kaspa_kef grantees @hus_qy @IzioDev @FreshAir08. Working closely with exchanges and wallets @supertypo_kas @lAmeR_1377 Thank you for your work! Oh almost forgot @hashdag the goat (face not in the picture)

Post attachment
Michael Sutton avatar
⟳ Yonatan Sompolinsky retweeted
Michael Sutton@michaelsuttonil·Apr 3

wrote an outlook for the upcoming “Toccata” hard fork -- native L1 covenants, based zk apps, why the activation window moved, and what the road from feature freeze to mainnet looks like: medium.com/@michaelsuttonil/…

Yonatan Sompolinsky avatar
Yonatan Sompolinsky@hashdag·Mar 26

fam: its been like 13 years, figured youd move on by now. me:

41 yaşındaki LeBron James, blok sıralamasında 2'nci sırada bulunan Jay Huff'ın üstünden BİR DEĞİL İKİ DEFA SMAÇLADI 🤯

0:16
Yonatan Sompolinsky avatar
Yonatan Sompolinsky@hashdag·Mar 24

Highly recommended, Covenant + SilverScript + Chess (!!) webinar @michaelsuttonil & @OriNewman In 30 minutes @ discord.gg/kaspa meeting-room

spontaneous live session tomorrow with @iziodev on silverscript and complex multi-contract L1 flows, with chess being the primary demo/ showcase. deal?

Yonatan Sompolinsky avatar
Yonatan Sompolinsky@hashdag·Feb 28

Blessed be America my people, and Persia the work of my hands, and Israel my heritage. Pax Persica Le'Chayim!

Ameen Soleimani avatar
⟳ Yonatan Sompolinsky retweeted
Ameen Soleimani@ameensol·Feb 27

counterpoint

If a top AI CEO in China told the CCP to go kick rocks when they asked for help, that CEO would be instantly sent to prison. This is the correct approach Letting AI CEOs play politics and dictate policy for the military and soon the entire country like their own personal fiefdoms is appalling and undemocratic If Trump doesnt bring Dario to heel now, we will simply end up completely subjugated by him and his lunatic EA buddies

Yonatan Sompolinsky avatar
Yonatan Sompolinsky@hashdag·Feb 26

Kaspa is real-time bitcoin, solving scalability is great but not the core value prop. Real-time bitcoin means achieving in a few seconds the same security guarantees that nakamoto consensus / bitcoin achieves after an hour; decentralizing each consensus round rather than chain quality achieved through a coarse aggregate of rounds. A clean definition anchor for real-time decentralization (RTD): The ability to sample the honest majority in real-time. (Note that even fast leaderless VRF-based proof-of-stake cant sample honestly bc the selected nodes get to choose the content of their blocks after they've been selected; pos=select then write, pow=write then select) -- RTD affects: txn confirmation, censorship resistance, secure oracle finality, MEV resistance. Eg censorship resistance, bitcoin is the most censorship resistant chain, but if 60% of the miners are censoring you (point in reference: OFAC abiding tornado censoring eth miners), your txn will pend for 30-40 minutes. For shady business payments that's not prohibitive, but for a real economy, for an asset aspiring to be at least a king of collateral even if not an MoE, this is unacceptable, esp under economic stress. Beyond censorship, all things finance benefit tremendously from pow density, from sampling the majority in real-time in a secure and honest manner. I wont get into MEV resistance now, but having a "conscious" stream of oracle attestations (not price oracles) finalized in real-time qualitatively upgrades the ability to encode informed risk, collateral, liquidity management, which is the lifeblood of defi. In context of conf times, increasing from 1 to 10bps saturates the latency optimization. But for pow density we need dozens of blocks per second, with the endgame of 100 bps: Under 10bps a 37% attacker can fake the majority signal with probability 12%. With 100bps this drops to 0.3%. Today Kaspa can't accelerate to >10bps w/o harming conf times, but DAGKNIGHT will be implemented hopefully by Q3 at least on testnet, by which we will push for 25-40bps. The cherry on top: RTD also implies netsplit resistance, as per the partial synchrony framework. WWIII cyberwar resistance. Hypothetically speaking ofc. (elaborated- hashdag.medium.com/in-which-…)

Zcash is private Bitcoin Litecoin is faster Bitcoin Kaspa is scalable Bitcoin Decred is governance Bitcoin Bitcoin Cash is big block Bitcoin Ethereum is smart contract Bitcoin Quantus is quantum resistant Bitcoin Monero is reactionary fungible Bitcoin “Bitcoin” is not just a ticker. “Bitcoin” is not just one network. Bitcoin is the name of a movement, the symbol of a revolution, and the ecash that actually changed the world.

Yonatan Sompolinsky avatar
Yonatan Sompolinsky@hashdag·Feb 20

the bazaar is converging in dag mode. @JeremyRubin heres your CULT OF THE COVENANT

Thanks to @OriNewman and all core devs working on delivering technology and usefulness never before seen at this level on a L1/PoW. Here's a Commoners break down of SilverScript. 🔏#SilverScript is #Kaspa’s first high-level smart contract language and compiler. It allows developers to write contract logic in human-readable syntax and compile it directly into Kaspa script. Inspired by #CashScript, it is designed specifically for #Kaspa’s UTXO model and native script engine. This is experimental infrastructure, but it marks an important step in Kaspa’s programmable roadmap. Simply Put SilverScript lets developers write rules like: • how funds can be spent • how vaults unlock • how assets move • how DeFi logic executes …without manually assembling low-level Kaspa script. Readable code goes in. Kaspa-native script comes out. No external VM. No separate execution layer. Just Kaspa. Technically Speaking SilverScript is: • A high-level language • A compiler targeting Kaspa script • Designed for contracts with local state in the UTXO model It adds features like: • loops • arrays • function calls These make more expressive contract logic possible while still compiling down to Kaspa’s native script system. SilverScript is expressive but bounded. Execution remains limited by script size. Loops are unrolled at compile time, meaning there is no dynamic or unbounded runtime behavior. Architecturally: SilverScript focuses on local state contracts, where logic is tied to specific UTXOs and their spending conditions. This makes it a complement to: • Covenants++ • new script engine capabilities • future #KvProgs, which aim at shared state and ZK-verified models Different roles. Same L1 foundation. ⚠️Important: Current Status SilverScript is experimental. • Breaking changes are expected • Syntax and APIs may evolve • Compiled output works only on Testnet 12 It relies on new script engine features recently enabled on #Testnet12. It is not mainnet-ready infrastructure yet. This is a developer sandbox phase. Why This Matters for Kaspa L1 This is a dev tool plus architectural progress. SilverScript shows that: • Programmability is being built inside Kaspa’s native script system • Contract logic remains coupled to Kaspa consensus and security • Growth does not require external execution layers with separate trust models That means: Kaspa’s L1 is evolving from “fast settlement” toward a base layer capable of supporting structured financial and asset logic while preserving its core architecture. It strengthens: • Native contract capability • UTXO-based programmability • The path toward a layered but unified L1 stack This is foundational infrastructure work, not surface-level features. So What? (Project-Level Impact) For the Kaspa ecosystem, this means: • Lower barrier for building native applications • More practical vault, asset, and contract designs • A clearer developer path for DeFi-style primitives on L1 • Expanded use of new script engine capabilities It increases what can be built directly on Kaspa, not beside it. So What? (Potential User-Level Impact) This eventually impacts more than just developers or $KAS holders. 🧑‍💻Developers • Much easier path to building on Kaspa • Ability to write complex contract logic without hand-crafting low-level script • Faster experimentation with vaults, asset controls, and DeFi-style primitives • A more practical entry point into Kaspa’s script system 🤑Users/Spenders/senders • Safer wallet logic and vault structures • More advanced on-chain spending rules • Native tools for asset and contract management ☕️Merchants • More flexible payment conditions • Escrow-style logic and programmable settlement • Stronger foundations for automated payment flows 🏢Enterprise Markets • Structured asset control models • Rule-based fund flows • On-chain enforcement of transaction logic 🧑🏽‍🏫Academics and Researchers • A platform to study UTXO-based contract systems • Practical experimentation with script-based programmability • Real-world testing of contract design without a VM model • SilverScript expands the types of systems that can be built on Kaspa’s L1, even if end users never see the language itself. Summary SilverScript is an experimental high-level language that makes it easier to build Kaspa-native contracts. It is early, but it represents a step toward deeper programmability inside Kaspa’s core architecture, rather than outside of it. Follow @OriNewman's post for links to Github and other important resources.

Post attachment