Repository navigation
Aleo Testnet → Sepolia ALEO transfer pending: validator checkpoint stops at 14 #10051
kenandkent
started this conversation in
General
Replies: 1 comment
|
Don't bother Hyperlane validators are run by some rando with zero due diligence There is a project that purposely
Hyperlane openly allows this kind of scam to run as long as they get the bridge fee If you end up on this discussion board, you already know their support ticket system is fake and they actually don't response. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi Hyperlane maintainers,
Could you check why the Aleo Testnet validator’s published checkpoint is still at index 14? If this testnet route is still supported, can the operator publish a valid checkpoint covering leaf index 15 so the existing message can be delivered to Sepolia?
AwaitingValidatorSignatures(0 of 1 signatures). The configured validator is0x7233d80194c69af6b84b0786a7fd2a7294396ca8, and its public latest checkpoint still returns 14 with Last-Modified on July 10, 2026. The index 15 checkpoint object returns HTTP 404.delivered(messageId)is false.Please let me know whether a checkpoint covering leaf 15 can be published or whether there is a supported recovery path for this same message. Thanks for taking a look.
All reactions