Jorge 𐤊 ױ

Holding gold on-chain without staking it is like having a Michelin-star chef in your kitchen and ordering DoorDash. The capability is there. You are just not using it. Earn ~12% APY on your $GGBR → stakemygold.com

Everyone talks about crypto's carbon footprint. Most of the time, that's fair, but it depends on what's behind the scenes. The gold backing $GGBR is in-situ or unmined. The environmental standard of tokenized gold should look like this.

@oneforonehaha note there exists a documentation website for programmability in Kaspa, the temporary link was published by izio a few weeks ago in the pub rnd channel progdoc.izio.fr/overview.html I presume it will migrate/redirect to a different URL soon. Please bombard core with questions and clarifications needed until they are sick of you and have no choice but to spell it all out fully clearly legibly onchain

On hashd.ag/staghunt/, we are able to see @hashdag's theory for why decentralized blockchain is still needed and more needed than ever. Link to Y speech at @OxfordUnion: hashd.ag/oxford-union-a…. We are very proud to have orchestrated and funded it. Full-length 40-min video to be released soon.

@Chris_Hutch7 @oneforonehaha @michaelsuttonil L2 and EVM on kaspa - just as ethereum is stepping away from both of these in favour of simply better tech - is just wholesome cringe. And calling it "a usecase". vitalik.eth.limo/general/2025/0… Chris, happy to address usecase/adoption - in more serious threads

AI just diagnosed cancer. Without a single human telling it where to look. A team of specialized AI agents analyzed gigapixel pathology slides on their own. No manual guidance. No selected regions. Just agents collaborating to find what matters. This is what multi-agent AI looks like in the real world. 🧵

Video diario! #KASPA $KAS youtu.be/sOAWbrm4660?is…

⚡️MAJOR UPGRADE: KASPA SET FOR "TOCCATA" HARD FORK Kaspa (@kaspaunchained) is gearing up for the Toccata hard fork, a major upgrade that adds powerful covenants via extended opcodes and enables based zk apps with verifiers like Groth16 and RISC Zero. This brings native L1 programmability and partitioned sequencing to Kaspa’s blockDAG, unlocking canonical bridging, stateful multi-contract flows, and proving costs that scale directly with app activity instead of the entire network. The original May 5 activation has moved to June 5–20, 2026, to finalize the sequencing architecture for full stability. Feature freeze hits April 15, followed by testnet validation and mainnet node upgrades. Toccata sets the stage for the next era of scalable, expressive blockchain tech on Kaspa.

imho we should stop treating Kaspa as being in sos mode whereby all means are required and justified. L2 fragmentation is a very real problem and risk, and we have the time to do it right. Hence vprogs. Hence escaping the L2 language and focusing on a single dimension of apps only

Hey @okx & @star_okx When are you going to list QUBIC on OKX 👀 Let’s show them how powerful and united the #QUBIC community truly is, 💪it’s time to make some noise!!

@Vladcostea Tachyon is not solving scalability rather it is solving the particular scalability challenge zcash had needing to store the entire note commitment tree history. Its solution is an adaptation of archival nodes to zcash. (Worry not, zcash can succeed even wo solving trilemmas;)

@Chris_Hutch7 @emdin @oneforonehaha @hashdag From all I know it will be a Solana-like experience. Of course my words carry weight and I can’t and won’t promise this until we’re much closer, but I see no big obstacles to this vision.

Guys check this out this is the coolest thing ever. You can now store encrypted files or passwords directly on $KAS L1 at kassword.com/#. I used this to encrypt a 12 word Kaspium seed phrase with 1,000 $KAS in it. First one to decrypt it will get the coins. Let’s see how good Kaspa’s encryption is. Once again, we see another project #PoweredByKaspa that would be considered spam on Bitcoin. Study Kaspa. Save in Kaspa. Use Your Kaspa. It’s that simple.

No, not really. The main focus of the vprogs effort is to establish a "meta-protocol" for applications and state to be seamlessly composable across VM and proving system boundaries. So the primary goal is to define something like a "common language and set of primitives" that ensures that different VMs can talk to each other. This doesn't mean that any based VM is automatically a vprog but it means that any VM could potentially become part of the vprogs ecosystem by adopting this common language. Depending on the modularity of the corresponding VM and how much it focuses on being an actual VM that drives state transitions rather than a full blown "protocol", this can vary in effort. Generally speaking, more modern VM's that put more effort on modularity should be easier to integrate than older ones and we have shown that both Move as well as Risc0 can be supported with less than a few hundred lines of code for the plumbing. Since you asked about RETH, I suspect that this would be a VM/protocol that would take slightly more effort as it takes care of things that should be left to the implementor (like commitment schemes and state management). Often times even older execution environments like the EVM are able to support more modern optimization mechanisms (like EIP-2930 for RETH) but to provide backward-compatibility these are usually "optional" which increases the amount of work necessary to comply with the vprogs standard (because here we care more about bare metal performance than backward compatibility). Instead of looking at vprogs as "just another VM" we should look at it as a "meta-vm" or an "interoperability layer for VMs" that takes care of exactly those things that are common to all VMs in a generic and optimized way while maintaining the freedom for developers to express logic in the way they are used to.

@tangem_spanish @venom1977t @Tangem Vamosssss!!!

🎉 Lanzamos nuestra cuenta en español… y lo celebramos contigo Sorteamos una billetera de @Tangem — edición a tu elección... ¡GRATIS! ¿Cómo participar? • Síguenos • RT + Like • Comenta en español 📅 Anunciamos ganador en 7 días Bienvenido a la nueva era de la autocustodia 🔐

I beg to differ @oneforonehaha. Cov+ZK is conceptually the same as what the OP_CAT camp in BTC is pushing for. In principle, we could've introduced programmability into kaspa by merely adding OP_CAT; that would've been easier to communicate, though not to build with; you'd still need a silverscript-like compiler cc ON, easy authentication of covenant lineage cc MS, etc. BTC's OP_CAT doesn't magically make program development accessible. Ecosystem differences aside, any practical, developer-friendly utilization of OP_CAT would be in the ballpark of what kas core designed here. (One arguable exception: BTC could've used the simpler block header sequencing commitment and require apps to zk-prove the entire onchain activity and not just their app's activity; infeasible for high throughput). With all the great ideas baked into the design, I still think we should view the upcoming HF as a natural next step, one that has no particular research angle or conceptual novelty. Think of it as OP_CAT++

Can we test how many Kaspians is there? Vote and RT. $KAS

@oct_gems $KAS & $QUBIC soon

Which Altcoin will reclaim their ATH First? $KAS - $0.2 $ANYONE - $3.9 $QUBIC - $0.0₄1 $OCTA - $2.4 $PAAL - $0.8 $RENDER - $13.5 $KTA - $1.69 $ZANO - $18 What do you think? 👇

The science side of $Qubic is next level. Two papers targeting Artificial Life 2026 and AGI-26 using MultiNeuraxon. Not just mining DOGE — advancing brain-inspired AI on a decentralized network. Most projects talk about AI. $Qubic is doing the research. huggingface.co/spaces/DavidVi…