[05:26:10] /bot [07:12:22] /bot [08:00:13] I'm feeling a bit better. I'll be having a good crack at clearing out some of these PRs tomorrow [08:00:26] Starting ~14 hours from now ish [08:00:49] Cleared my whole weekend to try and make some progress on core and the websites [08:42:30] @prole 👌 [08:43:02] Take your time man, don't push yourself too hard, otherwise you won't get well [09:35:26] still havent got the test results back from teh doc, but my throat is clearing up a bit. [09:35:45] but still just really tired and gettting random headaches and waking up in a pool of sweat in the middle of the night [09:35:46] fun times [09:36:11] ill do what i can tomorrow, but dont worry i wont be doing a 16 hour day or anything [09:36:12] 😛 [09:41:30] or maybe ill just exit scam, havent decided yet [09:41:36] 😂 [09:57:44] Lol [10:23:25] @aguycalled [10:23:54] hey [10:24:10] Did you push latest code for "coldstaking-pool-fee" [10:24:11] branch [10:24:37] Or were you able to fix it already? 😄 [10:24:51] not fixed yet, moved back to dao [10:24:56] yes i pushed [10:25:11] I see [10:25:36] Ok, we'll tackle that later then [10:27:11] No new coders picked up from bounty program? [10:27:42] nothing new [10:27:45] @sakdeniz @prodpeak you guys wanna code on core wallet? 😄 [10:28:25] I know you're all busy, but we need all the extra help we can get 🤣 [10:28:43] its hard to find c++ blockchain devs [10:28:55] Yeah [10:29:06] I wish it were more accesable [10:29:10] specially when some of them are retired [10:29:17] Bwahahaha [10:29:23] or others being offered massive salaries somewhere else [10:29:38] i was offered 20k per month at the beginning of the year [10:29:39] You mean, the devs have coins, coins go up, then they retired on a beach somewhere? 😄 [10:30:01] I'm glad you did not take it @aguycalled [10:30:18] Otherwise nav would not have anymore major changes [10:30:46] Actually i am thinking to contribute to core for a while [10:30:59] But yeah c++ is hard [10:31:00] Nice, we got a nibble 😄 [10:31:31] Once we get you hooked, you should be fine @sakdeniz [10:31:48] im sure if we have more resources the situation would be different [10:32:15] By resources you mean devs or funds or maybe both? [10:32:35] But also i am thinking our possibilities id limited on core wallet [10:32:50] funds to get more devs [10:33:02] I see [10:33:13] Yeah, that would make things easier [10:33:45] If I read correctly, Encrypt-S was paying for navcoin-core development right? [10:33:58] That was out of @prole's pocket I pressume [10:34:04] yes, it paid my salary [10:35:38] and other devs which eventually sometimes reviewed things in core, but they were mostly js devs so their main task was other [10:36:02] I see [10:36:15] I guess it was easier to pay devs when NAV was 4$ 😄 [10:36:27] It's pretty hard to do now at 0.2$ [10:37:01] About the UI discussion we had before [10:37:16] What was your idea about having a nodejs UI? [10:37:36] IIRC you had questions about web UI + navcoin-core using gitian [10:38:04] i said itd be easier to find js devs [10:38:11] Ahh [10:38:15] who could work in the ui [10:38:23] So if per se we switch from QT to web UI [10:38:27] We could get more devs [10:38:30] Makes sense [10:38:34] if it was based on electron or something similar [10:38:40] Yeah [10:38:52] right now our approach regarding gui is just minimal effort because its a pita [10:38:54] But that's a lot of work upfront [10:39:07] We would need to replicate all UI functionality on the QT wallet [10:39:27] well @sakdeniz did next in relatively short time [10:39:27] And I think wallet performance will be worst than with QT [10:39:51] that might be a good reason, performance [10:39:51] Most electron apps use like 1GB ram [10:40:02] honestly im more worried about qa [10:40:06] So our headers 1.6GB + 1GB for the new ui [10:40:35] Would mean it will use more ram and be less responsive [10:40:51] I mean the QT wallet does not look pretty, but it runs fast for what it is. [10:41:08] Hmmm, what aspect of QA do you mean? [10:41:45] pr reviewing, test writing. [10:41:51] I see [10:42:07] Reviewing the PRs will be harder I think [10:42:18] It's much easier to have malicious code in JS than in c++ [10:42:36] IE, you can hide an ajax request somewhere obscure [10:42:42] Hard to catch something like that [10:43:14] With the c++ it's an instant red flag when curl or boost networking libs are used 😄 [10:43:42] But QA and testing the UI would be easier I think [10:43:57] Since angular/react have nice test frameworks [10:44:15] If we use angular or reactjs, we could automate testing for the UI [10:44:30] i think there are tests for qt too [10:44:37] but what i mean is [10:44:49] we have a bottleneck reviewing prs [10:45:38] Ohh [10:45:41] the whole test unit suite needs some care. and tests should ideally be written by someone different from who wrote the code. [10:46:13] half of the tests are disabled because noone migrated them from btc [10:46:26] Yeah, I saw that [10:46:33] In the functional-test branch [10:46:50] I think once that is migrated, we can re-enable all the relevant tests [11:01:26] @aguycalled you know of any front-end c++ libs that are easier to use than qt but still c++ so that we preserve the performance but make it easier to learn for new devs? [11:01:39] Maybe you've seen other coins using a different framework/lib [11:02:02] I've only used QT and GTK [11:02:17] But both are similar in learning curve (Both hard to learn) 😄 [11:09:22] heard about those [11:09:22] https://ultralig.ht [11:12:32] @mxaddict [12:21:45] I've checked ultralig.ht [12:22:00] Seems like a viable solution [12:25:52] But then again so is electron or react-native [12:26:17] I think in terms of performance ultalight > react-native > electron [12:26:33] But electron is well documented and used in other crypto based projects [12:26:48] And electron is fully deterministic [12:27:14] React-Native is faster than electron, and has more documentation/usage then ultralight [12:27:35] Ultralight is fastest out of the 3, but has the least documentation/usage in crypto space [12:27:41] @aguycalled what do you think? [12:28:45] i'm not an ui guy, so can't say much [12:43:27] Hahaha [12:43:33] I'm not really a UI guy either [12:43:43] I know a little bit [12:44:25] I guess if we did do a new UI for core wallet with web tech stack, we'd have someone that has more exp. with it. [13:19:10] https://developer.trustwallet.com/wallet-core [13:19:16] You guys seen that? [13:19:23] Looks like Trust is open source. [13:33:00] Not sure it would help with our problem @Juguelio But looks like it would be nice for making ligh wallets [13:33:25] I thought you could get Nav integrated to Trust from there [13:33:50] Ohh [13:34:09] I thought you meant for the discussion we were having about UI for navcoin-core [13:34:10] 😄 [13:34:22] Hmmm, I've not used trust-wallet [13:34:27] Is it good? [13:35:14] I see it's "official binance wallet" statement on home page [13:35:36] Does that mean binance recommends it? Or they created and maintain it? [13:36:53] I'm installing on android, will test myself [13:44:57] @Juguelio trust wallet looks cool [13:45:08] But I'm not sure if anyone has the time to integrate with it as of the moment [13:48:55] Binance bought it [13:49:08] I see [13:56:24] You can stake there [14:01:08] Not sure what you mean by "you can stake there" [14:01:08] What coins? [14:23:14] Tezos [14:23:45] https://trustwallet.com/blog/trust-enables-tezos-wallet-and-staking-support