Address formats differ enough that a single validation regex is always wrong. Bitcoin bech32 starts bc1q and uses a restricted alphabet; Ethereum is 0x plus forty hex characters with meaningful capitalisation; Solana is base58 with no prefix at all.
What you can control
- Three Bitcoin address types — bech32, legacy P2PKH and P2SH — because wallets still emit all three.
- Ethereum addresses can carry mixed-case EIP-55 styling, which some validators check and some ignore.
- Optional balances use the right decimal precision per chain: eight places for Bitcoin, six for the rest.
- Transaction hashes match each chain's format, hex for Ethereum and base58 for Solana.
What this is not
These addresses have the correct shape but no private key exists for them and their internal checksums are not computed. Never send funds to a generated address — they would be permanently unrecoverable.
Questions
Are these real wallets?
No. They match the character set and length of each format, but no key pair generated them. There is no way to access anything sent to one.
Do they pass address validation?
Format and length checks, yes. Full checksum validation — bech32's BCH code, base58check's hash — will reject them, because those checksums are not computed here.
What is EIP-55 casing?
A checksum encoded in the capitalisation of an Ethereum address's hex letters. It catches typos without changing the address, and older tools ignore it entirely.