Rappex @Rappex_

Ronaldo Is Back.

$ETH holders: Time to rotate into $KAS. Here's why: 1. Speed kills. Kaspa runs 10 blocks per second (aiming for 100) with instant confirmations. ETH still crawls compared to that raw throughput. No more gas wars or waiting games. 2. True scalability without compromises. BlockDAG tech processes blocks in parallel not linear like ETH. This is Nakamoto consensus on steroids: decentralized, secure PoW, and hyper-scalable. 3. Massive upside asymmetry. Kaspa's market cap sits around ~$800M. ETH is over $200B. If KAS captures even a fraction of ETH's narrative, 10-50x is on the table. History rhymes. 4. Toccata hardfork is imminent (June 2026). Native tokens, covenants, ZK opcodes, SilverScript programmability turning Kaspa into a full programmable L1 while keeping blazing speed. This is ETH's 2017 smart contract moment. 5. Fair launch purity. No VC bags, no premine, no bullshit. Every KAS mined. Real PoW security vs. ETH's staked validator risks and centralization concerns. 6. Fees stay dirt cheap. High throughput = low costs forever. Perfect for DeFi, payments, NFTs, and mass adoption where ETH still bleeds users on gas. 7. Beta play in a bull market. Capital rotates from blue-chips to high-conviction tech like this. Kaspa is the fastest, purest PoW scaler out there.ETH was the king of smart contracts. Kaspa is building the king of performance with programmability incoming.Rotate before Toccata hits. $KAS is loading. What are you waiting for?

🛡️ El nuevo guardián de la defensa ya está aquí. 💪 @IbrahimaKonate_

Comunicado Oficial

@DigitalAssets And Kaspa will replace them all

👋 ¡Bienvenido, Mourinho! 👋

🚨 Bernardo Silva to Real Madrid, HERE WE GO! Agreement in place and contract approved. Two year deal plus one year option, fast deal by Madrid started 36h ago and closed immediately. Mourinho wanted Bernardo, he says yes and advanced talks revealed today are 100% confirmed.

@Lavozgalactica Venta de manual

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.

@orekilol @MarioHurtadoRM No por favor otro año así no

so this kaspa toccata thing is out now ⚡, wow

toccata live on testnet 10

@FolagoR Que le den por culo

🚨 BREAKING: José Mourinho back to Real Madrid, HERE WE GO! 💣🤍 All terms have been verbally agreed between José Mourinho and Real Madrid, waiting to sign all documents. Plan for initial two year deal, JM to travel to Madrid after Real-Bilbao game. The Special One is back.

why I’m personally excited about Kaspa’s upcoming Toccata covenants - for the first time, I can build creative, complex apps directly over infrastructure I helped design and build - we designed under architectural constraints, but the result came out surprisingly expressive and powerful - Silverscript is cool as hell - I can literally open a *.sil file and write a complex contract that will be fully verified on Kaspa L1 - (nottoself: create a 10-minute video showing the building of such an app e2e) - I can design my own vaults and safeguards, and manage funds securely without risking a heart attack each time I touch a wallet - covenant ids, contract templates, and inter-covenant communication (ICC) feel like a new set of axioms, or a new algebra to work with and discover - sig verify from stack / sighash anyone-can-pay + covenant ids can allow interesting shared-state covenants (requires a non-consensus miner policy; kudos to @maxibitcat for pushing this line of thinking) - complex contract systems can be deployed in one spk hash. no storage rent, no deployment tax; users pay only the transient mass for tx data as they use it - as I’ve mentioned in the past, this becomes especially interesting for AI/agentic environments, where bots could cheaply create one-time agreements between themselves - I didn’t even mention based apps yet. That’s a whole vertical that isn’t ready for exploration yet, but will be very soon

What most people are missing about Toccata is that it is not “smart contracts coming to Kaspa” in the Ethereum sense. That framing is lazy. Toccata is more specific and more important: it is Kaspa adding constraint logic, zk verification, and sequencing commitments to a high-throughput UTXO blockDAG without converting the base layer into a global execution machine. It is programmability without surrendering the architecture that made Kaspa distinct in the first place. The first piece is Covenants++. In a normal UTXO system, coins are locked by conditions and then spent if those conditions are satisfied. Covenants extend this by letting outputs impose rules on future spends. That means the transaction graph itself can carry enforceable structure: vaults, staged releases, spending paths, asset lineage, canonical bridges, escrow flows, multi-step contract interactions, and constrained application logic. This is not a VM where every node executes arbitrary program state. It is local UTXO computation with recursive constraints. The difference matters. Ethereum-style programmability globalizes execution. Kaspa-style covenants localize it. The second piece is zk verification. Toccata includes zk opcode/verifier infrastructure, with support discussed around flexible proof verification paths such as Groth16-style proving and RISC Zero-style STARK verification. This lets external computation be proven to L1 instead of replayed by L1. That is the real scaling primitive: do the heavy work elsewhere, submit a proof, and let Kaspa verify the commitment. This is how you get toward zk apps without turning every Kaspa node into an application server. The third piece, and maybe the least understood, is partitioned sequencing commitments. ZK applications need proof costs to scale with their own activity, not with the entire global DAG. Sequencing commitments are designed to let apps reference L1 ordering in a more scalable way, so based zk systems can follow Kaspa’s sequencing without needing to prove the whole network history every time. That is not a minor detail. That is the bridge between high-BPS settlement and practical zk application design. Toccata is not the final form of Kaspa programmability. It is explicitly not full vProgs yet. The current stage enables standalone zk applications, canonical proof-based bridging, covenant logic, and the primitives needed for later synchronously composable verifiable programs. In other words, Toccata is the hinge: Kaspa moves from fast money into programmable settlement, while still refusing the bloat of a monolithic world computer.

Kaspa.org has been refreshed. Kaspa has a lot going on, but the main site does not need to put it all at the front door. Its first job is simple: help someone arrive, understand what Kaspa is, and know where to go next. The previous site accumulated more over time. Pages, explanations, resources, and audiences were added. This version starts smaller, so it can grow with Kaspa from here. The refresh is not just visual. The wording, structure, and narrative direction all needed attention IMO. The content traces back to @hashdag’s writing, simplified for a first read. Kaspa is already deep enough. The first read should not make people work harder than necessary. There are many true ways to talk about Kaspa, but Kaspa.org cannot carry twenty narratives at once. For this version, the strongest one to unify around is real-time decentralisation. Part of the refresh was also about making the builder path easier to follow. Kaspa.org gives people the overview of what exists, why it matters, and where to go next. Docs.kaspa.org gives builders the deeper material, with room for examples, detail, and ongoing improvement. Docs.kaspa.org starts with @IzioDev's work and has the broader goal of bringing important Kaspa L1 builder documentation into one place. Both repos are public. Pages will be added, wording will change, gaps will be filled, and the work can happen in the open. Big shoutout to @kasmediadotcom for their support in helping bring this refresh together. Have a look around. If you see something that can be better, please open an issue or PR.

El peor virus que padecemos desde hace siete años se llama Psoe. La mejor vacuna, las urnas.

A mi hijo de 18 años le han preguntado en el instituto a quién va a votar. El ha dicho que a Vox. Respuesta del profesor: -No te da vergüenza? Respuesta de mi hijo: -Vergüenza me da no poder salir a la calle tranquilamente.