Insights
Din samlade hubb för utbildning och analys om Kaspa. Utforska wikin, ta del av Daily Pulse, fördjupa dig i Specials och följ flerdelade miniserier.
Bläddra i wikin

Who is buying 56 million KAS? Whale or market maker?
Daily Pulse
Dagliga videouppdateringar om marknadsinsikter, nyheter och analys för Kaspa.

Kaspa R&D Weekly: A merged node feature can trace a covenant coin to its origin, but only until pruning erases the trail
R&D Weekly
Veckovis djupdykning i Kaspa R&D, protokollutveckling och tekniska milstolpar.

Kaspa vProgs vs Smart Contracts: Sovereign L1 Magic vs zkEVM L2 Power
Specials
Fördjupade avsnitt om viktiga Kaspa-utvecklingar, djupdykningar och exklusivt innehåll.
Senaste avsnitten

Kaspa mining with one click? The room says scam
A newcomer asked if a one-click Kaspa mining site was legit, plus a mystery buyer, a hashrate check and a cruise ticket question.

The $4T ghost coin nobody can find
A chart glitch sent the community hunting a $4T ghost coin, while KAS rose 2.49% and chatters spotted another 4M KAS buy.

Kaspa Dollar: genius or gimmick?
A new stablecoin whitepaper lets miners power the price oracle. Genius design or risky gimmick? Hear how the community is split on the big idea.
Senaste R&D Weekly
Visa alla →Kaspa R&D Weekly: A merged node feature can trace a covenant coin to its origin, but only until pruning erases the trail
Developers can now ask a node where a covenant coin came from without a third-party service, but the answer expires with the node's pruning window, so long-term proof is still an open question.
Kaspa R&D Weekly: Developers float a fixed 10-ticks-per-second clock for covenants, while a covenant index nears sign-off
A proposed "10 ticks per second" rule could keep covenant timers meaning the same thing even if Kaspa produces blocks faster, but for now it is an idea with open design questions.
Kaspa R&D Weekly: Covenant lookup reaches review, but a reviewer shows how one request could strain a node
A new way to find covenant-tagged coins is ready for review, yet one reviewer argues its limits do not match the database work a request can trigger.
