Is not demanding low-R grinding still relevant for external signers? #33761

issue cobratbq openend this issue on November 1, 2025
  1. cobratbq commented at 7:18 pm on November 1, 2025: none

    Is there an existing issue for this?

    • I have searched the existing issues

    Current behaviour

    It seems that largest transaction coming from (my) external signer is not accepted in mempool. From what I understand, low-R grinding is not expected from external signers. That’s what I understand https://github.com/bitcoin/bitcoin/issues/26030.

    Is this still true? (it is desirable) This is the result for me in ‘regtest’ environment on Bitcoin Core v29.2.

    Expected behaviour

    Any transaction properly signed by external signer (because potentially low-capacity embedded device) is accepted.

    Steps to reproduce

    Connect “external signer” via External Signer interface (command-line tool, directly, not through HWI)

    Sign transaction until transaction with largest size is encountered.

    Relevant log output

    Three transactions. Largest is not accepted for me on ‘regtest’, and to my knowledge signature is good.

    0020000000122d24e014ba0566c52dcedc316116fc6c0506d8d4506a59df48c086dafa944be010000006a47304402203d2e4ad14e4ffde063fab547d074d842060054827dd2db26b6b77ac40faa6aec022014de31cfda5fbe61a789112e106cc07a13a6187682908b22ec28f5b41256dd80012103158a5f4fd7588aa696a13d49889895b4b077aae721b52f9b72cda919ff926dfffeffffff02d2d4e405000000001600143e445eb2b84a73fec1851628a8f20998880af04d00c39dd0000000001976a914d2d44c8765409c6cecb3eb0861f7beb78f232c9e88ac00000000
    
    00200000001b0a283e1c1634f1eb748cb1a7ca0c6bda1d385037a6a626cdf3aa0b865a1be9e000000006b483045022100d412738cb2a54c530f62ba4f2458660dfab5239297df074bf5bb829f369c4c70022077f6cd209178e9aff43269c42c8df34c710096aa88c8a77d8f860db218603e050121031d633694c1ba15687ff4c1eb9ecb5ec730d44131008fa250d49e5f80dc516379feffffff0288dde405000000001600143e445eb2b84a73fec1851628a8f20998880af04d00a493d6000000001976a91418a4d1bec02c5489bebdd6fbb304e8e1b173733588ac00000000
    
    0020000000122d24e014ba0566c52dcedc316116fc6c0506d8d4506a59df48c086dafa944be010000006c493046022100d21e82e9f292654f52bb3623f803b07e74c3b91f55aad40b6d0f5d767f2b66c9022100826102337dd415d4f9adcb4874da63f7981ffcaff18f0c2a94715d9ea3596c0d012103158a5f4fd7588aa696a13d49889895b4b077aae721b52f9b72cda919ff926dfffeffffff0288dde405000000001600143e445eb2b84a73fec1851628a8f20998880af04d00c39dd0000000001976a914d2d44c8765409c6cecb3eb0861f7beb78f232c9e88ac00000000
    

    How did you obtain Bitcoin Core

    Package manager

    What version of Bitcoin Core are you using?

    v29.2.0

    Operating system and version

    Fedora

    Machine specifications

    No response


cobratbq


github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2025-11-02 18:12 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me