Legacy Address

Overview

Legacy address is a network-specific term for an earlier destination encoding. In Bitcoin, it commonly refers to Base58Check pay-to-public-key-hash addresses beginning with 1, and sometimes older script formats contrasted with SegWit addresses. Legacy formats can remain valid indefinitely even when newer formats reduce transaction weight, improve error detection, or support upgraded scripts. The word does not identify one universal address type across all blockchains.

Wallets should validate the address against the intended network and supported script, then estimate fees using the actual input and output types. Payment processors should store the original string without truncation and avoid converting formats unless equivalence is cryptographically proven. A legacy address may be usable, but its costs and capabilities can differ from modern alternatives.

Higher-value transfers benefit from an independent destination check rather than reliance on shortened display text. Testing for Legacy Address should include valid and invalid examples, wrong-network values, boundary encodings, contract destinations, and any memo or tag requirements. Legacy Address must be interpreted with its network, address or account type, encoding rules, and any required routing fields. A string that passes a format check can still belong to the wrong chain, unsupported asset, contract type, or destination that requires a memo or tag.

Authorization depends on keys, scripts, contracts, or protocol rules, while custodial systems may expose an identifier without giving the user direct control of the underlying account. Legacy Address is an identifier or spendable object, not proof of legal ownership and not a secret credential. Implementation note: Legacy addresses may remain valid, but network-specific validation, script capability, fee impact, and compatibility should be checked before use.