Merged
Conversation
Upload genesis as assets on releases
backport v2.2.9
… db (#1623) Pass around a wrapper `vm.StateDB` instance and expose public methods for accessing underlying state db which can be different for normal v/s tracing mode.
…ncase of timeout (#1625) Interrupt block building in fill transactions if we're above time. We pass around the worker level interrupt atomic value to handle the interrupt in transaction pool's pending function and ordering function in worker.
* Remove v1 v2 hiemdall detection * Delete hv1/hv2 detection logic and self-committing of spans * Remove unused functions * Fix tests * Fix tests * Fix tests * Fix tests * Fix tests * Fix tests * Fix tests * Fix tests * Fix tests * Fix tests * Fix tests * If fetching state sync fails, just continue with empty state syncs
Use a new config for all tests (some of which run in parallel) instead of using a global test config which can cause race conditions if some fields (like commit interrupt) are modified for some tests.
* feat: use multi-stage build in Dockerfile * chore: nits * chore: remove comments * chore: add bash in runtime image * chore: use alpine latest
* feat(ci): kurtosis for e2e-tests * chore: kurtosis migration * use tag instead of commit
Decouple heap calculations to reduce the waiting time for miner/worker to produce the next block. This tweaks the consistency model of the pool from being strictly consistent to eventually consistent. During internal pool re-arrangements, it prioritises the miner waiting to access the pending pool instead of doing complex time consuming calculations.
Adds some observability to capture delays during block building. - Time taken to acquire lock in pending pool - Time taken for the whole pending call to finish (this matters the most for miner during block building) - Time taken to release the lock held during tx pool reorg - Time taken to init a heap out of the pending transactions before starting to execute transactions - Time taken to actually execute transactions in ideal mining workflow
* chore: bump kurtosis * chore: update test runner image * chore: add milestones test * chore: minor nit
* misc: migrated from maticnetwork to 0xPolygon * misc: bumped heimdall-v2 * misc: bumped heimdall-v2 and bor * misc: bumped heimdall-v2, build works now * misc: updated matic-cli branch * misc: updated cosmos version
* Key Value Read Priority on BorReceipts * simplify code
….2.10-candidate
|
Member
|
The |
Raneet10
approved these changes
Aug 21, 2025
kamuikatsurgi
approved these changes
Aug 21, 2025
Collaborator
No. Discussed once with Daniel and I disabled them once. We should delete them (not mandatory for this release ofc) |
Member
Got it. |
This file contains hidden or 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
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.


Description
Please provide a detailed description of what was done in this PR
Changes
Breaking changes
Please complete this section if any breaking changes have been made, otherwise delete it
Nodes audience
In case this PR includes changes that must be applied only to a subset of nodes, please specify how you handled it (e.g. by adding a flag with a default value...)
Checklist
Cross repository changes
Testing
Manual tests
Please complete this section with the steps you performed if you ran manual tests for this functionality, otherwise delete it
Additional comments
Please post additional comments in this section if you have them, otherwise delete it