rich1.0waxwing wrotewaxwing (npub1va…knuu7)https://nostr.now/npub1vadcfln4ugt2h9ruwsuwu5vu5am4xaka7pw6m7axy79aqyhp6u5q9knuu7njumphttps://nostr.nowI wonder if anyone here knows enough about Core's internal processing of utxos *in-wallet* to help with this thorny question?
https://github.com/JoinMarket-Org/joinmarket-clientserver/issues/1465#issuecomment-1494996171
Problem is easy to state, even perhaps easy to diagnose, but I just don't know how to correct it:
1. user broadcasts transaction, 2. transaction has low fee and gets ejected from user's Core node's mempool 3. listunspent RPC no longer reports the utxo as present and so Joinmarket (as currently coded) shows a missing balance (old utxos are spent but new utxo is uh "memory-holed").
For context, Joinmarket uses a bitcoin core wallet in watch-only mode to track its transactions.
Is it possible to either query Core, or have Core not "memory-hole" those utxos? I'm thinking maybe they would be tracked, but in a different state.
Maybe nostr:npub1s6z7hmmx2vud66f3utxd70qem8cwtggx0jgc7gh8pqwz2k8cltuqrdwk4c you would know about this? Only pinging you because you're the first Core dev I can think of on here 😆