lux/evm
2
0
Fork 0
mirror of https://github.com/luxfi/evm.git synced 2026-09-24 00:27:44 +00:00
Code Issues Packages Projects Releases Wiki Activity

evm: name the consequence of a divergent receipt, not an occurrence of one

Browse Source 
A receipt root that disagrees stops the node where it stands — that is the
property the placement of this rule exists to prevent, and it holds whether or
not it has ever been reached.

Comment only.

Co-authored-by: Hanzo Dev <[email protected]>
This commit is contained in:
zeekay
2026-08-26 13:27:49 -07:00
co-authored by Hanzo Dev
parent 5038e01344
commit e2739c0624
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
plugin/evm/dex_atomic_verify.go
+2 -2
View File
@@ -19,8 +19,8 @@ import (
// accept, and those two cannot both hold: execution has to be a function of the block
// alone, or a node re-executing it later — bootstrapping, state-syncing, re-tracing an
// archive call — finds the object already consumed and computes a different receipt
// from the one the network agreed. The seam
// settled live and wedged every node that tried to sync past it.
// from the one the network agreed, and a receipt root that disagrees stops that
// node where it stands.
//
// So execution now binds value to the object bytes the TRANSACTION carried (a pure
// function of the block, replayable forever) and DECLARES the consumption in a log.