Archive RPC needed: 12 stuck IBC orphan send_packet events at h<41M (osmosis-1 channel-232 → AssetMantle channel-0) #9682
Unanswered
deepanshutr
asked this question in
Q&A
Replies: 0 comments
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.
Need: archive tx-index for h<41M to recover 12 stuck IBC orphan packets
We've recovered 335/347 orphan packets on the AssetMantle ↔ Osmosis IBC channel (channel-0/channel-232). The last 12 are stuck because their original
send_packetevents live below every probed public Osmosis RPC's tx-index horizon.Probed endpoints' earliest tx-index
(Note: freshstaking advertises
earliest_block_height=0in /status, butblock_results?height=37000000returns "lowest height is 41066117". State-archive vs tx-index pruning differ.)What we need
For each of these osmosis-1 channel-232 sequences, the
send_packetevent JSON:51441, 52117, 52118, 52119, 52120, 52121, 52122, 52123, 52124, 52125, 52126, 52127Either:
tx_searchthe above seqs and paste the result, orExample query:
Tooling
Once we have the events, the mock-RPC + hermes timeout pipeline at https://github.com/deepanshutr/mantle-osmo-hermes-relayer/tree/main/scripts/orphan-recovery refunds the original osmo senders in a single batch tx (no funds need to move from the recovery operator). Documented full reproduction including the breakthrough that IBC packet commitments persist on src until ack/timeout, so proofs come from current state rather than archive state.
Tracking issue: deepanshutr/mantle-osmo-hermes-relayer#1
Thanks!
All reactions