Bible Pay

Read 12610 times

  • Rob Andrews
  • Administrator

    • 2275


    • 29
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #300 on: November 30, 2019, 09:51:48 AM »
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 19180
a1685482d58ba28526808dabe32b0794b8e5f72644b690bb35ff76bc6a48616b

Since 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.


Ok, good overall I suppose.  Thats great that GRC's points are showing in the leaderboard; just please let us know if it follows through with a payment too.  I assume it will.

On this sanctuary compile debacle, I have a hypothesis on that, because I have a similar problem compiling on my low end boxes.  I have a couple low-end for testnet and they are so low end they sometimes cant even finish the compile.  I can say this with certainty:  If cc1plus gets killed in the middle of a compile due to lack of ram, many times, the binary will already have the higher protocol version and the lower code (which is absolutely bad when you run it).  The way I personally had to solve this is make a compile script with 'cpulimit -l 45' (or something to that effect, if you want it I can post it) and it causes the compile to finish without getting killed.  Try that next time with a make clean first.  After that Ive had much better luck running it and leaving and then it starts back up successfully.

EDIT:  Just to clarify though, when I post a release the code is the latest; so it sounds like it *was* a compile issue.  (MIP then builds the linux binaries after the release is posted here).

EDIT2:  Starting with the last version, you can use -erasechain=1 again (we now delete all the files including instantsend.dat).  But, you shouldnt have to, unless we have a fork, and thats what we are trying to certify we dont have any more.  For example after this last release I did not erase my chain I just restarted the client.


« Last Edit: November 30, 2019, 10:11:58 AM by Rob Andrews »


  • sunk818
  • Sr. Member

    • 329


    • 11
    • April 24, 2018, 02:02:20 PM
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #301 on: November 30, 2019, 09:52:25 AM »
Ideally, I'd like to just do an exec associate user verification code and that's all I need to do to join podc 2.0.


i prefer everything else is done for me (create cpk, joining wcg, etc) and it sends out the daily podc update as long I have the wallet running.


  • Rob Andrews
  • Administrator

    • 2275


    • 29
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #302 on: November 30, 2019, 09:55:11 AM »

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.




I already posted my reply about this. 

Lets not spend more time on this or make assumptions.

Do the following:

Start a new wallet
Type 'exec createpurse'
Type 'exec boinc1' and paste the output.


Your current wallet is already successful.  Try with a new one - and do not manually edit the biblepay.conf file this time.

Do not paste third party representations of the data for the test.




  • sunk818
  • Sr. Member

    • 329


    • 11
    • April 24, 2018, 02:02:20 PM
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #303 on: November 30, 2019, 10:13:27 AM »
nevermind, I'm out of testing. This is no way to treat your testers.


  • Rob Andrews
  • Administrator

    • 2275


    • 29
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #304 on: November 30, 2019, 10:19:55 AM »
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 siginficant amount of time, and some 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.


« Last Edit: November 30, 2019, 12:06:34 PM by Rob Andrews »


  • sunk818
  • Sr. Member

    • 329


    • 11
    • April 24, 2018, 02:02:20 PM
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #305 on: November 30, 2019, 11:25:28 AM »

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%  ;D  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 -1
https://github.com/biblepay/biblepay-evolution/issues/26


One Click Mining Configuration corrupts biblepay.conf
https://github.com/biblepay/biblepay-evolution/issues/21


InstantSend not working - always confirms to 1 of 6
https://github.com/biblepay/biblepay-evolution/issues/17


Superblock Payment shows matured but requires 102 confirmations
https://github.com/biblepay/biblepay-evolution/issues/10


Runaway exception: bad lexical cast: source type value could not be interpreted as target
https://github.com/biblepay/biblepay/issues/102


One Click Miner Configuration writes tithing=1 instead of tithe=1
https://github.com/biblepay/biblepay/pull/87


exec bankroll: Signing transaction failed on locked wallet
https://github.com/biblepay/biblepay/issues/83


Invalid-tithe found from address xxx for amount of xxx
https://github.com/biblepay/biblepay/issues/81


Unable to mine... Cant sign block template with CPID - Error
https://github.com/biblepay/biblepay/issues/80


The auto-tithe feature was only tithing 90%.
https://github.com/biblepay/biblepay/issues/78


viewing PoG leaderboard causes crash if syncing blockchain <100k (pre-PoG)
https://github.com/biblepay/biblepay/issues/74


PoG Leaderboard - right click View makes QT wallet gets stuck
https://github.com/biblepay/biblepay/issues/73


PoG continues to auto tithe even though daily ~50k BBP donation was exceeded
https://github.com/biblepay/biblepay/issues/71


PODCUpdate: Unable to locate coins not marked as POG bankroll denominations.
https://github.com/biblepay/biblepay/issues/70


PoG Leadboard does show up in production
https://github.com/biblepay/biblepay/issues/67


1.1.5.4: InstantSend error: InstantSend doesn't support sending values that high yet.
https://github.com/biblepay/biblepay/issues/44


  • Rob Andrews
  • Administrator

    • 2275


    • 29
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #306 on: November 30, 2019, 12:09:32 PM »

I will admit some posted issues have been duds. We can't be 100%  ;D  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 -1
https://github.com/biblepay/biblepay-evolution/issues/26


One Click Mining Configuration corrupts biblepay.conf
https://github.com/biblepay/biblepay-evolution/issues/21


InstantSend not working - always confirms to 1 of 6
https://github.com/biblepay/biblepay-evolution/issues/17


Superblock Payment shows matured but requires 102 confirmations
https://github.com/biblepay/biblepay-evolution/issues/10


Runaway exception: bad lexical cast: source type value could not be interpreted as target
https://github.com/biblepay/biblepay/issues/102


One Click Miner Configuration writes tithing=1 instead of tithe=1
https://github.com/biblepay/biblepay/pull/87


exec bankroll: Signing transaction failed on locked wallet
https://github.com/biblepay/biblepay/issues/83


Invalid-tithe found from address xxx for amount of xxx
https://github.com/biblepay/biblepay/issues/81


Unable to mine... Cant sign block template with CPID - Error
https://github.com/biblepay/biblepay/issues/80


The auto-tithe feature was only tithing 90%.
https://github.com/biblepay/biblepay/issues/78


viewing PoG leaderboard causes crash if syncing blockchain <100k (pre-PoG)
https://github.com/biblepay/biblepay/issues/74


PoG Leaderboard - right click View makes QT wallet gets stuck
https://github.com/biblepay/biblepay/issues/73


PoG continues to auto tithe even though daily ~50k BBP donation was exceeded
https://github.com/biblepay/biblepay/issues/71


PODCUpdate: Unable to locate coins not marked as POG bankroll denominations.
https://github.com/biblepay/biblepay/issues/70


PoG Leadboard does show up in production
https://github.com/biblepay/biblepay/issues/67


1.1.5.4: InstantSend error: InstantSend doesn't support sending values that high yet.
https://github.com/biblepay/biblepay/issues/44


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.




  • MIP
  • Developer

    • 239


    • 27
    • February 13, 2018, 11:55:52 AM
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #307 on: November 30, 2019, 03:13:22 PM »
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


  • Rob Andrews
  • Administrator

    • 2275


    • 29
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #308 on: November 30, 2019, 03:37:56 PM »
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.


  • MIP
  • Developer

    • 239


    • 27
    • February 13, 2018, 11:55:52 AM
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #309 on: November 30, 2019, 04:08:03 PM »
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.


  • Rob Andrews
  • Administrator

    • 2275


    • 29
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #310 on: November 30, 2019, 04:17:08 PM »
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.




  • MIP
  • Developer

    • 239


    • 27
    • February 13, 2018, 11:55:52 AM
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #311 on: November 30, 2019, 05:01:54 PM »
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?


  • Rob Andrews
  • Administrator

    • 2275


    • 29
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #312 on: November 30, 2019, 05:24:41 PM »
BiblePay
1.4.8.3 - Leisure Upgrade for TestNet

- Fix bug preventing syncing from 0
- Fix 'exec rac' PODC transmission height
- Enhance 'exec sentgsc' to allow a CPK parameter to audit sent gscs by CPK
- Fix bug ensuring that unbanked cpids are included in the GSC
- Add warning when user executes sendgscc, if coin-age is low, that PODC rewards will be reduced.  Also add a warning to exec rac.

** This is the windows & self-compiled release **



  • Rob Andrews
  • Administrator

    • 2275


    • 29
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #313 on: November 30, 2019, 05:28:32 PM »
new version synced ok in my mac.

What can I test?

You can test the test cases in post #2.  Except, we don't need to test Cameroon-One or Kairos at this time (as Kairos is integrating now and expirimenting on their server).  We also don't need an extra sanc right now since we appear to have 7 going, but do monitor the situation if we get down to 3 again.

We primarily need to test PODC 2.0 and DWS.

I'll update when we are ready to test this branch against Prod; its not ready yet.



  • oncoapop
  • Full Member

    • 119


    • 12
    • October 23, 2018, 12:31:17 PM
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #314 on: November 30, 2019, 09:09:26 PM »
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.

I second what Rob said: your contributions are appreciated and acknowledged, Sunk And I am very happy that we will *all* be working together in bringing glory to our Lord and Saviour, Jesus Christ.