I'm not great, I'm not good, not even decent. But I'm trying, out of curiosity. Yet another human on earth, just like you. @Kaspa_KEF grantee since 12/15/2025
Joined October 2022
- Tweets1.6K
- Following453
- Followers1.8K
- Likes4.9K
'The "Doherty Threshold" was defined as ~400 milliseconds; the maximum amount of tolerable UX latency'
kaspa blocktime is 100ms, add a RTT and you're still below the threshold.
UX latency is the most frustrating (lack of) advancement in computing over the last ~50 years.
IBM, way back in the 80s, found that user productivity shot up *exponentially* as system response time dropped. The "Doherty Threshold" was defined as ~400 milliseconds; the maximum amount of tolerable UX latency before interrupting user flow state.
It's unbelievable how many modern operating systems (*cough* win11) violate this threshold constantly.
Literally all you need to do as a Dev is pay attention. Add a "Doherty Threshold" to your test suite. There's so many different profiling tools, and especially with how good models are, really no excuse. Sure, some stalls are unavoidable, but that's when you pull out other UX tricks to at least give the illusion of responsiveness.
Crazy how much vintage computing hardware feels immeasurably more responsive despite having thousands of times less overall performance.
a community funding wallet has been opened to reward security reporters who contributed in the software hardening, something that should be encouraged further.
here are all the details: discord.com/channels/5991532…
get utxos by covenant id, which was a long awaited node feature is now approved.
you can build the node from source code and try this feature out now, or wait for upcoming release.
WASM support and JS example provided, should be easy to use.
just add "--covenant-index" to the arguments list.
thanks to @Max143672 for the feature :)
cc @kascovio
Kas the coin can also be 'tokenized' as a kcc-20.
the need may not be very clear to everyone, but basically: my L1 app may want to uniformly manage kcc-20 and Kas the coin, without extra 'custom code'.
@manyfest_ details one of the direct use-case.
i have been convinced that designing kas-20 correctly only gives benefit with no tradeoff.
is it possible to have such an atomic covenant transaction that:
1. convert Kas to kas-20
2. trade it for the Many kcc-20 token
(=without adding one extra conversion step)
Onwards!
KCC-20 lets us create tokens that work together through a shared interface. Native KAS is a fungible token as well, but it isn’t a KCC-20 token.
Imagine a DEX, for example. KCC-20 lets us write a generic pool covenant that supports any pair of KCC-20 tokens. But if one side of the pair is KAS, we’d need special logic to handle it.
Representing KAS as a KCC-20 token would let covenants handle KAS the same way they handle other KCC-20 tokens. There could be different implementations and deployments of a KAS-backed KCC-20 token, but it would be beneficial to agree on a single one to avoid fragmentation.
I'm proposing a simple implementation, KAS20. Join the discussion on Kas-Smiths:
kas-smiths.org/t/a-kas-backe…
Status final = beginning of a new era
Greetings $KAS. KCC-1, KCC-2 and KCC-20 are now Final, meaning they are ready for full adoption across the ecosystem.
We invite Kaspa builders to join the public KCC channel to ask questions, get support, discuss implementations and share what you build.
Come build with us.
did you know that miners sometimes see their submitted block become a "chain block" on Kaspa?
when this happens, the block merges other blocks, called "merged blocks", and together they form a "merge set".
if it happens to merge red blocks, guess who wins the red pots? (reward that should have been allocated to the red merged block if it was blue instead of red)
Max inviting devs to try a testnet vProg app in their browsers and then be curious on how it works, maybe even write their own prog?
i assume it will also help to identify bottlenecks, so let's congest there.
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…
covenant: deployment-time static metadata such as symbol name, image/logo, decimals and all.
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…
here is how i evaluate the kcc-12 proposal in a second pass.
i sketch a user journey, observe flaws on existing web3 platform, see if my user journey fixes it, iterate.
once i have a viable sketch, i take kcc-12, see if it **enforce** this flow. if not, it needs changes.
kcc-12 should also be taken from a UX perspective, and we have a lot to learn from, lot of challenges to crack produce-wise.
this KIP-12 is superseded by KCC-12.
goal: dApp doesn't need to integrate browser wallet 1 by 1.
If you own a dApp (/want to), or you own a browser wallet, please read the proposal and add your thoughts (not LLM thoughts, we can do that on our own)
aiming to build composable application on Kaspa L1? you probably don't want to miss this one.
this Saturday 8PM UTC. event link in thread.
RC (release candidate) for SilverScript.
1 week to make feedback. If no major blocker, official release will be published.
Support on Discord if needed.
Seven months since the first commit, and after an extensive review and standardization process (thanks to @manyfest_,@iziodev,@michaelsuttonil and @asaefstroem), I'm publishing a release candidate for Silverscript v1.
The last merged PR was written by @michaelsuttonil and numbered #235, which is a nice reminder to the fact that Silverscript started as my (someone235) project and is now becoming a project involving the entire Kaspa community.
You can find a link to the release candidate in the reply, and I'd love to hear the community's feedback. If we don't receive any substantial feedback, we'll release Silverscript v1 for mainnet use one week from now.
