Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: Short Block Interval Phase One: 1.5 seconds for BEP-520 #618

Draft
wants to merge 2 commits into
base: develop
Choose a base branch
from

Conversation

buddh0
Copy link
Contributor

@buddh0 buddh0 commented Mar 6, 2025

Description

BEP-520: Short Block Interval Phase One: 1.5 seconds

Rationale

tell us why we need these changes...

Example

add an example CLI or API response...

Changes

Notable changes:

  • add each change in a bullet point here
  • ...

@buddh0 buddh0 force-pushed the bep-520-short-block-interval branch 2 times, most recently from f5ae956 to 31c4c06 Compare March 6, 2025 09:45
@NathanBSC NathanBSC changed the title BEP-520: Short Block Interval Phase One: 1.5 seconds feat: Short Block Interval Phase One: 1.5 seconds for BEP-520 Mar 6, 2025
@buddh0 buddh0 force-pushed the bep-520-short-block-interval branch from 31c4c06 to 3e1318e Compare March 6, 2025 09:52
@@ -385,6 +390,7 @@ contract BSCValidatorSet is IBSCValidatorSet, System, IParamSubscriber, IApplica
function getMiningValidators() external view override returns (address[] memory, bytes[] memory) {
uint256 _maxNumOfWorkingCandidates = maxNumOfWorkingCandidates;
uint256 _numOfCabinets = numOfCabinets > 0 ? numOfCabinets : INIT_NUM_OF_CABINETS;
uint256 _shuffleInterval = 200;
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is no mention of shuffleInterval in the BEP-520. Is it supposed to be same as epoch or something else?

Copy link
Contributor Author

@buddh0 buddh0 Mar 7, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

just use it to replce EPOCH here,
before the change, EPOCH = 200, so the result is the same as before.

The effect is the same as following:
change name of the constant var EPOCH to shuffleInterval

Copy link
Contributor Author

@buddh0 buddh0 Mar 7, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the purpose is let the shuffle process not depend on a var called Epoch Length
because, Epoch Length will change from bsc client side.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants