What does an orphaned tx look like via rpc? I am testing with a currency forked from Pivx, but I see that bitcoind responds the same way here https://bitcointalk.org/index.php?topic=100824.0 with error code -5
If I send/receive a tx that then some time after a few confirmations (the block) was to become orphaned or stale; Would I get the same reply from rpc gettransactions as below (where I intentionally typed a non transaction id in) if I were to look for the tx or should it come back with a full tx object?
zdx-cli gettransaction &quot;gyyyyf&quot;
error: {&quot;code&quot;:-5,&quot;message&quot;:&quot;Invalid or non-wallet transaction id&quot;}
There are two cases here:

Block with the tx became orphaned and the transaction is still valid. In this case it is returned to the mempool. gettransaction will return unconfirmed transaction detail
Another conflicting transaction got confirmed ( having same inputs). In this case existing txid becomes invalid and it is discarded