[03:55:06] @salmonskinroll an easy way to check is delete the datadir (Mainnet) then start the client. With my testing it found peers/nodes in a few seconds after starting it. [03:55:18] yeah same for me as well [03:55:21] but is that it? [03:55:33] and i usually just fine 1 other connection [03:55:40] actaully no [07:16:54] @salmonskinroll yes, the purpose of the seed domain is to return a list of A records with IPs for other nodes [07:17:13] So when a fresh node goes online that does not have a peers.dat [07:17:23] It will attempt to get a list from the seed domain [07:17:30] And attempt to sync with those nodes [07:17:55] But once you have nodes connected the seed domain is no longer needed as you can ask for nodes from already connected nodes [07:18:01] This is how I understand it. [12:03:04] @salmonskinroll do you think you can review https://github.com/navcoin/navcoin-core/pull/636 [13:09:24] i've just found multithreaded script verification is constrained to 2 parallel job by default [13:09:27] @mxaddict [13:09:45] ill open a pr now [13:11:04] Isn't there a setting for that? [13:11:12] yes [13:11:13] -par [13:11:20] it was 2 by default [13:11:30] while 0 is auto [13:11:36] bitcoin has 0 by default [13:11:42] Ahh [13:11:49] That should help with faster machines [13:13:07] Were you able to check the changes to https://github.com/navcoin/navcoin-core/pull/636? [13:16:05] yes good catch, looks like i didnt commit correctly [13:16:36] What about the changes to the test? [13:18:32] yes they make sense [13:18:37] and its a good add [13:28:29] I approved the PR for verification threads [16:38:48] for 636, im seeing that the staking report is correct with the current master after orphaned blocks. am i missing something? [17:19:07] @roast was reporting wrong numbers [18:21:49] did the test fail on master and pass on the PR? Im just struggling to reproduce it but I think the code change seems simple enough [18:22:35] i tried on devnet and saw not completely accurate numbers invalidating blocks, sometimes they were right sometimes off [18:23:14] i see. im just lucky i guess. [18:40:24] i found a bug in #634 ill describe what i found in the pr [21:10:18] https://github.com/navcoin/navcoin-core/pull/634#issuecomment-556331539 @mxaddict @prole @salmonskinrolI [21:17:27] what does the first parameter of verify chain do? [21:17:37] the verification mode [21:17:40] 3 only disconnects [21:17:47] 4 disconnects and then reconnects [21:18:12] reconnecting chains means it's resyncing from described amount? [21:18:20] yes [21:18:29] it reconnects the same blocks it disconnected [21:18:44] what's the purpose of it? [21:18:51] it's the same blocks right? [21:19:27] verifies that blocks can be disconnected and connected again [21:19:47] even if it's the same blocks it's a good test for the logic [21:20:00] i see, good for the cfund stuff we're dealing with [21:23:28] good find, can how did you set up your test node to find it? is it the testnet you guys been working on? [21:23:54] ive found it in mainnet, but then replicated the issue on devnet [21:24:16] with the chain i've attached, but i think every chain with a payment request and/or payout would see this [23:17:28] what does satoshi_round mean in tests? [23:24:17] rounding the decimal numbers to the smallest acceptable units which is 1 satoshi?