You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The prefixes for the Bech32 encoded txref's are tx for BTC Mainnet and txtest for BTC Testnet. Should these instead conform to the human readable parts in SLIP-0173 that is referred to in BIP-0173 that defines Bech32?
Changing them to bc for BTC Mainnet and tb for BTC Testnet would bring the code in line with the existing conventions.
The text was updated successfully, but these errors were encountered:
To give a bit more context to this: using tx and txtest was as it seemed to be too restrictive to either mainnet or testnet3.
There are a number of other possibilities that came to mind such as using regtest or signet for testnet which offer a better platform to develop on. Perhaps txtest could be used for all of these but it could make it more confusing to follow tutorials using the same HRP value for multiple chains.
The possibility of utilising this on the liquid sidechain for mainnet also sprang to mind.
The prefixes for the Bech32 encoded txref's are
tx
for BTC Mainnet andtxtest
for BTC Testnet. Should these instead conform to the human readable parts in SLIP-0173 that is referred to in BIP-0173 that defines Bech32?Changing them to
bc
for BTC Mainnet andtb
for BTC Testnet would bring the code in line with the existing conventions.The text was updated successfully, but these errors were encountered: