[12:23:45] *** Quits: navcoin-bot (~navcoin-b@nav.community) (*.net *.split) [12:24:01] *** Joins: navcoin-bot (~navcoin-b@nav.community) [13:30:07] Do we still have to bud the rc? [13:47:11] there are some binaries [13:47:24] https://builds.navcore.org/v4.7.0-rc [14:48:14] okay thanks [14:48:19] gonna give it a shot now [15:54:39] is the dark mode already in? [15:54:49] how do I apply it? [16:13:30] @LordNelsson [16:13:37] No, it's not merged into this version [16:13:42] ah okay [16:13:47] shame :( [16:13:58] Don't worry it will be in next release 🙂 [16:14:09] I'm aiming to get it ready by end of this week [16:14:20] Been super busy, which is the cause of the delay [16:14:52] ah okay np [16:15:53] @developer can someone have a quick look at this PR https://github.com/navcoin/navcoin-core/pull/592 [17:57:15] how would you redirect your stakes with cold-staking once 4.7 is out? is it poolfee=100 pooladdress=XXX in config file? [17:57:27] yes [17:59:11] let's try to get more members to contribute to the bounty programs and if we have enough people we can probably look into increasing the bounty [21:45:58] is it capable of multiple output addresses? like poolfee=10 prooladdress1=ADDRESS1 poolfee2=20 pooladdress=POOLADDRESS2 [22:26:11] it'll be accepted by the consensus rules, but the wallet does not have the functionality yet [22:26:19] i'll put a bounty if u create the issue 😉 [22:26:33] i'll create a bounty and issue [22:32:30] Not sure if I understand it, but is there a limit? If not could it not be used for a spam attack? [22:46:15] the limit would that the sum of all the pool fees is never more than 100% [22:51:44] I was thinking the stakes will be splittet to many addressed without tx fees. So that without limit every navoshi could be sent to a other address to spam the blockchain. But how I said I am not sure I understand the functionalty here. 🤐