Skip to content

"sprt" regtest HRP isn't in BIP 352 #55

Open

Description

@notTanveer

just raising this in case it's useful. i noticed while working on a BIP 352 PR that drongo uses "sprt" as the silent payments HRP for regtest:

REGTEST("regtest", "Regtest", "regtest", 111, "mn", 196, "2", "bcrt", "sprt", "tspscan", "tspspend", ExtendedKey.Header.tprv, ExtendedKey.Header.tpub, 239, 18443),

the BIP only defines "sp" for mainnet and "tsp" for testnets, and doesn't mention a separate regtest HRP. more context in the PR discussion: bitcoin/bips#2312

not sure if this was intentional, but other implementations that follow the BIP would likely use "tsp" on regtest, so addresses might not work between them.

Activity

  1. craigraw commented on Sep 29, 2026

    @craigraw
    Collaborator

    Thanks for raising this. If, as @josibake says, "regtest is a bitcoin core implementation specific concept" then it seems other implementations should follow Bitcoin Core's implementation if they want to offer regtest support? If they don't, then they will be incompatible with the one implementation that could be considered the reference implementation for this network.

    Personally I have never used regtest without Bitcoin Core, so changing this to tsp seems entirely at odds with practical reality.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    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