We appreciate the update and the work already in motion.
One ask from the community: please do this revert the careful way. Replay the full Kaspa history on the fixed indexer if you can, rather than skipping a DAA score range.
@argonmining raised that here. A lot of KRC-20 / L2 holders are just trying not to get caught in the middle.
Happy to wait on the 3–5 days. Clarity on the method would help everyone sleep.
$KAS $NACHO
KRC20 Incident Update:
A vulnerability in the underlying protocol has been confirmed. Code-level fixes are complete, and a hard fork will follow. A full-state revert verification must be completed prior to the hard fork; this process is expected to take 3–5 days.
Public node APIs will be disabled during this period; please do not perform any KRC20 token operations (such as transfers).
For self-hosted nodes, please wait for the release of the new "go-krc20d" version before upgrading.
Sep 24, 2026 · 7:54 PM UTC
2
11
33
776
