9

Segwit addresses like the one you posted are case insensitive. Assuming your wallet is up to the spec, it should be able to send the BTC just fine. If you have a transaction ID, look it up on an explorer to see if it has been confirmed. If you don't have a transaction ID, and you have the private keys for the wallet, you should simply be able to make another ...


3

Yes. The format used for encoding native version 0 SegWit scriptPubKeys (P2WPKH and P2WSH) is bech32, defined by bip-0173. Unfortunately, at the time of writing, a weakness has been discovered regarding the usage of this encoding for the proposed version 1 SegWit scriptPubKeys (Taproot). There are ongoing discussions for how to modify this encoding for ...


3

The Bitcoin URI scheme is defined in BIP21: Bitcoin URIs follow the general format for URIs as set forth in RFC 3986. The path component consists of a bitcoin address, and the query component provides additional payment options. You can read through the entire RFC document or the summary on Wikipedia which answers your question: An optional authority ...


2

There are multiple aspects to the design of bech32. There is the choice of character set (i.e. which characters are included in the 32 options and which characters are excluded because they visually look like other characters e.g. 1 because it looks like l), the mapping of specific bits to this character set, the type of checksum to use and the final address ...


2

Your bitcoin client is generating a P2WPKH (bech32 encoded) address, which is a newer address format which has some benefits compared to legacy formats. The address is valid, but for whatever reason, the exchange mentioned has not upgraded it's code to recognize and send to this address type yet. The fix is easy: you just need to tell bitcoin-core to ...


Only top voted, non community-wiki answers of a minimum length are eligible