Anybody brave enough to give this a try? I will gladly help with the technicals. The comparison may be unfair (because btc is simpler, because it has been around for longer at that point, and because 3b1b is the absolute top tier of math communicators and not a realistic.

Imagine people were like "we don't need optical fibers, the internet scales in layers". The OSI model consists of 7 layers, but it never exempted engineers from improving each layer individually. Coaxial cables were lossy and noisy, and their limitations restricted the system as.

Another call for action:.

“We want a cryptocurrency to ping and be ponged”. A small wish list of mine for community devs:.1) Bullet Chess, obviously. 2) Battleships: You can use commitments (hashing) to hide your ships from the other player. 3) Trivia: Kaspa operates in real time, players could compete on

@OriNewman I'd also like to believe that the blogpost writer does not represent the wider Litecoin community in thinking that "not needing RBF" and relying on 0-conf "security" is a good thing.

I deleted a previous iteration of this post where I insinuated Btc disables RBF by default as well. @OriNewman corrected me that I was malinformed on the resolution of the RBF arguments and that it has been standard for a while now. My apologies to BTC on my mistake.

Just an excerpt on that Litecoin blogpost:.taking pride in not having RBF so you could put your trust in the mempool's good will is a testament to having given up any pretense of being mathematically sound money.

(just some thoughts, not meant to be exhaustive).

Lastly - this of course has value in being a proof of prowess for Kaspa. Moreso, this is a nice message to all enthusiasts - You can build and experiment on Kaspa right now using payloads and etc. I think there is a world of creativity to be found still.

Secondary - normal services are typically dependent on some centralized server, which even if it is encrypted, could still censor you specifically, or just crash. Kaspa messaging would be dependent on a decentralized (time restricted, but still) archive.

There's a discussion to be had regarding what edge this has over "normal" messaging services - the immediate usage I see is intra crypto - you could communicate with an anonymous crypto merchant via their address alone.

I really like this idea. it is very much still in Beta, and is missing many many features and consistency, but its potential is there. On BTC something like this would be considered spam, not to mention any message would take forever. On Kaspa it's a Tuesday.

And assume they coexist, how would the interaction and the back and forth look like? What would each be used for, and by who? .How do we see a world of "adoption"?.

Some of the real questions in crypto are hardly ever discussed. What is the actual future vision? Does cryptocurrency truly replace fiat in its entirety? Or do they coexist? is there a single coin future or specialized coins for different needs?.

I am grateful to @DesheShai for being pivotal in my understanding of Kaspa. I believe that I’m not the only who benefitted from his communicative qualities, and I believe these shoes are a harder fit than some believe them to be.

Kaspa, now and moving forward, sets to reveal what the true limits of pow are. 10bps is another leap towards the so called "impossible". Instantaneous confirmations, visa-competetive throughput, Pow level security. Ran on your laptop.

There is an inherent tension between logic zones independence, to sync interoperability. The following post, is the first of probably several that will gradually attempt to resolve this tension.

RT @coderofstuff_: 110165000.

In the sequencing commitment (previously history root) naive design, every rollup is forced to prove the sequencing of all txs on Kaspa. Below I discuss how to optimize provers' workload so it corresponds to the activity on the individual rollup.

I wrote a little post on the Kaspa research forum, with an important question targeted to zk-technology experts: .