add: GDPool (Lucky pool)

[deadmanoz]

Summary

This adds GDPool to the mining pool dataset with tags GDPool and Lucky pool, paying to 1DnPPFQPrfyNTiHPXhDFyqNnW9T62GEhB1. Both tags are required: the operator rebranded from Lucky pool to GDPool on the same payout address, and keeping both ensures historical blocks stay attributed.

Closes #101.

Context

GDPool and Lucky pool are the same pool, not two distinct operators. The parallel mempool/mining-pools dataset carried this pool as luckyPool until PR #90 (merged 2025-11-26) renamed the entry to GDPool, keeping the same pool id, the same single payout address, and the Lucky pool regex alongside the new GDPool regex. Block 903840 carries the Lucky pool coinbase text while later blocks carry GDPool, all paying the same address.

Issue #101 also mentions Miningcore as a candidate name. The earliest three blocks from this operator (heights 808964, 810717, 812535, Sept–Oct 2023) do carry a Miningcore coinbase tag, but Miningcore is the default string emitted by the open-source Miningcore pool software rather than a pool name/branc. Adding it as a tag here would mis-attribute any other self-hosted Miningcore BTC pool to GDPool (if there are any, haven't checked); the three blocks in question already pay 1DnPPFQPrfyNTiHPXhDFyqNnW9T62GEhB1 and are therefore attributed via the address match regardless.

Evidence

Coinbase tag evidence for GDPool:

• block 906701: scriptSig ends with 064744506f6f6c (GDPool), pays to 1DnPPFQPrfyNTiHPXhDFyqNnW9T62GEhB1
• block 908662: scriptSig ends with 064744506f6f6c (GDPool), pays to 1DnPPFQPrfyNTiHPXhDFyqNnW9T62GEhB1

Coinbase tag evidence for Lucky pool:

• block 903840: scriptSig ends with 0a4c75636b7920706f6f6c (Lucky pool), pays to 1DnPPFQPrfyNTiHPXhDFyqNnW9T62GEhB1

Testing

• python3 qa/check-data.py
• python3 contrib/generate-old-pools-json.py

[0xB10C]

Looks good! I also had a look at https://mempool.space/mining/pool/gdpool

The switch is clearly visible there: