Sorry, I had trouble with the re-syncing of two of those sancs following the recent upgrade. I had to delete the whole biblepay-evolution folder suggesting that there was some issue with the compilation which allowed me to start the wallet but somehow failed to sync after days... I have now just used the pre-compiled binaries and it is working fine as all of my testnet servers are at the top of the chain and can confirm your hash.>cli getblockhash 19180a1685482d58ba28526808dabe32b0794b8e5f72644b690bb35ff76bc6a48616bSince one of those wallets that would not sync was my controlling wallet, I could not perform an update_service to the POSE_BANNED sancs which I have now done and as far as I can see all 7 sancs on testnet are ENABLED.>list status{ "a46074dac98333269341fee5b712f795fdeaa615b276fee12175e1c537ce8a43-1": "ENABLED", "efbe80743321967f9d94b124b6670e3d87492e711f34acbe6fdada608007e055-0": "ENABLED", "24ba631e105c9f1d1923fe32d9c534e51556cddb15f625a5c42d5c902c868583-1": "ENABLED", "7570652f63502f29b610c4bf134f3d1d589c970c383b20a88545cd683c802130-1": "ENABLED", "7c30c4cf73a81ce8ebb90b3cd6bcda3c279d86fb044605b3f95f75a1657cd19e-1": "ENABLED", "c49f6f1e8fc8829b048abc37e790f4d6fc6364e05b9c433b77838ba575c15477-0": "ENABLED", "05a42edd711c8225b6febc0a422a0c8308dbd700d5ebd3b8af00571c7c5870d3-1": "ENABLED"}Finally, the Gridcoin RAC has been accumulating similarly to Biblepay RAC since the start of testnet PODCv2. I just noticed the higher coinage requirement and lower points on the leaderboard with the recent spork to add a higher requirement to gridcoin team members.
biblepay.conf is in Mac format according to Notepad++. This is on my Windows 10 64-bit Home edition.I can send you the file after I do exec createpurse.the line ending is 0d0d0a instead of 0d0a . I think I mentioned this in the github. I didn't mention it because it didn't seem relevant, but if wallet is not reading biblepay.conf that creates all sorts of Issues I noticed in the past.
nevermind, I'm out of testing. This is no way to treat your testers.
Just to clarify though Sun, you have been entering tickets in github with a lot of issues that have taken a significant [sic] amount of time that always ended up turning into non issues. MIP and I have taken a look at this and already explained that there is no "Mac" format and his external purse collateral works fine on his macs.You should be more respectful of our time. I only asked for a regimented test because we have spent a considerable amount of time on these things in total.
I will admit some posted issues have been duds. We can't be 100% all the time -- only Jesus. If you feel some issues are not worth investigating, then it is your job to prioritize or ignore them. I hope you can appreciate just how many issues don't reach you because many of us address it before it gets to you. > always ended up turning into non issues. Why would say "always". That sounds very dismissive of my contributions. I got tired so I had to stop before finishing...Here are some issues I posted in the past that required fixing... GSC Transmission for CameroonONE occurs even with -1https://github.com/biblepay/biblepay-evolution/issues/26One Click Mining Configuration corrupts biblepay.confhttps://github.com/biblepay/biblepay-evolution/issues/21InstantSend not working - always confirms to 1 of 6https://github.com/biblepay/biblepay-evolution/issues/17Superblock Payment shows matured but requires 102 confirmationshttps://github.com/biblepay/biblepay-evolution/issues/10Runaway exception: bad lexical cast: source type value could not be interpreted as targethttps://github.com/biblepay/biblepay/issues/102One Click Miner Configuration writes tithing=1 instead of tithe=1https://github.com/biblepay/biblepay/pull/87exec bankroll: Signing transaction failed on locked wallethttps://github.com/biblepay/biblepay/issues/83Invalid-tithe found from address xxx for amount of xxxhttps://github.com/biblepay/biblepay/issues/81Unable to mine... Cant sign block template with CPID - Errorhttps://github.com/biblepay/biblepay/issues/80The auto-tithe feature was only tithing 90%.https://github.com/biblepay/biblepay/issues/78viewing PoG leaderboard causes crash if syncing blockchain <100k (pre-PoG)https://github.com/biblepay/biblepay/issues/74PoG Leaderboard - right click View makes QT wallet gets stuckhttps://github.com/biblepay/biblepay/issues/73PoG continues to auto tithe even though daily ~50k BBP donation was exceededhttps://github.com/biblepay/biblepay/issues/71PODCUpdate: Unable to locate coins not marked as POG bankroll denominations.https://github.com/biblepay/biblepay/issues/70PoG Leadboard does show up in productionhttps://github.com/biblepay/biblepay/issues/671.1.5.4: InstantSend error: InstantSend doesn't support sending values that high yet.https://github.com/biblepay/biblepay/issues/44
I am trying to sync testnet but I am stuck at block 17444. I see many peers so I don't know how to get it updated.I will try to rescan and come back when ready
Actually if you are on 1.4.8.2, double check that, then delete 'instantsend.dat' and restart, and let us know?Let me know if it still re-hangs.
it's the latest version I compiled myself. I tried to delete bnstantsend.dat and rescan but still at 17444.
Ok, your right, sorry, I did not realize we introduced a bug in the latest version that prevents syncing from zero.Please stand by for a new leisure upgrade.
new version synced ok in my mac.What can I test?
Yes, you are right, sorry, I just read what I wrote and corrected it to say "some".Sorry, I apologize for coming across with that impression to you.Actually to clarify, all of your support contributions have been very welcome and helpful in detecting, diagnosing, and solving the bugs we had over the entire duration of BiblePay.Thank you for what you have already contributed.Hopefully we will be working together in this endeavor.