-
Notifications
You must be signed in to change notification settings - Fork 316
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ibc: relayer can't find nodekey during packet proof query #2834
Comments
Can we run the relayer with Debug so we can see the output of this debug statement? (in PenumbraProvider.QueryTendermintProof)
|
I think this error is returned by pd when we request a state key that doesn't exist |
this error is emitted by our jmt's TreeReader: we're querying for a packet commitment that doesn't exist (this is possibly due to a channel id getting swapped, using the wrong channel id in the relayer due to an issue in our query or events api- note that the channels are different in your test, channel-0 vs channel-2) |
I found one issue: our state path for packet receipts is wrong:
it should instead be
|
I think #2837 should fix this |
Testing this today, will report back with results. |
Unfortunately I'm still seeing the error, testing on the latest main, which includes #2837:
so a bit more investigation is required. |
This issue is resolved. In fact, it's so resolved that we have working IBC transfer between two Penumbra test chains:
which is huge, and deserves its own writeup. I'm closing this issue as complete, but also cross-referencing related PRs that patched blocking bugs:
|
Describe the bug
The relayer currently fails to process withdrawals between Penumbra chains with the following error:
To Reproduce
Steps to reproduce the behavior:
rly start
pcli -n http://localhost:8080 tx withdraw penumbrav2t1kneqjxx8gt2twc885gfn7n2tk68m730432hxlzn47hrzmz29a4thccz4yqfkfvjvmjkwxpy47clqhf45d8zq9j9efxj94c2jyhgzm59slf8akpgww06xzeka6w2k09fqaqkgqn@penumbra-testnet-ganymede-be7bab59 upenumbra 1 channel-0
Note that you'll need to update the chain id in that address to be the actual chain id of testnet-preview. To find it:
curl -s https://rpc.testnet-preview.penumbra.zone/status | jq -r .result.node_info.network
.Additional context
I made sure to update the to the latest penumbra protos in my local relayer build, and that did not resolve the problem. Let's dig around and figure out why the relayer is not happy looking up the packet proof.
The text was updated successfully, but these errors were encountered: