[04:32:39] anyone know how to read this tx. was there 26870 nav created/earn as a stake? https://chainz.cryptoid.info/nav/block.dws?3124851.htm [04:36:44] https://chainz.cryptoid.info/nav/block.dws?3084531.htm [04:37:19] nope [04:37:47] the 26,868.99 NAV were an actual transaction written into the block [04:38:05] the hash below it for 1,225.5411 NAV, that was the staking address [04:38:20] some one payed in fees as error? [04:38:21] notice the last hash out value is 2 NAV > [04:38:26] it wasn't fees [04:38:36] they literally sent 26,868.99 NAV [04:38:48] i forget how much the transaction fee is now [04:38:55] something ridiculously low [04:38:59] .00002 NAV or something [04:39:25] Created 26,870.99 NAV [04:39:53] 0 Generation + Fees N/A 26,868.99 NAV [04:39:59] https://chainz.cryptoid.info/nav/tx.dws?6870012.htm [04:41:53] let's check navexplorer [04:42:07] i'm thinking this might be because chainz doesn't support cold staking [04:42:32] Community Fund Payout [04:42:36] ah kk. [04:42:47] i was thinking gotta be com fund [04:42:58] https://www.navexplorer.com/block/3124851 [04:43:12] i should have checked this explorer first : ) [04:44:46] it's something to do with cold staking [04:44:48] https://www.navexplorer.com/address/Ncjpj4GU5RfSsYTLzpzqnKWYFa3YzqVihd [04:44:55] i traced some of the nav to that address [04:44:58] it's a cold staking address [04:45:16] ah yeah that makes sense [04:46:30] i like to watch chainz over view page here and there. and saw that damn 26k nav staked in a day and was wondering wt.. was that [09:56:55] I have updated my navcoin-core but 8hours they are still saying "synchronizing clock attempt" which I doesn't understand @Juguelio [10:07:44] @cryptoeye might be that you can't connect to NTP servers for clock sync [10:07:59] Is your network behind a firewall? [10:08:06] Maybe NTP port is blocked [10:21:50] Even the next wallet too is the same problem I'm having with it [11:36:12] Yes, if core is having NTP issue, then NEXT would have it too as NEXT wallet runs navcoin-core as a backend [11:41:31] @cryptoeye maybe your network connection is blocking UDP port 123? [11:41:45] I think that is what is used by standard NTP connections [11:54:52] @mxaddict i can't use qt creator debugger anymore since last updates, any clue why could it be? [11:57:00] You mean on my patch? [11:57:02] Or on master? [11:57:06] @aguycalled [11:57:30] on your patch [11:58:12] well actually its not working on master neither [12:02:39] im going to upgrade creator [12:12:17] looks like compiler is not seeing -g [12:13:27] reconfiguring with --enable-debug it used to be enabled by default [12:13:28] Hmm, I can't really help, I don't use QT Debugger ( I don't know how to use it yet ) 😄 [12:14:36] Maybe it was a change in 4.6.0? [12:17:28] now it works had to configure with --enable-debug [12:25:55] 👌 [12:46:11] @aguycalled [12:46:22] I'm not sure where we left off on this PR discussion https://github.com/navcoin/navcoin-core/pull/485 [12:46:36] I'm a little confused by what you mean about the changes [12:46:54] Did you mean to only have 1 attribute for average? [12:47:17] So IE you have a 15 day old wallet, then you see "Last 15 Days Avg" ? [12:49:04] nope, i meant how the calculation is made [12:50:08] Ahh [12:50:17] So just modify the calculations not the name [12:50:18] Gotcha [12:50:40] I see you're making good progress on the cfunddb changes [12:50:43] 👌 [12:53:58] yeah, wanted to have it today, want to move to other things soon [13:41:15] @mxaddict next thing i will do when done with this is test all your prs [13:45:43] Nice [13:45:53] I'm about done with my desk job stuff 😄 [13:46:08] I'm gonna make the changes to the report [13:46:23] Then maybe work on some GUI stuff (I saw an issue for GUI about block sync details)