-
Notifications
You must be signed in to change notification settings - Fork 638
docs: document max values for PBTS Precision and MessageDelay #5046
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
Conversation
Hi @melekes , Could you check this ? |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Ironbird - launch a networkTo use Ironbird, you can use the following commands:
Custom Load Test ConfigurationYou can provide a custom load test configuration using the `--load-test-config=` flag:
Use |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
I think this is worth adding. |
/ironbird start |
Ironbird failed to run command
|
Closes #4893
This PR updates the PBTS-related documentation to reflect the implementation constraints introduced in #4816.
In
proposer-based-timestamps.md
, added notes underPrecision
andMessageDelay
to document the hard-coded caps:Precision
≤ 30sMessageDelay
≤ 24hIn
data_structures.md
, added a note below the SynchronyParams table to mention these limits as implementation constraints.In
pbts-sysmodel.md
, included a note after [PBTS-MSG-DELAY.0] explaining that although these parameters are bounded in the implementation, it has no impact on the formal model.These updates ensure that readers are aware of the practical limitations applied in the implementation and help prevent misconfiguration or misunderstanding.
PR checklist
.changelog
(we use unclog to manage our changelog)docs/
orspec/
) and code comments