Dead Transactions

[fluidvanadium]

send is broadcast. transaction is at sending n minutes after send.
conversions to Mempool happen only in the first block. otherwise the transaction is dead
reboot causes transaction to disappear

[fluidvanadium]

discovered in at-least 3 wallets

[james-katz]

Maybe related, not sure if this should be a separate issue...
Recently I upgraded my Dizzy bot (A discord bot for receiving and sending $ZEC directly from discord) to use ZingoLib (before it was using zecwallet-lib).
But so many transactions are failing and I have to manually send these transactions to users.
Zingolib generates a txid, but it's an invalid txid, the transaction does not exist.
One thing I noticed is that so far, is that every failed transaction had a 20000 zats fee, indicating more than 1 note was used. Maybe there's some glitch with the zip-317 implementation? After a while (a hour or so) the lib prints the message Removing expired mempool tx txid_here

For sending transactions I'm using the send command followed by a confirm command: https://github.com/james-katz/zingolib-wrapper/blob/dev/zingolib.js#L420

Here some examples:

Failed transaction:

 Sending [{"address":"[UA redacted for privacy]","amount":3988999,"memo":"Sent from Dizzy."}]
 End Sending, response: {
   "fee": 20000
 }
 Confirming
 End Confirming, response: {
   "txids": [
     "ac586480aa6cba1c194fa80a71ff5f07d1f72af15abb777e6667405c30a65ec4"
   ]
 }

Another failed transaction:

Sending [{"address":"[UA redacted for privacy]","amount":4090000,"memo":"Sent from Dizzy."}]
End Sending, response: {
 "fee": 20000
}
Confirming
Already scanning new payments or wallet is busy ...
End Confirming, response: {
 "txids": [
   "ebd900ad543c3ea4b063828c8e6ce955536d9b9417b51bc00e04b4b18711c7ad"
 ]
}

Successful transaction:

Sending [{"address":"[UA redacted for privacy]","amount":1150000,"memo":"Sent from Dizzy."}]
End Sending, response: {
  "fee": 10000
}
Confirming
Wallet is sending, will sync after send is done.
End Confirming, response: {
  "txids": [
    "270188daacbb3dfa07e0b6abd53ab284c2a1e98ecab8c412c05f64efa0c38e58"
  ]
}

[juanky201271]

@james-katz I can see in your repo that you are using a commit from 2 weeks ago, my advise is: update zingolib to: tag = "1.10.2".

[juanky201271]

@james-katz NOTE: the field txids of sendprogress now is an array, same that how works confirm... we unified this field in both commands...