13:06:57 <woodser[m]> I'm building monero binaries on mac with make release-static, but when I run the binaries on another mac, they fail with the error "dyld: library not loaded: /usr/lib/libmd.dylib" with "reason: image not found". I thought the binaries are supposed to be portable. any ideas?
13:10:38 <moneromooo> They might need building with an old mac for this to work ? Like the glibc version problem on linux and the need to provide replacememts for newer calls.
13:29:29 <izrail[m]> Здравствуйте.
13:29:29 <izrail[m]> комьюнити рускоговорящее есть?))
13:35:43 <moneromooo> Try in English.
14:38:41 <selsta> woodser[m]: which macOS did you build them and which macOS version did you run them?
14:38:59 <Lovera[m]> > <@izrail:matrix.org> Здравствуйте.
14:38:59 <Lovera[m]> > комьюнити рускоговорящее есть?))
14:39:00 <Lovera[m]> https://t.me/XMR_RU
14:39:01 <selsta> best way to build portable mac binaries is using make depends
14:43:01 <woodser[m]> built on 13.3.1, and also tried the version before that. testing on 11.7.4. I'm on the old chip, not the new m1 if that matters. been trying to get through errors with depends (currently libstdc++ not found)
14:43:52 <izrail[m]> Lovera[m]: спасибо)
15:00:30 <selsta> woodser[m]: you can't build on a new version and use on an old version without without using the old sdk
15:01:14 <woodser[m]> ok. trying the depends route
15:01:19 <selsta> there are also some deployment_target settings but i'm not familiar with them
15:01:31 <selsta> you have to use ubuntu for depends
15:01:44 <selsta> 18.04 and 20.04 works, don't remember 22.04
18:36:46 <izrail[m]> Hello. How do I get a UAH/XMR course in JSON format?
18:43:10 <ofrnxmr[m]> Monero Community Dev  
21:53:06 <r4v3r23[m]> moneromooo: is it possible to see size reduction of `unsigned_monero_tx` like you did for outputs?
21:58:54 <r4v3r23[m]>  * moneromooo: is it possible to get a size reduction of `unsigned_monero_tx` like you did for outputs?
22:04:13 <moneromooo> Maaaybe... You'd need to rummage in the struct to see what is truly necessary. I have no idea how much you could gain right off the bat.
22:04:51 <moneromooo> I *think* you're a lot less likely to see large improvements though.
22:05:38 <moneromooo> Because the other side recreates the tx, and the data in that file is basically the data needed to recreate it.
22:05:59 <moneromooo> But without an attempt to optimize the size.
22:07:29 <r4v3r23[m]> yeah, i remember you said there were easy wins that could be made on outputs, wanted to know if unsigned could benefit too
22:08:13 <moneromooo> Oh, there's multisig keys. Not needed for cold signing.
22:08:43 <moneromooo> That's an easy win. 128 bytes per input.
22:09:40 <r4v3r23[m]> unsigned tx isnt nearly as big as outputs file was, but obviously the smaller they are the better, especially when trying to fit into as few QR codes as possible