01:42:52 <gingeropolous> take me out to the black, tell em I aint comin back
01:46:51 <gingeropolous> so we're getting Oxygen Orion?
01:48:02 <nioc> yep
01:48:21 <nioc> boring
01:48:27 <gingeropolous> wonder what thunderosa_ might come up with for that one
01:50:08 <gingeropolous> for some reason im seeing a bull
01:50:11 <gingeropolous> is orion a bull?
01:50:17 <nioc> nope
01:50:24 <moneromooo> A hunter.
01:50:24 <nioc> a human hunter
01:50:45 <nioc> he has a dog
01:50:53 <moneromooo> A bull dog ?
01:50:57 <nioc> hunting the bull
01:51:01 <moneromooo> :o
01:51:03 <gingeropolous> y am i seeing bull. ah well.
01:51:05 * moneromooo does not like
01:51:27 <nioc> why did we choose to hunt the bull o_O
01:51:33 <gingeropolous> well, you shoulda sock puppeted the shit outta that poll
01:51:53 <nioc> my choice was not even in the poll
01:52:05 <gingeropolous> Oxygen Rasmataz
01:52:09 <nioc> just realized now about the bull lol
01:52:15 <gingeropolous> little known constellation
01:52:37 <nioc> Oumuamua
01:52:47 <gingeropolous> yeah, monero';s the only cryptocurrency that would name their release after a bull hunter
01:52:53 <nioc> pronounced Oh mooo ah mooo ah
01:53:00 <gingeropolous> yeahi liked that one
01:53:28 <nioc> next time I will pay 1000 moooneros to name the release
01:53:37 <gingeropolous> ah well, there's always whatevers after oxygen
01:54:16 <nioc> Flourine
01:55:24 <gingeropolous> Fluorine Fettuccine
01:55:25 <nioc> I'll start working on that one
01:55:30 <gingeropolous> another little known constellation
01:56:22 <gingeropolous> ah but this friggin tx_extra. what a bowl of fettucine
01:56:56 <nioc> fetid fettucine
01:57:33 <nioc> cc
01:58:31 <gingeropolous> so, we either effectively ensure that all txs are uniform, protecting privacy
01:58:58 <gingeropolous> or we say "but, we dunno whats gonna happen" and leave it as a fingerprinting mechanism
02:00:58 <gingeropolous> that deadbeef was funny
02:01:39 <gingeropolous> 36 kb of deadbeef
02:05:25 <gingeropolous> there's gotta be a way to have both
02:46:54 <yanmaani> gingeropolous: by being an idiot who leaks info you threaten not only your own privacy but that of others
07:42:58 * Inge- mirrors the number of transactions for a week, and publishes the view key
07:45:08 <Inge-> in other news, paypal outlaws tardigrades https://twitter.com/ArchieMcPhee/status/1304434532293046272
11:34:13 <s3rb31> Hello, I am trying to make a transaction with monero-wallet-gui/cli but I consistently get the error: "Error: internal error: Transaction sanity check failed". I tried a few things like reimporting wallet, re-syncing but to no avail. Using Win10 x64 with remote node.
11:37:15 <moneromooo> A quick way out for now is likely to remove the ~/.shared-ringdb directory, and run the wallet again.
11:37:20 <moneromooo> HOWEVER:
11:37:38 <moneromooo> This will mean that node will be able to tell the real output that's being spent.
11:37:51 <moneromooo> I assume it's not yours. If it's yours (as it should be), it's fine.
11:38:13 <moneromooo> There's some code to deal with this but it seems to not work :/
11:42:32 <s3rb31> So you're saying: exit wallet, delete "C:\ProgramData\.shared-ringdb", open wallet and retry?
11:43:09 <moneromooo> Yes.
11:43:34 <moneromooo> That database remembers rings used for your outputs, so it can reuse them if necessary.
11:44:02 <moneromooo> Here, when you send again, it reuses th esame ring. But this ring ain't passing the sanity check, so you get stuck.
11:44:33 <moneromooo> If the db is removed, it forgets that ring, and will create a new one, which will most likely pass the sanity check.
11:45:04 <moneromooo> But it means you will have sent two requests to the node: both will contain your real output, and a set of fake outputs.
11:45:22 <moneromooo> Most likely, the two sets' intersection will be just your output, so the node knows which output you're sending.
11:45:29 <moneromooo> That's why rings are remembered/reused.
11:45:46 <s3rb31> Thanks. I will try that in a few minutes. I am not really concerned about privacy with this transaction
12:23:51 <s3rb31> moneromooo: I tried the steps you explained but I still get the same error.
12:24:34 <moneromooo> Alright. Now that's unexpected...
12:25:48 <moneromooo> If you run with --log-level 2, you should see what exactly fails in the log.
12:26:30 <moneromooo> Actually --log-level 1 is enough for this.
12:27:16 <moneromooo> Or it could be the node you're using is sending dud data. I'll assume not for now.
12:28:15 <s3rb31> I am using node.moneroworld.com:18089
12:36:07 <selsta> s3rb31: try node.xmr.to:18081 or node.supportxmr.com:18081
12:36:28 <selsta> node.moneroworld.com is a node aggregator so bad nodes might be included
12:42:24 <s3rb31> I got the log with log-level 1 and it shows some errors but I don't know what that means to be honest.
12:42:25 <s3rb31> https://hastebin.com/raw/axehovuwag
12:42:46 <s3rb31> I'll try the other nodes now
12:43:16 <moneromooo> The interesting part: median offset index is too low (median is 128421 out of total 20690220offsets)
12:43:24 <moneromooo> That's *way* too low..
12:43:41 <moneromooo> Is your wallet synced ?
12:43:48 <moneromooo> ie, type "status" in it.
12:43:59 <s3rb31> yes it was
12:44:26 <moneromooo> Oooh, I think I might know.
12:44:30 * moneromooo goes read code
12:56:23 <moneromooo> It's assuming rct here, but you're asking for pre-rct outputs. So it's comparing apples and oranges.
12:56:42 <moneromooo> So it's a bug in the monero wallet. It needs to skip the rct sanity check for pre-rct outputs.
12:57:26 <moneromooo> Foir now, you can find the line in wallet2.cpp which has:
12:57:26 <moneromooo>     if (tx_sanity_check(unique.first, unique.second, rct_offsets.empty() ? 0 : rct_offsets.back()))
12:57:36 <moneromooo> And comment it out.
12:57:40 <moneromooo> So it reads:
12:57:43 <moneromooo>     // if (tx_sanity_check(unique.first, unique.second, rct_offsets.empty() ? 0 : rct_offsets.back()))
12:57:56 <moneromooo> Then you should be able to send thoes old outputs.
12:58:36 <moneromooo> selsta: a fix for this is something that we'd want in the release.
12:58:58 <selsta> sounds good
12:59:42 <s3rb31> Okay, I'll give it a try. Very nice, thanks
13:02:57 <moneromooo> Alternatively, I might have a real patch soon.
13:14:20 <moneromooo> https://paste.debian.net/hidden/b329edf4/
13:14:44 <moneromooo> That should fix it properly. It would be nice if you could confirm whether if fixes your partiuclar case.
13:15:08 <moneromooo> s3rb31: ^
13:17:42 <s3rb31> Yeah thanks, will do.
14:47:14 <monerod[m]> Hm new qiesrd thing happening to me.  THe XMR address that im inputing in the GUI is not the same that is shown on the ledger nano S when it is asking to confirm the TX
14:47:19 <monerod[m]> never seen that before.
14:49:33 <monerod[m]> Hmm.. but just found this site. and when i insert the address and "check address"
14:49:33 <monerod[m]> the one shown on the ledger is in the "Standard XMR" field..
14:49:44 <monerod[m]> https://xmr.llcoins.net/addresstests.html
14:51:27 <moneromooo> Is it mostly the same ? ie, most of the middle of it.
14:51:55 <moneromooo> If so, it's probably an integrated address, which is the address with a payment id appended, and a different prefix.
14:52:03 <monerod[m]> yeah true they are
14:52:53 <moneromooo> Would be nice for the ledger to show the integrated address instead. Maybe in the future.
14:53:08 <monerod[m]> indeed
14:53:47 <monerod[m]> thanks bro
14:53:47 <Inge-> <3 subaddresses
14:53:57 <Inge-> they show up correctly
14:57:23 <s3rb31> moneromooo: Got it compiling after a little fight with the makefile xD, will report about the patch once it's done
15:01:16 <moneromooo> Cool, thanks.
16:19:59 <s3rb31> moneromooo: Okay, I tried with your patch applied but it gives me the same error.
16:20:01 <s3rb31> https://hastebin.com/raw/senovuyiwi
16:21:17 <s3rb31> I even added some log output to make sure the binary reflects the code changes
16:22:01 <s3rb31> https://hastebin.com/raw/tekuviyuxa
16:24:42 <moneromooo> Hmm. Thanks. /me looks at the code again
16:27:49 <moneromooo> Ah, I think I know. rct here is we're making a rct tx, but it can include pre rct outputs...
16:29:33 <moneromooo> And we don't know which outputs are rct or not at this point.
16:30:22 <moneromooo> I guess I can disable the check if we have at least one non rct output.
16:36:26 <moneromooo> Apply https://paste.debian.net/hidden/4147fe0a/ on top of the existing patch.
16:36:47 <moneromooo> This skips the rct check even on rct txes if they include at least one pre-rct output.
16:41:16 <s3rb31> Alright, will try that
17:23:00 <s3rb31> Okay with the new patch the tx_sanity_check errors disappeared but it still runs into the exception
17:23:12 <s3rb31> https://hastebin.com/raw/mevevumofa
17:24:53 <Mochi101> because you're exceptional s3rb31
17:25:33 <s3rb31> why?
17:28:27 <moneromooo> Oh right, it defaults to the exception.
17:33:00 <moneromooo> https://paste.debian.net/hidden/87e23f2a/ (on top of last)
17:35:50 <s3rb31> Alright, thanks
17:48:35 <s3rb31> Nice, it worked.
17:50:37 <s3rb31> moneromooo: Big thanks :D
17:51:18 <moneromooo> Thanks for testing :)
17:54:17 <s3rb31> no problem, cya