refactor(blockchain): Minor cleanup and add safety checks. #1266
Conversation
|
Warning Rate Limit Exceeded@itsdevbear has exceeded the limit for the number of files or commits that can be reviewed per hour. Please wait 7 minutes and 40 seconds before requesting another review. How to resolve this issue?After the wait time has elapsed, a review can be triggered using the @coderabbitai review command. Alternatively, push new commits to this PR. We recommend that you space out your commits to avoid hitting the rate limit. How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per repository. WalkthroughThe changes revolve around enhancing the blockchain and EVM keeper functionalities in the Polaris project. Key modifications include improved block processing and validation, addition of new methods to the Changes
TipsChat with CodeRabbit Bot (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Review Status
Actionable comments generated: 1
Configuration used: CodeRabbit UI
Files selected for processing (8)
- cosmos/x/evm/keeper/abci.go (1 hunks)
- cosmos/x/evm/keeper/genesis.go (1 hunks)
- cosmos/x/evm/keeper/keeper.go (1 hunks)
- eth/core/chain.go (4 hunks)
- eth/core/chain_reader.go (1 hunks)
- eth/core/chain_resources.go (1 hunks)
- eth/core/chain_writer.go (2 hunks)
- eth/polar/api_backend.go (1 hunks)
Files skipped from review due to trivial changes (3)
- cosmos/x/evm/keeper/abci.go
- eth/core/chain_reader.go
- eth/polar/api_backend.go
Additional comments: 12
cosmos/x/evm/keeper/genesis.go (1)
- 44-49: The changes in this hunk seem to be in line with the pull request's summary. The
PreparePluginsmethod is now called directly onk.chaininstead of being nested within another method. This improves readability and makes the code more straightforward. The replacement ofInsertBlockWithoutSetHeadwithInsertGenesisBlockis also mentioned in the summary. Ensure that the newInsertGenesisBlockmethod correctly handles all the cases that the old method did.eth/core/chain.go (2)
66-72: The
validatorfield has been added to theblockchainstruct and is initialized in theNewChainfunction. Ensure that thevalidatoris used correctly throughout the codebase.132-135: The
validatoris initialized with a new instance ofcore.BlockValidator. This is a good practice as it ensures that thevalidatoris always in a valid state when ablockchaininstance is created.cosmos/x/evm/keeper/keeper.go (2)
31-37: The import statements have been updated. Ensure that the new imports are used correctly in the code and the removed import is not used anywhere.
39-45: The
Blockchaininterface has been updated. Make sure all implementations of this interface are updated accordingly.- core.ChainWriter - core.ChainReader + InsertGenesisBlock(*coretypes.Block) error + InsertBlockWithoutSetHead(*coretypes.Block) error + GetBlockByNumber(uint64) *coretypes.Blocketh/core/chain_writer.go (7)
22-32: The import statements are well organized and separated by functionality. Good practice.
34-41: The
ChainWriterinterface has been updated to include new methods and removecore.ChainWriterandcore.ChainReader. Ensure that all implementations of this interface have been updated accordingly.44-50: The
InsertGenesisBlockfunction now includes a validation check for the genesis block. This is a good practice to ensure the integrity of the genesis block.52-80: The
InsertBlockWithoutSetHeadfunction has been updated to include block validation and processing logic. This is a good practice to ensure the integrity of the blocks being inserted into the blockchain.82-132: The
WriteBlockAndSetHeadfunction has been updated to include block validation, processing logic, and storing block headers and historical data. This is a good practice to ensure the integrity of the blocks being inserted into the blockchain and the consistency of the blockchain state.134-165: The
writeBlockWithStatefunction is a new function introduced to write the block and its state to the blockchain. This is a good practice to ensure the integrity of the blocks being inserted into the blockchain and the consistency of the blockchain state.22-178: > Note: This review was outside of the patch, so it was mapped to the patch with the greatest overlap. Original lines [167-193]
The
writeHistoricalDatafunction is a new function introduced to store block headers and historical data. This is a good practice to ensure the integrity of the blocks being inserted into the blockchain and the consistency of the blockchain state.
There was a problem hiding this comment.
Review Status
Actionable comments generated: 1
Configuration used: CodeRabbit UI
Files selected for processing (1)
- eth/core/chain_writer.go (2 hunks)
Additional comments: 5
eth/core/chain_writer.go (5)
34-41: The
ChainWriterinterface has been updated to include theInsertGenesisBlockandInsertBlockWithoutSetHeadmethods. Ensure that all implementations of this interface have been updated accordingly.44-51: The
InsertGenesisBlockfunction now checks if the block being inserted is the genesis block (i.e., its number is 0). If not, it returns an error. This is a good safety check to prevent incorrect usage of this function.54-83: The
InsertBlockWithoutSetHeadfunction has been significantly updated. It now validates the block body, processes the EVM block, and validates the state after block processing. If any of these steps fail, it logs an error and returns the error. This is a good improvement in terms of safety and error handling.137-168: The
writeBlockWithStatefunction writes the block and its state to the blockchain. It also logs an error if storing the block header or writing historical data fails. This function seems to be well-structured and handles errors appropriately.22-181: > Note: This review was outside of the patch, so it was mapped to the patch with the greatest overlap. Original lines [170-196]
The
writeHistoricalDatafunction writes the block, receipts, and transactions to the host chain if the historical plugin is supported. It logs an error and returns it if any of these operations fail. This function seems to be well-structured and handles errors appropriately.
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #1266 +/- ##
==========================================
- Coverage 49.23% 48.73% -0.50%
==========================================
Files 84 84
Lines 4789 4838 +49
==========================================
Hits 2358 2358
- Misses 2257 2306 +49
Partials 174 174
|
There was a problem hiding this comment.
Review Status
Actionable comments generated: 2
Configuration used: CodeRabbit UI
Files selected for processing (5)
- cosmos/x/evm/keeper/genesis.go (1 hunks)
- cosmos/x/evm/keeper/keeper.go (1 hunks)
- cosmos/x/evm/keeper/processor.go (1 hunks)
- eth/core/chain.go (4 hunks)
- eth/core/chain_writer.go (2 hunks)
Additional comments: 14
cosmos/x/evm/keeper/keeper.go (3)
31-37: The import statements have been updated to reflect the new dependencies. Ensure that these packages exist and are accessible.
39-45: The Blockchain interface has been updated. Ensure that all implementations of this interface have been updated to reflect these changes.
47-47: The Keeper struct remains unchanged.
cosmos/x/evm/keeper/processor.go (1)
- 64-66: The
InsertBlockAndSetHeadfunction is now being used instead ofInsertBlockWithoutSetHead. Ensure that this change is intentional and that the new function behaves as expected in all scenarios where it is used.cosmos/x/evm/keeper/genesis.go (1)
- 44-49: The changes to the
InitGenesisfunction look good. The addition ofk.chain.PreparePlugins(ctx.WithEventManager(sdk.NewEventManager()))ensures that the plugins are prepared with a new event manager context before writing the genesis block. This could improve the efficiency and reliability of the function. However, ensure that thePreparePluginsandWriteGenesisBlockfunctions handle errors appropriately internally, as they are not checked here.eth/core/chain.go (3)
66-72: The addition of the
validatorfield and the removal ofcurrentReceiptsandcurrentLogsfields are noted. Ensure that all references to these fields in the codebase have been updated accordingly. Thevalidatorfield should be initialized properly in the constructor.80-85: The
currentBlockandfinalizedBlockfields have been updated to useatomic.Pointer. This is a good practice for concurrent programming to avoid data races. However, ensure that all operations on these fields are done using atomic operations.95-105: The
loggerfield has been updated to typelog.Logger. Ensure that all logging operations in the codebase have been updated to use this new type.eth/core/chain_writer.go (6)
34-41: The
ChainWriterinterface has been updated to include theWriteGenesisBlockandInsertBlockAndSetHeadmethods. Ensure that all implementations of this interface have been updated accordingly.44-51: The
WriteGenesisBlockmethod has been added to theblockchainstruct. It writes the genesis block and sets it as the head. The genesis block is validated to ensure its block number is 0. If not, an error is returned. The method then callsWriteBlockAndSetHeadto write the block and set it as the head. If an error occurs during this process, it is returned.53-83: The
InsertBlockAndSetHeadmethod has been added to theblockchainstruct. It validates the block body, processes the EVM block, validates the state after processing, and then writes the block and sets it as the head. If an error occurs at any point, it is logged and returned.85-151: The
WriteBlockAndSetHeadmethod has been updated to include theemitHeadEventparameter and additional logic for setting the current block and finalizing the block. It writes the block to the store, validates the parent block, sets the current block, finalizes the block, stores txLookup entries for all transactions in the block, writes the receipts cache, and fires off the feeds. IfemitHeadEventis true, it fires aChainHeadEvent.153-184: The
writeBlockWithStatemethod writes the block along with its state (receipts and logs) into the blockchain. It stores the header, writes the block to the database, commits all cached state changes into the underlying memory database, and logs the finalization of the EVM block. If an error occurs at any point, it is logged and returned.22-197: > Note: This review was outside of the patch, so it was mapped to the patch with the greatest overlap. Original lines [186-212]
The
writeHistoricalDatamethod writes the block, receipts, and transactions to the host chain if the historical plugin is supported. If an error occurs at any point, it is logged and returned.
There was a problem hiding this comment.
Review Status
Actionable comments generated: 3
Configuration used: CodeRabbit UI
Files selected for processing (6)
- cosmos/miner/miner.go (3 hunks)
- cosmos/runtime/runtime.go (3 hunks)
- cosmos/x/evm/keeper/abci.go (1 hunks)
- e2e/precompile/contracts/distribution/distribution_test.go (1 hunks)
- e2e/testapp/app.go (1 hunks)
- eth/core/chain_writer.go (2 hunks)
Files skipped from review due to trivial changes (1)
- cosmos/x/evm/keeper/abci.go
Additional comments: 16
e2e/testapp/app.go (1)
- 191-196: The
app.Polaris.Buildfunction call has been modified to passappinstead ofapp.BaseAppas the first argument. This change may indicate a modification in the way theBuildfunction is implemented or how it interacts with theappobject. Ensure that theBuildfunction can handle the entireappobject and that this change doesn't introduce any unintended side effects.- if err := app.Polaris.Build(app.BaseApp, app.EVMKeeper); err != nil { + if err := app.Polaris.Build(app, app.EVMKeeper); err != nil { panic(err) }cosmos/runtime/runtime.go (4)
21-27: The
contextpackage is imported. Ensure that it is used in the codebase.51-55: The
PrepareCheckStatemethod is added to theEVMKeeperinterface. Make sure all implementations of this interface have this method.58-63: The
miner.Appinterface is embedded in theCosmosAppinterface. This will add all the methods ofminer.ApptoCosmosApp. Ensure that this is the intended behavior.101-111: The
miner.Newfunction is called with an additional argumentappof typeminer.App. Ensure that theminer.Newfunction has been updated to accept this new argument.cosmos/miner/miner.go (6)
32-38: The new import "pkg.berachain.dev/polaris/cosmos/x/evm/keeper" is added. Ensure that the package is available and accessible.
49-51: The new interface "App" is added with the method "BeginBlocker". Ensure that all implementations of this interface have this method.
53-58: The new interface "EVMKeeper" is added with the methods "Setup" and "PrepareCheckState". Ensure that all implementations of this interface have these methods.
63-66: The new field "app" of type "App" is added to the struct "Miner". Ensure that all instances of "Miner" are updated to include this field.
69-74: The function "New" now takes an additional parameter "app App". Ensure that all calls to this function are updated to include this parameter.
84-96: The method "PrepareProposal" now calls "app.BeginBlocker". Ensure that the "BeginBlocker" method is implemented correctly in the "App" interface.
eth/core/chain_writer.go (5)
34-41: The
ChainWriterinterface has been updated to include theWriteGenesisBlockandInsertBlockAndSetHeadmethods. Ensure that all implementations of this interface have been updated accordingly.44-51: The
WriteGenesisBlockfunction has been added to theblockchainstruct. It checks if the block number is 0 (which is expected for a genesis block) and then callsWriteBlockAndSetHead. The error handling is appropriate.88-153: The
WriteBlockAndSetHeadfunction has been updated to include an additional parameteremitHeadEvent. It writes the block to the store, checks if the parent is the head block, sets the current block, finalizes the block, updates the caches, and fires off the feeds. The error handling is appropriate.156-186: The
writeBlockWithStatefunction has been added. It writes the block header, the block itself, commits all cached state changes, and logs the finalization of the EVM block. The error handling is appropriate.22-199: > Note: This review was outside of the patch, so it was mapped to the patch with the greatest overlap. Original lines [189-213]
The
writeHistoricalDatafunction has been added. It stores the block, receipts, and transactions if the historical plugin is supported. The error handling is appropriate.
| // Wait for 5 blocks to be produced, to make sure there are rewards. | ||
| for i := 0; i < 5; i++ { | ||
| Expect(tf.WaitForNextBlock()).To(Succeed()) | ||
| } |
There was a problem hiding this comment.
The change from waiting for 2 blocks to 5 blocks is reasonable if it ensures that there are enough blocks produced to have rewards. However, it might increase the test execution time. If the test suite has many tests that wait for blocks, this could significantly slow down the overall test execution. Consider if there's a more efficient way to ensure that enough blocks are produced, such as by mocking or simulating block production.
eth/core/chain_writer.go
Outdated
| // For now, it is a huge lie. It does infact set the head. | ||
| func (bc *blockchain) InsertBlockAndSetHead(block *types.Block) error { | ||
| // Validate that we are about to insert a valid block. | ||
| if block.NumberU64() > 1 { // TODO DIAGNOSE | ||
| if err := bc.validator.ValidateBody(block); err != nil { | ||
| log.Error("invalid block body", "err", err) | ||
| return err | ||
| } | ||
| } | ||
|
|
||
| // Process block using the parent state as reference point | ||
| pstart := time.Now() | ||
| receipts, logs, _, err := bc.processor.Process(block, bc.statedb, *bc.vmConfig) | ||
| // Process the incoming EVM block. | ||
| receipts, logs, usedGas, err := bc.processor.Process(block, bc.statedb, *bc.vmConfig) | ||
| if err != nil { | ||
| log.Error("failed to process block", "num", block.NumberU64(), "err", err) | ||
| return err | ||
| } | ||
| ptime := time.Since(pstart) | ||
| bc.logger.Info("processed block in", "time", ptime) | ||
| return bc.InsertBlock(block, receipts, logs) | ||
| } | ||
|
|
||
| // InsertBlock inserts a block into the canonical chain and updates the state of the blockchain. | ||
| func (bc *blockchain) InsertBlock( | ||
| block *types.Block, | ||
| receipts types.Receipts, | ||
| logs []*types.Log, | ||
| ) error { | ||
| var err error | ||
| if _, err = bc.statedb.Commit( | ||
| block.NumberU64(), | ||
| bc.config.IsEIP158(block.Header().Number), | ||
| ); err != nil { | ||
| // ValidateState validates the statedb post block processing. | ||
| if err = bc.validator.ValidateState(block, bc.statedb, receipts, usedGas); err != nil { | ||
| log.Error("invalid state after processing block", "num", block.NumberU64(), "err", err) | ||
| return err | ||
| } | ||
|
|
||
| // TODO: prepare historical plugin here? | ||
| // TBH still think we should deprecate it and run in another routine as indexer. | ||
| // We can just immediately finalize the block. It's okay in this context. | ||
| if _, err = bc.WriteBlockAndSetHead( | ||
| block, receipts, logs, nil, true); err != nil { | ||
| log.Error("failed to write block", "num", block.NumberU64(), "err", err) | ||
| return err | ||
| } | ||
|
|
||
| // ***************************************** // | ||
| // TODO: add safety check for canonicallness // | ||
| // ***************************************** // | ||
| return err | ||
| } |
There was a problem hiding this comment.
The InsertBlockAndSetHead function has been added. It validates the block, processes it, validates the state after processing, and then writes the block. The error handling is appropriate. However, the comment on line 55 is misleading and should be updated to reflect the actual behavior of the function.
- // For now, it is a huge lie. It does infact set the head.
+ // This function inserts a block and also sets it as the head.Commitable suggestion (Beta)
| // For now, it is a huge lie. It does infact set the head. | |
| func (bc *blockchain) InsertBlockAndSetHead(block *types.Block) error { | |
| // Validate that we are about to insert a valid block. | |
| if block.NumberU64() > 1 { // TODO DIAGNOSE | |
| if err := bc.validator.ValidateBody(block); err != nil { | |
| log.Error("invalid block body", "err", err) | |
| return err | |
| } | |
| } | |
| // Process block using the parent state as reference point | |
| pstart := time.Now() | |
| receipts, logs, _, err := bc.processor.Process(block, bc.statedb, *bc.vmConfig) | |
| // Process the incoming EVM block. | |
| receipts, logs, usedGas, err := bc.processor.Process(block, bc.statedb, *bc.vmConfig) | |
| if err != nil { | |
| log.Error("failed to process block", "num", block.NumberU64(), "err", err) | |
| return err | |
| } | |
| ptime := time.Since(pstart) | |
| bc.logger.Info("processed block in", "time", ptime) | |
| return bc.InsertBlock(block, receipts, logs) | |
| } | |
| // InsertBlock inserts a block into the canonical chain and updates the state of the blockchain. | |
| func (bc *blockchain) InsertBlock( | |
| block *types.Block, | |
| receipts types.Receipts, | |
| logs []*types.Log, | |
| ) error { | |
| var err error | |
| if _, err = bc.statedb.Commit( | |
| block.NumberU64(), | |
| bc.config.IsEIP158(block.Header().Number), | |
| ); err != nil { | |
| // ValidateState validates the statedb post block processing. | |
| if err = bc.validator.ValidateState(block, bc.statedb, receipts, usedGas); err != nil { | |
| log.Error("invalid state after processing block", "num", block.NumberU64(), "err", err) | |
| return err | |
| } | |
| // TODO: prepare historical plugin here? | |
| // TBH still think we should deprecate it and run in another routine as indexer. | |
| // We can just immediately finalize the block. It's okay in this context. | |
| if _, err = bc.WriteBlockAndSetHead( | |
| block, receipts, logs, nil, true); err != nil { | |
| log.Error("failed to write block", "num", block.NumberU64(), "err", err) | |
| return err | |
| } | |
| // ***************************************** // | |
| // TODO: add safety check for canonicallness // | |
| // ***************************************** // | |
| return err | |
| } | |
| // This function inserts a block and also sets it as the head. | |
| func (bc *blockchain) InsertBlockAndSetHead(block *types.Block) error { | |
| // Validate that we are about to insert a valid block. | |
| if block.NumberU64() > 1 { // TODO DIAGNOSE | |
| if err := bc.validator.ValidateBody(block); err != nil { | |
| log.Error("invalid block body", "err", err) | |
| return err | |
| } | |
| } | |
| // Process the incoming EVM block. | |
| receipts, logs, usedGas, err := bc.processor.Process(block, bc.statedb, *bc.vmConfig) | |
| if err != nil { | |
| log.Error("failed to process block", "num", block.NumberU64(), "err", err) | |
| return err | |
| } | |
| // ValidateState validates the statedb post block processing. | |
| if err = bc.validator.ValidateState(block, bc.statedb, receipts, usedGas); err != nil { | |
| log.Error("invalid state after processing block", "num", block.NumberU64(), "err", err) | |
| return err | |
| } | |
| // We can just immediately finalize the block. It's okay in this context. | |
| if _, err = bc.WriteBlockAndSetHead( | |
| block, receipts, logs, nil, true); err != nil { | |
| log.Error("failed to write block", "num", block.NumberU64(), "err", err) | |
| return err | |
| } | |
| return err | |
| } |
There was a problem hiding this comment.
Review Status
Actionable comments generated: 1
Configuration used: CodeRabbit UI
Files selected for processing (2)
- cosmos/miner/miner.go (3 hunks)
- cosmos/runtime/runtime.go (3 hunks)
Additional comments: 9
cosmos/runtime/runtime.go (4)
21-27: The import of the
contextpackage is new. Ensure that it is used appropriately in the code.51-55: The
EVMKeeperinterface has a new methodPrepareCheckState. Ensure that all implementations of this interface have this method.58-63: The
CosmosAppinterface now embeds theminer.Appinterface. Ensure that all implementations ofCosmosAppare compatible with this change.105-107: The
WrappedMinerfield in thePolarisstruct is modified to include theappandekparameters in theminer.Newfunction call. Ensure that this change is compatible with theminer.Newfunction definition.cosmos/miner/miner.go (5)
32-38: The new import
evmkeeper "pkg.berachain.dev/polaris/cosmos/x/evm/keeper"is added. Ensure that the package is available and accessible.46-58: The new interfaces
AppandEVMKeeperare introduced. Make sure that these interfaces are implemented wherever required.61-67: Two new fields
appandkeeperare added to theMinerstruct. Ensure that these fields are properly initialized and used.70-76: The
Newfunction is modified to acceptappandkeeperparameters. Make sure that all calls to this function are updated to match the new signature.84-103: The
PrepareProposalfunction is updated to callPrepareCheckStateandBeginBlockermethods. Ensure that these methods are correctly implemented and that they return the expected results.
There was a problem hiding this comment.
Review Status
Actionable comments generated: 1
Configuration used: CodeRabbit UI
Files selected for processing (4)
- cosmos/miner/miner.go (3 hunks)
- cosmos/runtime/runtime.go (3 hunks)
- cosmos/x/evm/keeper/abci.go (2 hunks)
- cosmos/x/evm/module.go (1 hunks)
Additional comments: 13
cosmos/x/evm/keeper/abci.go (2)
35-43: The error handling has been improved to provide more detailed information about the failed block. This is a good practice as it aids in debugging and understanding the system's behavior.
52-56: The function
PrepareCheckStatehas been renamed toSetLatestQueryContext. Ensure that all calls to this function throughout the codebase have been updated to match the new name.cosmos/x/evm/module.go (1)
- 126-132: The function
PrepareCheckStatehas been renamed toSetLatestQueryContextand now returns an error. Ensure that all calls to this function throughout the codebase have been updated to match the new signature and handle the returned error appropriately.- func (am AppModule) PrepareCheckState(ctx context.Context) { - am.keeper.SetLatestQueryContext(ctx) - } + func (am AppModule) SetLatestQueryContext(ctx context.Context) error { + return am.keeper.SetLatestQueryContext(ctx) + }cosmos/runtime/runtime.go (4)
21-27: The import of the
contextpackage is added. Ensure that it is used in the code.51-55: The
EVMKeeperinterface is extended with a new methodSetLatestQueryContext. Make sure that all implementations of this interface are updated to include this method.58-63: The
CosmosAppinterface now extends theminer.Appinterface. Ensure that all implementations ofCosmosAppare updated to include the methods fromminer.App.101-111: The
Buildfunction now takes an additionalappargument of typeCosmosAppand an additionalekargument of typeEVMKeeper. Ensure that all calls to this function throughout the codebase have been updated to match the new signature.cosmos/miner/miner.go (6)
32-38: The new import statement looks fine. Ensure that the package "pkg.berachain.dev/polaris/cosmos/x/evm/keeper" is available and accessible.
49-52: The new interface
Appwith methodsBeginBlockerandPreBlockeris introduced. Ensure that the methods are implemented wherever this interface is used.54-59: The new interface
EVMKeeperwith methodsSetupandSetLatestQueryContextis introduced. Ensure that the methods are implemented wherever this interface is used.62-68: The
Minerstruct now includes two new fields:appof typeAppandkeeperof typeEVMKeeper. Ensure that these fields are properly initialized and used.70-77: The
Newfunction now accepts two additional parameters:appof typeAppandkeeperof typeEVMKeeper. Ensure that all calls to this function throughout the codebase have been updated to match the new signature.85-117: The
PrepareProposalfunction has been modified to include additional logic related to the new interfaces and methods. Ensure that the logic is correct and that error handling is properly done.
| @@ -68,11 +85,34 @@ func (m *Miner) Init(serializer EnvelopeSerializer) { | |||
| func (m *Miner) PrepareProposal( | |||
There was a problem hiding this comment.
@alexanderbez is this safe?
There was a problem hiding this comment.
I haven't dug into the specifics of each individual method call, but since PrepareProposal state is discarded upon round timeout, any state modifications should be safe assuming you use the provided ctx (which it looks like you are!).
There was a problem hiding this comment.
If you'd like, I can dive into the individual method calls for further analysis.
Summary by CodeRabbit
Refactor:
Precommitfunction for better debugging.InitGenesisfunction for improved block processing.Blockchaininterface andblockchainstruct for better block handling and validation.ChainWriterinterface.New Features:
HasBlockAndStatefunction to check the existence of a block and its state.validatorfield in theblockchainstruct for block validation.Bug Fixes:
SubscribeLogsEventfunction for cleaner logs.Tests:
Chores: