Skip to content
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

All shielded IBC transfers get rejected #2752

Closed
StoneMac65 opened this issue Feb 28, 2024 · 4 comments
Closed

All shielded IBC transfers get rejected #2752

StoneMac65 opened this issue Feb 28, 2024 · 4 comments

Comments

@StoneMac65
Copy link

I haven't been able to make a successful shielded ibc transfer since two days ago

P.S: shielded-sync been implemented and it was synced

Enter your decryption password: 
converting current asset type to latest asset type...
Enter your decryption password: 
Transaction added to mempool.
Wrapper transaction hash: A8216AC7CBDA233E8FBAC11DDC146F50DFB118947C6BBCC5E996732186460F10
Inner transaction hash: 41161711A0E1AEA22E73FF73E1A647E2395AADD5FC74DE27AE515FAC535B8924
Wrapper transaction accepted at height 84920. Used 130 gas.
Waiting for inner transaction result...
Transaction was rejected by VPs: [
  "tnam1qcqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqvtr7x4"
].
Changed keys: [
  "#tnam1pcqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqzmefah/commitment_tree",
  "#tnam1pcqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqzmefah/nullifiers/0555047CC4D6142DA710C04E7C59314F1A4A58BBADEA6977518A5FF5C181132E",
  "#tnam1pyqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqej6juv/#tnam1qxvg64psvhwumv3mwrrjfcz0h3t3274hwggyzcee/balance/#tnam1pcqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqzmefah",
  "#tnam1pyqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqej6juv/#tnam1qxvg64psvhwumv3mwrrjfcz0h3t3274hwggyzcee/balance/#tnam1qcqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqvtr7x4",
  "#tnam1qcqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqvtr7x4/commitments/ports/transfer/channels/channel-367/sequences/1",
  "#tnam1qcqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqqvtr7x4/nextSequenceSend/ports/transfer/channels/channel-367"
]

@StoneMac65
Copy link
Author

StoneMac65 commented Feb 28, 2024

here is the logs of channels health check. both ends open and fine



2024-02-28T05:13:01.397030Z  INFO ThreadId(01) using default configuration from '/root/.hermes/config.toml'
2024-02-28T05:13:01.411493Z  INFO ThreadId(01) running Hermes v1.7.4+38f41c62-dirty
SUCCESS ChannelEnd {
    state: Open,
    ordering: Unordered,
    remote: Counterparty {
        port_id: PortId(
            "transfer",
        ),
        channel_id: Some(
            ChannelId(
                "channel-3853",
            ),
        ),
    },
    connection_hops: [
        ConnectionId(
            "connection-562",
        ),
    ],
    version: Version(
        "ics20-1",
    ),
}

2024-02-28T05:13:47.895888Z  INFO ThreadId(01) using default configuration from '/root/.hermes/config.toml'
2024-02-28T05:13:47.899788Z  INFO ThreadId(01) running Hermes v1.7.4+38f41c62-dirty
SUCCESS ChannelEnd {
    state: Open,
    ordering: Unordered,
    remote: Counterparty {
        port_id: PortId(
            "transfer",
        ),
        channel_id: Some(
            ChannelId(
                "channel-367",
            ),
        ),
    },
    connection_hops: [
        ConnectionId(
            "connection-3352",
        ),
    ],
    version: Version(
        "ics20-1",
    ),
}

@smartpaopao
Copy link

Hello, can you provide your shielded IBC command to help pinpoint the issue?

@StoneMac65
Copy link
Author

Hello, can you provide your shielded IBC command to help pinpoint the issue?

hello again. I created new channel and that working fine. I have no idea why it happened.
this was the command i used
namadac ibc-transfer --source stone-shielded --receiver cosmos19clk9klm89ycrvhmzldzz4vcm6jryahexk6lza --channel-id channel-367 --token naan --amount 10 --memo "tpknam1qrdt82h05vhq3yd6t969r43ekxnquu50yvgjup72l25t76xwrx5lw9pmee6" --signing-keys stonese --node https://namada.stonemac65.xyz/

@cwgoes
Copy link
Contributor

cwgoes commented May 24, 2024

No action appears to be necessary here.

@cwgoes cwgoes closed this as not planned Won't fix, can't repro, duplicate, stale May 24, 2024
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

No branches or pull requests

3 participants