Could it be a workaround to use the integrated block explorer for that?
Unfortunately not. Block browsers have difficulty with addresses - they require a horizontal slice through what is essentially vertically-indexed data (blocks) and so an additional address index must be created and maintained. The more sophisticated explorer that Mr Spread created for Spreadcoin (also
sported by PIVX) has all the details:
https://github.com/spreadcoin-project/spreadcoin/commit/f36d3d2b5dbb88b1b5c8bebc57d55153b3f35cee#diff-a8f23ed02dbd9dbe8eb37b2097341d55R346And I finally tracked down the details of the wrinkle introduced by Mr Spread that (I think) explains why the Spreadcoin vanity address generator uses uncompressed addresses:
SpreadCoin uses a more compact representation for signatures in transactions.
SpreadCoin as well as Bitcoin uses ECDSA signatures. While bitcoin keeps a copy of the public key of the corresponding signature around, SpreadCoin ommits this by recovering the public key on the fly directly from the signature.
This way it is not necessary to keep the public key of every ECDSA signature in the blockchain, so this leads to *smaller transactions and hence a smaller blockchain (at the cost of a few CPU cycles more).
(*reduction in size of transaction from 139 or 107 bytes in Bitcoin to 67 bytes in SpreadCoin.)
I don't know whether this factoid will unblock the issue but at least I now know what I'm looking for.
Cheers
Graham