Robert Mueller died today at 81.
Vietnam veteran. Marine. 50 years of public service. FBI Director under two presidents.
Trump’s response.
“Good, I’m glad he’s dead. He can no longer hurt innocent people.”
The President of the United States celebrated the death of a decorated American veteran and public servant within hours of his passing.
Mueller found Trump likely obstructed justice.
Trump found that unforgivable.
James Comey was subpoenaed this week.
130 subpoenas issued to everyone who ever investigated Trump.
Pam Bondi testifies under oath on April 14th.
The Epstein files are half sealed.
A man who served his country for 50 years died today.
The President said he’s glad.
That tells you everything about who he is.
Never stop connecting the dots.
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- https://t.co/o8vKa7gBwm)
🔴💸 ALERTE : Raphaël Arnault avoue avoir utilisé l’argent de l’Assemblée pour les extrémistes antifas.
"À l’Assemblée, tu as des enveloppes. Je vous avoue que c’est pas mal : comme ça l’argent personnel peut aussi aller un peu dans la lutte ! C’est pas mal tout ça !" (LFI)
Kaspa’s covenant stack is converging on a shared goal: make real L1 apps approachable, and make secure design the default rather than an expert-only art.
tl;dr
Two layers are landing in tandem:
(i) Top of stack: a high-level language that makes covenant authoring feel like “writing apps”, not “fighting script”
(ii) Base of stack: a consensus primitive that makes stateful covenants practical at scale, without recursive lineage proofs
Silverscript was just announced as Kaspa’s first high-level covenant language/compiler, targeting local-state apps in the UTXO model. Complementing that tooling is KIP-20: Covenant IDs.
The strategic role of KIP-20: UTXO already ties “rules own state” locally via the spending script. The difficulty is carrying that relation temporally across transitions in a local-compute model, without turning every spend into a recursive “prove my ancestors” witness construction.
KIP-20 tightens that temporal linkage at the consensus layer by introducing a covenant_id tracked by consensus. Result: stateful designs no longer depend on parent or grandparent transaction witnesses as a lineage workaround. They become first-class citizens: covenant identity and lineage are native, so designing secure stateful schemes becomes simpler and more robust.
The broader theme is security-by-construction: Approachability isn’t just syntax. It is making it easy to write covenants that correctly validate state transitions, and hard to accidentally ship an insecure scheme. The compiler/scheme connection is still wip, but the direction is clear: have the compiler generate transition logic, then wrap it in schematic code that enforces a declared covenant pattern.
For now, Silverscript’s covenants/sdk folder is the best reference for how these pieces should meet from my pov. I am planning a longer overview tying together the various recent components.
Spec: https://t.co/aoTBUlAqsZ
PR: https://t.co/gOKQEZlOet