[00:18:53] @aguycalled Is it possible that being in regtest mode can produce unexpected scenarios that wouldn't exist on mainnet? [00:19:34] Examples are that I saw a paymentrequest change from accepted and paid back to pending and expired and funds returned to available [00:19:59] regtest lets you do things like roll back the blockchain, since you're the only node [00:20:33] And proposals ending in a locked state where even when not expired i can create paymentrequests but votes are never counted [00:20:42] also the settings are different for various things (CF acceptance criteria) but you are probably aware of that already [00:21:06] you could have found a bug, are you able to replicate it? [00:21:39] I was trying to replicate the first example, but discovered the second example. :/ [00:22:12] I'm almost convinced it is related to me creating multiple paymentrequests at the same time [00:22:30] if u could please document how to replicate it, ill review it [00:22:56] I'll have a go. [00:33:45] @Matt (Dev) Maybe related, but I see that when I generate a block in regtest it arrives with confirmations -1 and when I build on it doesnt improve [00:34:26] I thought a -1 confirmation suggested i'm building on a orphaned chain? [00:35:11] Or there are no confirmations in regtest... [00:38:56] 🤔 interesting [00:40:18] root@045853a2ab54:/# nav getinfo { ... "blocks": 2061, ... } root@045853a2ab54:/# nav generate 1 [ "a6c174441c28949b68ee1bfa0335fdd032d84c0996cef7d9a238e73846a0eec4" ] root@045853a2ab54:/# nav getblock a6c174441c28949b68ee1bfa0335fdd032d84c0996cef7d9a238e73846a0eec4 { "hash": "a6c174441c28949b68ee1bfa0335fdd032d84c0996cef7d9a238e73846a0eec4", "confirmations": -1, ... } root@045853a2ab54:/# nav generate 1 [ [00:40:18] "3874c79fc9ab1f1db7b297f6140f151e4148d67f63efffa2428a1a5d2d321cf7" ] root@045853a2ab54:/# nav getblock 3874c79fc9ab1f1db7b297f6140f151e4148d67f63efffa2428a1a5d2d321cf7 { "hash": "3874c79fc9ab1f1db7b297f6140f151e4148d67f63efffa2428a1a5d2d321cf7", "confirmations": -1, ... } [00:40:35] So actually I cant build on block 2061 [00:40:46] And that was what was causing votes to be ignored. [00:59:54] what does ur debug.log say [01:00:00] @prodpeak [01:01:52] Did you end up catching up with Paul and Craig today? @aguycalled [01:04:32] nope [06:12:15] Sorry went to bed [06:12:48] debug logs show this when generate 1 is called: 2018-10-31 06:11:43 keypool added key 481, size=101 2018-10-31 06:11:43 keypool reserve 381 2018-10-31 06:11:43 keypool keep 381 [06:12:53] @aguycalled [10:32:40] should show something more [11:29:55] I've still got my docker alive so I'll double check but pretty certain [11:36:46] @aguycalled confirmed just those three lines in debug.log [11:58:17] I think these steps replicate it: [11:58:20] u should see the new block updatetip line [11:58:21] navcoin-cli generate 800 navcoin-cli getnewaddress navcoin-cli createproposal 10000 10000 "Test 1" navcoin-cli donatefund 1000000 navcoin-cli generate 1 navcoin-cli proposalvote yes navcoin-cli createproposal 10000 10000 "Test 2" navcoin-cli generate 1 navcoin-cli proposalvote no navcoin-cli generate 180 navcoin-cli createpaymentrequest 500 "Test [11:58:21] 1" navcoin-cli createpaymentrequest 1000 "Test 2" navcoin-cli createpaymentrequest 1000 "Test 3" navcoin-cli generate 1 navcoin-cli paymentrequestvote yes navcoin-cli paymentrequestvote no navcoin-cli generate 180 navcoin-cli generate 180 navcoin-cli generate 180 navcoin-cli generate 180 navcoin-cli generate 180 navcoin-cli generate 180 navcoin-cli [11:58:22] createpaymentrequest 1000 "Test 4" navcoin-cli generate 1 [11:58:34] or the block rejection msg [11:59:11] 2018-10-31 11:56:42 CommitTransaction: CTransaction(hash=ed47b65958b6a327f5de80e5588a14b0b535cb38f78e311b49352855d9bc710e, nTime=1540987001, ver=5, vin.size=1, vout.size=2, nLockTime=2058), strDZeel={"h":"8b8c91c49a274529bb43339c) CTxIn(COutPoint(a136af9d79, 1), scriptSig=48304502210091c8d3acbba5, nSequence=4294967294) CTxOut(nValue=0.00010000, CommunityFundContribution) CTxOut(nValue=49.99880000, scriptPubKey=OP_DUP [11:59:11] OP_HASH160 bdc83d639a2f59e73cc471c28134afd85f876ad2 OP_EQUALVERIFY OP_CHECKSIG) 2018-10-31 11:56:42 keypool keep 444 2018-10-31 11:56:42 AddToWallet ed47b65958b6a327f5de80e5588a14b0b535cb38f78e311b49352855d9bc710e new 2018-10-31 11:56:42 AddToWallet ed47b65958b6a327f5de80e5588a14b0b535cb38f78e311b49352855d9bc710e 2018-10-31 11:56:42 Relaying wtx ed47b65958b6a327f5de80e5588a14b0b535cb38f78e311b49352855d9bc710e 2018-10-31 11:56:47 keypool added [11:59:12] key 545, size=101 2018-10-31 11:56:47 keypool reserve 445 2018-10-31 11:56:47 keypool keep 445 [11:59:22] This is the tail of the steps above [11:59:43] The last payment request being made and then the three keypool lines [12:00:46] nothing follows [12:01:12] I've noticed this for a while, that the regtest env eventually fails on me [12:01:52] I just accepted it previously and a non issue. Only since trying to replicate the paymentrequest being reset have i been paying more attention. *still cant replicate that [12:32:38] can u send me the whole log? [14:30:02] I've destroyed my docker. I'll run it again and send a full log [16:43:39] https://cdn.discordapp.com/attachments/416000318149754881/507233201178148884/debug.log [16:45:47] @aguycalled ^ here is my full log for the execution of the commands listed above [17:37:40] yeah im not able neither to generate more blocks in that case [17:37:56] digging whats going on [17:39:29] if i leave staking on [17:39:34] then i can generate blocks [17:39:48] so it looks like an issue with the generate command @prodpeak [17:41:27] if i generate an extra payment request it is correctly included through staking [17:47:04] Great. Thanks :) [17:54:54] not sure why its happening tho [17:54:58] ill put it on my todo list [17:55:15] but nothing applicable to mainnet [20:27:39] I can drop a ticket in Github with the details if you want one