Skip to content

feat: add bridge E2E latency measurement with updated consensus config#563

Merged
ByteYue merged 1 commit intomainfrom
latency_for_oracle_teast
Feb 9, 2026
Merged

feat: add bridge E2E latency measurement with updated consensus config#563
ByteYue merged 1 commit intomainfrom
latency_for_oracle_teast

Conversation

@ByteYue
Copy link
Contributor

@ByteYue ByteYue commented Feb 9, 2026

Description

feat: add bridge E2E latency measurement with updated consensus config

  • Update consensus_config across all test clusters (bridge, four_validator, fuzzy_cluster, single_node) to use proper on-chain consensus configuration
  • Add per-event latency measurement from source chain MessageSent to Gravity chain NativeMinted events
  • Enhance BridgeStats with median and P95 latency metrics
  • Add query_message_sent_timestamps() helper to fetch source chain event timestamps
  • Optimize block timestamp fetching with batch queries

How Has This Been Tested?

Key Areas to Review

Type of Change

  • New feature
  • Bug fix
  • Breaking change
  • Performance improvement
  • Refactoring
  • Dependency update
  • Documentation update
  • Tests

Which Components or Systems Does This Change Impact?

  • Validator Node
  • Consensus
  • EVM Runtime
  • Gravity SDK Core
  • CLI Tools
  • E2E Tests
  • Documentation
  • Other (specify)

Checklist

  • I have performed a self-review of my own code
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes

@ByteYue ByteYue merged commit 77226b6 into main Feb 9, 2026
3 of 4 checks passed
@ByteYue ByteYue deleted the latency_for_oracle_teast branch February 9, 2026 07:30
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