pull down to refresh
0 sats \ 1 reply \ @hynek OP 13 Feb \ parent \ on: Channel Factories fueled by Cashu bitcoin
Trust is used mainly to build the network.
Just use https://vexl.it/
You are paying for data stored. Which is basically inputs, outputs, and headers.
Please have a look on the schema above.
Output B (of original TX) is the same as input B (of CPFP TX). When you remove them you save on fees. Both are redundant.
And you don't need even the second TX header since it will be one transaction now.
Fee rate has to be increased a bit to motivate nodes to broadcast the new transaction. But total fee can be still lower. See the schema where I'm removing B output, B input, and one header. Or the example from app print-screen is real case where I save 16% even with increased fee rate.
The bigger fees the bigger saving...
Thanks,
Payjoin is cool. Here is the difference, that users don't need to actively communicate, but mempool is used as a "marketplace" or communication platform → which is not optimal but sometimes might be handy.
And just like Payjoin this is creating aliby for chain analysis...
Why would the recipient use this? What's the advantage?
Recipients transaction will be boosted because fee rate increases.
the part B would have to be the same amount for both parties
There's no need to use same amounts. Or how do you mean it?
Trezor is transparent with these discoveries:
https://trezor.io/learn/a/past-security-issues
I didn't want to go into technical details yet.. but imagine that the
defense transaction looks similar to commitment transaction in lightning.In our example there will be two outputs:
- 8 BTC for Alice - spendable without restrictions
- 0.5 BTC for Bob
- Alice can spend immediately if she has some secret from Bob (this way can Bob invalidate this transaction)
- Bob can spend after
CSV_delay
Alice can create another transaction where Bob has nothing.. She will loose slightly more, but Bob will be punished.