Bible Pay

Read 105420 times

Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #285 on: November 17, 2017, 09:33:58 AM »
Thats very interesting.  Im honestly thinking, the Ryzen processor may be so fast that one mining thread is loading the AES512 encryption key partially in the core while the other receives a hash based on a faulty encryption key.  I did find a circumstance where I believe that is possible, so all this effort is definitely worth it, as this will "potentially" give us a stable biblehash, if this is the problem.

Ok, I tested the new version to ensure it yields the same hashes and mines in prod and testnet so I am checking it in.
Please grab 1061.

In this version, we use a different call to openssl's md5 (IE directly from the biblehash lib), we change our call to AES512 to be more efficient, and we set up a few miningparams once before we mine to not require those calls for every hash (so thats a slight improvement there too).  The biggest change, the one that might make or break this as the fix, is this:  I found the bibleminer was re-loading the encryption key for every hash, and that could be the problem.  I fixed this! So lets go ahead and try it again and see if it fixes.

Hey Rob, I finished updating one node and it is now mining on mainnet. How should I test that new version? Wait until I get an error in the log or should I spam the forensics command and see if I get different hashes again?


  • Rob Andrews
  • Administrator

    • 2602


    • 42
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #286 on: November 17, 2017, 09:38:57 AM »
Hey Rob, I finished updating one node and it is now mining on mainnet. How should I test that new version? Wait until I get an error in the log or should I spam the forensics command and see if I get different hashes again?

You can do both, go ahead and try to break it.

Yeah, we wont know its broken til it spurts out an error though....



Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #287 on: November 17, 2017, 09:45:04 AM »
Well well, I've been spamming the forensics command and I can happily say that it is now giving me the same hash no matter what!

However, with the same parameters but the block height, am I still getting the wrong hash for block 17078 and 17079 for example?

biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17078
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"

biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17079
{
  "Command": "biblehash",
  "BibleHash": "0000000000002aaa46b9dc122688a0e203a7ddec60b104c95c0f1372eb43e0dd"

Did you say 0011 was invalid?


  • Rob Andrews
  • Administrator

    • 2602


    • 42
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #288 on: November 17, 2017, 09:52:38 AM »
Well well, I've been spamming the forensics command and I can happily say that it is now giving me the same hash no matter what!

However, with the same parameters but the block height, am I still getting the wrong hash for block 17078 and 17079 for example?

biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17078
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"

biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17079
{
  "Command": "biblehash",
  "BibleHash": "0000000000002aaa46b9dc122688a0e203a7ddec60b104c95c0f1372eb43e0dd"

Did you say 0011 was invalid?

Im not able to reproduce that on 1061, I am running 1061 in testnet and moving from 78 to 79 still yields the 011 (not seeing the 2aaa).
What network are you in and is this definitely 1061?   Yeah, no changes should occur until you hit something like block 27000 etc.

Great on the improvement so far!  I bet we fixed it!  I bet this anomaly you found has a reason, such as cli being connected to 1060 :)


Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #289 on: November 17, 2017, 09:53:12 AM »
Im not able to reproduce that on 1061, I am running 1061 in testnet and moving from 78 to 79 still yields the 011 (not seeing the 2aaa).
What mode are you in and is this definitely 1061?   Yeah, no changes should occur until you hit something like block 27000 etc.

Great on the improvement so far!  I bet we fixed it!  I bet this anomaly you found has a reason, such as cli being connected to 1060 :)

Oh this is mainnet not testnet sorry


  • Rob Andrews
  • Administrator

    • 2602


    • 42
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #290 on: November 17, 2017, 09:56:30 AM »
Oh this is mainnet not testnet sorry
Let me restart in mainnet and try that....


  • Rob Andrews
  • Administrator

    • 2602


    • 42
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #291 on: November 17, 2017, 10:01:57 AM »
Oh this is mainnet not testnet sorry

Oh I see, OK we have a solid reason for this.  So in mainnet, tithe blocks are active til Christmas but in TestNet they are not.
Since the block the miner works on is n+1, if it will be an *upcoming* tithe block, the hash changes to be Higher, to allow the Diff to be Lower, so is normal for the blocks in Prod that will end in n+1 % 10 to be different, you can see if you increment the height up through n+9 no changes until you hit another tithe block.
Yeah, I confirm that hash is 011 in prod, and 2aaa for the tithe block :).

So far, so good! I guess I can let you burn in for a while longer.


This is excellent, this will most likely fix the reason we went out of sync twice in testnet.

EDIT:  THANKS ALEX FOR YOUR PERSEVERANCE AND FINDING THIS FLAW!!!!!



Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #292 on: November 17, 2017, 10:15:47 AM »
Oh I see, OK we have a solid reason for this.  So in mainnet, tithe blocks are active til Christmas but in TestNet they are not.
Since the block the miner works on is n+1, if it will be an *upcoming* tithe block, the hash changes to be Higher, to allow the Diff to be Lower, so is normal for the blocks in Prod that will end in n+1 % 10 to be different, you can see if you increment the height up through n+9 no changes until you hit another tithe block.
Yeah, I confirm that hash is 011 in prod, and 2aaa for the tithe block :).

