[00:07:43] You need to delete your regnetnchain [00:08:35] Otherwise there will be a Genesis block mismatch as it tries to make a new one but sees the old one. [00:10:49] I see, the changelog should probably be updated to make this more clear [00:11:07] Or the error message [00:12:04] That said, changelog is the easy fix. Updating the error message can always be done on a version 4.3.1 [00:12:37] There's a few QoL things we can probably throw into a minor version update [00:29:11] @Matt (Dev) you need to delete the regtest folder inside .navcoin4 [02:03:29] How does one write the version for -banlist=[version] ? [02:03:40] "4.2.1" or 4.2.1 dp [03:46:38] @aguycalled I was testing the vote recount, but when i invalidateblock the core ui quits with Segmentation fault (core dumped) [04:00:30] @aguycalled when invalidating block with payment requests the app exits with Segmentation fault (core dumped) [04:01:20] invalidating a block in the when a propsal vote is working fine. [04:02:04] Im just about to catch the ferry but will do some more digging and see what turns up [04:03:02] i will see if i can quicly replicate for you [04:05:09] also there is nothing in the debug log [04:10:11] Also the votes are only starting on voting cycle 2 [04:15:36] This is the commands i ran testing the block invalidation [04:15:36] https://cdn.discordapp.com/attachments/416000318149754881/478416306912362496/cmd [09:22:04] cool ill check it in a lil while [10:38:46] @aguycalled meet @Gal he is one of the AUT student getting into navcoin [10:39:09] I intro'ed them to the cfund today [10:39:16] Hi Alex, I just got into testing the community fund [10:41:01] And I have a question about the payment requests: if you've got a proposal for 1000 NAV, is it possible to stack up several payment requests that amount to more than 1000 NAV? [10:55:56] hi @Gal nice to have you here! [10:56:34] its not possible to requests payments of higher amount than the parent proposal [10:56:34] Thanks, it's exciting to be involved! [10:57:18] How about a sum of payments, for example requesting 4x500NAV on a 1500 NAV proposal? [10:57:30] oh sorry [10:57:37] I just re-read your answer [10:57:39] my bad [10:57:52] the 4th request wont be validated [10:58:31] I might have found a small glitch then, but I don't know if it's even valid [10:58:52] Because I just started with all this [10:59:02] The way I get to it is: [10:59:19] Create a proposal and accept it. [11:00:22] Once it's accepted, create 2 payment requests with the same name and (possibly) different amounts. [11:00:54] only one payment request will move to accepted state [11:01:05] once the first takes the coins [11:03:41] a prequest should never move to accepted state if there are no enough available coins in the parent proposal [11:06:18] Makes sense yeah. When I submitted the 2 requests within the same block, without generating any in between, the second one didn't display in the 'listproposals' [11:06:32] I could still vote on it and get the money though [11:06:55] And 'listproposals' didn't log the payment [11:07:59] But I couldn't get out more than what was listed in the proposal so this might just be a n RPC thing [11:09:35] I could vote on the other request and it was looping between 'pending' and 'waiting on period end' [11:19:23] Actually no, now it's stuck on "accepted waiting for end of voting period", but it never gets paid out [11:19:25] yeah as long as it never gets to accepted [11:21:51] Alright, thanks for clarifying! I'll look at it again tomorrow with fresh eyes [17:37:09] *** Joins: navcoin-bot3 (~navcoin-b@nav.community) [17:39:36] *** Quits: navcoin-bot (~navcoin-b@nav.community) (Read error: Connection reset by peer) [17:40:03] *** navcoin-bot3 is now known as navcoin-bot [23:52:41] @paul I got the Windows VM syncing in the background