Core: Build Cross-Chain Message Passing Bridge Monitoring Service

[Smartdevs17]

Context

AgenticPay uses cross-chain bridges for liquidity movement. Bridge failures can result in stuck funds and failed settlements.

Current Limitation/Problem

There is no monitoring for cross-chain bridge operations. Failed or delayed bridge messages go undetected until a user reports an issue.

Expected Outcome

A bridge monitoring service that tracks all cross-chain messages from source to destination, alerts on delays/failures, and provides a dashboard for bridge health.

Acceptance Criteria

• Track message lifecycle: initiated, confirmed on source, relayed, executed on destination
• Monitor multiple bridge providers (Wormhole, LayerZero, Axelar, custom)
• Alert when message exceeds expected delivery time (configurable per bridge)
• Detect stuck messages and provide retry/recovery actions
• Dashboard showing bridge message volume, success rate, average latency per bridge
• Historical bridge analytics with failure trend analysis
• Retry failed messages via admin API
• Gas cost tracking per bridge message

Technical Scope

• backend/src/services/bridge-monitor/ - bridge monitoring service
• backend/src/services/bridge-monitor/listeners/ - per-bridge event listeners
• backend/src/services/bridge-monitor/alert-engine.ts - alerting logic
• Prisma: BridgeMessage, BridgeAlert, BridgeRetry models
• Frontend: /dashboard/monitoring/bridges - bridge monitoring UI
• Edge cases: chain reorganization, gas price spikes, bridge downtime, message expiry

[frank0277]

@frank0277 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I would like to work on this

ℹ️ Repo Maintainers: To accept this application, review their application or assign @frank0277 to this issue.

[sammycee769]

@sammycee769 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi, I’d like to take on this feature. I have experience building backend services and monitoring systems, including event-driven architectures and handling cross-chain interactions. I’ll design a modular bridge monitoring service to track message lifecycles across providers, implement alerting for delays and failures, and ensure reliable retry/recovery mechanisms. I’ll also structure the data models and APIs cleanly for analytics and dashboard integration. I’ll make sure the solution is scalable, well-tested, and handles edge cases like reorgs and downtime. I can deliver this within a good timeframe. Looking forward to contributing!

ℹ️ Repo Maintainers: To accept this application, review their application or assign @sammycee769 to this issue.

[Bigmehelen]

@Bigmehelen has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I would like to work on this issue, please assign me to this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Bigmehelen to this issue.

[code-0-stella]

@code-0-stella has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi, I'd like to work on this issue.

I've gone through the requirements, understand the problem, and have the skills needed to implement a solution.

Could you please assign it to me?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @code-0-stella to this issue.

[somotochukwu-dev]

@somotochukwu-dev has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Good day maintainer
Please I would like to work on this issue, please assign this issue to me.
Thanks.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @somotochukwu-dev to this issue.

[devsimze]

@devsimze has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi I'd like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @devsimze to this issue.

[drips-wave]

Congratulations, @devsimze! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @devsimze: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