From 9d48097de0ba67141947a3eab569e1c5f3a02e77 Mon Sep 17 00:00:00 2001
From: tersec <tersec@users.noreply.github.com>
Date: Thu, 17 Jun 2021 07:22:39 +0000
Subject: [PATCH] fix assertion in beacon block creation rollback/restore
 (#2655)

---
 beacon_chain/validators/validator_duties.nim | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/beacon_chain/validators/validator_duties.nim b/beacon_chain/validators/validator_duties.nim
index b4caacc88..2995e0bf7 100644
--- a/beacon_chain/validators/validator_duties.nim
+++ b/beacon_chain/validators/validator_duties.nim
@@ -313,7 +313,7 @@ proc makeBeaconBlockForHeadAndSlot*(node: BeaconNode,
       # TODO address this ugly workaround - there should probably be a
       #      `state_transition` that takes a `StateData` instead and updates
       #      the block as well
-      doAssert v.addr == addr proposalStateAddr.data
+      doAssert v.addr == addr proposalStateAddr.data.hbsPhase0
       assign(proposalStateAddr[], poolPtr.headState)
 
     return makeBeaconBlock(