Closed JeanlChristophe closed 7 months ago
Same issue when I am trying to open channel (no-Cjit)
https://github.com/synonymdev/bitkit/assets/46056211/cddf0c84-9588-4cbd-9f3d-715890c1c888
Not everyone has the same mempool. Each mempool also purges transactions below a certain fee threshold. The Electrum server and corresponding Bitcoin Core node we use has a lower fee threshold than most so that we do not refuse to broadcast and/or purge low fee transactions during times of high fee volatility. This is why you are unable to see your broadcasted transaction in other services mempool until the fee threshold drops.
However, we are not in a period of high fee volatility, plus:
Two UI improvements/features we might want to consider to help improve this:
hey. We tried to CPFP a transaction today and it doesn't work:
We first did a transaction with lo sat/vb. then we tried to boost it. Current fees are 15sat/vb and I setup a tx of 30/vb. now I am trying to find this tx f6b35a5bc2eecdd68ea532a15af7bde9ec38014bb77e58dd377a4dd5b45126b1 on the mempool but it doesn't appear.
https://mempool.space/tx/f6b35a5bc2eecdd68ea532a15af7bde9ec38014bb77e58dd377a4dd5b45126b1
We tried another transaction:
From todays testing session it took several minutes for some transactions to eventually appear in some block explorer's mempool (blockstream & mempool specifically) even though the fees were set appropriately and were above the purge threshold.
@rbndg, would it be possible to more directly add mempool and blockstream nodes as peers with our Bitcoin Core node that Electrum is connected to? If so, this may help propagate our unconfirmed transactions and ensure they show up in their mempool/block-explorers faster and more reliably.
On my side, 2 days after the issue, the tx is still not found by the mempool @coreyphillips
Doubt it will get propagated at this point unless you CPFP or RBF.
Sound to be fixed.
"Reza said he added more peers. If you do make a transaction, make sure that all of your utxo's and their parent transactions are confirmed. One theory I have is that in our testing session we first made an extremely small and low-fee tx. This could have resulted in it not being propagated by Bitcoin Core nor any of the child txs that followed. If that's the case, we might want to reconsider allowing extremely low-fee transactions in the app depending on network fee conditions."
Describe the bug
I carried out two transactions:
Reproduce
Screenshots / Recording
https://github.com/synonymdev/bitkit/assets/46056211/bf7729e9-f1ae-4923-8b50-1f5c53f7ec32
Operating system
GrapheneOS
Bitkit version
v106
Log output
No response