SegWit addresses don't safe on fees when receiving transactions, the savings happen when you make a payment from a SegWit address.
When sending to a P2PKH the pk_script is:
Code:
OP_DUP OP_HASH160 Size PubKey_hash OP_EQUALVERIFY OP_CHECKSIG
bytes: 1 + 1 + 1 + 20 + 1 + 1 = 25When sending to a Bech32 address the pk_script is:
Code:
OP_0 Size PubKey_hash
bytes: 1 +1 + 20 = 22paying ~58 people with Bech32 means 174 bytes smaller
Loyce is referring to the legacy address that pays us from DarkStar_. That's why the fee won't fall due directly to it being bech32.
Also @DarkStar_ do you know if you can convert your address with the 1Chip in it to a bech address or a non-native segwit address and then it won't have too many issues if people pay to exchanges (as most exchanges don't support native segwit).
pooya87 pointed out that the output script of a bech32 is slightly smaller than legacy, which saves a few bytes, per output. So yes, I do save a few satoshi on fees by sending to bech32, but nothing really noticeable. I have talked to ChipMixer about switching to a segwit address, but they didn't say anything about it.