@Kaspoide
Account based inItaly
About this account
- Account based in
- Italy
- Connected via
- Italy Android App
Account-level information from X, not a live location or the device used for a specific post.
My portfolio is 100% $KASPA, the future of the crypto world. Yonatan Sompolinsky embodies the vision of Satoshi Nakamoto.
World
Joined October 2024
- Tweets1.5K
- Following308
- Followers80
- Likes2.3K
Kaspoide retweeted
you can build a kaspa vault that only lets you spend once a price condition is met.
silverscript’s HodlVault example checks your signature and a signed price message from an oracle, an outside source of data.
kaspa checks that the message meets the contract’s conditions. you’re still trusting the oracle to report the price accurately.
the example code is in the comments for devs to build from.
Kaspoide retweeted
bitcoin dev's were discussing covenants back in 2013.
bip-119 later proposed one approach to covenants, restricting spending to a predefined transaction template. it was never activated on btc tho.
kaspa’s covenants go further (covenants++ if you like). scripts can enforce spending rules, carry application state forward and let that state split into branches that progress independently. multiple contracts can also update together in one transaction, with all changes accepted or none of them.
dev's write that logic in silverscript, which compiles it into scripts kaspa enforces on L1.
Kaspoide retweeted
So, kaspa:native is trending again, but what is it?
🧵What if PoW could be fast?
That’s where Kaspa (kaspa:native) comes in. Instead of using a traditional linear blockchain, Kaspa uses a blockDAG architecture.
Here’s why that matters 👇
Traditional blockchains process blocks one after another:
Block → Block → Block
Kaspa allows multiple blocks to be created and processed in parallel.
That’s the core idea behind its GHOSTDAG protocol. Resulting in:
⚡ Faster block production\
⚡ Higher throughput\
⚡ Efficient PoW consensus\
⚡ Scalability without abandoning Proof-of-Work
Kaspa uses kHeavyHash for mining and keeps Proof-of-Work at the center of its security model. So it’s not simply “another fast chain.” It’s experimenting with a different way to scale PoW.
The token? kaspa:native is the native coin of the network.
It’s used for transactions and fees, while miners earn KAS for helping secure the network. Kaspa also launched without a premine or hidden allocation.
The bigger idea behind Kaspa is simple: Keep the principles of PoW, but rethink the architecture. Instead of one block at a time… Think many blocks working in parallel.
Kaspoide retweeted
A lot of you forget kaspa:native ran alone in a bear market last time.
I wonder how hard it can run in a bull market that actual has liquidity outside of the top 10.
Kaspoide retweeted
hello again. the devs made things this week and i made a list.
1 / Rusty Kaspa v2.1.0
nodes now download sync data in smaller chunks to avoid bottlenecks and timeouts while catching up with the network. v2.1.0 also includes Stratum bridge fixes and moves the existing zero-knowledge proof tools into their own package.
github.com/kaspanet/rusty-ka…
2 / vProgs
@Max143672 announced the first vProg running on testnet. it’s a playable tic-tac-toe game with real execution and settlement. still a working proof of concept, with public code for devs to build from.
nitter.cf/Max143672/status/21034…
3 / Python SDK
@smartgoo_ released Python SDK v2.1.0. devs can now compile SilverScript contracts in Python and debug them without running a node. it also adds tools for using zero-knowledge proofs, examples and bug fixes. SilverScript support is still experimental.
github.com/kaspanet/kaspa-py…
4 / SilverScript Studio
@KasperoLabs announced SilverScript Studio is live on mainnet. build, compile and deploy covenants from your browser. write them yourself, describe what you want to its AI, or use the wizards for things like vaults, escrow, recurring payments and payroll.
nitter.cf/KasperoLabs/status/210…
5 / KCC23
@manyfest_ explained a proposal for linking details like token names, symbols and images to a covenant, without copying them into every holder’s coins. KCC23 is still a draft and open for review.
nitter.cf/manyfest_/status/21030…
6 / KCC standards
@asaefstroem’s proposal to finalize KCC0 was merged. it sets out how shared ecosystem conventions are proposed and reviewed. he also proposed moving KCC20 into last call review. that hasn’t merged, so KCC20 is still a draft.
github.com/kaspanet/kccs/pul… github.com/kaspanet/kccs/pul…
7 / DNS seeder
@supertypo_kas released DNS seeder v0.9.6, fixing a bug that counted some offline nodes as online.
github.com/supertypo/simply-…
thanks to everyone building. see you next week.
While prototyping KCC-20 I got asked how should token symbols, descriptions, images, and other kind of metadata be defined.
On EVM systems, there is a single SC which represents a token, and holds both its balance state and global state.
On the UTXO model there is no global state, the token is split and held across holders, each one holds his specific token (UTXO/covenant).
This means that adding state fields for metadata would duplicate them across each UTXO, which is wasteful. Things such as representation, name, symbol or image are also not part of the SC logic, and should not be part of it.
A naive approach is to declare such metadata in the payload field of a tx, which is an "empty space" that can be used to write whatever information.
The issue is that Kaspa is prunable. Eventually, the block containing this tx would no longer be available for verification, so at some point the data would need to be trusted by off chain entity.
After drafting a few solutions, we came up with KCC-23, a convention for binding the metadata to the covenant ID itself.
Read more on Kas-Smiths:
kas-smiths.org/t/kcc-23-conv…
Or read the KCC draft:
github.com/kaspanet/kccs/pul…
Kaspoide retweeted
its not about what you're looking at, it's what it represents
docs.kaspa.org/programmabili…
Kaspoide retweeted
Tic-tac-toe is live on Kaspa testnet: the first vprog, a verifiable program with real execution and real settlement, running since yesterday.
You can play it here: vprogs-tt.izio.fr/
(Requires private key and some testnet funds)
We still need to review and merge a stack of PRs, however this is already a working POC. UI/UX was never a priority; the frontend can be enhanced or built separately
I'm gonna work on mdBook covering the parts of the system I consider meaningful and a workshop on vprogs and building apps on top
For Devs: this is the invitation. Play the game, read the code, build your own vprog.
Game code: github.com/biryukovmaxim/vpr…
vprogs framework: github.com/kaspanet/vprogs/t…
Kaspoide retweeted
i used to think real-time execution was the one thing that couldn’t be faked on bitcoin L1.
i stand corrected.
Kaspoide retweeted
Another great one is kaspa:native.
This one signaled a bottom was happening at the low, as there was a strong bullish divergence in play.
Since then: continuation with higher highs, higher lows and constant flips of the levels.
I don't think that this will stop soon, especially if this takes out the recent high, the next target for me is $0.0743.
Kaspoide retweeted
owning KAS doesn’t mean owning the kaspa network.
kaspa is an open, permissionless proof-of-work network. holding more coins doesn’t give you more say in its consensus.
that’s what the last post was trying to say. intern has been asked to use more words.
Kaspoide retweeted
**Open Letter to Vlad Tenev**
CEO, Robinhood @RobinhoodCrypto
Vlad,
@vladtenev
Robinhood already lists plenty of coins that are narrative first and infrastructure second. Kaspa is the opposite. It’s time to list $KAS
$Kaspa is the people’s coin. Fair launched. Proof of work. No premine. No VC allocation. No insider float hanging over retail. Every coin was mined. That alone should matter to a platform that built its brand on giving regular people access.
The tech is not a slogan. BlockDAG and GHOSTDAG let the network produce blocks in parallel instead of waiting in a single-file line.
Crescendo took it to 10 blocks per second. Toccata went live on mainnet June 30, 2026 and added native L1 covenants and on-chain ZK proof verification. Payments were already fast and cheap.
Programmability is now on the base layer without turning the chain into another account-model copy.
That combination of speed, PoW security, decentralization, and now real L1 programmability is rare. Most “fast” chains trade away one of those. Kaspa doesn’t.
Robinhood’s own product direction makes the listing more obvious, not less. You’re building Robinhood Chain for tokenized stocks and you already list speculative names because retail wants them. Kaspa sits in a better spot than most of those listings: real throughput, real security model, growing builder activity, and a community that actually holds instead of rotating every week.
Listing $KAS does three things for you:
1. Gives your users a high-throughput PoW asset that isn’t Bitcoin or a Bitcoin fork with extra branding.
2. Puts Robinhood in front of a community that has been asking for this listing for a long time and will actually use the product.
3. Aligns with the access story better than another meme with no base-layer reason to exist.
I’m not asking you to shill it. I’m asking your listings team to do the work. Look at the launch history, the hashrate, the post-Toccata capability set, and the holder distribution. Then decide on the merits.
Kaspa is the people’s coin. It’s time.
Sincerely,
The Kaspa Community
P.S. Contact our Director of Business Development and Listings at your earliest convenience.
@wolfie
