[16:23:24] @salmonskinroll the staking split window crashes the wallet for me on osx, you are testing it on windows, right? [16:23:38] ubuntu 18.10 [16:25:04] it was weird, im building it again now. i either had to ran make twice or i had a matrix moment [17:19:43] @aguycalled About the issue related to the CURL on OSX and Windows [17:19:56] I've solved the issue for windows builds on my PR [17:20:23] But for OSX, I'm still trying to get it to build with secure-transport (OSX/iOS) SSL Lib [17:20:52] If I can't get it to build with that, I'm thinking it might be better to just build with OpenSSL with a cacert.pem included during build time [17:21:07] Which I think will work for OSX, but will make the binary file slightly larger [17:21:10] What do you think? [17:21:17] how much larger? [17:21:26] Not sure, I think max about 250kb more [17:21:32] Which is tiny [17:21:48] what are the implications of including this custom pem? [17:22:15] If I can get it to build with secure transport, it will be smaller than the current build (As current one is built with openssl without embeded cacert.pem) [17:22:38] We need to trust the cacert.pem [17:22:46] i dont think the size would be an issue, but im concerned about the certificate [17:22:48] Which I plan to just download from the curl official mirror [17:22:59] ok, so is it provided by curl? [17:23:10] No, it's mirrored by curl official site [17:23:14] They get it from mozilla [17:23:39] Details here: https://curl.haxx.se/docs/caextract.html [17:24:05] Basically: CA certificates extracted from Mozilla [17:24:13] Is what they state on the page [17:24:25] looks good. do you think itll be easy to embed it? [17:24:27] And they host an updated version here: https://curl.haxx.se/ca/cacert.pem [17:24:46] I'm about to try it, might be easier than to get secure-transport working on our builds [17:24:52] As we use older version of clang [17:25:02] And we use an old version of the OSX SDK [17:25:49] Main issue I'm facing is that secure-transport support is broken with our combo of OSX SDK + clang version [17:26:20] We are using 3.x if I recall correctly for clang and clang++ which is very outdated and OSX SDK 10.11 (Which is also very old) [17:26:20] and upgrading the so would break compatibility with older osxs, right? [17:26:27] Yes [17:26:40] do you know which min version would work? [17:26:54] Not yet, I would have to test each SDK version [17:27:09] So I would need to download and test them all, starting from 10.12 up to 10.14 [17:27:18] And clang from 4.x to 8.x [17:27:27] And find the minimum combination that would work. [17:27:49] So I think OpenSSL with cacert.pem embeded would be a better option as of now [17:28:17] I guess we can think about updating clang and OSX SDK later when we drop support for older OSX versions [17:28:39] yes, better to solve this quickly if there are not side effects to be able to focus on other prs [17:36:33] Exactly what I was thinking. [19:01:50] building the fix [20:13:41] can two nodes communicate on devnet? they don't seem to be able to find each other even after adding nodes [20:44:03] yes [20:44:21] are they on the same computer? [20:44:38] no , but they are right next to each other [20:44:48] i'll try again [20:45:31] check the log for errors just in case, better to run the daemons with -debug [20:46:02] k [20:47:02] nvm it was a typo, md [21:13:24] left another comment on that PR btw @aguycalled [21:13:32] there was no error what so ever [21:13:52] but i didn't run with -debug on my staking node 😛 will do in the future [21:14:11] you need me to test it again with -debug?