Open buhtignew opened 3 weeks ago
Thank you. I'm already working on the discrepancy, but this could take some time.
I'll think about what can be done with the unconfirmed transactions. pacli itself can't detect if they are invalid as it shows the result of a slimcoind command, so for example if you just created some transactions which are still unconfirmed they will be shown in the same way than old invalid transactions that still "hang" in your mempool.
I would prefer to not have to add another flag (e.g. "only-confirmed" or so) nor "mark" them in any special way (this is difficult, and also the user already sees that the txes are unconfirmed).
The inconsistencies are now probably solved. I had inconsistencies too with this address, and they disappeared now with the fix in commit 8d83d95.
The reason was that the address mkwJijAwqXNFcEBxuC93j3Kni43wzXVuik is a P2TH address. For optimization reasons, however, I had excluded the P2TH accounts from the query which is called by transaction list
(without -x) even if single addresses are queried. Only those transactions where other addresses from the wallet were also involved were displayed. I now added a check which will include the P2TH accounts in the case a P2TH address is queried. So far it worked.
Regarding the unconfirmed transactions, I have still not modified the policy, so this issue can stay open until this is solved.
The discrepancy is gone. Looking forward for your decision on what to do with the pending transactions.
I've run transaction list
transaction list mkwJijAwqXNFcEBxuC93j3Kni43wzXVuik
and got this output, while theaddress cache mkwJijAwqXNFcEBxuC93j3Kni43wzXVuik
reports as following:Thus the number of blocks in
address cache mkwJijAwqXNFcEBxuC93j3Kni43wzXVuik
output is 68, while thetransaction list mkwJijAwqXNFcEBxuC93j3Kni43wzXVuik -t
reports only 61 transactions.I've further compared
transaction list mkwJijAwqXNFcEBxuC93j3Kni43wzXVuik
output withtransaction list mkwJijAwqXNFcEBxuC93j3Kni43wzXVuik -x -l
andtransaction list -x -o mkwJijAwqXNFcEBxuC93j3Kni43wzXVuik -l
outputs (the-x
flag doesn't work on my side without the-l
flag for the moment, as reported here) and got that thetransaction list mkwJijAwqXNFcEBxuC93j3Kni43wzXVuik
has the following two transactions that are not present in the other two outputs:(which is a kind of expected because those are probably my test with
--sign
and--send
flags as per issue #109, but probably we have to decide what we should do with the invalid transactions for different command. Maybe we create another flag for them? (although it could be a big challenge to find a letter for that)).The
transaction list mkwJijAwqXNFcEBxuC93j3Kni43wzXVuik -x -l
have the following 14 transactions that are not reported intransaction list mkwJijAwqXNFcEBxuC93j3Kni43wzXVuik
output:The
transaction list -x -o mkwJijAwqXNFcEBxuC93j3Kni43wzXVuik -l
has the following transaction that is not present intransaction list mkwJijAwqXNFcEBxuC93j3Kni43wzXVuik
output:For your convenience here are the
transaction list mkwJijAwqXNFcEBxuC93j3Kni43wzXVuik -x -l
and thetransaction list -x -o mkwJijAwqXNFcEBxuC93j3Kni43wzXVuik -l
outputs I'm getting: transaction_listmkwJijAwqXNFcEBxuC93j3Kni43wzXVuik-x_-l(20240614).txt transactionlist-x_-omkwJijAwqXNFcEBxuC93j3Kni43wzXVuik-l(20240614).txt