Pinned Tweet
Si acabas de llegar a mi perfil:
Principalmente hablo de Kaspa y Qubic.
Pero intento hacerlo de una forma distinta.
No solo “ha subido KAS” o “Qubic anuncia X”.
Me interesa explicar qué hay detrás:
⚡ BlockDAG y DAGKnight
🧠 Useful Proof of Work y AI
🔐 ZK, Covenants y vProgs
🧩 KCC20, KRC20 y smart contracts
⚙️ Computors, quorum y arquitectura de Qubic
Si algo es bueno, lo digo.
Si algo no me convence, también.
Y siempre intentando explicarlo para que se entienda.
Jorge 𐤊 ױ retweeted
🚨 KCC-20 GOES LIVE TOMORROW
14 days after final call, the token standard that powers #Kaspa L1's DEXs, launchpads and order books lands on mainnet.
The venues will follow shortly after — and
@daggertradebot is ready for every one of them. All 7 are already live and proven on our testnet bot (buy, sell and launch), so the moment a venue is good for mainnet, we flip it on. No waiting, no catch-up.
🌊 Zealous
🍳 KCom
🚀 KaspaRocket
🪢 Braid
🦭 KasSeal
⚒️ KForge
🏭 PumpForge ( KasForge )
One wallet. One place. Every venue on Kaspa L1.
All venues. One place. Dagger. 🗡️
🗡 Set up now, ready for day one 👉 t.me/Daggerkcc20bot?start=DA…
🌐 daggertrade.com
Jorge 𐤊 ױ retweeted
So many tradeoffs, nuances, and complexities, so why not ditch it all and just implement native smart contracts on-dag?
The gist: I believe zk tech provides a leap in the ability of replicated state machines to scale computationally. So any sc sys without zk is inferior
New research post exploring a core challenge: multileader consensus (great for speed & MEV-resistance due to execution uncertainty) vs. inclusion-time zk proving (ideal for atomic composability).
Why they contradict and why this points to timebound proof settlement where proof availability is decoupled from txn data availability:
research.kas.pa/t/on-the-inh…
Kii is giving a keynote at the ETIM Forum 2026 in Torremolinos, Spain on 28 October.
We will show KiiWORKS: digital product passports for industry, built from the ETIM data manufacturers already publish and verifiable by anyone on Kaspa.
#Kaspa
Jorge 𐤊 ױ retweeted
Woah! Kaspa does what zcash does!
Woah! Kaspa does what monero does!
Woah! Kaspa has what solona has!
Woah kaspa has what Bitcoin has
Woah! Kaspa has apps like the app store has!!!
Very soon it will click
And people will realize that kaspa just ended 99% of cryptp
Jorge 𐤊 ױ retweeted
Hi DEXTools team,
Shawn from KRON here. We saw you're looking to connect with projects on Kaspa, so I'm reaching out directly.
What KRON is
KRON is a DEX running natively on Kaspa L1. Pools are Kaspa covenants (no L2, no bridge), and tokens are KRON's KCC-20 covenant tokens paired against native KAS. It's been live on mainnet since July 2026, and the covenants were independently audited by Hashlock in September 2026 (kron.technology/audit).
What we've already built for data aggregators
CoinGecko pointed us to GeckoTerminal for onboarding. We built a full adapter in GeckoTerminal's Integration API format, and GeckoTerminal is integrating us now. The same data is open to you:
DEX events API (GeckoTerminal format), base idx.kron.technology/v1/dex-e…
- /latest-block: latest indexed block
- /asset?id=: name, symbol, decimals, total and circulating supply
- /pair?id=: pair assets, creation block/tx, fee (bps)
- /events?fromBlock=&toBlock=: every swap and liquidity event, with exact amounts, maker address, reserves after each event and native price
Market data API, base idx.kron.technology/v1/aggre…
- /tickers: price, volume and liquidity per pair
- /historical_trades and /supply/{tick}
The full history is backfilled from the first pool. All endpoints are public with open CORS.
A few Kaspa-specific notes:
- Kaspa is a blockDAG, so "block number" is the blue score of the accepting chain block; timestamps are in seconds.
- Token ids are covenant ids (64-hex). KAS is the native quote asset.
- A signed token list with per-token metadata and logos is at api.kron.technology/api/regi….
- An open-source SDK is on npm as @kronsdk/kron-sdk (github.com/KronSDK/kron-sdk).
What would you need from us?
Could you let us know what your integration requires? In particular:
1. Can you consume an API like the one above, or do you index chain data yourselves? If so, what node or RPC access would help?
2. Do you need a specific data format or extra fields?
3. Token metadata, logos or socials in a particular format?
4. Any listing form, verification step or point of contact on your side?
Happy to set up a shared channel and turn around whatever you need quickly.
Thanks,
Shawn
KRON (kron.technology)
@DEXToolsApp
Jorge 𐤊 ױ retweeted
A proof of concept for shielded native $KAS has run on testnet TN10, @kaspaunchained developer Olaf Weller says.
The work is unaudited and not yet a finished privacy protocol.
bsc.news/news/kaspa-shielded…
I like! This is a really simple and inexpensive way to significantly reduce the quantum threat to Kaspa users.
Traditional addresses expose the public key controlling the funds. A sufficiently powerful quantum computer could derive the private key from that public key and steal the funds.
KIP-22 proposes a simple change: instead of exposing the public key, an address commits to a cryptographic hash (a fingerprint) of the spending conditions. The public key stays hidden, and unlike elliptic-curve cryptography, strong cryptographic hashes remain highly resistant to quantum attacks.
Only when we spend the funds do we reveal the necessary information for the network to verify the transaction.
There is still a theoretical attack vector where an attacker could intercept a spending transaction, derive the private key, and attempt to front-run the original transaction. But since PoW relies on hashing, which is far more resistant to quantum attacks, the network should remain operational and continue confirming transactions, leaving an attacker with only a very narrow window to act.
Exploiting this would require not just a quantum computer capable of breaking public-key cryptography, but one powerful enough to do this faster than the network converges. On Kaspa, that means just a few seconds. That's a much stronger "theoretical adversary," and it's unclear whether such a machine will ever exist.
Personally, I doubt quantum computers will ever be able to break public-key cryptography at realistic key sizes (I suspect that Hilbert space itself is discrete and has a much coarser resolution than commonly assumed, but that's a different topic).
So TL;DR: KIP-22 isn't a "complete" post-quantum solution, but it's an elegant, relatively low-cost way to significantly reduce the attack surface for quantum adversaries.
Published KIP 22 to help Kaspa users better protect their funds from future quantum attackers by keeping public keys hidden until spending
github.com/kaspanet/kips/blo…
Jorge 𐤊 ױ retweeted
Not only does Kaspa solve the Blockchain Trilemma, but it also solves another trilemma: the Money Trilemma (a problem we believe to be more significant). The Money Trilemma claims that a form of money can only provide and maintain two of the three properties at any given time: a store of value (or salability across time), a medium of exchange (or salability across space), and a unit of account (or salability across scale).
Solving the Money Trilemma implies three things: a) a perfect form of money is created, winning the world’s money war; b) the world’s first, stateless world reserve currency can be achieved; and c) decentralized finance is possible, as this hasn’t yet been the case.
No form of money has solved this trilemma until now with Kaspa, as argued in our new article series, "A Path to Digital Silver as a Stateless World Reserve Currency: A History and Philosophy of The Money Trilemma,” by @NicholasSismil and @Shay_Shao
See part one of the series here: kasmedia.com/article/solving…
#Kaspa $KAS #ProofofWork
@KaspaCurrency
Jorge 𐤊 ױ retweeted
JUST IN: Kaspa completes testnet proof of concept for private $KAS transactions
Developer Olaf Weller says TN10 tests confirmed transaction ordering, zero-knowledge proof execution and settlement on Layer 1, though the privacy system remains under development and has not been independently audited.
Jorge 𐤊 ױ retweeted
Published KIP 22 to help Kaspa users better protect their funds from future quantum attackers by keeping public keys hidden until spending
github.com/kaspanet/kips/blo…
Valour, which managed $640.2M in ETPs as of September 25 and is owned by Nasdaq-listed DeFi Technologies, offers a Kaspa ETP on Sweden's Spotlight Stock Market. Investors can buy it through Avanza, Nordnet, Montrose and SAVR.
@kaspaunchained
Jorge 𐤊 ױ retweeted
𝗞𝗔𝗦𝗣𝗔. 𝗕𝗨𝗜𝗟𝗧 𝗗𝗜𝗙𝗙𝗘𝗥𝗘𝗡𝗧.
Bitcoin proved Proof of Work works.
Kaspa made it parallel.
Ethereum chose Proof of Stake.
Kaspa stayed true to Proof of Work.
Solana prioritized speed.
Kaspa combines speed with decentralization.
Cardano relies on staking.
Kaspa relies on mining.
Polkadot connects multiple chains.
Kaspa scales through a single blockDAG.
10 blocks per second.
No premine. No presale. No insiders.
Not another copy.
Not another compromise.
$KAS
Jorge 𐤊 ױ retweeted
🚨 KASPA SCHLIESST SICHERHEITSLÜCKE IN DER CLI WALLET
Kaspa Entwickler haben eine Schwachstelle beim Signieren gemeinsam vorbereiteter Transaktionen behoben. Unter bestimmten Bedingungen konnten spezielle Signaturtypen Änderungen an Empfängern oder Beträgen zulassen, ohne dass die Signatur ungültig wurde. Seit dem Fix akzeptiert die CLI standardmäßig nur noch SIG_HASH_ALL. Wichtig: Kaspa L1 selbst war nicht betroffen, und bestätigte Diebstähle durch diese Schwachstelle sind bislang nicht bekannt.
🔐 Gleichzeitig macht die Kaspa Privacy Initiative Fortschritte: Auf Testnet 10 wurde ein erster funktionierender Machbarkeitstest für die technische Basis privater kaspa:native Zahlungen abgeschlossen. Einzahlungen und Auszahlungen funktionierten, und eine absichtlich fehlerhafte Abrechnung wurde vom Netzwerk abgelehnt. Aber: Private KAS Transaktionen sind noch nicht live, der Test beweist bislang nur, dass zentrale Bausteine technisch funktionieren.
Jorge 𐤊 ױ retweeted
just to be clear, there’s a lot going on across many fronts. it’s just not helpful to talk about things before they happen; they simply need to happen, and serious things take time. some serious efforts also won’t necessarily mature for various reasons, which is another reason ppl don’t always lay out their plans publicly (until they happen). i anticipate something of a “baby boom” in a few months, but teams will simply pursue delivery rather than talk
Jorge 𐤊 ױ retweeted
🔴 Hoy, DIRECTO a las 21 HORAS (GMT+2):
youtube.com/live/_ekqjYbBsSI
Jorge 𐤊 ױ retweeted
@CodesXBT i genuinely do my best to tolerate and respect ppl. i never block, and i try to answer any constructive criticism. i’m sorry but sometimes i just don’t understand what ppl even want. how can utility and apps be built without programibility infrastructure and compilers as MUST prerequisites, and why should i not hope for Kaspa’s vibrant community to utilize these fresh tools before or in parallel to myself building apps over this infra






























