Skip to content

[TESTNET BUG] reward_slot_holders endpoint isn't always showing the correct address #2295

@BowTiedDevOps

Description

@BowTiedDevOps

Describe the bug

Since the Bitcoin chain behind Testnet is regtest, some of the addresses on the reward_slot_holders page are not in the correct format (i.e. they are testnet addresses instead of regtest ones, even if the node processes them as regtest addresses).

Steps To Reproduce

For example, at block 54053, the 2 rewarded addresses according to the bitcoin chain were:

  • mgZ5KJFnXmSvdrPNR7eQGz2RUKeqBanpAM
  • bcrt1qxnzlc57krja4jzq6vq3fylll0rydxr2xst4erg

However, the reward_slot_holders endpoint shows one of the addresses as a testnet one (tb1qxnzlc57krja4jzq6vq3fylll0rydxr2xjzv55p):

Image

Going to the individual reward_slot_holders for each address:

This example is relevant because tb1qxnzlc57krja4jzq6vq3fylll0rydxr2xjzv55p and bcrt1qxnzlc57krja4jzq6vq3fylll0rydxr2xst4erg contain the same version and hashbytes, but the first is on testnet while the last one is on regtest.

Expected behavior

The reward slot holders endpoint should show the slots received by tb1qxnzlc57krja4jzq6vq3fylll0rydxr2xjzv55p under the bcrt1qxnzlc57krja4jzq6vq3fylll0rydxr2xst4erg address instead.

Environment

Hosted API (https://api.testnet.hiro.so) and hosted bitcoin explorer (https://mempool.bitcoin.regtest.hiro.so)


Minor, Non-launch blocking bugs

Minor bugs

  • Bugs in non-critical software (CLI, UI, etc) that doesn’t impact critical functionality

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't workingtestnet

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions