"Mined by" pool in Coinbase for Explorers

Development
1

Why do explorers like ours and BTGExplorer not show the Mined By?

I was contacted by someone from solopool.org to get added.

They already found this block:
https://explorer.bitcoingold.org/insight/block/00000000e098c1a58ad7384c58f1fc7c0cd00e2806dc7b567913c9febbf7d6a0

This is the Coinbase TX:
https://explorer.bitcoingold.org/insight/tx/18c5a1fe1751d57612371d394b28eadb990ffec4cc6a72cc54bd1818cbe1626f

And this is the Coinbase, itself:
030a060900736f6c6f706f6f6c2e6f7267

It contains hex 736f6c6f706f6f6c2e6f7267, which hex=>ASCII is:
solopool.org

Is it just a matter of adding them to the pools.json?

Or is there a bug in the reporting code used at our explorers?

Unrelated question: what needs to happen for our explorer to properly display SegWit addresses?

1 Like
2

About SegWit -> We need to implement native segwit address parsing. About half the explorer support it and there is a node package that has support for it. Maybe we can try to implement it in Insight.

More info here about SegWit addresss (aka Bech32 address) - https://github.com/bitcoin/bips/blob/master/bip-0173.mediawiki

2 Likes
3

And the node package - https://github.com/bitcoinjs/bech32

4

Mostly. They can submit a Pull Request to include their pool tag in our explorer. We also need to upgrade the production code to the latest one. This should be done by Sysops.

About Bech32: Actually newer version of the Insight explorer already has good support. However they also changed their api A LOT. It means that a ā€œfull upgradeā€ may break our existing clients. A better way is to run both the old and the new explorers together and tell the people to migrate in a transition period.

BTW I think this thread can be moved to a public category.

1 Like