Kasplex

Update on the KRC20 incident:

The code repository has been updated:
github.com/kasplex/go-krc…

If you are running your own node, please upgrade:
github.com/kasplex/go-krc…
Stop the node process (or Docker container), delete the data directory, and restart the node; it will then automatically begin syncing.

Update on the KRC20 incident:

Public APIs have been restored, and final checks to screen for anomalous transactions are currently underway.

A code fix update for the go-krc20d repository will be released this week.

Update on the KRC20 incident:

The full data revert process is currently 90% complete, and no consistency errors have been encountered so far.

Once final verification is complete and successful, the latest version of the code and the docker-image will be released on GitHub.

Update on the KRC20 incident:

The full revert and verification processes are proceeding smoothly; based on current progress, completion will still take several days.

Once finished, the public API will be reopened, and further investigations will be conducted into the chains of transactions linked to the exploit.

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.