06:26:29 <layter[m]> <t.dennysanfo> "I'll 20 people on how to earn $4..." <- Dafuq is this?!! 🤨🤣
06:53:53 <jadeydi[m]> https://github.com/mymonero/monero-core-custom anyone who can tell me how to compile the project? not familiar with c thanks
06:59:38 <grumblemobile> While I don't know, if you find out how, I'm sure a PR adding those steps to the README (or a new README if there isn't one) would be appreciated by the author(s).
06:59:55 <grumblemobile> Assuming the steps aren't there in a different file you've missed.
07:14:15 <grumblemobile> Looking at the repo, it looks like it's not meant to be used standalone.
07:18:19 <jadeydi[m]> Yeah, I think it supports some interface for sign a xmr transactions, still try to figure out
09:33:01 <jadeydi[m]> https://github.com/monero-project/monero/blob/master/src/cryptonote_core/cryptonote_tx_utils.cpp#L206
09:33:01 <jadeydi[m]> Does this function supports spend multiple outputs from multiple accounts in one tx?
09:35:18 <grumblemobile> 95% sure it does.
09:35:38 <grumblemobile> Still not a good idea for privacy reasons though.
09:36:53 <jadeydi[m]> Yeah I know, but have to do like that. If it does, does there have an c library, so other languages can integrate xmr more easily, and I'm using go now 
09:38:55 <jadeydi[m]> I think the biggest problem for other languages is the method https://github.com/mymonero/monero-core-custom/blob/master/ringct/rctSigs.h#L117
09:39:02 <grumblemobile> We're hardly going to create an easy to use lib to do the wrong thing :)
09:39:48 <grumblemobile> (on purpose anyway)
09:40:20 <jadeydi[m]> I see, thanks anyway
12:10:59 <sethforprivacy> Is it known that the armv7 link is dead from getmonero.org?
12:11:09 <sethforprivacy> https://downloads.getmonero.org/cli/monero-linux-armv7-v0.18.1.1.tar.bz2 404s
12:11:46 <sethforprivacy> Have some builds failing as a result, wouldn't have noticed it otherwise
12:19:16 <sethforprivacy> * that the Linux armv7 link
12:20:13 <sethforprivacy> selsta luigi1112 binaryFate ^
12:20:43 <selsta> it used to be up
12:22:08 <selsta> anything else dead?
12:25:53 <plowsof> sanity check: all links work bar armv7
12:27:35 <sethforprivacy> Yes, no issues with any other links that I can find! Just armv7 for some reason
12:28:11 <selsta> it used to be up because otherwise the check hashes ci script would have failed
12:28:33 <sethforprivacy> Agreed, thus my confusion when hashes etc are there but the binary isn't 😄
12:28:36 <sethforprivacy> Have never seen that before
12:41:19 <duggavo[m]> Hello, I built monerod with make depends and it compiles successfully, however if i try running it on another machine it fails with this error:
12:41:53 <duggavo[m]> ./monerod: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.33' not found (required by ./monerod)
12:41:53 <duggavo[m]> ./monerod: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by ./monerod)
12:41:53 <duggavo[m]> ./monerod: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by ./monerod)
12:42:09 <grumblemobile> Then build it on the other machine.
12:42:37 <duggavo[m]> grumblemobile: and i need to build it on every machine using it?
12:42:48 <grumblemobile> Always best.
12:42:50 <duggavo[m]> how does the release from https://getmonero.org/ work ?
12:43:30 <grumblemobile> It includes stubs for newer glibc entry points and outright disables some code that uses others.
12:44:02 <duggavo[m]> How can I make reproducible builds to getmonero.org?
12:45:01 <grumblemobile> Are you suggesting you run a reproducible build from instructions, and ended up with a different binary than the one from getmonero.org ?
12:45:20 <grumblemobile> (I have no odea what glibc version the repro build targets)
12:46:44 <selsta> duggavo[m]: if you build it on 22.04 then you also have to use it on 22.04 machines
12:47:01 <duggavo[m]> selsta: So it won't work on Debian?
12:47:22 <duggavo[m]> But if I compile it on debian, will it run on Ubuntu?
12:47:58 <grumblemobile> It's more about the version of glibc on those machines.
12:48:21 <duggavo[m]> Isn't it possible to bundle glibc inside the executable?
12:48:38 <grumblemobile> It's too close to the kernel for it AFAIK.
12:48:51 <selsta> there is a CMake flag -DBACKCOMPAT=ON that might help, but not guranteed
12:49:07 <grumblemobile> Repro builds don't use it ?
12:49:21 <selsta> repro builds uses -DBACKCOMPAT=ON and 18.04 VM
12:49:39 <selsta> or docker
12:50:14 <selsta> glibc is never bundled from what I know
12:50:50 <grumblemobile> Given it's what makes syscalls, at least part of it can't easily be.
12:53:02 <selsta> duggavo[m]: compile on the machine with the oldest glibc you have
12:54:08 <selsta> then it should work on all machines with the same or newer glibc
13:03:20 <duggavo[m]> <selsta> "duggavo: compile on the machine..." <- Like Ubuntu 18?
13:03:23 <duggavo[m]> I'll do a VM
13:04:34 <duggavo[m]> or maybe ubuntu 16 or 14 is better?
13:05:14 <selsta> ubuntu 18 will be enough
13:06:35 <duggavo[m]> Oh, I also have issues cross-compiling for windows on an ubuntu machine: https://paste.debian.net/hidden/6959db3c/
13:10:12 <selsta> might be easier for you if you use the gitian build process, which is what we use for release binaries
13:10:47 <selsta> it uses `make depends` internally but sets everything up correctly, should also solve your glibc issue
13:11:04 <duggavo[m]> selsta: aka dockerfile?
13:11:20 <selsta> https://github.com/monero-project/monero/tree/master/contrib/gitian
13:13:09 <selsta> the instructions are more complicated than it is
13:14:07 <selsta> this should be the easiest way https://github.com/monero-project/monero/blob/master/contrib/gitian/DOCKRUN.md
13:14:35 <selsta> it also has instructions on how to copy out the binary
13:15:14 <duggavo[m]> Ok thanks
13:17:33 <selsta> I did cross compile to Windows yesterday with 22.04 and it worked: https://github.com/selsta/monero/actions/runs/3091744278/jobs/5002197898
13:17:56 <selsta> so unsure why you had this error, but using gitian should solve it as it will properly setup your build env
13:21:07 <duggavo[m]> Why isn't Gitian building the first method explained in README.md, since it is the easiest and it's reproducible?
13:22:12 <grumblemobile> You might have a flawed idea of "easiest"...
13:22:56 <selsta> most users just install dependencies and run `make`
13:23:21 <selsta> but yes gitian should be mentioned somewhere in the readme
13:31:04 <duggavo[m]> https://github.com/monero-project/monero/pull/8580
13:41:22 <grumblemobile> Thanks.
13:42:31 <hyc> most users don't care about building a reproducible binary, or one that works on multiple machines.
13:42:39 <hyc> most users only have one machine they care about
14:24:55 <sethforprivacy> Is there a similar build command to only build monero-wallet-rpc like there is for the daemon? If so, are the options for building specific binaries alone documented anywhere?
14:27:49 <sethforprivacy> Would it be `wallet` instead of `daemon`, similar to that seen here: https://github.com/sethforprivacy/simple-monerod-docker/blob/main/Dockerfile#L131
14:35:34 <duggavo[m]> If there are
14:35:34 <duggavo[m]> `(60 / blockTimeMinutes) * 24 * 365 = 262800` Monero blocks a year, why is the current Monero height 2716807?
14:35:34 <duggavo[m]> `2716807 / 262800` is 10.34, but Monero is not 10 years old. In fact, block 1 was mined in 2014-04-18.
14:35:42 <duggavo[m]> How is this possible? 
14:38:30 <jeffro256[m]> Back in ancient times, the blocktime used to be 1 minute long 
14:38:40 <duggavo[m]> Oh
14:39:08 <duggavo[m]> Did that alter the supply reward?
14:39:10 <grumblemobile> make wallet_rpc_server
14:39:32 <grumblemobile> They're in the Makefile generated by cmake. Try make help, it might show them.
14:39:38 <jeffro256[m]> https://bitinfocharts.com/comparison/monero-confirmationtime.html#alltime
14:40:02 <grumblemobile> It does. make help -C build/wherever
14:40:30 <grumblemobile> The block reward got doubled.
14:40:30 <jeffro256[m]> I don't think it altered supply reward over time, now there's 2x as much reward per block
14:40:35 <jeffro256[m]> Don
14:40:40 <jeffro256[m]> 't quote me on that
14:44:14 <sethforprivacy> grumblemobile: Thanks!
14:46:16 <duggavo[m]> <jeffro256[m]> "I don't think it altered..." <- You are right
14:46:45 <duggavo[m]> I just checked
14:46:58 <duggavo[m]> It looks like monero's emission does not change when you change block size 
14:47:38 <UkoeHB> vtnerd: can you review the new commits to 8329?
14:48:07 <grumblemobile> It is supposed to, or the block size could increase unchecked, which would be bad.
14:48:28 <grumblemobile> I suspect you just eyeballed it and missed it.
14:49:06 <grumblemobile> Miners will usually get past the penalty start only slightly, since they're self interested, and thus not wanting to lose most of the reward.
14:49:25 <duggavo[m]> s/size/time/
14:49:35 <duggavo[m]> grumblemobile: i meant block time, i typed block size
14:57:19 <CidadoisAncap[m]> <sethforprivacy> "Thanks!" <- Hi seth could you pls check dms👉👈
16:52:01 <duggavo[m]> Does
16:52:01 <duggavo[m]> c++: internal compiler error: Killed (program cc1plus) mean that the OS has killed the compiler for out of memory?
16:56:50 <grumblemobile> Technically no, but it is still very likely your OS did just that.
16:57:07 <grumblemobile> You'll usually find out by checking dmesg.
16:57:33 <duggavo[m]> grumblemobile: yeah i was trying to compile on a 512 mb computer
16:57:56 <grumblemobile> Well, that's one of the main reasons to copy a binary to another machine indeed...
17:36:34 <vtnerd> UkoeHB: reviewed 8329
17:37:02 <selsta> UkoeHB: did you also open it against release?
17:37:34 <UkoeHB> no, should I? selsta ?
17:37:54 <selsta> I think you wanted to include it in a release?
17:38:16 <selsta> we will have another release
17:39:12 <UkoeHB> vtnerd: I squashed those commits
17:40:27 <UkoeHB> selsta: existing multisig wallets aren't usable without this (surprising how little noise there has been about it)
17:41:20 <UkoeHB> selsta: should I open a PR against the v0.18 branch?
17:41:32 <selsta> yes
17:41:38 <UkoeHB> ok
17:42:51 <sethforprivacy> <sethforprivacy> "Is it known that the armv7..." <- Opened an issue for this in case other people notice and wonder what's up: https://github.com/monero-project/monero/issues/8581
18:00:11 <UkoeHB> vtnerd: ok #8582 is on the release branch