-
gingeropolous
interesting. so i go and make a transaction
-
gingeropolous
i hit "confirm" or whatever. and then it sorta goes back to the wallet. i try and click around to see if things worked..
-
gingeropolous
and then a pop up informs me that the transaction succesfully sent
-
gingeropolous
i expected it to show up in my transaction history, like, immediately.
-
gingeropolous
hrm. sending to self not a good idea?
-
gingeropolous
so i effectively sent all to my own address. (sweep all to same)
-
gingeropolous
just by hitting all
-
gingeropolous
and it says the tx is failed
-
gingeropolous
so, i go and make a new tx
-
gingeropolous
and now it says error double spend
-
selsta
how long did you wait?
-
tobtoht
is there a hard limit on the d++ embargo timeout?
-
tobtoht
seems like the current strategy of waiting 3/2 * average_dandelion_timeout before setting a transaction to failed isn't reliable
-
tobtoht
I often observe transactions unfailing themselves given enough time
-
selsta
tobtoht: yep, it should be reliable with
monero-project/monero #7021
-
selsta
currently it can take 2 extra minutes which we didn't take into account
-
selsta
sending from tor / i2p can result in 4 extra minutes
-
selsta
but both should be resolved with 7021
-
tobtoht
selsta: ty, looks good
-
selsta
I did not test it myself yet but it matches with what I have been experiencing with delays
-
gingeropolous
ermagerd i can't send because of this double spend error
-
gingeropolous
ah the tx is in the mempool
-
gingeropolous
i connected to a different node and wi tworked
-
nioc
turn it off and on again. mebbe rescan_bc
-
nioc
oh
-
gingeropolous
im using the gui bro
-
gingeropolous
there's no button for dat
-
nioc
we have a gui now?
-
nioc
w0w
-
tobtoht
two, even
-
» tobtoht flees
-
nioc
:)
-
nioc
ty for that tobtoht
-
nioc
say hello to that other guy
-
gingeropolous
gui output control would be neat
-
gingeropolous
like a screen with "with note would you like to spend?"
-
gingeropolous
and then it has a depiction of different notes (outputs) with their details
-
gingeropolous
and you click on them and a little field in the top right starts adding their value together
-
gingeropolous
cause here I am waiting 20 minutes to play with my damn magic internet money
-
gingeropolous
like a tool!
-
gingeropolous
should be ale to just fire it off like lazers! Ptchoooo! ptchooooo!
-
tobtoht
feather has coin control if you want the true poweruser gui experience (tm)
-
tobtoht
no lazers tho
-
tobtoht
we'll look into that
-
xiphon
"cause here I am waiting 20 minutes to play with my damn magic internet money"
-
xiphon
you have only 1 unspent output
-
xiphon
output control won't help you anyhow
-
xiphon
btw, i wonder what is the real world use case for output control feature
-
xiphon
at a glance it seems as a useless feature to me. Though like i said, would love to hear any real world use case in case i'm missing something
-
xiphon
gingeropolous ^
-
tobtoht
xiphon: it's mostly for high threat model coin routing: excluding dust outputs, mitigating output merge analysis (by default wallet2 will prefer spending outputs that belong to the same subaddress, this can be undesired behaviour in some scenarios), churning specific outputs
-
tobtoht
churning is useful when moving coins from high to low threat model wallets, or vice versa to make make sure there is no longer any association between the two
-
tobtoht
also the ability to split outputs is useful when you're expecting to send a bunch of transactions in rapid succession, if you only have one output you're forced to wait 10 blocks after every tx
-
tobtoht
multi destination transactions are not a solution in some cases because they are inherently bad for privacy because they allow for trivial off-chain linking
-
xiphon
I wouldn't rely on a user doing all this correctly.
-
xiphon
Letting users control their outputs could (and in most cases will) do the things worse
-
xiphon
Also churning idea is quite questionable
-
tobtoht
yes, these address protocol issues that can currently only be mitigated by users that know what they are doing
-
moneromooo
Dust outputs can be frozen (and won't be spent if too small already). Rules to weigh outputs when selecting what to spend should be added to wallet2 if they're good.
-
tobtoht
churning is indeed very hard to get right
-
tobtoht
"mitigating output merge analysis", moreover wallet2 will often prefer 2-in/2-out transactions when the number of coins in the wallet is high enough. This has the possibility of linking those two inputs together which in some cases may be undesirable if the transaction could have been made with 1-in/2-out instead.
-
xmr-pr
selsta opened issue #3241: Portable mode .cache traces
-
xmr-pr