-
Notifications
You must be signed in to change notification settings - Fork 677
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
Merge develop onto clarity wasm #5509
Merge develop onto clarity wasm #5509
Conversation
Signed-off-by: Jacinta Ferrant <jacinta@trustmachines.co>
…on-check fix: include txid in more failure logs
…tition test: additional scenarios for empty sortition tenure extends
Signed-off-by: Jacinta Ferrant <jacinta@trustmachines.co>
merge release branch back to develop
…. Not the tip consensus hash as it may not match and will result in a bad signer slot generation when writing block proposal Signed-off-by: Jacinta Ferrant <jacinta@trustmachines.co>
…d-of-tenure-blocks Add config option tenure_last_block_proposal_timeout_secs and do not allow reorgs at tenure boundary before it is exceeded
Signed-off-by: Jacinta Ferrant <jacinta@trustmachines.co>
Signed-off-by: Jacinta Ferrant <jacinta@trustmachines.co>
… into fix/fast-block-test
… reward set for nakamoto prepare phases eagerly, and pass the stacks tip height via NetworkResult to the relayer so it can update prometheus
Signed-off-by: Jacinta Ferrant <jacinta@trustmachines.co>
Signed-off-by: Jacinta Ferrant <jacinta@trustmachines.co>
Fix: snappy downloader
Signed-off-by: Jacinta Ferrant <jacinta@trustmachines.co>
Signed-off-by: Jacinta Ferrant <jacinta@trustmachines.co>
We can't wait for all signatures, because if a signer sees the global acceptance before sending its signature, it will not send it.
This is safe because schema 4 has not yet been released
…ocks Tenure extend when the previous tenure is bad
Feat: Shadow block recovery mechanism
chore: add more logging in `StacksClient`
…tch-data-from-key Feat/rpc endpoints to fetch data from key
merge Release/3.0.0.0.3 branch back to develop
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.
Code LGTM from the clarity-wasm perspective. Changes previously added to feat/clarity-wasm-develop
are not being overridden by this PR.
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Merge develop branch