I figured out that conflicted transactions are erased from the list
How much many time is needed or in which conditions they are erased?
listransactions : documentation missing : erasure of txs with negative confs #21924
issue mrbianchi opened this issue on May 11, 2021-
mrbianchi commented at 10:47 PM on May 11, 2021: none
- mrbianchi added the label Feature on May 11, 2021
- mrbianchi renamed this:
listransactions : documentation missing?
listransactions : documentation missing about conflicted txs
on May 11, 2021 - mrbianchi renamed this:
listransactions : documentation missing about conflicted txs
listransactions : documentation missing : erasure of txs with negative confs
on May 11, 2021 -
ghost commented at 1:22 AM on May 12, 2021: none
I figured out that conflicted transactions are erased from the list
How can I reproduce this issue?
What arguments did you use with
listtransactionsand the values for them?Which version of Bitcoin Core are you using?
- fanquake deleted a comment on May 12, 2021
-
mrbianchi commented at 7:36 AM on May 13, 2021: none
I figured out that conflicted transactions are erased from the list
How can I reproduce this issue?
What arguments did you use with
listtransactionsand the values for them?Which version of Bitcoin Core are you using?
receive transactions , use replace by fee , the new tx should be confirmed , wait (i dont know how much confirmations or time, the replaced tx will dissapear) "*" 1000 0 true
- mrbianchi closed this on May 14, 2021
-
mrbianchi commented at 1:42 AM on May 14, 2021: none
I got confused, I'm sorry
- DrahtBot locked this on Aug 18, 2022
