Live visualization of Kaspa's Testnet-12 BlockDAG — the proving ground for Covenants++
Covenants · ZK proofs · Native assets · SilverScript · Programmable UTXOs
Every block. Every connection. Live. And keep an eye out for the visitor.
tn12.kaspadrome.xyz
Kaspadrome is back online after some tune-ups!
⚡ Cycling fuel now targets a max speed of 1024 TPS for minimal impact on broader network activity
⚡ New 15-minute periodic boosts to near max-throughput until 10 KAS is expended in fees (10 KAS in boost fuel needed to trigger the countdown)
⚡ Redesigned and improved gauges
⚡ Improved visual fidelity for mobile users in 3D mode
Here's to the next 500M transactions together! Stay tuned as we find new ways to showcase the Kaspa blockDAG and support the miners who power it.
This, plus a way to spotlight Kaspa's expanding technical capabilities. A 24/7 showcase of the most advanced features on the fastest L1? Small update coming tomorrow to start us in this direction.
(8379.04 KAS still in reserves)
Could @Kaspadrome become a strategic way to show appreciation to the Kaspa ecosystem as a whole by basically donating to miners. Big KAS projects could route a tiny amount of their profits towards keeping this on 24/7.
@PoW_Odie@thekaspaonion@Themooseisloos5
Work continues on the Kaspadrome. While this is great for extending our fuel and smoothing out the network hiccups it limits us to 2900 TPS. I was thinking we could revamp the boost ship to come in on intervals for a short display of Kaspa's ultimate power.
Heads up: expect slightly degraded performance on the Kaspadrome while we optimize our fee strategy. This will help us extend the mileage of our fuel and speed up transactions for all Kaspa users. Short-term tuning for long-term speed.
The Kaspa community just pushed 179M transactions through the DAG on a community experiment. No incentives. No airdrops. Just people who genuinely want to see this technology succeed.
After feedback from the community, we're reverting mempool thresholds back to 10k/20k. A large mempool adds unnecessary delay to transaction confirmations and puts extra strain on nodes. Kaspadrome should push the network's throughput, not clog it.
for those of you wondering why the Kaspadrome and Kaspa.stream TPS numbers differ:
kaspadrome.xyz measures: Per-block TX count — "How many transactions were processed across all blocks?" (block throughput / network workload)
Kaspa.stream measures: Unique TX count — "How many distinct user actions were settled?" (economic activity)
500 KAS in fees on the Kaspadrome! Every transaction helps secure the Kaspa network by rewarding miners who keep it running. Fueled 100% by the Kaspa community!
kaspadrome.xyz
btw I'm still making some front end tweaks so the kaspadrome could go down for a few seconds here and there.
all fuel levels are preserved and picked right back up on restart.