Why does bitaddress.org use uncompressed pubkeys for paper wallets?

Why does bitaddress.org use uncompressed pubkeys for paper wallets? Is there a reason or is it just an oversight? At this point all services should be encouraging the use of compressed pubkeys and support for uncompressed pubkeys should just be for backwards compatibility.

Can anyone think of a reason other than just it being an oversight for generating new paper wallets with uncompressed pubkeys?

As an example, Bitaddress > PaperWallet > Generate

Quote

Private Key:
5JgfcLRNEASqdrLKktL8Ygcftj9S7DTvSFYnMUtdd5Bmn8G9oYz

Address:
1Lux7wJ4cyoVqG3N3oWuitYmGpxZaK8nM3

Using the private key 5jgf... produces the following PubKeys (compressed & Uncompressed):
0x024649935EA7EB7A0B39021F07B41F20E12324CF2329569117157536C2A416FDA7
0x044649935EA7EB7A0B39021F07B41F20E12324CF2329569117157536C2A416FDA7971262798AFAB30BC060C03540E5E7451170256C4DC77C4C0CF7F3A1FAD75FF6

Addresses:
1F2NCcW4LCe7FebbqL89NpZKZ6gPNEDWzT (from the compressed PubKey)
1Lux7wJ4cyoVqG3N3oWuitYmGpxZaK8nM3 (from the uncompressed PubKey)

Note that the bitaddress paper wallet option outputs the 1Lux address. Why waste blockchain space?

Topic: Why does bitaddress.org use uncompressed pubkeys for paper wallets? (Read 650 times)