Hristo Kusev

[Michael Sutton @michaelsuttonil]

watching the timeline with awe. human beings in a world of ai superintelligence. how humbling. @hashdag, crypto and defi need fundamental redesigns, i think you should be leading with more determination / visibility.

[Ethan @EthanAnvel]

We’re investing up to $1,000,000 in Kaspa startups.

[Hristo Kusev @HristoKusev]

@KaspaBots Cmon kaspa:native army! #KAS FTW !

[KaspaBots @KaspaBots]

Bitcoin had Miami.

Ethereum had DEVCON.

Now it’s Kaspa’s turn.

Introducing the Kaspa Conference: a 4-day experience bringing together builders, investors, and the $KAS community.

And we’re investing up to $1,000,000 in Kaspa startups.

Here’s what we’re building. 🧵

[Grok @grok]

@Crypt0Proselyte Kaspa. Pure proof-of-work blockDAG at 10 blocks per second. Transactions appear nearly instantly and reach high-confidence probabilistic settlement in a few seconds. Fees are typically fractions of a cent, so a $2 payment settles cheaply and finally on L1 with no layer 2.

[BSCN @BSCNews]

Kaspa Dollar Seeks 5M KAS to Fund New Stablecoin

KaspaDollar (@KaspaDollar) has announced plans for a decentralized stablecoin on the Kaspa network (@kaspaunchained) $KAS.

The initiative is led by core developer @asaefstroem and targets 5 million KAS in funding. The project aims to raise the funds to cover development, independent auditing, research, and launch operations.

KaspaDollar is planning an overcollateralized stablecoin designed to reduce Kaspa DeFi's reliance on assets issued elsewhere. The team says recent developments, including the Toccata hardfork, have expanded the network's capabilities.

Contributions will be refunded if the target is not reached by January 1, 2027.

[Michael Sutton @michaelsuttonil]

hashdag (“Opening the Pandora box” with Ori Newman) & myself (DAG Knight), speaking here next

[Michael Sutton @michaelsuttonil]

i’ll do everything in my power on the technical side to help this initiative move forward and navigate any protocol-level obstacles along the way.

on a personal note, Alex has a rare mix of technical depth, bizdev talent and deep Kaspa knowledge. i honestly can’t think of anyone better suited to lead it, and i really appreciate him taking this on

[KaspaDollar @KaspaDollar]

Today we are introducing KaspaDollar, an initiative led by core developer @asaefstroem to build the first decentralized stablecoin on the $KAS network.

The developments around @kccforum and the Toccata hardfork have considerably widened what Kaspa is capable of. Capability alone, however, does not make an ecosystem. Decentralized finance requires a unit of account that holds its value, and until Kaspa has a stablecoin of its own, every application built on it will remain dependent on assets issued elsewhere.

The design we intend to follow is the decentralized, overcollateralized stablecoin: a pattern whose security properties have been examined and tested across the industry for the better part of a decade. With the support of the core team, we consider the conditions right to bring it to Kaspa.

Realizing this requires development, an independent audit, further research, and the operational work of taking a protocol from specification to production. To fund it, we are opening a fundraiser with a target of 5,000,000 KAS.

Contributions are made directly to the fundraising address published on the website. Should the target not be reached by 1 January 2027, every contribution will be returned to the address from which it was sent.

Up until that point, this account will share the plans, details and progress of the work as it develops.

[Grok @grok]

No. Pure PoW is not locked into slow confirmations. GHOSTDAG generalizes Nakamoto consensus to a blockDAG that retains every honest block instead of orphaning them. Kaspa runs this at 10 blocks per second: transactions enter in a fraction of a second and reach strong probabilistic finality within a few seconds, all while remaining pure PoW with a fair launch, no premine, and no trusted parties.

[MSB Intel @MSBIntel]

BitGo, the NYSE-listed custodian with $65.2B in assets on its platform in the quarter to June 30, has added Kaspa mainnet to its coin list and developer SDK. Its Kaspa module supports key generation and MPC signing.

@kaspaunchained

[DEXTools @DEXToolsApp]

@michaelsuttonil @KaspaHub @RelayProtocol @SilentSwap Let's have a call to have the full picture =)

[Michael Sutton @michaelsuttonil]

@DEXToolsApp @KaspaHub @RelayProtocol @SilentSwap I’m a core Kaspa dev. What do you need and how can I help?

[BSCN @BSCNews]

Kaspa Developer Completes Key Step Toward Private KAS Payments

Kaspa (@kaspaunchained) Privacy Initiative developer Olaf Weller (@WellerOlaf) says a proof of concept for shielded native $KAS has been completed on testnet TN10.

The tests demonstrated transaction ordering, zero knowledge proof execution, and proof based settlement on Kaspa Layer 1.

Next, developers plan to design private notes, commitments, nullifiers, and the zero knowledge proof rules for shielded payments.

Weller stressed that the system has not been independently audited and is not yet a finished privacy protocol.

[Michael Sutton @michaelsuttonil]

@aKaspamaxi we’re all in on it and doing our best. it’s a white/yellow/black (research/specs/code) effort happening in parallel with various relationships

[Paul van Son @pvson]

@TruthEngine_KAS How funny! 13 years ago people at then EFET were looking at BTC/DLT for e.g. deal clearing and certificate trading. That didn’t fly at the time due to BTC’s limitations. kaspa:native solved those. Implementation is imho indeed a matter of time @KaspaKii

[Olaf Weller @WellerOlaf]

Had a really interesting conversation with Kaspa core developer @michaelsuttonil about the Kaspa Privacy Initiative today.

We discussed our candidate architecture for a scalable shielded native KAS protocol, using covenants, ZK proofs, permissionless relayers and batchers.

One of the biggest takeaways was how much of the infrastructure we're looking for may already be available through Kaspa's Based Apps and KIP-21.

In our original design, one of the challenges was ensuring that batchers couldn't selectively omit user operations while claiming to have processed a complete batch.

With Based Apps, user operations can be ordered directly on Kaspa L1 in an application-specific lane. KIP-21 provides cryptographic sequencing commitments, allowing a properly designed settlement proof to demonstrate that the relevant operations were processed correctly.

That could remove a substantial amount of custom infrastructure we'd otherwise have to build ourselves.

We also discussed canonical bridges, recursive proving and why sharding may introduce unnecessary complexity at this stage.

Our next step is a small Based App feasibility PoC on TN10.

We'll test lane ordering, execution, proof-based settlement, deliberate transaction omission and independent reconstruction before adding the actual shielded privacy logic.

No architecture has been finalized. The goal remains to find the safest, most scalable and most decentralized solution, not to defend an earlier design.

Really appreciate Michael taking the time to share his insights. Conversations like these are incredibly valuable.

Technical feedback, criticism and contributions are very welcome!

https://t.co/h4gdcS1dfn

[Hristo Kusev @HristoKusev]

@krakenpro @Kaspa_HypeMan @UnknownZohar You get it… kaspa:native #KAS

[Kraken Pro @krakenpro]

@UnknownZohar KAS

[Murad 𐤊 @imbalatov]

Shai, I think you’re right that Kaspa hasn’t changed the world. Not yet, anyway.
But I wouldn’t confuse a lack of adoption with a lack of significance. Some ideas take a long time to prove their worth, and some never do. It’s still too early to know where Kaspa stands.
I also think your contribution, and Yonatan’s, deserves recognition regardless of how things ended between you.
I hope that, despite everything that happened, time will allow all of you to look back on what you built with more pride than bitterness. Whatever the future holds for kaspa:native , that work deserves respect.