Important: VM Security Update for Devs

English CKB Development & Technical Discussion
1

As part of strengthening CKB, we regularly review older VMs and share issues we find. One of CKB’s strengths: you can always choose past VM versions. This design keeps asset ownership safe—even through hardforks.But older VMs aren’t without risks.

In our theoretical analysis, we found that v1 exec might display deterministic but non-standard behavior in certain edge cases, potentially leading to unexpected script execution results.

We recommend developers avoid exec in VM v1.

In cases like this, we may add protective measures (e.g., at the mempool) to filter risky txs. These are NOT consensus changes—VM choice stays yours. The network adds safeguards, but you remain in control.

More on Security Measures for VM Issues: VM Selection | Nervos CKB

Original post: https://x.com/CKBdev/status/1962420370641977423

5 Likes
2

Good to know!! :+1::+1:

Glad to see more public talk about the possibility of apply this kind of mitigations! :+1:

In general, I would like to see more public discussions about the possibility of mitigating vulnerabilities in contracts deployed immutably. In my opinion, it would give a great boost to this kind of deployments.

Love & Peace, Phroi

2 Likes