Can you break down what data is encoded into a bech32 address? Can you break down what data is encoded into a bech32 address?
e.g. bc1qw508d6qejxtdg4y5r3zarvary0c5xw7kv8f3t4
How do bech32 addresses on testnet, regtest, signet compare?
bech32 addresses are defined in BIP 173. A list of address prefixes on the Bitcoin wiki is here.
This slide is taken from Pieter Wuille's presentation on bech32 at SF Bitcoin Devs in March 2017.


bc is representing Bitcoin (mainnet) and is human readable.

Testnet bech32 addresses start tb

Signet (both default Signet and custom Signets) bech32 addresses also start tb (although an earlier iteration of Signet used sb).

Regtest bech32 addresses start with bcrt. This is defined in chainparams.cpp here.

1 is just a separator and doesn't represent any particular data

q is the witness version. This represents zero as the first SegWit witness version introduced was SegWit v0. Taproot introduces SegWit v1.

w508d6qejxtdg4y5r3zarvary0c5xw7k is the hash of the witness program.

v8f3t4 is the checksum


As the slide says, mainnet P2WPKH addresses are 42 characters and mainnet P2WSH addressses are 62 characters under SegWit v0. Future witness versions can be up to 74 characters although SegWit v1 addresses (Taproot) will be the same length as v0 P2WSH addresses (62 characters). Witness programs as defined under SegWit v1 are 32 bytes.
There is a bech32 demo decoder site here.