So far, so good! I guess I can let you burn in for a while longer.


This is excellent, this will most likely fix the reason we went out of sync twice in testnet.

EDIT:  THANKS ALEX FOR YOUR PERSEVERANCE AND FINDING THIS FLAW!!!!!

Ohhhh ok that makes sense. Thanks for the explanation!

Haha thanks for the perseverance too. I must have ruined some of your nights! Glad I could help.

« Last Edit: November 17, 2017, 10:28:50 AM by Alex »


  • klondike
  • Full Member

    • 157


    • -10
    • October 10, 2017, 09:00:24 AM
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #293 on: November 17, 2017, 10:58:40 AM »
ROB im enabled now .... i was think,that when i run watchman ... PRE_ENABLED will be immediately ENABLED: we have to wait few minutes


  • togoshigekata
  • Sr. Member

    • 493


    • 25
    • September 01, 2017, 10:21:10 AM
    • USA
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #294 on: November 17, 2017, 12:09:46 PM »
Ok on Linux machine I just realized I never removed the banlist.dat file from the ~/.biblepaycore/testnet3 folder, woops,
I only had 2 connections before, now I have 12! Not sure how much this affected the retirement coin testing  :-\

I assume in the future we will want banlist.dat file?
Is there a linux command to delete the contents inside the file?
I just used rm (remove) command, but I assume that means I cant ban anyone going forward now.

===

Rebuilding/Resyncing Chain:

GUI:  Tools >> Wallet Repair >> Rebuild index
Linux:  ./biblepayd -daemon -reindex

===

Windows GUI Wallet is now v1.0.5.9
Linux Wallet is now v1.0.6.1
« Last Edit: November 17, 2017, 12:15:57 PM by togoshigekata »


  • Rob Andrews
  • Administrator

    • 2602


    • 42
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #295 on: November 17, 2017, 01:34:34 PM »
Ok on Linux machine I just realized I never removed the banlist.dat file from the ~/.biblepaycore/testnet3 folder, woops,
I only had 2 connections before, now I have 12! Not sure how much this affected the retirement coin testing  :-\

I assume in the future we will want banlist.dat file?
Is there a linux command to delete the contents inside the file?
I just used rm (remove) command, but I assume that means I cant ban anyone going forward now.

===

Rebuilding/Resyncing Chain:

GUI:  Tools >> Wallet Repair >> Rebuild index
Linux:  ./biblepayd -daemon -reindex

===

Windows GUI Wallet is now v1.0.5.9
Linux Wallet is now v1.0.6.1

Thanks, well that would have worked its way out after 24 hours as the max ban flag is one day, but yeah, I think Alexs discovery had a lot to do with our shrinking and decomposing network, with increasing banned nodes.

Since a few hours have passed I think the general consensus is that Alex hasnt found any new issues so I will probably ask you all to update to the latest version so we can do a pulse test of stability over the next 10 days.  Id like to see no banned nodes, no lost syncs, and a good masternode list.  But hold off for a couple hours as I am working on a feature we may be able to test together.

Regarding the retirement testing, I did find a bug in there, very minor, and its "technically" corrected in the last version but not tested.  Let me go ahead and test that first before we try more retirement tests.

The other thing is I am hoping to release e-commerce alpha soon.  Then we can test that also.


Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #296 on: November 17, 2017, 06:37:27 PM »
Just checked all my logs and Yup, no errors!

I've also successfully set up a masternode on testnet.


  • Rob Andrews
  • Administrator

    • 2602


    • 42
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #297 on: November 17, 2017, 07:02:48 PM »
Just checked all my logs and Yup, no errors!

I've also successfully set up a masternode on testnet.
Best thing I heard all week!  Great!  Thanks for the help!

Yeah, Im testing the new version and compiling one for windows now, and Im going to send it out as a highly recommended (just short of mandatory upgrade) to Prod & Testnet in a few hours.

(Cant go with Mandatory as it may upset CCEX).





  • Rob Andrews
  • Administrator

    • 2602


    • 42
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #298 on: November 18, 2017, 07:52:34 AM »
BiblePay - 1.0.6.1 Available
Mandatory Release for TestNet


- Fix checkblock(1) errors diagnosed with Alex that occasionally results in an invalid BibleHash
- Upgrade wallet graphics with new logo pack
- Show OpenSSL version in Tools | Info

www.biblepay.org | Downloads
https://github.com/biblepay/biblepay/





  • Rob Andrews
  • Administrator

    • 2602


    • 42
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #299 on: November 18, 2017, 08:04:28 AM »
I guess we can try another retirement trade.  Togo?  If not, anyone else?

You must be on 1061 to test retirement trading.  Windows is out there also.