[01:05:22] Does someone have the bootstrap that works? the last 4.2.1 is stuck [02:26:07] @Santi what block is it stuck on? [02:49:29] @aguycalled Noticed that my transaction history in the Navcoin core wallet includes the .25 in each stake that goes to the community fund. However, when I search my wallet address on cryptoid the transaction history doesn't include the .25 in each stake going to community fund,. Was a little confused at first why the transaction histories were different, but once I realized it was due to community fund it wasn't a big [02:49:30] deal. However, wanted to point it out because wasn't sure if it was intended for transaction history in core wallet to show the .25 going to community fund in each stake. The only risk I see with how it currently is would be if someone started adding up all the staking amounts from their transaction history in core wallet they might be confused why the total coins in their wallet is lower than what the added together. [05:10:24] could u illustrate this with some screen capture? [07:48:22] @paul i'm resetting the testnet today, pushing a new genesis to cold staking branch [07:52:06] Great. I cant even get mine to compile at the moment. Qt issues again. [07:52:37] osx? unix? [07:52:44] what is the issue? [07:54:12] @paul [07:59:40] linux [08:00:00] think its a qt lib location error [08:00:07] checking for Qt < 5.4... no checking for static Qt plugins: -lqxcb -lxcb-static... no configure: WARNING: Could not resolve: -lqxcb -lxcb-static; navcoin-qt frontend will not be built [08:00:32] and / or version error [08:00:45] tracking it down now [08:01:03] daemon and cli build [08:03:20] can you tell me what qt version you are running qmake -v [08:09:53] $ qmake -v QMake version 3.0 Using Qt version 5.7.1 in /usr/local/Cellar/qt@5.7/5.7.1/lib [08:09:55] but im on osx [09:36:43] https://github.com/NAVCoin/navcoin-core/pull/241 [09:36:51] new pr @paul [09:44:17] @aguycalled approved [09:59:47] i suggest another variable for ban all nodes if version different from client [10:02:28] with current scenario ban version <4.2.1 [10:02:42] An option to ignore nodes on older versions perhaps [10:02:54] feel free to pr it 😉 [10:03:00] I don't think we need to ban nodes, it's just the only opt atm [10:03:14] I'll see what I can do @aguycalled hehe [11:29:19] Is strSubVersion the 004002001 type of versioning [11:40:25] @aguycalled how do we log to the logs or debug cnsole? [11:40:42] does std::cout work [11:43:49] LogPrintf("text %s\n", "moretext"); [11:43:55] and watch debug.log [11:46:45] I'm trying at add another flag -banversionstrict which will ban all nodes with a version =< bannedVersion [12:24:43] @aguycalled do nodes announce there version in a way that isn't a nice string like /NavCoin:4.2.1/? [12:49:50] *** Joins: rapofran (~rapofran@unaffiliated/rapofran) [12:50:07] *** Parts: rapofran (~rapofran@unaffiliated/rapofran) ("bye") [13:02:13] yes [13:02:21] ah [13:03:08] sorry out of home now cant check it [14:44:51] no worries