Best way to receive multiple payments to minimize sending fees later?

[Don911]

What is the preferable way to receive multiple bitcoin payments in order to minimize fees when eventually sending the bitcoin to someone else?

Scenario 1:
I received 10 different payments of 0.01 BTC to the same bitcoin address.

Scenario 2:
I received 10 different payments of 0.01 BTC to 10 different bitcoin addresses.

Now I have 0.1 BTC in my wallet that I want to send to someone. Which of the above scenarios will result in lower fees when sending that 0.1 BTC to someone else?

Any additional clarification of this issue would be greatly appreciated.

[1714563810]

1714563810

[1714563810]

1714563810

[1714563810]

1714563810

[codewench]

Scenario 1:
I received 10 different payments of 0.01 BTC to the same bitcoin address.

Scenario 2:
I received 10 different payments of 0.01 BTC to 10 different bitcoin addresses.

Now I have 0.1 BTC in my wallet that I want to send to someone. Which of the above scenarios will result in lower fees when sending that 0.1 BTC to someone else?

Both scenarios have the same fee. Either way you are spending 10 payments.

If you wish to reduce fees, look into using SegWit addresses to receive your funds. It is cheaper to spend out of SeqWit addresses.

[Kakmakr]

There are several ways of doing this, but it depends on the situation.

My local exchange charge zero fees for transactions that are done within their service, if both sender and receiver are registered on their exchange. <Reason : This transaction is not done on the Blockchain, but rather on their internal ledger/data base>

The other option, if your local exchange does not allow for that, is to register both parties in this transaction with a service that allow off-chain transactions, like Xapo.

The catch is, once you send those bitcoins to someone outside of their service, you have to go on-chain with 1 transaction and then you have to pay miners fees. <Still a lot less if you did multiple transactions on-chain>

Last option - Wait for the Lightning Network to mature <It does the same thing, but you are not using centralized services>