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

pools.json - How does it works? #502

Open
globaltoken opened this issue Mar 26, 2017 · 1 comment
Open

pools.json - How does it works? #502

globaltoken opened this issue Mar 26, 2017 · 1 comment

Comments

@globaltoken
Copy link

Hey,

How does Pools.json works, how can the Blockexplorer can find which Address is from Which Pool - I mean how is it possible to match them ?

So how can I modify these pools.json, that it shows in Frontend the Mined By Tag?

Thanks.

@losh11
Copy link

losh11 commented Apr 7, 2017

Unfortunately Insight doesn't look at Coinbase output address to match a miner/pool. This would've been the best solution.

Currently, miners voluntarily insert some unique text into the coinbase identifier of the block they've mined. In lib/blocks.js it cycles through the coinbase identifier and tries to find keywords from pools.json. So a keyword for F2Pool/Discus Fish might be 'Mined by'. Probably not the most unique identifier. Lots of pools don't even bother to do this, some even keep the default identifier for their pool software.

In the future, someone should add the feature to look at coinbase output address and compare it to a list of known pools addresses.

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