One contributing reason why the mempool got really congested in the bull run of 2017 is because of the lack of SegWit support from the exchanges and from the bitcoin users in general. While SegWit adoption is a lot higher this year, it's still nowhere close to 100%. So please, just so the same won't happen like in 2017, use a wallet that supports any of these two:
Not to mention that you're going to save a significant amount of satoshis when you transact quite frequently(when using P2SH or Bech32).
Not to mention that you're going to save a significant amount of satoshis when you transact quite frequently(when using P2SH or Bech32).
P2SH transactions won't necessarily save you money on fees. P2SH ≠ Segwit. P2SH is just a type of output comprising a hashed script. Many types of transactions use it, including multi-signature transactions which are much, much larger than standard or native Segwit transactions.
Quote
‘P2SH and ‘non-standard’ transaction categories, which together comprise 87% of atypical transactions, have average byte sizes that are 52% and 80% higher than ‘basic’ transactions, respectively.
Of note, P2SH transactions have accounted for 7% of total transactions thus far 2015, while the overall data size is disproportionately higher at 10% of the total.
Source: https://tradeblock.com/blog/analysis-of-bitcoin-transaction-size-trends
Of note, P2SH transactions have accounted for 7% of total transactions thus far 2015, while the overall data size is disproportionately higher at 10% of the total.
Source: https://tradeblock.com/blog/analysis-of-bitcoin-transaction-size-trends
While Segwit adoption can mitigate some fee pressure (by removing witness data from legacy blocks), we shouldn't overstate its effects on the fee market. It still only represents a small linear increase in overall block size.
