Closed landergate closed 4 years ago
There is a ambiguity when encoding P2PK output into an address - since given a public key, we can create two different scripts that can be authorized by its corresponding private key:
Those scripts are are different - so their "scripthash" (used by Electrum for querying and Electrs for indexing) are different as well.
Some explorers are encoding P2PK output scripts using a "related" P2PKH by hashing the corresponding public key (e.g. Blockchain.info) - but not all of them (e.g. Esplora).
Personally, I am not sure what is the optimal solution here though :)
Looks like some old P2PK transactions are not accounted with corresponding addresses:
It shows 0 transactions/received/spent while other engines display some activity on that address.
77 could be related?