heliaxdev/hermes

IBC Relayer in Rust

hermes's Issues

RUSTSEC-2021-0127: serde_cbor is unmaintained

serde_cbor is unmaintained

Details
Status	unmaintained
Package	serde_cbor
Version	0.11.2
URL	https://github.com/pyfisch/cbor
Date	2021-08-15

The serde_cbor crate is unmaintained. The author has archived the github repository.

Alternatives proposed by the author:

• ciborium
• minicbor

See advisory page for additional details.

Transfers to `znam` addresses via ibc drain the balance of the relayer.

Hello, I apologize for going out of template.

bug

If I do an ibc transfer to znam addresses with XCS contracts deployed on Osmosis, hermes gets stuck, constantly trying to send tx to namada and draining the balance of the relayer address.

my question

Is there a command like drop-packets to fix this temporarily? Otherwise I will have to redeploy all contracts and set up a relayer to prepare a new testbed.

Move back to mainstream tendermint-rs

After moving Namada tendermint-rs back to the mainstream, we can remove the redundant tendermint handling for our forked tendermint-rs

Namada chain didn't receive the ack with Hermes relaying

Summary of Bug

When a Namada chain sent a token to another Namada chain, (if the other chain didn't send, i.e. SendPacket event didn't happen,) the source chain didn't receive the ack though Hermes caught the WriteAcknowledgement event from the destination chain.

• When I executed the CLI tx packet-ack manually, the source chain received the ack as expected
• When both chains sent each token, both chains received each ack

Version

v1.7.1-namada-beta4

Steps to Reproduce

Acceptance Criteria

---

For Admin Use

• Not duplicate issue
• Appropriate labels applied
• Appropriate milestone (priority) applied
• Appropriate contributors tagged
• Contributor assigned/self-assigned

IBC client gets suddenly frozen despite of being constantly updated

I have already reported a similar (or perhaps related) behavior internally one month ago or so. It looks like something is broken with IBC clients statuses on Namada's side. Frozen height isn't even emitted correctly, so I assume that it's somehow related to the IBC client that suddenly starts not being properly updated at some point. I have no clue what may cause this, though.

hermes query client status --chain shielded-expedition.88f17d1d14 --client 07-tendermint-3546
SUCCESS Frozen

hermes query client state --chain shielded-expedition.88f17d1d14 --client 07-tendermint-3546
SUCCESS Tendermint(
    ClientState {
        chain_id: ChainId {
            id: "theta-testnet-001",
            version: 0,
        },
        trust_threshold: TrustThreshold(
            Ratio {
                numer: 2,
                denom: 3,
            },
        ),
        trusting_period: 115200s,
        unbonding_period: 172800s,
        max_clock_drift: 50s,
        latest_height: Height {
            revision: 0,
            height: 21020900,
        },
        proof_specs: ProofSpecs(
            [
                ProofSpec {
                    leaf_spec: Some(
                        LeafOp {
                            hash: Sha256,
                            prehash_key: NoHash,
                            prehash_value: Sha256,
                            length: VarProto,
                            prefix: [
                                0,
                            ],
                        },
                    ),
                    inner_spec: Some(
                        InnerSpec {
                            child_order: [
                                0,
                                1,
                            ],
                            child_size: 33,
                            min_prefix_length: 4,
                            max_prefix_length: 12,
                            empty_child: [],
                            hash: Sha256,
                        },
                    ),
                    max_depth: 0,
                    min_depth: 0,
                    prehash_key_before_comparison: false,
                },
                ProofSpec {
                    leaf_spec: Some(
                        LeafOp {
                            hash: Sha256,
                            prehash_key: NoHash,
                            prehash_value: Sha256,
                            length: VarProto,
                            prefix: [
                                0,
                            ],
                        },
                    ),
                    inner_spec: Some(
                        InnerSpec {
                            child_order: [
                                0,
                                1,
                            ],
                            child_size: 32,
                            min_prefix_length: 1,
                            max_prefix_length: 1,
                            empty_child: [],
                            hash: Sha256,
                        },
                    ),
                    max_depth: 0,
                    min_depth: 0,
                    prehash_key_before_comparison: false,
                },
            ],
        ),
        upgrade_path: [
            "upgrade",
            "upgradedIBCState",
        ],
        allow_update: AllowUpdate {
            after_expiry: true,
            after_misbehaviour: true,
        },
        frozen_height: Some(
            Height {
                revision: 0,
                height: 1,
            },
        ),
    },
)

Opening this issue on both Hermes Heliax fork and Namada repositories since I'm not fully sure which of them fits better to report this bug.

Add Namada key without Namada wallet file

Like adding cosmos key

tpknam in memo

SE: how i can include my public key (tpknam) as the –memo for all transactions in hermes memo_prefix = '' ?
Specify a string that Hermes will use as a memo for each transaction it submits to this chain.
The string is limited to 50 characters.
but tpknam is 66 characters.