Now that we have programmability paths on Kaspa, the need to converge on ecosystem standards in the right way becomes paramount.
It appears we lack a fitting forum for such discussions.
A primary and timely example would be a standard specification for native assets. We need a place for technical discussions where wallet devs, explorer devs, community thinkers, and core devs can brainstorm and rapidly converge on ideas without communication gaps, and without important ideas and messages getting lost to oblivion.
As a start, here is a call for community discussion on native assets.
An initial discussion on kas pub rnd is linked below, but again, to me this feels like an echo chamber, with probably the most important voices missing.
>>
The coordination and effort required to synchronize a complex upgrade across a truly decentralized network are a real challenge, and success is never a given. A good moment for a toast to all non-trivial life accomplishments
~18 Hours to Crescendo
There are some community managed Live Stream Parties set for Crescendo. Here are 2 to consider hosted by @KaspaSilver and @BlockchainBants
Links in Thread.
Please share a link to others in comments.
24 hours to Kaspa Crescendo v1.0.0
10 BPS | 5/5/25 | ~1500 UTC
Crescendo F.A.Q.
Q: How will Crescendo impact Block Rewards??
A: Block rewards will reduce to 1/10 what they are post-fork. If the block reward is expected to be 55 in 1bps, post-fork the block reward becomes 5.5.
Leave your questions in comments.
Read more about Crescendo in thread link.
𝆒 Crescendo v1.0.0
~ 72 Hours to 10 BPS
"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"
~ Kaspa Dev
Read about all the features for Crescendo - https://t.co/zvVtjVugRf
4 Days Kaspa Crescendo v1.0.0
10 BPS | 5/5/25 | ~1500 UTC
Crescendo F.A.Q.
Q: When 10bps rolls out, is there going to be a change in block size?
A: No. Kip 9 (storage mass) activates on consensus level but has been active for a while through mempool rules (=miner collaboration)
Leave your questions in comments.
Read more about Crescendo in thread link.
𝆒 Crescendo FAQ
The Crescendo hard fork, scheduled for May 5, 2025, incorporates several KIPs (KIP=Kaspa Improvement Proposal) aimed at enhancing Kaspa's scalability, efficiency, and fairness.
Read about KIP 14 which activates KIPs 4,9,10,13,15
Link in thread.
Crescendo v1.0.0 Upgrade Report
~14 days left until the Crescendo HF.
Node agent count = 57.76% (Kasnodes .com)
Mining share = 52.38% (kaspalytics .com)
Current data as of time of post