Jorge 𐤊 ױ

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…

Paid close attention to the "already-in" and "finalized" parts. Does it mean that we will see a release candidate version by Apr. 15 (the finalized deadline)? Saw a lot of exciting progress on TN12 these days by multiple core devs... looks like there will be a wave of PR merges -> a finalized version of TN12. Will devs have a TN10 with the TN12 features and changes to be brought by this HF by Apr 15 (or when will it be available according to your estimate)? cc @michaelsuttonil @oneforonehaha

The chairman of @KaspaKii , @pvson, is the founder and president of an international group of 120+ energy infrastructure and financial companies with a combined valuation of more than $5T based on my best estimates. Five...trillion…dollars. And that’s probably on the low end of things…and they are going with #Kaspa. This man is telling you that they specifically chose $KAS to “position Kaspa as the ultimate base layer for various applications…for industrial and enterprise applications in finance, supply chain, energy, and the public sector, while promoting sustainable and ethical development.” They are now telling you that only $KAS can do what is needed to build their infrastructure for energy trading and other applications that I don’t even understand lol. They told you that Bitcoin and Ethereum cannot do what they need them to do to accomplish their tasks. Anyone telling you AI agents are going to use $BTC is lying to your face. Anyone telling you Bitcoin’s slow speed is a feature is coping and doesn’t understand anything about the world. Please read the attached article posted by KII to see the results of all the stress testing they did on Kaspa’s testnet-12.

@c___f___b My Last Match (MLM) is a post-apocalyptic survival MMORPG built on Qubic using Unreal Engine 5. Set in the 90s. One persistent world. Up to 50,000 players. Every in-game transaction runs on-chain using $QUBIC as the native currency.

While the mining side of Qubic just had the biggest week in its history, there's something else cooking that most people haven't even noticed yet. My Last Match. Built by @c___f___b himself. 🧵 Here's what it is, how it works, and why it matters 👇

Video diario! #KASPA youtu.be/7O3fenNIQos?is…

I’ll take the liberty of answering, but of course I’d love to hear @hus_qy’s perspective as well. In short, no. It will not be a vprog in the sense defined by the vprogs yellow paper. And that’s because it will not allow synchronous composability (aka syncompo) with other zk apps. The vprogs design aims to solve a tension that is inherently hard to solve: - giving each app sovereignty, including proof-liveness sovereignty, which means it has a dedicated covenant on L1 - enabling synchronous composability with other progs that do not necessarily share the same L1 covenant, and can even belong to a different vm with a different zk proof system The reth L2 you are describing is like a standalone mega-app. I call it mega because it allows its users to submit custom smart contracts into it. It indeed supports syncompo between inner contracts, but that comes at the cost of sovereignty: these contracts are not standalone units, but rather parts of the same monolithic mega-app. In contrast to its inner syncompo, it does not support syncompo with external applications or with other external mega-apps

@SatoshiCheckEco @KaspaSphere @BitcoinRachy Here is cryptographic proof of an empty UTXO set at the genesis block, faggot github.com/kaspagang/kasp…

@maxibitcat okay okay to your original point then: if push comes to shove i'd bet a change of pow to pouw - which budgets mining thru AI inference (really thru any MatMul) - before any dirty talk on tail emissions. I'm NOT hinting this is planned concretely, but imo it should be on the table