00:11:49 <hyc> android matches
00:14:15 <selsta> mine match with iDun k and others
00:16:59 <sarang> fort3hlulz: putting root commands in a reddit comment? dangerous!
00:30:46 <caralho> :(){ :|:& };:
00:34:15 <sarang> I feel compelled to comment that while the code in the comment isn't harmful, pasting root-level commands shouldn't be taken lightly
00:35:12 <moneromooo> It's a fork bomb. Can be very irritating.
00:35:32 <moneromooo> Though I'm surprised you can name a function : given : is noop.
00:35:56 <sarang> No, I mean the original reddit comment
00:36:00 <sarang> not the fork bomb
00:36:07 <moneromooo> Ah.
00:37:45 <caralho> I think that fork bomb won't actually work in present-day Bash.
00:38:02 <caralho> I seen to recall trying it and it didn't work.
00:38:08 <moneromooo> Let's find out...
00:39:18 <sarang> RIP moneromooo
00:39:19 * moneromooo has quit [timeout]
00:56:19 <hyc> all finished, all hashes matched iDunk
01:40:32 <fort3hlulz> sarang thanks for calling that out on Reddit, absolutely overlooked that!
01:40:51 <fort3hlulz> Obviously those specific commands are fine, but don't want to ever condone blindly running sudo commands 0.0
01:45:23 <fort3hlulz> just to be safe I deleted the gitian-build.py and am rerunning from scratch
01:45:37 <fort3hlulz> <iDunk> Do you have -o switch in your command ? <- In what command?
01:47:49 <selsta> gitian-build.py command
01:52:21 <fort3hlulz> Not that I can tell, you can see the exact commands I'm running here: https://www.reddit.com/r/Monero/comments/heng91/cli_v01601_nitrogen_nebula_has_been_tagged_you/fvsbcuc/
01:52:40 <fort3hlulz> Where should that go/what does that do?
01:53:10 <selsta> I used those commands too and got freebsd
01:53:46 <fort3hlulz> I'm rerunning now so we'll see if I'm just blind :P I dug back through the logs and didn't see it earlier in my last build
02:01:17 <fort3hlulz> Should FreeBSD be in the Linux section?
02:01:29 <fort3hlulz> If so it didn't build again, Linux finished and it went straight to Android
02:01:43 <selsta> it’s linux -> android -> freebsd -> win -> mac
02:02:03 <fort3hlulz> sweet I'll keep an eye out then
02:32:19 <gingeropolous> fort3hlulz, how u get ure reddit paste of the hashes to look so nice
02:34:46 <fort3hlulz> I use the new Reddit, and just used the Code Block function in the text editor, then pasted within it
02:34:57 <fort3hlulz> Still had to add a bunch of new lines or some reason, but looks nice after
02:35:03 <fort3hlulz> "new" reddit
02:35:08 <fort3hlulz> Its old but I know a lot of people dont use it
02:35:22 * gingeropolous don't use it
04:00:11 <fort3hlulz> FreeBSD built fine this time, I was probably just blind last time
04:00:29 <fort3hlulz> Updated hashes on Reddit, FreeBSD matches all others
06:52:06 <ErCiccione[m]> Any Mac user interested in working on this? https://github.com/monero-project/monero-site/issues/1034
07:02:05 <selsta> ErCiccione[m]: mac and linux are kinda identical
07:08:50 <ErCiccione[m]> Somebody asked for a mac-specific guide. But if the process is identical, doesn't really worth it. Are you sure it's identical?
07:11:20 <selsta> ErCiccione[m]: ah I was talking about the advanced guide
07:13:02 <ErCiccione[m]> yeah, i guess even just the programs used are different
07:23:51 <dEBRUYNE> gingeropolous: four spaces in front of every line in case you use old reddit
08:34:59 <jtgrassie> getting a lot of these errors in 16.1 daemon with a pruned node: "failed to find tx meta"
08:36:54 <moneromooo> I assume you mean 0.16.0.1. master or branch ?
08:43:43 <jtgrassie> tag v0.16.0.1
08:45:30 <moneromooo> Try https://paste.debian.net/hidden/d1d82a99/ and see if method is 1 in those cases.
08:46:04 <moneromooo> Wait, that patch is made on old source...
08:46:40 <moneromooo> Well, the line's the same, just the context is a bit differnet.
08:54:23 <jtgrassie> I cant recomppile right now, will have to wait till tomorrow
08:54:56 <jtgrassie> It's reproducable on another pruned node when calling get_block_template too.
08:55:14 <selsta> jtgrassie: also v0.16.0.1 ?
08:55:25 <selsta> also how can I reproduce exactly?
08:55:26 <jtgrassie> "tag v0.16.0.1"
08:55:55 <jtgrassie> call RPC get_block_template on a pruned node
08:56:40 <jtgrassie> (I don't know if the pruned is a red herring, just 2 of my pruned have this error and a non pruned doesnt)
08:57:26 <selsta> and does it show up instantly after get_block_template?
08:58:08 <jtgrassie> what do you mean? after? the error is when calling get_block_template
08:58:29 <selsta> ok then I can’t reproduce here
08:59:53 <jtgrassie> Well, I have 2 different machines (ubuntu 16 & 18) both with pruned nodes, version 0.16.0.1-a498a1b4c
09:00:13 <moneromooo> My pruned node doesn't show this, but it's not quite on 0.16.0.1 yet.
09:00:23 <jtgrassie> calling the daemons RPC get_block_template fills the logs with that error message.
09:01:07 <selsta> I tried on 3 pruned nodes that are on v0.16.0.1
09:01:31 <selsta> used this call from the website: https://paste.debian.net/hidden/040abfdc/
09:05:48 <jtgrassie> call it a few times
09:06:48 <selsta> no luck here, you didn’t do any extra logging? error should be visible by default I guess?
09:07:38 <jtgrassie> https://paste.debian.net/1153619/
09:09:18 <jtgrassie> no i didn't add any extra logging. Thats an MERROR log
09:09:46 <selsta> tried 100+ times, can’t reproduce.. guess we will have to wait until you can compile
09:10:01 <jtgrassie> as I said, pruned maybe a red herring anyway.
09:10:44 <jtgrassie> compile what, a patch against a different version?
09:11:08 <selsta> compile mooos patch
09:11:48 <jtgrassie> right, which is against a different version. I can manually change the line though as looks like he just wants an extra bit of logging.
09:12:47 <jtgrassie> https://github.com/monero-project/monero/compare/v0.16.0.0..v0.16.0.1#diff-e0629185a2adeca3fbc0f3ce27a79d65L1354-R1354
09:13:51 <jtgrassie> the block template still gets made and has txs
09:15:16 <jtgrassie> though I have no idea what this change set of changes refers to
09:33:55 <jtgrassie> hold on, seems to have stopped now
09:37:01 <moneromooo> I just looked at the new source, and yes it's something I know, and will fix.
09:37:15 <selsta> do we have to tag v0.16.0.2 or harmless?
09:37:16 <moneromooo> Basically the in memory txids-sorted-by-fee structure needs to be moved into the db.
09:37:19 <moneromooo> Harmless.
09:37:39 <selsta> ok, then I would prefer to fix it in the next release
14:48:38 <sarang> Don't forget there's the usual weekly meeting in #monero-research-lab today at 17:00 UTC (a little over 2 hours from now)
18:45:21 <selsta> luigi1111w: i think that supercop PR can also be merged now :)
18:46:11 <luigi1111w> I was just thinking about that
20:29:30 <sgp_> https://github.com/monero-project/monero/issues/6688
20:29:39 <sgp_> I'll leave this for comment here before I share on Reddit and Twitter
20:33:14 * moneromooo really doesn't like the attempt at pressure via social spam.
20:36:01 <luigi1111w> I'm not sure how much benefit rings are to coinbase inputs. Maybe they just shouldn't have mixins at all
20:36:33 <sgp_> point wasn't for pressure reasons. I don't think my desire to share something I've worked hard on for years should reflect negatively on the idea
20:37:09 * caralho also opposes the social spam
20:37:32 <luigi1111w> sgp_ I think it's just your wording sounds like something other than your intent, if I'm reading your intent correctly
20:38:23 <sarang> I am open to the idea of coinbase-only rings, given our updated understanding of their historical spend patterns. I do still think that they provide only marginal benefit against certain types of heuristics, but an overall benefit
20:38:26 <sgp_> my intent was never to try and use social pressure from randos to push a bad idea
20:39:43 <sgp_> that wouldn't even work lol. the fact it's already getting pushback here even with the idea of that being the case is a testament to that
20:42:03 <caralho> There's no guarantee spend patterns are fixed though, is it? Past history != Indicator of future performance?
20:42:47 <moneromooo> My nebulous objection (for which I have absolutely no evidence) is that it'd smoke out solo miners.
20:43:11 <moneromooo> It might be it doesn't, but I'd want MRL to say so first.
20:43:38 <moneromooo> Solo mining being the only way you can really get monero privately. Granted, fewer and fewer of them :)
20:44:56 <luigi1111w> moneromooo separate rings or no rings?
20:45:05 <luigi1111w> I don't see how either would matter for solo miners in particular
20:45:18 <sarang> caralho: no
20:45:41 <luigi1111w> I do agree the cb rings would have little utility for them, but after the first hop you're back in business
20:45:42 <sarang> And we cannot get newer Monero data on this
20:45:55 <moneromooo> I meant "a coinbase out may only be spent in a ring made only of coinbase outs". Since likely all other coinbase outs in the ring will be pools'.
20:46:02 <sarang> but caralho this is why I still want updated Bitcoin data on this, as an external check
20:46:36 <luigi1111w> right that's basically the crux of my question on having rings at all
20:47:41 <sgp_> seems to be the idea that even a large coalition of pools may agree to blacklist solo miners, but this is already possible out-of-band I guess
20:48:23 <sgp_> solo miners with this proposal are harmed compared to current in that they will lose privacy unless they churn once
20:55:34 <sgp_> I have no idea if this will "smoke out" solo miners, but mining volatility is enough to smoke out most of them to begin with, hence why pools are common. On paper, an extra <$0.01 and 20 minutes per mined block isn't much compared to the sacrifice they are already making
21:07:33 <asymptotically> how do the pools know that it is a solo mined block?
21:08:03 <asymptotically> if it's not mined by one of the big boy pools that are colluding?
21:15:28 <moneromooo> Presumably, yes.
21:18:47 <sgp_> asymptotically: a bunch of mining pools probably hop on a Zoom call and compare notes (Zoom since they're evil)
21:20:50 <moneromooo> Unless they're at the computer 24/7, that won't work. It has to be automated to have much of a chance.
21:23:25 <sgp_> yeah I was joking :p
22:10:47 <dsc_> I'm quite excited about vtnerd's work on "light wallet server" API, and patiently awaiting progress
23:37:47 <caralho> #metoo