3 Commits (b314d3e4d16118fa27156ee4cb4373faaca5a588)

Author	SHA1	Message	Date
Daniel Savu	8809f37271	feat: checkpoint syncer fraud flag (#4587) ... Upon detection of a merkle root mismatch between the local merkle tree (built from indexed events) and the onchain one, reorg diagnostic data is posted to checkpoint storage. This PR focuses on the submitter logic and leaves two things for a follow up PR: - adding logic to not spin up the validator if a fraud flag has been posted - integration testing with S3 and GCP I assume rolling out to validators will happen after the follow up PR, but running with logic from this PR will already mean the reorg diagnostic flag is posted to S3 (though not tested).	2 months ago
Daniel Savu	bf53f087c3	fix(relayer): dry-run before sending txs (#4565) ... ### Description Fixes a bug in the individual submission logic. There is a race condition where a message can become undeliverable between when it was simulated in the `prepare` step and when it's actually submitted. ### Context The bug was discovered as part of batched messages but affects chains without batching too. - when delivery fails inside batch submission simulation, we fall back to individual submission - individual submission doesn't simulate the tx outcome, and instead just submits directly - this is wrong, because the batch may cause messages to become undeliverable for long periods of time (such as when a mint cap is reached) - I believe simulation used to happen in the individual submission step, but we switched to using the already computed gas estimate from the IGP check in the `prepare` step, to save an RPC call - this results in senders being charged from their IGP allowance unnecessarily, and messages becoming undeliverable due to insufficient gas The correct flow requires three delivery simulations: 1. in the `prepare` step, to estimate gas and check the IGP policy 2. in the batch submission logic, to filter messages that are made invalid by earlier messages in the batch 3. right before submitting again, in case the batch caused the message to not be deliverable ### Solution Dry-run right before submitting an operation, and if it fails send it back to the prep queue	2 months ago
Mantas-M	096aeff13e	feat: Splitting `rust` workspace into `main` and `sealevel` (#4438) ... ### Description The single rust workspace has been split into 2 workspaces. The sealevel workspace includes the contents of the previous `sealevel` folder and the main workspace includes everything else. The workspaces differ in rust versions as the sealevel has the old one to ensure compatability, the main workspace has and updated `rustc` version of `1.80.1`. Some dependencies and sub-dependencies have been locked in versions of the old pre-split workspace to ensure no breaking code changes. The rust CI workflow has been updated to include both workspaces in the tests. ### Drive-by changes N/A ### Related issues Relates to https://github.com/hyperlane-xyz/hyperlane-monorepo/issues/4361 ### Backward compatibility No. ### Testing Rust Unit tests from the CI	3 months ago