ain-4.0.0-beta1 - DFI disappearing when sending UTXO to Ethereum address?

[AndiyNW]

Summary

I installed the beta code on my Raspberry Pi 4 and got via the faucet 1000 DFI into my wallet. All good, though when I then send 100 DFI to my MetaMask Address, I expected 900 DFI still in my wallet, but nope, went down to 0! And, the 100 DFI didn't show up in my MetaMask either!

Steps to Reproduce

[Please use step-by bullet points to help the team reproduce the bug]

dfi@c0c441402596:~/ain-4.0.0-beta1/src$ ./defi-cli -changi sendtoaddress "0x9a13162923b5Ea734f658d70BB154FF27A6037dB" 100

dfi@c0c441402596:~/ain-4.0.0-beta1/src$ ./defi-cli -changi listtransactions
[
{
"address": "tjzAFkx23CXSrQTV5xRh1X4NvQ1vqipQ66",
"category": "receive",
"amount": 1000.00000000,
"label": "changiAndiy",
"vout": 0,
"confirmations": 776,
"blockhash": "85dbadf235371aa24980d0b0c8bb6408ae488ef3ec98f042fb9dfb778e375837",
"blockindex": 1,
"blocktime": 1687043165,
"txid": "e687d4f6df9f7165b317f10308cbb7de05a7df5b498ad5f5b7ee29785baf4f25",
"walletconflicts": [
],
"time": 1687043132,
"timereceived": 1687043132,
"bip125-replaceable": "no"
},
{
"address": "0x9a13162923b5Ea734f658d70BB154FF27A6037dB",
"category": "send",
"amount": -100.00000000,
"vout": 0,
"fee": -0.00003320,
"confirmations": 0,
"trusted": false,
"txid": "690ebb68a77e1a3cb4e72d0aebfb3e6f220fe26119523974fda6d4c93c4c70f6",
"walletconflicts": [
],
"time": 1687043722,
"timereceived": 1687043722,
"bip125-replaceable": "unknown",
"abandoned": false
}
]

dfi@c0c441402596:~/ain-4.0.0-beta1/src$ ./defi-cli -changi getbalances
{
"mine": {
"trusted": 0.00000000,
"untrusted_pending": 0.00000000,
"immature": 0.00000000
}
}

suggestion from Kügi brings the 1000 DFI back:
dfi@c0c441402596:~/ain-4.0.0-beta1/src$ ./defi-cli -changi abandontransaction 690ebb68a77e1a3cb4e72d0aebfb3e6f220fe26119523974fda6d4c93c4c70f6

dfi@c0c441402596:~/ain-4.0.0-beta1/src$ ./defi-cli -changi getbalances
{
"mine": {
"trusted": 1000.00000000,
"untrusted_pending": 0.00000000,
"immature": 0.00000000
}
}

Environment

[Please fill all of the following or NA if not applicable]

• Node Version: ain-4.0.0-beta1
• Block height on bug if applicable:
• TX or TX type on bug if applicable: 690ebb68a77e1a3cb4e72d0aebfb3e6f220fe26119523974fda6d4c93c4c70f6
• OS with version: Raspberry Pi Bullseye with Docker
• Any other relevant environment info:

[prasannavl]

Thanks for the report @AndiyNW - these TXs are disabled by default on the miner to avoid such confusion. However, we've not yet gotten around to disabling them on the RPCs, so you are still able to send it, but the TX just doesn't get mined.

#2083 should have more usability checks around it that should help.

[AndiyNW]

thx for the update @prasannavl