xmrpow: yes

I think I remember from the dev meeting that an issue about naming the new release should go up. Will this be here? github.com/monero-project/meta/issues

Nitrogen... ?

Nitwit

nitrogen nebula?

Nitrogen Nemesis, after the asteroid: en.wikipedia.org/wiki/128_Nemesis We will revenge any attempt to deanonymize :)

Will make a meta issue later

Alright :)

when opening a wallet and entering wrong password, wasn't it before saying "wrong password"? Maybe I misremember

now it's "Error: failed to load wallet: std::exception"

binaryFate: fixed in latest master

coolio :)

With a viewkey can I prove a integrated address/subaddr belongs to the associated public address? Preferably via an explorer or such a website

Don't think so. The viewkey allows to see and decode incoming transactions. If you have no transaction to the subaddress you want to prove ownership off, I would say you are out of luck

azy: integrated address can always be converted to normal address.

without any view key

How so?

type `integrated_address address` into CLI

Ty both

moneromooo: You mentioned testing dandelion++, how does one verify whether it is actually working properly?

One could check logs (net.p2p.msg:INFO would do it) to check that txes go to one (or two ?) peers only if they're in stem phase.

Send a tx, check it's received on another node not connected to the first one.

vtnerd might have better ways.

On the real network, a tx marked as stem will be seen as a normla tx, so you won't get long stem paths, most likely one hop from your node.

Would be interesting also to modify a node to drop all dandelion txes, to check the first node hits the timeout and fluffs it.

Thanks

moneromooo: the black hole attack?

it would

Context ?

You mean simulating a malicious node that tries to block propagation by ignoring stems

and ensuring that the transaction eventually gets fluffed despite this "black-hole" node

(the paper calls this a black hole attack)

Yes.

roger

Yes, that's an important test, since D++ is supposed to fall back to fluffing in the worst-case scenario

fluffing ;)

luigi1111w: when you have time, could you please take a look on ccs servers? The funding required page has not been updated since you merged my proposal

netrik182[m]: I left you a comment on your proposal.

Can you please remake your proposal. Something funky happened and it didn't work.

Please pay super attention to formatting and look at other proposals that got it correct. If you need help message me (on Matrix as I see you have it).

@rehrar:matrix.org

Doing it right nowrehrar:

Epic. Thanks.

Testing 0.16, the only weird thing is that monero-wallet-cli says this everytime you send to a normal 4* address: "NOTE: this transaction uses an encrypted payment ID: consider using subaddresses instead"

I'm not specifying a payment ID, isn't that just the one that's added to all Tx now?

That ought to have been fixed. Can you detail what you're doing exactly ?

I noticed that message with most outputs when syncing wallet from 0, and then I get it everytime I send to my own normal address

Let me grab exact command

oops wallet autolocked, thats quick 0.0

Lost the command history

I'll retry what I think caused it before

The message is displayed when the output I send from "sweep_all <default wallet address" is received by the wallet with the next block

well, didn't happen this time

Maybe I just had an input in the first sweep it didn't like?

I'll keep trying to reproduce.

moneromooo reproduced it.

Sending using "donate 0.1" gives this output once the Tx confirms:

NOTE: this transaction uses an encrypted payment ID: consider using subaddresses instead

But it doesn't appear that the "donate" command actually specifies a payment ID (idk why it would)

OK, I'll try to see/fix.

Want me to open an issue for it?

Might as well.

Ok!

Ah, it triggers on change.

Verified sending to another 4-addr with the same issue

moneromooo-monero/bitmonero a90e9bf should fix it. Won't get built for a while, two VMs building atm.

That's a quick turnaround 0.0

Nice work, I'll rebuild with that later tonight

Again, it's not even built yet.