02:28:50 Is mastering monero a good reading material if I want to get involved in monero development? 02:31:41 citrus-flagman[m: it's a good starting point 02:32:10 Are there any other resources you would recommend? 02:34:54 citrus-flagman[m: zero to monero 2 02:36:40 UkoeHB: Reading the table of contents of this and this looks perfect thanks for the tip 07:52:40 hyc: nice, will test 11:48:20 Working on my PR that updates the Readme with the new network upgrade info. Is there only one network upgrade to v15 or will there be a settlement upgrade to v16 like in the past? 11:48:59 v15 at 2,688,888 and v16 720 blocks after 11:49:05 If you're asking whether it'll be two forks in quick succession, it will. 11:53:04 Cool that’s what I was asking about 12:37:39 now that empty blocks are a rare occurrence, is reverting the block time back to 1 minute worth considering? 12:38:21 why? that will just increase rate of orphans 12:39:55 But reduces the time for 0 conf txs too 12:40:20 I mean 1 conf 12:40:20 And distributes rewards more frequently 12:41:48 faster block emission = more block metadata = more blockchain bloat 12:42:32 hyc: did some initial testing and left a comment on the PR 12:43:12 jeffro256[m]: can you test if the Intel binary runs on your 10.13 Mac? https://github.com/monero-project/monero/pull/8312#pullrequestreview-963296167 12:46:10 thanks 12:52:33 selsta: what's the uname -a and sw_vers output for that Intel 10.15.7 box? 12:53:30 https://paste.debian.net/hidden/44abc3f1/ 12:54:51 thanks 12:57:03 so my MacCheckOSver hack isn't super-accurate but it's close enough for that check 12:58:08 I'll append your patch to this branch, thanks 13:19:08 selsta: my build hashes https://paste.debian.net/1240013/ 13:34:12 starting the build now 13:34:55 cool. fortunately rebuilding from the prev commit should be relatiely painless 13:39:41 selsta I just noticed your CI patch grabs MacOSX SDK 11.3, not 11.1. any particular reason for that? 13:40:07 https://github.com/phracker/MacOSX-SDKs/releases/download/11.3/MacOSX11.1.sdk.tar.xz 13:40:18 that should be the URL, it just says 11.3 due to the github url 13:40:37 ah ok 13:41:03 "fortunately rebuilding from the prev commit should be relatiely painless" <-- I ran it on Github so I have to start from scratch 13:43:48 oh, you're just using the CI, cute 13:45:24 Cannot build for MacOS, SDK does not exist. Will build for other OSes 13:45:42 huh. 13:45:45 should this show up? I have `MacOSX11.1.sdk.tar.xz` in `builder/inputs` 13:46:22 `./gitian-build.py --docker -j 3 --memory 8000 --detach-sign --no-commit --build --os m --url https://github.com/LMDB/bitmonero selsta macarm2` 13:46:45 did you update gitian-build.py ? 13:46:52 ah right, wrong gitian-build 13:47:27 it's a shame we don't have a single location to set the SDK version 13:50:10 works now with the correct gitian-build.py 13:50:18 cool 13:53:29 or maybe we should just make the SDK into a depends package and not treat it specially any more 13:55:13 xz: (stdin): File format not recognized 13:55:42 ok, broken file 13:56:35 or you need xzcat and don't have it 13:56:39 curl doesn't like the github link, wget worked 13:56:43 probably some redirect stuff 14:00:36 SDK as depends package would simplify things 14:41:13 will save that for a future PR 14:58:48 hyc: seeing a lot of linker warnings, like https://paste.debian.net/plainh/26ac88b9 14:58:57 can we ignore this? 14:59:01 yes 14:59:20 my hashes match 14:59:24 ltmp1 is a compiler-internal tmpvar 15:00:22 not sure why it thinks libprotobuf was built oddly... 15:00:39 matching hashes - great 17:43:30 building protobuf with -fvisibility=hidden makes some of the aarch64 warnings go away, but not all. and causes other warnings to appear in the x86-64 build. 17:43:40 nuts... 17:44:06 just gonna ignore it 18:23:08 Monerod failed to initialize after I shutdown my computer because my whole system froze 18:23:12 > Exception in main! Failed to open db handle for m_hf_starting_heights : MDB_CORRUPTED: Located page was wrong type - you may want to start with --db-salvage 18:23:45 I get this then 18:23:47 > Existing lmdb database is incompatible with this version. 18:23:52 > Please delete the existing database and resync. 18:24:02 > Stopping cryptonote protocol... 18:24:10 > Cryptonote protocol stopped successfully 18:24:14 And lastly: 18:24:14 > Exception in main! Failed to initialize core 18:24:20 This is on OpenBSD 7.1 release 18:24:47 I guess I would have to sync everything FROM SCRATCH again, which would take like weeks 18:24:53 And even then - it would just be luck 18:25:24 no backup? 18:25:55 😂 not really 18:26:08 Dude the blockchain ain't small.. 18:26:12 I do not have terrabytes 18:26:22 if your OS is hanging you've got more serious problems 18:26:32 probably some hardware is dying 18:26:45 \] 18:26:52 none of this is -dev material 18:27:05 Weeks ? Syncing on 5.25" floppies ? HDD ? 18:28:00 Anyway, an OpenBSD filesystem ought to be sane enough to allow lmdb to txn correctly. Which fs is this ? 18:28:10 hyc: > is dying 18:28:11 😭 18:28:23 hyc: CHILL man, how was I supposed to know .. 18:28:34 moneromooo: Acktually - yeah xD 18:28:42 "Am I looking at the source" is a good rule of thumb :) 18:29:07 You mean the code? 18:29:16 User -> #monero, hacker -> #monero-dev. This is what "-dev" means. 18:29:20 moneromooo: I am thinking FFS? 18:29:43 OK, I'm not familiar with this fs, I'll butt out then. 18:29:59 CalmrAge[m]: they're saying your issue is not a development topic 18:30:25 Man why does no one on here use one of the world's most secure OS, together, with this currency that's the world's most secure (I think)? 18:30:47 because openBSD has a 1970s era kernel 18:30:52 that's a dubious claim 18:30:55 Because we've switched to the more secure hypervisor ? :D 18:31:02 :D 18:31:47 hyc: Lol what? 18:31:58 OpenBSD is mach, right ? 18:32:07 the memory manager in OpenBSD still has no unified buffer cache 18:32:11 What do you mean by "mach"? 18:32:13 no, openBSD is BSD 18:32:29 Whee. Original ? 18:32:30 just like FFS is the original BSD filesystem 18:32:46 Interesting, I had no idea. Thanks :) 18:33:03 Now I dare you to install it, and face the issues yourself 😂 18:33:11 Come on, test it out 👀 18:33:21 Could be beneficial for Monero dev? 18:33:38 s/for/to/ 18:33:45 If you want to make patches to make it work better on OpenBSD (or any BSD), feel free, sure. 18:34:03 freeBSD is already well supported 18:34:18 > If YOU want... 18:34:18 I'm not made out of time xD sorry 18:34:29 ah right, so it's ok for you to 18:34:33 hyc: Yeah, but OpenBSD implement TONS of security features 18:34:36 ask us to spend our time on it instead... 18:34:46 Well, you're in -dev... 18:34:50 and FreeBSD has a Linux kernel module thing , so perhaps that's how it works? 18:35:02 hyc: Well - you're the Monero devs 😂 not me ... :d 18:35:13 then you're still in the wrong channel 18:36:03 An project development includes support for operating systems 18:36:10 * An project's development 18:36:11 #worksforme, issue closed, patches welcome 18:36:12 I am here for that 18:36:29 Why OpenBSD rocks (also - security implementations listed) - https://why-openbsd.rocks/fact/ 18:37:47 Well, if you're here for that, you're welcome. I took "I'm not made out of time" to mean "I won't do it" :D 18:38:05 was this page made in 1995 or something 18:39:35 moneromooo: I'd rather get a job that involves programming :( sorry 18:39:53 louipc: Why? 18:40:21 OK, you're blowing hot and cold here. Are you trying to hack on momero (this channel) or trying to use monero (#monero) ? 18:40:44 nvm :) 18:41:24 You bunch are the most weirdest devs I have contacted with yet. 18:41:32 I am not sure whether you're fine with this conversation or not 18:41:55 CalmrAge[m] this channel is about writing code and making pull requests, your problem is for #monero 18:42:00 You're on the verge of getting on my /ignore list for wasting my time. 18:42:14 sech1: So not even a discussion about dev? 18:42:39 Yes, discussion about dev is here. "Help me run monero on my OS while I won't try to fix it" is not. 18:43:25 > I won't try to fix it 18:43:25 I AM NOT A MONERO DEVELOPER 18:43:25 What the fuck is not understood here? You are that! 18:43:25 I can help test patches you make, but I am not doing your job/passion. 18:43:40 > on my OS 18:43:40 Holy fucking shit 18:43:40 Bye. 18:43:46 Bye 18:43:47 Idiots 18:43:57 moron 18:43:58 Jesus. I helped before, and this is what I get. 18:44:42 you guys are way too patient 18:44:58 Well, I try to be nice. Most people get the hint. 18:45:25 give me OP here and I'll rule with the iron fist :D 18:45:46 Shouldn't be hard, you see -dev suffix -> for coders. 18:45:54 It's unbelievable. 18:49:38 the guy was from matrix. one step removed from discord 18:51:29 Do users from Matrix see channel topic when they join? 18:52:24 no, but I asked the operators to set the same topic 18:52:38 it may be obscured. depends on client 19:48:05 moneromooo So you're telling me you're not a 24/7 tech support firm? 20:17:34 Someone who is knowledgeable in SSL: Are X509 certificates deterministically generated from private key files, or do they involve some random data? 20:27:25 "Jesus. I helped before, and this..." <- we helped the fag spiritually in #monero:monero.social , point him there next time 20:27:32 * next time, he is happy member now 20:28:15 "Do users from Matrix see channel..." <- most use element.io, they do see 20:28:52 Thanks. Is the matrix version of #monero still split from #monero ? 20:29:24 Wait. Is #monero:monero.social matrix ? There might be three #moenro versions now... 20:29:40 moneromoo the irc monero room is not bridged :( 20:30:26 I'll /unignore now since "he is happy member now". Thanks morria[m]. 20:38:39 +1 vote for sech1 to rule with an iron fist fist here (seems to be a problem of techsupport q's / off topic users) 21:35:36 selsta have fun 21:37:39 jeffro256[m]: an X.509 cert has names and attributes and options, it's more than just a pub/priv keypair 21:43:28 selsta: by the way, those linker warnings are all triggered by device_trezoer's use of libprotobuf 21:44:06 I haven't tested trezor use here, someone should try that.