Skip to content

rpc-client: submit_chain_lock sends block hash in reversed byte order #1128

Closed

Description

@ZocoLini

submit_chain_lock (rpc-client/src/client.rs:1628) sends hex::encode(block_hash), which is internal byte order. dashd parses it with ParseHashV, which expects display order, so it rejects the ChainLock with invalid signature.

Fix: send block_hash.to_string().

Activity

  1. self-assigned this
    on Oct 7, 2026
  2. added a commit that references this issue on Oct 11, 2026
    f4abb26
  3. added a commit that references this issue on Oct 19, 2026
    f22f7d6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions