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
'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.
@kheavyhash i'm tired of prompting boss, i'm at a point where i spend less time actually writing the small doc rather than prompting it.
it's still useful for isolated section.
nb: it's a relatively small doc, 200 lines or so
there is one subtle difference in usual platforms, crypto auth is not the only native method, if it's even provided.
here, solutions built abstractions hiding inherent mechanisms and i think that's what @KaspaSilver refers to. in these contexts, there are now two ways of spending my coins instead of one, and users should be aware of that.
@stepheaw@livingdevops there are other valid reasons than user count, but I generally agree we're witnessed and keep witnessing madness in term of architecture where any trendy blog article should be implemented in ur next SaaS
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
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: https://t.co/x4PxskANfJ
@KaspaSilver any Type 5 card should do for this use case, allowing users to not be forced with one brand. The writer and reader (kachat) still can use secured RW.
@michaelsuttonil pointed me to a better alternative given the current context.
1. get utxo DAA score
2. execute a node built-in search get_transactions_by_accepting_daa_score (https://t.co/01XfebCIgJ)
it will return the transaction that created this utxo.
if 2. is exposed as a RPC method, then you don't need to do anything external, which is cool.
created a GH issue here: https://t.co/hzC3XG93vl
@michaelsuttonil pointed me to a better alternative given the current context.
1. get utxo DAA score
2. execute a node built-in search get_transactions_by_accepting_daa_score (https://t.co/01XfebCIgJ)
it will return the transaction that created this utxo.
if 2. is exposed as a RPC method, then you don't need to do anything external, which is cool.
created a GH issue here: https://t.co/hzC3XG93vl
the only link you'll currently have is the outpoint (parent txid and index of the utxo in the outputs list). so intuitively, you'd fetch the tx by its id, and retrieve the utxo by its index.
get tx by id doesn't exist at RPC level as of today, you can either do an external db read or keep an external track of txs (sort of indexing them on your own)