[00:08:02] Ideally this is what release candidate means, [00:08:52] cfund is in beta, 4.3.0-rc is a release candidate [00:10:12] this is inline with all other projects [00:11:15] maybe NavCoin Core - Wallet [Release Canidate] [00:21:49] Yeah [00:21:56] That sounds good [00:23:53] @aguycalled, i just merged 4.3.0-rc into your cfund branch [00:24:21] I just want to work on it in one place [00:24:22] 😃 [03:23:22] @Matt (Dev) like this [03:23:23] https://cdn.discordapp.com/attachments/416000318149754881/477315998727274496/Screenshot_from_2018-08-10_15-22-18.png [03:23:51] Perfect [03:24:12] That's pretty much what I imagined haha [03:26:28] I have added config flags i have one for test builds as well [03:33:01] @aguycalled is there reason why these generated files are commited? [03:33:16] https://cdn.discordapp.com/attachments/416000318149754881/477318492215967749/Screenshot_from_2018-08-10_15-32-30.png [03:33:41] just asking before i untrack them [03:57:06] @aguycalled i have a pr for for ^ here: " " + [04:43:52] https://img.devrant.com/devrant/rant/r_219962_cFJ8j.jpg [04:44:35] me having to recomple the whole project [05:02:43] Any reason why I can't send? [05:02:43] https://cdn.discordapp.com/attachments/416000318149754881/477340999182712852/unknown.png [05:02:58] The address is owned by this wallet but I don't see why that is an issue [05:06:48] rpc command validateaddress needs to have it's help or man or whatever you call it, updated [05:07:02] Atm you wouldn't know you can use an openalias address with it [05:08:39] We should update this to mention you can use an OpenAlias address too [05:08:41] https://cdn.discordapp.com/attachments/416000318149754881/477342502194642944/unknown.png [05:09:47] I'll do a PR for this, but I'm not sure what to write for the help text. You guys can correct me if it's wrong lol [05:26:32] https://github.com/NAVCoin/navcoin-core/pull/271 [05:55:11] is this on 4.3.0? [06:29:30] @paul those headers are autogenerared at compile time dont push them [06:32:45] @Matt (Dev) most likely u are using 127.0.0.1 as your dns server and it does not support dnssec [06:36:23] Ok they have been previously committed. I will untrack them [06:39:36] try: - setting global env DNS_PUBLIC to 8.8.8.8 - -dnsserver=8.8.8.8 to the wallet on launch - look at the log file [06:42:26] @aguycalled just saw your comment. There was no rationale I just editedbthebold bitcoin copy that was there it use to say mining. I will remove it. [09:33:53] @aguycalled that's the most speedy proval I have ever received [09:33:59] 😉 [09:53:29] @aguycalled do you mind if i merge 4.3.0-rc into your cfund branch? [09:53:45] just trying to make it the source of truth [10:06:09] MacBook-Pro-de-alex:navcoin-core alex$ git checkout cfund-db Switched to branch 'cfund-db' Your branch is up-to-date with 'origin/cfund-db'. MacBook-Pro-de-alex:navcoin-core alex$ git merge v4.3.0-rc Already up-to-date. MacBook-Pro-de-alex:navcoin-core alex$ [10:26:45] i just merged some of my changes in [10:26:54] made the v4.4.0 [10:40:26] main.cpp: In function 'std::__cxx11::string GetWarnings(const string&)': main.cpp:5719:12: error: 'CLIENT_BUILD_IS_RELEASE_CANDIDATE' was not declared in this scope if(CLIENT_BUILD_IS_RELEASE_CANDIDATE) ^~~~~~~~~ main.cpp:5719:12: note: suggested alternative: 'CLIENT_VERSION_IS_RELEASE' if(CLIENT_BUILD_IS_RELEASE_CANDIDATE) ^~~~~~~~~ CLIENT_VERSION_IS_RELEASE In file included [10:40:27] from chain.h:15:0, from main.h:15, from main.cpp:7: util.h: At global scope: [10:40:31] getting this when tryingto build [10:40:35] @paul [10:41:24] hmm let me look [10:42:16] can you pull the cfund branch [10:43:38] @aguycalled [10:43:44] yes trying [10:44:42] you will need to ./autogen [10:44:51] and ./configure [10:48:01] building ? [10:52:45] waiting for it to finish [10:53:21] ok [10:53:52] me to, i just did a make distclean [10:53:58] and satarted again as well [10:54:45] with this sts.cpp:5: ./util.h:255:20: warning: ‘std::__cxx11::string random_string(size_t)’ defined but not used [-Wunused-function] [10:54:52] can we remove it? [10:54:57] or is it used? [10:55:09] its used on rpcwallet.cpp [10:55:15] ah ok [10:55:34] we can move it there [10:56:20] yea I might do next week, it just makes me ignore all the warnings [10:56:49] and there might be something in there that i care about one day 😉 [11:00:25] ok im all built [11:01:33] @aguycalled how did you get on? [11:02:44] still going [11:45:37] built [12:59:47] Is there a way currently to crate openalias addresses for testnet on nav.community? [13:08:06] Or any existing that I can use to test validation with? [13:38:29] i can manually add it @prodpeak [13:39:16] testnet@nav.community [13:39:19] should resolve to mrrbc7vGPsugGbhj8PYZq8HNQCUYGUVYnP [13:39:27] Thanks mate! [13:39:41] 😉 [13:39:42] perfect [13:40:09] Great that validateaddress multi purposes to openalias addresses as well [13:40:46] I hope people are aware that their navcoin address can be deduced from the openalias [13:41:52] I saw LordNelsson state he has linked three addresses to his main nav address. Hope that's not his staking address and he's leaking his balance to people [13:42:08] assume his openalias is lordnelsson@... [13:42:23] :p [13:59:59] *** Quits: navcoin-bot (~navcoin-b@nav.community) (Remote host closed the connection) [14:00:31] *** Joins: navcoin-bot (~navcoin-b@nav.community) [14:15:14] Well hmm [14:16:04] I wouldn't care too much as I can easily change adresses hehe [14:16:28] And I don't care about you seeing them atm [14:19:39] Since it's not too much and you cannot do anything with that [14:21:23] And ofc I know you can deduct the address from the open alias, how else would you be able to send coins to one hehe [14:22:06] Sure. Just thought maybe you'd be telling everyone how many millions you had 😃 [14:26:20] Yeah thank you anyways ;) [14:27:39] If one would want to take full advantage of the aliases and also keep their funds hidden, just use it on another wallet/address and send them through navtech [15:25:18] yep