Feat/scheduled sc execution #3628
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…er-instantiation # Conflicts: # go.mod # go.sum
…e from the proposer side
…ution in the caller side
…anagement Scheduled txs root hash management
* Extracted functionality of normal and scheduled scs dest me in a common method, differntiated by the given parameters embeded in a DTO
…hard in scheduled situation
…xs execution handler
…eduled execution handler
…ation trigger registry versioned header support
# Conflicts: # go.mod # go.sum
…sing * Added check for reserved len > 1 in interceptors * Added epoch activation for scheduled txs in tx coordinator
…sing * Added check for reserved len > 1 in interceptors * Added epoch activation for scheduled txs in tx coordinator
* Fixed situation when proposer would not include SCRs from previous block which had scheduled txs execution, because it is running out of time even before starting the creation of the block
…k/elrond-go into fix-processed-mbs-scheduled
…o fix-processed-mbs-scheduled
…k/elrond-go into fix-processed-mbs-scheduled
…o fix-processed-mbs-scheduled
epochStart: fix pending mininBlocks for scheduled
…ion-28.01.2022 # Conflicts: # genesis/process/shardGenesisBlockCreator.go # process/smartContract/hooks/blockChainHook_test.go # storage/pruning/pruningStorer.go # storage/pruning/triePruningStorer.go
…ed-sc-execution-28.01.2022 Merge dev into feat scheduled sc execution - 28.01.2022
…registry epochStart, storage: fix backwards compatibility metachain trigger registry
# Conflicts: # dblookupext/esdtSupply/logsProcessor_test.go
Merge dev 2022.01.31
LucianMincu
approved these changes
Jan 31, 2022
iulianpascalau
approved these changes
Jan 31, 2022
raduchis
approved these changes
Jan 31, 2022
sasurobert
approved these changes
Jan 31, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This feature branch introduces Scheduled Smart Contract Execution.
The scheduling of smart contract calls is done for the current round by the block producer and also executed during the current round when the scheduling is done, but the results are only available in the next block. This is done in order to not affect the consensus time, but to better use the processing capacity of the validators during consensus.
Activating this feature allows the validators in the consensus group (including the block producers) to use up to 3 seconds of the 6 seconds block time, instead of only 1.5 seconds, to execute transactions (and especially in the second half smart contract calls), which leads to a doubling of the processing capacity of each shard, in the scenarios where the majority of gas is used for smart contract calls processing (which is also the current case of the network).
The implementation follows the internal EIP, which should be checked before reviewing.