For all Kaspians,
One of Kaspa’s important next steps is building a wider base of people who understand and can explain $KAS. Right now, too much depends on a handful of core developers being the “single source of truth,” which creates a bottleneck for growth. To scale, we need
Ori Newman
353 posts
I'm a Bitcoin enthusiast since 2013 and I'm recently working on Kaspa
Joined October 2017
- Doing code review for Crescendo activation logic. I get excited only from reading these lines :)
- Congratulations to @kasplex for the upcoming launch tomorrow! I wanted to share my two cents: 1) Kasplex still didn't open source their project. 2) Until vProgs proposal (or something similar) is implemented, any L1-L2 bridge will be centralized. These two points mean that when
- We're nearly done writing the consensus component on Rust and are finally able to start benchmarking the codebase as a whole. The results are amazing! Validating 10K blocks with a total of 1.6M transactions took 48 seconds, while the same benchmark took 23 MINUTES on the existing
- A post-mortem on the 20 minute freeze Kaspa has experienced last saturday
- rusty-kaspa v1.0.1 has been released github.com/kaspanet/rusty… This version removes the obsolete dust prevention mechanism and allows for easier work with multi output transactions. It also includes some wallet related updates that can be read here github.com/kaspanet/rusty…
- Less than 24 hours :)72 hours to a big crescendo moment in permissionless distributed systems, showing that a multi-leader consensus real-world system can achieve block times shorter than global internet round-trip time (RTT) without artificially suppressing the P2P network size or assuming proximity
- $kas users, I'm reminding you that the Crescendo hardfork will happen in less than 48 hours. If you're running a node and don’t upgrade, your wallet may show incorrect balances and your transactions might fail. See upgrade links in the following post
- Replying to @maxibitcat @DesheShai and @FreshAir08Kaspa is going to have OP_CAT and covenants, which covers the "simple SC functionality" while preserving the simple parallizeable utxo model
- Shai is the best Kaspa educator and content creator we ever had, and we wouldn't be where we are without himHi $kas, here's a statement of intentions and some other thoughts about my current efforts. 1. In my excitement about the prospects of community funding, I rushed to announce and discuss it with the community without really thinking about the optics. In what I now consider my
- 🚨NEW Exclusive Podcast w @OriNewman - A true visionary & original core developers of Kaspa. @OriNewman shares his incredible insights from the early Bitcoin days through Kaspa's revolutionary launch. Agenda ✅ How Ori discovered Bitcoin in 2013 through libertarian forums ✅
00:00 - Replying to @NickSzabo4 @number33_ and @brandonturp1. Kaspa currently have ~150 public nodes, and each public node has ~4000 peers. It's fairly easy to run a Kaspa node and it can be run on relatively old laptops. 2. Kaspa is using pruning with UTXO commitment, so even in peak usage (about 3000 TPS), its storage is limited to
- Replying to @kaspaunchained and @KaspaCurrencyThanks to everyone who helped this happen, from new community devs, people who invested in the Rust fund, people who gave us use their servers, and more!






