Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Addresses begin with bc1 while running with bitcoin testnet4 #1154

Open
ertenmehmet opened this issue Nov 7, 2024 · 2 comments
Open

Addresses begin with bc1 while running with bitcoin testnet4 #1154

ertenmehmet opened this issue Nov 7, 2024 · 2 comments

Comments

@ertenmehmet
Copy link

ertenmehmet commented Nov 7, 2024

Running couple of different instances of blockbook while managing our migration to testnet4,
We have noticed that in the explorer interface it shows addresses as begin with bc1 style e.g bc1qgrcex95y6mdankp5t5uz6wlwve6333pjdt4v4m; instead of tb1qhjxlhw07m9tcm07tjzufjxt47m26qqq2gmsdtg

But when it comes to resolving them it is ok, when requested testnet4-blockbook-url/api/v2/address/tb1qhjxlhw07m9tcm07tjzufjxt47m26qqq2gmsdtg it responds successfully, but with
"address": "bc1qhjxlhw07m9tcm07tjzufjxt47m26qqq2zat7sm"

also noticed in the logs:
1 bitcoinrpc.go:146] rpc: block chain mainnet

Environment is as follows:
newly built from fe676b35
and running with the following config

{
    "network": "test",
    "coin_name": "Testnet4",
    "coin_shortcut": "TEST",
    "coin_label": "Bitcoin Testnet4",
    "coin_alias": "bitcoin_testnet4",
    "rpc_url": "http://bitcoind:18030",
    "rpc_user": "rpc",
    "rpc_pass": "rpc",
    "rpc_timeout": 25,
    "parse": true,
    "message_queue_binding": "tcp://bitcoind:48332",
    "subversion": "",
    "address_format": "",
    "xpub_magic": 70617039,
    "xpub_magic_segwit_p2sh": 71979618,
    "xpub_magic_segwit_native": 73342198,
    "slip44": 1,
    "mempool_workers": 1,
    "mempool_sub_workers": 1,
    "block_addresses_to_keep": 300
}

and running with the following parameters
blockbook -blockchaincfg=/opt/etc/blockchaincfg.json -datadir=/opt/data -workers=1 -sync -internal=:19030 -public=:19130 -explorer= -logtostderr

We also have our own bitcoin node, running with the 28.0.0 official release from https://bitcoincore.org

Not sure if we miss something with the configuration or something we miss while building blockbook; or an actual issue.

@wakiyamap
Copy link
Contributor

#1130 (comment)
Maybe this will fix it.

@ertenmehmet
Copy link
Author

so @wakiyamap, would it be running as expected (by showing actual wallet addresses with tb1) if we build and run from your fork?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants