It's been over six years and I've done entirely too little research to state the below with confidence, but what I can roughly piece together quickly between cursory research and from what I remember:
There was a big debate about the merits of RBF since at least 2013, when Peter Todd and John Dillon provided a Full RBF patch. Gavin Andresen described it as ...
The answer to this question is: no, inherited signaling is not currently implemented in Bitcoin Core as described in BIP 125.
In May 2021, Antoine Riard discovered the missing implementation could be exploited in the context of the Lightning Network "pinning attacks against second-stage HTLCs" as well as other contexts:
Such a transaction is standard and would relay. However neither the Bitcoin Core wallet (via the bumpfee command) nor the Electrum wallet (via the GUI) would create such transaction.
More information about fee bumping in the Bitcoin Core wallet can be found here.
As far as I'm aware, there are currently no formal proposals to introduce Full RBF. Therefore, I'm expecting that the default behavior of upcoming nodes will remain to forward and create transactions according to the rules specified in BIP125, Opt-in RBF.
I can not see any transaction resting in Mempool having different values for Fee and Modified Fee fields?
That's probably because you haven't modified any.
The prioritisetransaction RPC exists for miners to signal that particular transactions are paid for out of band, or are the miner's own transactions that should prioritized for block construction over ...
Ledger Wallet doesn't support RBF but you can do Child Pays For Parent:
Make a transaction to your address 3M6EhQL3QUQHAFkSPH3vLc3VDCrJKP3iMv with amount 0.011, set a fee rate, preview the transaction and check and confirm the transaction only if one of the inputs is 0.01187067 BTC.
If this doesn't work, download Electrum and CPFP from there.
But honestly, ...
What are we trying to predict in fee estimation and why?
Different Bitcoin projects try to predict fee rates for improving UX because its not easier for every user to understand all the technical things involved, look at different charts and decide a fee rate for the transaction.
Are different estimations misleading and affect the way fees are used in ...
There are 2 workarounds possible:
It takes few minutes for most of the transactions to be included in a block. So, you can prepare all the steps in advance and perform within couple of minutes before this transaction is confirmed.
Broadcast transactions with fee rate below 1 sat/vByte
Change Min Transaction Relay Fee in bitcoin.conf with minrelaytxfee=0....
Yes, the rules of RBF explicitly allow changing the outputs of RBF transactions. But Roger Ver's concerns are blown out of proportion.
Bitcoin has been fundamentally broken on
purpose by introducing the "replace-by-fee" feature, which, according
to him, allows you to "reverse" (take back) Bitcoin transactions for
minutes, hours and "...
Basically, he is saying that Bitcoin has been fundamentally broken on purpose by introducing the "replace-by-fee" feature, which, according to him, allows you to "reverse" (take back) Bitcoin transactions for minutes, hours and "sometimes even weeks" after it was sent.
Not true. Bitcoin transactions with ZERO confirmations were ...
I would like to prove that a certain transaction was in the mempool on a certain date before it got replaced via RBF with another transaction.
Consider Tx de8ba282831c6d645aa777a35a5b9f2107cbd96913a9cd4c5880420db092e399 as an example.
gettransactionin Bitcoin Core returns:
The fees for the htlc are covered by whoever claims the output
The fees for the commitment tx are always covered by the party who opened the channel.
Sorry to say that but I believe there are many things wrongly stated in your question:
The fee for the commitment transaction is not necessarily paid by Alice even if she force closes the ...