Claudio đ€ â retweeted
Sr. Presidente me pasĂ© 30 años de mi vida dando clases en USA, de todo esto, debo haber convencido a unos 2000 maximum, Ud convenciĂł a 16 mill, su conocimiento y magnetismo lo lograron. Ahora "que el mundo, no Argentina pasa por momentos difĂciles", no afloje, tiene la capacidad de demostrarle a los argentinos cual es el Ășnico camino. Pd "el dĂłlar esta atrsado decian al unĂsono, ahora que subiĂł un poquito, dicen pobre gente como va a pagar los crĂ©ditos" "nadie comenta de los seguros contra la caĂda del oroahora, pero antes lo tenĂa el Ministro de EconomĂa en su casa" estos argentinos son traidores a la Patria y Ud y su equipo, para mi lo mejor que le pasĂł a la Argentina en los ultimos 90 años. Mis respecto aunque sea mayor que Ud. @fededomin
Claudio đ€ â retweeted
I'm tired of armchair experts crying about "locked stablecoins" on Kaspa when they don't even know how the chains they use every day work. So here are the real numbers. $KAS
BNB has been running for over 6 years with $9.18B locked and there's still no native Tether USDT. Tether never issued it there. Binance owns the contract, holds the reserves and mints its own pegged token on a 21 validator PoS chain.
Arbitrum has been running for over 5 years and peaked at $3.46B in bridged USDT, with $1.31B in bridged USDC.e for 2 years. There's still no native USDT, it's all locked on ETH and it runs on a centralised sequencer.
Polygon has been running for over 6 years and peaked at $1.48B in bridged USDT, with $2.31B in bridged USDC.e for more than 3 years. There's still no native USDT there either and it's all locked on ETH.
Avalanche peaked at $1.98B in bridged USDC.e and $940M in bridged USDT.e, and native USDT only came after more than a year.
Every big chain ran billions on the exact same lock and mint model. Now look at Trestly on Kaspa L1.
It's the first pure PoW L1 with a native covenant stablecoin and a built in L1 DEX. It settles at 10 blocks per second and there's no centralised sequencer.
It's not controlled by one company like Binance's pegged USDT. 5 independent, known Kaspa signers secure it, so 3 of them have to sign every transfer and 4 have to agree to change the rules.
It's open source so everyone can audit its code, and you can check the 1 to 1 reserves on chain any time.
The critics can keep waiting for Tether to save them. We actually shipped it on Kaspa L1.
Do what you want with this information.
Claudio đ€ â retweeted
$KSD whitepaper update coming tomorrow!
Claudio đ€ â retweeted
Riesgo Pais :
Argentina es high Beta. ( por cada unidad de cambio global, ARG CAMBIA un mĂșltiplo mayor). Y es asimĂ©trico: para abajo es peor para arriba no tan mejor.
Por que: la deuda argentina es un activo de frontera ( no esta en ninguna bolsa junto con otras similares- es Ășnica- )
Estos activos son los q se compran muy baratos ( y apalancados- o sea con plata prestada mas barata, asĂ la diferencia se hace con la ajena-) , por si la llegan a pegar, ganas un montĂłn, pero es probable q no pase.
Entonces con una parte del portafolio ( la espuma) los inversores grandes compran estos galerazos q cuando salen bien les empujan para arriba el portafolio total un montĂłn ( y con eso sus bonus)
Cuando el dĂłlar se aprecia mucho, y empieza a subir la tasa q te pagan por tener dĂłlares ( los portafolios crecen con eso - menos pero seguro) Entonces los inversores venden de arriba para abajo activos de riesgo para ponerse en dolares, y ademas se desapalancan. Esto es logico porq el negocio se hace menos atractivo, la prestada se encarece y el galerazo se aleja, y eso se retroalimenta y se acelera como hoy.
Venden la espuma (arg) , las acciones mas volatiles ( techs ) y hasta el oro. Y se posicionan en dĂłlares.
Esto viene pasando las ultimas 2 semanas y ayer y hoy se acelerĂł. Tan simple como eso
Nadie en W St mira ningĂșn discurso del Pj, ni nada de milei, ni nada interno de ARG. NO HAY TIEMPO NI RELEVANCIA PARA ESO. Solo venden la espuma y se ponen en dolares. Despues recompran en algĂșn momento, con la misma logica.
Es asĂ de simple, llegan a un piso, y despues vuelve. Y asĂ en ciclos
Utter ignorance or malicious? I say the latter
Things are falling apart in Argentina. The peso is down ~6% in the last week, country risk is over 1000, inflation is ~33%/year & there's a recession. The carry trade could implode next week with $25 T in peso debt maturing at rates below peso:dollar devaluation.
24
Claudio đ€ â retweeted
NingĂșn medio o economista va a hablar del oro, la baja del precio internacional, el seguro y la ganancia de Argentina?
Solo @SalvaDiStefano lo harĂĄ?
Claudio đ€ â retweeted
The case for the uniqueness of fast pow
tl;dr
Finality has two moving parts: (i) fast inclusion (= high bps, how quickly a tx gets into a block), and (ii) fast confirmations (= how quickly that tx becomes irreversible). Any system with rapid block production can achieve the first. The second is where the tension shows: in pos, fast confirmations press directly against decentralization. In fast pow, the two properties are decoupled.
prologue
A few weeks ago I came across Solanaâs founder claiming: âSolana is the fastest monetary system in the worldâ. Since Kaspa already runs at a faster block rate, I was curious to check Solanaâs finality times. That curiosity quickly pointed me to a deeper issue: not raw speed, but how speed interacts with decentralization.
ââââââ
The tension is structural. In pos, finality means accumulating staked votes, and the more decentralized the stake distribution, the more time is required to reach finality. Here Iâm not talking about hardware requirements or validator specs. The axis Iâm discussing is centralization around the security mechanism itself: stake in pos vs. hardware in pow. To be secure, a block must be confirmed by a supermajority--typically >66.7% of the total economic stake. In a truly decentralized network, where n stakers with uniform share grows without bound, the time to coordinate this supermajority becomes a real bottleneck.
Pow works differently. It samples the hardware space without requiring the protocol to explicitly collect evidence from a majority of miners. Each block is itself a statistical proof that the finder out-competed the full networkâs hash power. This process--and its timing--remains independent of how many individual miners participate.
Ethereumâs researchers understood this when moving to pos. Unlike Solana, which tolerates concentration to reach ~13-second finality, Ethereumâs designers could not accept that trade-off. Their solution was to introduce rotating committees. A rotating committee is a smaller subset of validators, randomly chosen from the full set, that votes on behalf of everyone else.
But this comes with a different security model, known in the literature as exposure to a BFT adaptive attacker. The committee is selected first and then votes. That âselect-then-workâ sequence is theoretically exposed to adaptive attackers, since members are known in advance. Pow, by contrast, is âwork-then-selectâ: the winner is only revealed after the work is done. Think of it this way: in pos, you know who the referees are before the game starts, which gives an attacker time to pressure them. In pow, you only learn who won after the work is already done, which removes that attack surface. So n confirmations provide consistent confidence regardless of miner granularity, and the system stays secure even under adaptive targeting.
Beyond attack subtleties, the real issue is economic weight. When I send a billion-dollar transfer in a pos system, the question I care about is simple: how much stake is actually securing it? A committee vote provides strong statistical evidence, but only a true supermajority puts the full economic stake of the network behind my confirmation. In other words, a sampled committee may convince me that things are probably safe, but only the weight of the entire stake provides an overwhelming guarantee. And this is exactly where pow shines: each confirmation is not just a probability estimate, but a direct proof of work done against the full hash power of the network, no matter how many miners there are.
closing remark
I donât claim to know every engineering detail of Ethereum or Solana. But Iâm convinced the core principle holds.
Iâll state it simply: fast pow uniquely enables fast finality without forcing a compromise on decentralization.
Claudio đ€ â retweeted
This is indeed where the energy markets will be heading to! @ZETAlliance
We're genuinely excited about Kii-EnergyOS.
Energy is turning into a system of millions of moving parts: buildings, depots, chargers, heat networks, storage, molecules, ships. Every one of them has to be coordinated, paid and trusted. Today that trust still lives in spreadsheets, invoices and phone calls.
EnergyOS gives all of it one record:
· 12 programme families, from generation to buildings
· settlement held by covenant until delivery is proven
· verification anyone can run, with private data kept private
· one record, reported in every regulator's format
Powered by Kaspa.
Pilots commencing shortly.
#kaspa $kas #EnergyOS #EnergyTransition
We're genuinely excited about Kii-EnergyOS.
Energy is turning into a system of millions of moving parts: buildings, depots, chargers, heat networks, storage, molecules, ships. Every one of them has to be coordinated, paid and trusted. Today that trust still lives in spreadsheets, invoices and phone calls.
EnergyOS gives all of it one record:
· 12 programme families, from generation to buildings
· settlement held by covenant until delivery is proven
· verification anyone can run, with private data kept private
· one record, reported in every regulator's format
Powered by Kaspa.
Pilots commencing shortly.
#kaspa $kas #EnergyOS #EnergyTransition
Claudio đ€ â retweeted
Working on #Kaspa I can find myself thinking/discussing 5 very different topics in a single day. Bouncing back and forth from mathematical proofs and modeling (KIP9, oracles, DK etc), to system design and future architecture (zk opcodes, L2 state handling), and code reviewing (mempool fee estimation, RBF, TN11 optimizations).
Kind of challenging but mostly I feel blessed being part of this amazing decentralized force while doing things I'm passionate about <3
Kaspa Stick Fighter | Kaspa and the Lost Ledger
Check out the full series on YouTube
youtube.com/playlist?list=PLâŠ
#Kaspa #KaspaAnimation #KiiLabs $KAS
Kaspa turns 5, and for the birthday party at Wolfyâs in London we animated a Kaspa stick fighter to go with it. Here is the birthday film. The rest of the series follows on YouTube. đ
youtube.com/playlist?list=PLâŠ
@WolfysBar @BlockchainBants #kaspa $KAS
Claudio đ€ â retweeted
Replying to @Justin_Bons
SOLâs fast finality requires a supermajority of the stake to sign off on the state. If SOL were properly decentralized (in its most important security axis: number of independent stakers), aggregating that agreement fast enough would be the processing bottleneck. Thatâs a tension which seems unavoidable in the PoS model.
(teapaw.org/michaelsuttonil/statusâŠ)
The case for the uniqueness of fast pow
tl;dr
Finality has two moving parts: (i) fast inclusion (= high bps, how quickly a tx gets into a block), and (ii) fast confirmations (= how quickly that tx becomes irreversible). Any system with rapid block production can achieve the first. The second is where the tension shows: in pos, fast confirmations press directly against decentralization. In fast pow, the two properties are decoupled.
prologue
A few weeks ago I came across Solanaâs founder claiming: âSolana is the fastest monetary system in the worldâ. Since Kaspa already runs at a faster block rate, I was curious to check Solanaâs finality times. That curiosity quickly pointed me to a deeper issue: not raw speed, but how speed interacts with decentralization.
ââââââ
The tension is structural. In pos, finality means accumulating staked votes, and the more decentralized the stake distribution, the more time is required to reach finality. Here Iâm not talking about hardware requirements or validator specs. The axis Iâm discussing is centralization around the security mechanism itself: stake in pos vs. hardware in pow. To be secure, a block must be confirmed by a supermajority--typically >66.7% of the total economic stake. In a truly decentralized network, where n stakers with uniform share grows without bound, the time to coordinate this supermajority becomes a real bottleneck.
Pow works differently. It samples the hardware space without requiring the protocol to explicitly collect evidence from a majority of miners. Each block is itself a statistical proof that the finder out-competed the full networkâs hash power. This process--and its timing--remains independent of how many individual miners participate.
Ethereumâs researchers understood this when moving to pos. Unlike Solana, which tolerates concentration to reach ~13-second finality, Ethereumâs designers could not accept that trade-off. Their solution was to introduce rotating committees. A rotating committee is a smaller subset of validators, randomly chosen from the full set, that votes on behalf of everyone else.
But this comes with a different security model, known in the literature as exposure to a BFT adaptive attacker. The committee is selected first and then votes. That âselect-then-workâ sequence is theoretically exposed to adaptive attackers, since members are known in advance. Pow, by contrast, is âwork-then-selectâ: the winner is only revealed after the work is done. Think of it this way: in pos, you know who the referees are before the game starts, which gives an attacker time to pressure them. In pow, you only learn who won after the work is already done, which removes that attack surface. So n confirmations provide consistent confidence regardless of miner granularity, and the system stays secure even under adaptive targeting.
Beyond attack subtleties, the real issue is economic weight. When I send a billion-dollar transfer in a pos system, the question I care about is simple: how much stake is actually securing it? A committee vote provides strong statistical evidence, but only a true supermajority puts the full economic stake of the network behind my confirmation. In other words, a sampled committee may convince me that things are probably safe, but only the weight of the entire stake provides an overwhelming guarantee. And this is exactly where pow shines: each confirmation is not just a probability estimate, but a direct proof of work done against the full hash power of the network, no matter how many miners there are.
closing remark
I donât claim to know every engineering detail of Ethereum or Solana. But Iâm convinced the core principle holds.
Iâll state it simply: fast pow uniquely enables fast finality without forcing a compromise on decentralization.
Claudio đ€ â retweeted
Replying to @michaelsuttonil
@michaelsuttonil still thinks kaspa can have a dagknight testnet this year.
he was on @Vladcostea's bitcoin takeover last night (s17 e52), a stream postponed more than a month by conferences. asked when people would see a testnet, he said the work is moving on three fronts at once: finishing the proof, a yellow paper closer to code, and the implementation. "i mentioned on x a few weeks ago that i think we will get to a testnet by the end of year. i still think so." a bigger release of materials is coming "in a few weeks when it's all ready."
other notes from the three-hour talk:
- with current performance, 20 blocks a second is already in reach, "but it's still an effort and it requires a lot of testing." getting toward 100 would take more r&d. he said the point of 100 is frequency: a second or two of miner samples, not more room for transactions.
- kaspa did covenants "the right way" by putting the simple lineage tools on l1, chiefly kip-20.
- since the recent hard fork, kaspa can verify two kinds of zk proofs on chain, including a full stark (no trusted setup, post-quantum). one of those transactions "will fill up a block," so you could do about 10 a second if you saturated the dag. shielded payments are possible. the zk opcodes are mainly for scaling based apps, and can also be used for privacy.
- he called miner emission the main motivation for everything he has done in the last year and a half: enough utility and fees for the network to sustain itself "without printing more money, so to speak."
"go ahead and do it. don't wait for others."
youtube.com/watch?v=v1FWc5r-âŠ
Claudio đ€ â retweeted
A transaction that changes no application data could still stop vProgs from processing new batches.
In issue #193, @hus_qy describes a bug where a batch containing transactions that access no state resources produces an empty state root, even when the application already has data.
The prover then compares that incorrect root with the actual stored state, hits an assertion and stops. Restarting alone may not resolve the problem because the incorrect receipt has already been cached.
The failure was reproduced in development mode, and a proposed fix was tested. The regression tests have not yet been added to the repository.
This concerns experimental vProgs infrastructure, not Kaspa's mainnet consensus. There is no evidence in the issue of an attack in production.
#kaspa
github.com/kaspanet/vprogs/iâŠ
Claudio đ€ â retweeted
Michael Sutton on Kaspa R&D @michaelsuttonil (Bitcoin Takeover Podcast S17 E52) teapaw.org/i/broadcasts/2NgQykpjPâŠ
Claudio đ€ â retweeted
the dagknight branch got its first merge since september.
@coderofstuff_'s rusty-kaspa #1168 landed on nov 16. it prepares the coloring code for later shortcut work. @Max143672's #1172, still open, sets how dagknight picks a winner when two block groups are closely matched.
not on mainnet. no activation date.
github.com/kaspanet/rusty-kaâŠ






















