From 11ac325d1a1763eea9f63cfa64f59c0962827502 Mon Sep 17 00:00:00 2001 From: raulk Date: Tue, 14 Feb 2023 14:06:33 +0000 Subject: [PATCH] Revert "fix: stmgr: check message validity before invoking vm" (#10270) This reverts commit 2bbd1fbbb610645650bc439abb2984f8c38ded61. --- chain/stmgr/call.go | 8 -------- 1 file changed, 8 deletions(-) diff --git a/chain/stmgr/call.go b/chain/stmgr/call.go index e6b742255ff..ea2758705fa 100644 --- a/chain/stmgr/call.go +++ b/chain/stmgr/call.go @@ -107,14 +107,6 @@ func (sm *StateManager) callInternal(ctx context.Context, msg *types.Message, pr } } - // This isn't strictly necessary, but the underlying VM will assume that the message is - // valid and may not return helpful debugging information. Checking here makes message - // validity issues easier to debug. - nv := sm.GetNetworkVersion(ctx, ts.Height()) - if err := msg.ValidForBlockInclusion(0, nv); err != nil { - return nil, xerrors.Errorf("message not valid for network version %d: %w", nv, err) - } - // Unless executing on a specific state cid, apply all the messages from the current tipset // first. Unfortunately, we can't just execute the tipset, because that will run cron. We // don't want to apply miner messages after cron runs in a given epoch.