zeekayandHanzo Dev d5cacdc31b chain: state what the test pins, not where it was first seen ...

The header opened with a labelled incident, a date, a node name and a captured
stack. What the test pins is a standing property: State was written against an
upstream contract that the consensus engine holds the chain lock across every VM
call, the ZAP VM server does not reinstate that contract, and verifiedBlocks and
lastAcceptedBlock are the fields that are not self-synchronising.

Comment only.

Co-authored-by: Hanzo Dev <[email protected]>

2026-08-26 13:35:09 -07:00

..

blocktest

chore: sync dependencies and format code

2026-02-04 15:44:34 -08:00

block.go

fix(chain): P0 — accept the inner block BEFORE advancing wrapper state

2026-08-03 21:17:30 -07:00

state_race_test.go

chain: state what the test pins, not where it was first seen

2026-08-26 13:35:09 -07:00

state_test.go

fix(chain): State owns the lock for its two unsynchronised fields

2026-07-28 03:09:54 -07:00

state.go

fix(chain): State owns the lock for its two unsynchronised fields

2026-07-28 03:09:54 -07:00

status.go

move shared vm components and utils

2026-01-08 22:09:59 -08:00

test_block.go

move shared vm components and utils

2026-01-08 22:09:59 -08:00