blog post announcing the upcoming network upgrade: web.getmonero.org/2020/08/18/network-upgrade-october-2020.html

please spread it on social media

I guess this requires upgrafing HW wallets too, to support CLSAG?

Inge-: yep

wrong channel

nothing like some violence to kickstart the weekend

azy: How is that related to this chat? Let's remember this is not -pools

sorry it was meant for my JUST BLEED bros in #redditmma

usually its my default channel, but i guess i left this as my default channel when copypasting kayront's blog

Oh ok. Didn't see the "wrong channel" message right after :)

Hello all, anyone else having a weird bug in the new version of Monero wallet where there are duplicated incoming transfers of zero value?

As in, I have my real transfers with correct amounts, and there are also incoming transfers listed of 0.000000000000 amount with the same txid

Entering "incoming_transfers verbose" has them deduplicated, however

More info is needed.

I type in "show_transfers"

Correct transfers display. But transfers in the same block with zero value also display.

For example:

15449** in unlocked 2018-04-** 21:**:** *.**8289040000 3**************************************************************a 0000000000000000 0.000000000000 49****:*.**8289040000 0 -

15449** in unlocked 2018-04-** 21:**:** 0.000000000000 3**************************************************************a 0000000000000000 0.000000000000 49****:0.000000000000 0 -

It is a wallet file that was generated in a previous version.

It has never shown phantom transactions until I loaded it using the latest version of the CLI

Can you try without 096a9dbdf958d23f74d132247143b8b8d3cb6dcd ?

(rescan_bc would be needed)

Actually, first:

I recently made a new transaction to it (as in literally just now); this resulted in only a single output, as expected

Run with --log-level 2, rescan_bc, post the wallet log for that height.

Censoring of addresses is fine.

what parameters should be used for rescan_bc, a full/hard rescan?

No parameters should be fine.

Ok, it's going to take a while now

So, not every transaction has a duplication. Ones prior to 2020-07-04 do duplicate, but ones after 2020-07-13 do not. (I wouldn't know more specifically as I did not receive any outputs between those dates)

Is that when you updated monero-wallet-cli ?

I do not think so, but I couldn't tell you for sure.

Actually, I will try reopening the previous file I saved in a different folder for v0.16.0.1

Ok, so one of my older backup wallets is also showing this, which means I might have misrememebered and it isn't related to the update

This wallet is a view-only wallet if it would make a difference

ugh, when I try to rescan it keeps crashing

Run with gdb, and "bt" once crashed.

Also, do all the txes showing these 0 outputs come from the same person ?

It occurs to me that using my usual script that launches monerod as a solo-miner may have contributed to crashes during blockchain rescan. I've turned it off

They are show an identical transaction id that was a real output

*all

these transactions come from different parties and to different address types (main address and subaddress)

Well it crashed again without any mining. With regards to gdb/bt, I am using windows

It being monerod or monero-wallet-cli ?

monero-wallet-cli during blockchain rescan

Maybe the level 2 log shows something interesting just before the crash.

Is it the .log file, or the .log-part-10 file that is the latest?

.log

It wasn't up to a point where I had transactions, so I don't think it would be relevant to the duplication of transfers

The last few lines are:

2020-08-22 10:45:25.770 16968 DEBUG wallet.wallet2 src/wallet/wallet2.cpp:2564 Processed block: <61378797e9b72d076d2c8367ea5cc1532b12ba393f1f0d65a8b5a833f1a68713>, height 271728, 1(0/1)ms

2020-08-22 10:45:25.773 18396 DEBUG wallet.wallet2 src/wallet/wallet2.cpp:2620 Pulling blocks: start_height 0

2020-08-22 10:45:25.975 18396 DEBUG wallet.wallet2 src/wallet/wallet2.cpp:2644 Pulled blocks: blocks_start_height 272727, count 1000, height 273727, node height 2169909

What is the crash message ?

None, it just quit

Well, I guess I'll do a rescan_bc here to see if it crashes.

I think this would not be such a big deal to fix though, just suppress outputs displayed where the amount is exactly zero if the user requests a print via "show_transfers". Though why it's showing up in the first place is a mystery to me.

I opened a watch-only of the donation address that I definitely created using v0.16.0.1 of monero cli. And it does not show any transfers of 0.0000000, so I think if it was an issue with versions I think it may have been a prior version that introduced this error and later versions have not fixed it.

By "not fixed it" I mean that they won't create wallets with the issue, but they will also not rectify wallets with this issue if they're opened by them

Do you thin that having monero connected to a trezor is any advantage vs having a debian linux with fs encrypted running monero-wallet-cli with the local keys (adding paper wallet printed with some kind of my own encryption in the printed paper, and recovery tested) ?

Do not know if it brings any added value to my monero protection that I'm not comprehending... It seems one more technology to make me depending on it. Any opinion on this?