Bible Pay

Read 66526 times

  • Rob Andrews
  • Administrator

    • 2045


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #255 on: November 16, 2017, 06:55:04 pm »
I got some errors for you  8)

https://pastebin.com/NaHRQBi7

Also I'm not sure if you saw it but this is what I got on mainnet just before switching that box to testnet

Oh good, thanks :).

Oh I see its in mainnet, so that should be easy to research, hopefully.

Will check it out right now.



  • Rob Andrews
  • Administrator

    • 2045


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #256 on: November 16, 2017, 07:28:35 pm »
I got some errors for you  8)

https://pastebin.com/NaHRQBi7

Also I'm not sure if you saw it but this is what I got on mainnet just before switching that box to testnet


Thanks, this is extremely helpful as we went out of sync in testnet a couple times, like I said I saw this error a few times in prod in random logs, but it was so elusive I couldnt reproduce it.  Luckily, it looks like our advanced forensic logging yielding some info (knock on wood).  Lets hope we can get to the bottom of this in only a few passes.  Id hate to see this take a month to fix.

Anyway heres what I am seeing.  On the extremely bright side, I am generating the exact same biblehashes as your node was at the time of the problem.  Thats good, because I didnt want to see some type of non-deterministic biblehash.  So to follow me on that part of it, the biblehash requires 4 inputs, for example your first checkblock error requires me to run this command:


exec biblehash 333e1c9e6fc52027012f734b2b701a3325591759ec6f29686879faae98a4b585 1510797674 1510797171 16911
yielding biblehash: 0000000000072c18e0c42605b5431bd2e2343ced7942038c6a39f76ffa077225

Which matches yours, so that is great.

Next I checked the bits in that block that yields the difficulty and therefore the targethash which matches your targethash in the checkblock message. 

Here is where it gets interesting.  If you convert the hex to decimal (if you need to unless you can do this in your head) the biblehash with a 7a7 prefix must be Lower than the uint256 target (947e).  The 7a7 is 1959 decimal and the 947e is 38014, meaning that it passes. 

So basically what I am saying here is your arithmetic library is failing to calculate the less than operator here (LOL).  I know it sounds strange, now Bitcoin is using something called UintToArith256  to convert the uint256 big number to an arithmetic vector, allowing the math problem to be performed.  So of course that leads me to wonder how can the node function at all if that less than is failing? LOL.  So I move on and I tested the next two examples.  Same issue:  677a (26490) is less than (43096) meaning that the test should have passed, and the block was good and the error was a bad call.
Next 72c1 < 7e28: same issue, block was good, bad call.

So what Im going to do now is Ill add some more code to store the biblehash before its compared, and then compare it, then store it again and log both the original and the compared values in the log, then we can see if somehow, your biblehash changes between the hash and the comparison.  Because obviosly you are doing math for all other blocks. 

Alright Ill be back in about a half hour with the new version.

Good Job.




Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #257 on: November 16, 2017, 07:39:29 pm »
Welp that is indeed really strange since it's not failing on every block! There must be something special about these numbers :P

It will be interesting to see what the issue is/was.


  • Rob Andrews
  • Administrator

    • 2045


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #258 on: November 16, 2017, 07:46:30 pm »
Welp that is indeed really strange since it's not failing on every block! There must be something special about these numbers :P

It will be interesting to see what the issue is/was.

Yeah, it will have to reveal itself as either a vector problem in the biblehash accessor, or a problem in that arithmetic lib, or it could even be a BOOST lib issue, maybe one particular boost lib in your version being manipulated a certain way before the call, Oh who knows :)

Anyway, I just pushed out 1.0.6.0 if you want to run that for a while until we get more examples. 


Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #259 on: November 16, 2017, 07:49:11 pm »
Yeah, it will have to reveal itself as either a vector problem in the biblehash accessor, or a problem in that arithmetic lib, or it could even be a BOOST lib issue, maybe one particular boost lib in your version being manipulated a certain way before the call, Oh who knows :)

Anyway, I just pushed out 1.0.6.0 if you want to run that for a while until we get more examples.

Doing that now, would like me to run on testnet or mainnet?


  • Rob Andrews
  • Administrator

    • 2045


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #260 on: November 16, 2017, 07:58:27 pm »
Doing that now, would like me to run on testnet or mainnet?
Mainnet is probably better.


Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #261 on: November 16, 2017, 08:03:14 pm »
Mainnet is probably better.

Alright, finished upgrading a few nodes so hopefully we will get something quickly.


Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #262 on: November 16, 2017, 09:09:20 pm »
Not sure if you're still around Rob but I just got that

2017-11-17 02:43:04 ProcessNewBlock : ACCEPTED
2017-11-17 02:56:42 CheckProofOfWork(1.0): BlockHash d07f0bd5d5fbebd8317309465b14c5ab94684f41d68944c0aab938d306ab60fb, ProdChain TRUE, SSLVersion OpenSSL 1.0.1t  3 May 2016, BlockTime 1510887401.000000, PrevBlockTime 1510886577.000000, BibleHash1 0004010c0376b246463104ca838735effd6c8d9d8294084276cf15bb4fd602c7, BibleHash2 0004010c0376b246463104ca838735effd6c8d9d8294084276cf15bb4fd602c7, TargetHash 0000000000074772000000000000000000000000000000000000000000000000, Forensics exec biblehash d07f0bd5d5fbebd8317309465b14c5ab94684f41d68944c0aab938d306ab60fb 1510887401 1510886577 17065
2017-11-17 02:56:42 ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 17065.000000 pindexPrev 7ec3beeb8f2710d57961c2a75687578b19687f7d219d6a062037c764bcb1f712
2017-11-17 02:56:42 ERROR: CheckBlockHeader(): proof of work failed
2017-11-17 02:56:42 Misbehaving: 35.199.177.240:40000 (0 -> 5)
2017-11-17 02:56:42 ERROR: invalid header received d07f0bd5d5fbebd8317309465b14c5ab94684f41d68944c0aab938d306ab60fb
2017-11-17 02:56:42 UpdateTip: new best=d07f0bd5d5fbebd8317309465b14c5ab94684f41d68944c0aab938d306ab60fb  height=17066  log2_work=57.808768  tx=28757  date=2017-11-17 02:56:41 progress=1.000000  cache=0.0MiB(7tx)
--
2017-11-17 02:58:23 ProcessNewBlock : ACCEPTED
2017-11-17 03:03:54 CheckProofOfWork(1.0): BlockHash de3fdeb9096b6eca09358af07e7f126a6064a00024ca86f361e0b23233d13261, ProdChain TRUE, SSLVersion OpenSSL 1.0.1t  3 May 2016, BlockTime 1510887834.000000, PrevBlockTime 1510887502.000000, BibleHash1 0016bc69d09c727fedfac1fda865bf9666d94e4a20d02527c18efebeaaea19fb, BibleHash2 0016bc69d09c727fedfac1fda865bf9666d94e4a20d02527c18efebeaaea19fb, TargetHash 000000000008528c000000000000000000000000000000000000000000000000, Forensics exec biblehash de3fdeb9096b6eca09358af07e7f126a6064a00024ca86f361e0b23233d13261 1510887834 1510887502 17067
2017-11-17 03:03:54 ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 17067.000000 pindexPrev 8c7665df98db007329275eb36a43f6f4d735324af64728e787811dc7d0079578
2017-11-17 03:03:54 ERROR: CheckBlockHeader(): proof of work failed
2017-11-17 03:03:54 Misbehaving: 51.15.89.39:40000 (0 -> 5)
2017-11-17 03:03:54 ERROR: invalid header received de3fdeb9096b6eca09358af07e7f126a6064a00024ca86f361e0b23233d13261
2017-11-17 03:03:54 UpdateTip: new best=de3fdeb9096b6eca09358af07e7f126a6064a00024ca86f361e0b23233d13261  height=17068  log2_work=57.809114  tx=28759  date=2017-11-17 03:03:54 progress=1.000000  cache=0.0MiB(9tx)


  • Rob Andrews
  • Administrator

    • 2045


    • 27
    • June 05, 2017, 08:09:04 pm
    • Patmos, Island Of
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #263 on: November 16, 2017, 09:53:41 pm »
Not sure if you're still around Rob but I just got that

2017-11-17 02:43:04 ProcessNewBlock : ACCEPTED
2017-11-17 02:56:42 CheckProofOfWork(1.0): BlockHash d07f0bd5d5fbebd8317309465b14c5ab94684f41d68944c0aab938d306ab60fb, ProdChain TRUE, SSLVersion OpenSSL 1.0.1t  3 May 2016, BlockTime 1510887401.000000, PrevBlockTime 1510886577.000000, BibleHash1 0004010c0376b246463104ca838735effd6c8d9d8294084276cf15bb4fd602c7, BibleHash2 0004010c0376b246463104ca838735effd6c8d9d8294084276cf15bb4fd602c7, TargetHash 0000000000074772000000000000000000000000000000000000000000000000, Forensics exec biblehash d07f0bd5d5fbebd8317309465b14c5ab94684f41d68944c0aab938d306ab60fb 1510887401 1510886577 17065
2017-11-17 02:56:42 ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 17065.000000 pindexPrev 7ec3beeb8f2710d57961c2a75687578b19687f7d219d6a062037c764bcb1f712
2017-11-17 02:56:42 ERROR: CheckBlockHeader(): proof of work failed
2017-11-17 02:56:42 Misbehaving: 35.199.177.240:40000 (0 -> 5)
2017-11-17 02:56:42 ERROR: invalid header received d07f0bd5d5fbebd8317309465b14c5ab94684f41d68944c0aab938d306ab60fb
2017-11-17 02:56:42 UpdateTip: new best=d07f0bd5d5fbebd8317309465b14c5ab94684f41d68944c0aab938d306ab60fb  height=17066  log2_work=57.808768  tx=28757  date=2017-11-17 02:56:41 progress=1.000000  cache=0.0MiB(7tx)
--
2017-11-17 02:58:23 ProcessNewBlock : ACCEPTED
2017-11-17 03:03:54 CheckProofOfWork(1.0): BlockHash de3fdeb9096b6eca09358af07e7f126a6064a00024ca86f361e0b23233d13261, ProdChain TRUE, SSLVersion OpenSSL 1.0.1t  3 May 2016, BlockTime 1510887834.000000, PrevBlockTime 1510887502.000000, BibleHash1 0016bc69d09c727fedfac1fda865bf9666d94e4a20d02527c18efebeaaea19fb, BibleHash2 0016bc69d09c727fedfac1fda865bf9666d94e4a20d02527c18efebeaaea19fb, TargetHash 000000000008528c000000000000000000000000000000000000000000000000, Forensics exec biblehash de3fdeb9096b6eca09358af07e7f126a6064a00024ca86f361e0b23233d13261 1510887834 1510887502 17067
2017-11-17 03:03:54 ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 17067.000000 pindexPrev 8c7665df98db007329275eb36a43f6f4d735324af64728e787811dc7d0079578
2017-11-17 03:03:54 ERROR: CheckBlockHeader(): proof of work failed
2017-11-17 03:03:54 Misbehaving: 51.15.89.39:40000 (0 -> 5)
2017-11-17 03:03:54 ERROR: invalid header received de3fdeb9096b6eca09358af07e7f126a6064a00024ca86f361e0b23233d13261
2017-11-17 03:03:54 UpdateTip: new best=de3fdeb9096b6eca09358af07e7f126a6064a00024ca86f361e0b23233d13261  height=17068  log2_work=57.809114  tx=28759  date=2017-11-17 03:03:54 progress=1.000000  cache=0.0MiB(9tx)

Whats very strange is in these two examples, the exec biblehash command does not produce the same output as the error.  This is very strange, especially since each of your error messages we call it twice.

Anyway, I have to close out soon, in the mean time, what does your node report for this command in prod:

exec biblehash de3fdeb9096b6eca09358af07e7f126a6064a00024ca86f361e0b23233d13261 1510887834 1510887502 17067

Mine reports : 000000000005fc7360c14e1b6c3d3a7530d27e942b928bdb17c8801fdafc19ba
Which is a different hash than the error message reports.



Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #264 on: November 16, 2017, 10:04:01 pm »
Whats very strange is in these two examples, the exec biblehash command does not produce the same output as the error.  This is very strange, especially since each of your error messages we call it twice.

Anyway, I have to close out soon, in the mean time, what does your node report for this command in prod:

exec biblehash de3fdeb9096b6eca09358af07e7f126a6064a00024ca86f361e0b23233d13261 1510887834 1510887502 17067

Mine reports : 000000000005fc7360c14e1b6c3d3a7530d27e942b928bdb17c8801fdafc19ba
Which is a different hash than the error message reports.

biblepay-cli exec biblehash de3fdeb9096b6eca09358af07e7f126a6064a00024ca86f361e0b23233d13261 1510887834 1510887502 17067
{
  "Command": "biblehash",
  "BibleHash": "000000000005fc7360c14e1b6c3d3a7530d27e942b928bdb17c8801fdafc19ba"
}

Same thing as yours


  • tiras
  • Jr. Member

    • 57


    • 1
    • September 01, 2017, 02:00:09 pm
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #265 on: November 16, 2017, 10:41:36 pm »
all nodes on testnet are down except for 1 :
./biblepay-cli masternode list
{
  "04ca4bd54153476e6d19b72dc26bc27b74cdbbd687aea07c6cc1cd2182beab60-1": "ENABLED",
  "a23321871670924fa669c26284aeb9b36987d6bb3d7a590eaf2b5406b85201f4-1": "WATCHDOG_EXPIRED",
  "a27ae7dcc93df0ff266d2f11cb906f4929b7ad7d6b46bc98c192ac7998aa1058-1": "WATCHDOG_EXPIRED",
  "8ff3d83216612e2c79a36c5f66f191b34a07eb1d01600b104a76b3151de9e7f6-1": "WATCHDOG_EXPIRED",
  "78a235e8d3427b7fec1a0f3635cf3aeb2dbf7d0d53c44578815060d80280a271-1": "WATCHDOG_EXPIRED",
  "7b3873de1969b087f63cd287c64694b14250aecf7779c67f68691533a6616f3c-1": "NEW_START_REQUIRED",
  "d183b913e7a4b95c0202bf15d296e00bbdf0bedce317e340985a2c78af06cba4-1": "WATCHDOG_EXPIRED",
  "404f50700e2ffc8c4adb76bea92fb572584b1f3e24ec736d6883a64cc88417fb-1": "WATCHDOG_EXPIRED",
  "be3eaf8322909bbb150d89058bf261f0a2bf96369c8928313a3d69e2d5087add-1": "WATCHDOG_EXPIRED",
  "e413e134f7ecb6388ddfe401870f1e0ba602479abb8de8a5bf78c59c4087ee28-1": "NEW_START_REQUIRED",
  "b0cfdfa2194556e211099bc620a7e27487958aa5774db0c78ded0f839e3105d2-1": "NEW_START_REQUIRED",
  "c5a8405cbc39dd97004a64c1db586313ed25f3c4553ca59a0bdad30dd0c551d5-1": "NEW_START_REQUIRED",
  "44d550fef16c8bc5e340599cddbd6d98736218e1900f92b4625768e5830abfd0-1": "NEW_START_REQUIRED",
  "847be5b647856e9b030d785d7bc82f146362371a28663348e7a3d28df3e38c55-1": "WATCHDOG_EXPIRED"


I upgraded mine to 1.0.6    and after re-syncing it's showing "watchdog expired"   .  Watchdog is running with no errors. I didn't touch it.

  "78a235e8d3427b7fec1a0f3635cf3aeb2dbf7d0d53c44578815060d80280a271-1": "WATCHDOG_EXPIRED",


  • tiras
  • Jr. Member

    • 57


    • 1
    • September 01, 2017, 02:00:09 pm
    more
Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #266 on: November 16, 2017, 11:07:29 pm »
all nodes on testnet are down except for 1 :
./biblepay-cli masternode list
{
  "04ca4bd54153476e6d19b72dc26bc27b74cdbbd687aea07c6cc1cd2182beab60-1": "ENABLED",
  "a23321871670924fa669c26284aeb9b36987d6bb3d7a590eaf2b5406b85201f4-1": "WATCHDOG_EXPIRED",
  "a27ae7dcc93df0ff266d2f11cb906f4929b7ad7d6b46bc98c192ac7998aa1058-1": "WATCHDOG_EXPIRED",
  "8ff3d83216612e2c79a36c5f66f191b34a07eb1d01600b104a76b3151de9e7f6-1": "WATCHDOG_EXPIRED",
  "78a235e8d3427b7fec1a0f3635cf3aeb2dbf7d0d53c44578815060d80280a271-1": "WATCHDOG_EXPIRED",
  "7b3873de1969b087f63cd287c64694b14250aecf7779c67f68691533a6616f3c-1": "NEW_START_REQUIRED",
  "d183b913e7a4b95c0202bf15d296e00bbdf0bedce317e340985a2c78af06cba4-1": "WATCHDOG_EXPIRED",
  "404f50700e2ffc8c4adb76bea92fb572584b1f3e24ec736d6883a64cc88417fb-1": "WATCHDOG_EXPIRED",
  "be3eaf8322909bbb150d89058bf261f0a2bf96369c8928313a3d69e2d5087add-1": "WATCHDOG_EXPIRED",
  "e413e134f7ecb6388ddfe401870f1e0ba602479abb8de8a5bf78c59c4087ee28-1": "NEW_START_REQUIRED",
  "b0cfdfa2194556e211099bc620a7e27487958aa5774db0c78ded0f839e3105d2-1": "NEW_START_REQUIRED",
  "c5a8405cbc39dd97004a64c1db586313ed25f3c4553ca59a0bdad30dd0c551d5-1": "NEW_START_REQUIRED",
  "44d550fef16c8bc5e340599cddbd6d98736218e1900f92b4625768e5830abfd0-1": "NEW_START_REQUIRED",
  "847be5b647856e9b030d785d7bc82f146362371a28663348e7a3d28df3e38c55-1": "WATCHDOG_EXPIRED"


I upgraded mine to 1.0.6    and after re-syncing it's showing "watchdog expired"   .  Watchdog is running with no errors. I didn't touch it.

  "78a235e8d3427b7fec1a0f3635cf3aeb2dbf7d0d53c44578815060d80280a271-1": "WATCHDOG_EXPIRED",

looks ok now :

Code: [Select]
./biblepay-cli masternode list
{
  "04ca4bd54153476e6d19b72dc26bc27b74cdbbd687aea07c6cc1cd2182beab60-1": "ENABLED",
  "a23321871670924fa669c26284aeb9b36987d6bb3d7a590eaf2b5406b85201f4-1": "ENABLED",
  "a27ae7dcc93df0ff266d2f11cb906f4929b7ad7d6b46bc98c192ac7998aa1058-1": "WATCHDOG_EXPIRED",
  "8ff3d83216612e2c79a36c5f66f191b34a07eb1d01600b104a76b3151de9e7f6-1": "WATCHDOG_EXPIRED",
  "78a235e8d3427b7fec1a0f3635cf3aeb2dbf7d0d53c44578815060d80280a271-1": "ENABLED",
  "7b3873de1969b087f63cd287c64694b14250aecf7779c67f68691533a6616f3c-1": "NEW_START_REQUIRED",
  "d183b913e7a4b95c0202bf15d296e00bbdf0bedce317e340985a2c78af06cba4-1": "ENABLED",
  "404f50700e2ffc8c4adb76bea92fb572584b1f3e24ec736d6883a64cc88417fb-1": "ENABLED",
  "be3eaf8322909bbb150d89058bf261f0a2bf96369c8928313a3d69e2d5087add-1": "EXPIRED",
  "e413e134f7ecb6388ddfe401870f1e0ba602479abb8de8a5bf78c59c4087ee28-1": "NEW_START_REQUIRED",
  "b0cfdfa2194556e211099bc620a7e27487958aa5774db0c78ded0f839e3105d2-1": "NEW_START_REQUIRED",
  "c5a8405cbc39dd97004a64c1db586313ed25f3c4553ca59a0bdad30dd0c551d5-1": "NEW_START_REQUIRED",
  "44d550fef16c8bc5e340599cddbd6d98736218e1900f92b4625768e5830abfd0-1": "NEW_START_REQUIRED",
  "847be5b647856e9b030d785d7bc82f146362371a28663348e7a3d28df3e38c55-1": "EXPIRED"


Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #267 on: November 17, 2017, 12:50:17 am »
I got an error message on a different node than the one in my previous post. The exec biblehash command result also doesn't seem to match what's in the log.

2017-11-17 03:52:37 ProcessNewBlock : ACCEPTED
2017-11-17 04:18:58 CheckProofOfWork(1.0): BlockHash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347, ProdChain TRUE, SSLVersion OpenSSL 1.0.1t  3 May 2016, BlockTime 1510892191.000000, PrevBlockTime 1510890756.000000, BibleHash1 00122557bcb25dd4eb7085498a23c566de5e187a11d6655685f61333f40ae11a, BibleHash2 00122557bcb25dd4eb7085498a23c566de5e187a11d6655685f61333f40ae11a, TargetHash 00000000000395f6000000000000000000000000000000000000000000000000, Forensics exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17074
2017-11-17 04:18:58 ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 17074.000000 pindexPrev b8f34304d7ce0ef3e10f4ea7812d4c85e2e6fd93a72cd51f128eaa32bede2dd6
2017-11-17 04:18:58 ERROR: CheckBlockHeader(): proof of work failed
2017-11-17 04:18:58 Misbehaving: 80.211.200.215:52172 (0 -> 5)
2017-11-17 04:18:58 ERROR: invalid header received e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347
2017-11-17 04:18:58 UpdateTip: new best=e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347  height=17075  log2_work=57.811358  tx=28767  date=2017-11-17 04:16:31 progress=0.999994  cache=0.0MiB(20tx)

On the exact same node I use the forensic command and get a different biblehash again..how strange!

biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17074
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"
}
« Last Edit: November 17, 2017, 01:05:32 am by Alex »


Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #268 on: November 17, 2017, 12:55:23 am »
Wow I just noticed something strange. I was spamming the forensic command and got different results?? One of them seems to match what I got in the logs!

[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17074
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"
}
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17074
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"
}
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17074
{
  "Command": "biblehash",
  "BibleHash": "00122557bcb25dd4eb7085498a23c566de5e187a11d6655685f61333f40ae11a"
}
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17074
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"
« Last Edit: November 17, 2017, 04:19:10 am by Alex »


Re: BIBLEPAY - TESTNET THREAD - TESTING SANCTUARIES FOR GO LIVE AT CHRISTMAS
« Reply #269 on: November 17, 2017, 01:03:51 am »
Just started a VM to try it and I also managed to get different biblehash!

Note: The mn4 machine above is running OpenSSL 101t while this one is running OpenSSL 102g

}
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17074
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"
}
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17074
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"
}
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17074
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"
}
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17074
{
  "Command": "biblehash",
  "BibleHash": "0014bf432d9989ac1e7a93a8918e37b4aa9694f82fa3d86684a249f2c444394d"
}
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17074
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"
}

Trying on a different machine with OpenSSL 101t

[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17074
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"
}
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17074
{
  "Command": "biblehash",
  "BibleHash": "00122557bcb25dd4eb7085498a23c566de5e187a11d6655685f61333f40ae11a"
}
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17074
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"
}
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17074
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"

[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17074
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"
}
---
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17074
{
  "Command": "biblehash",
  "BibleHash": "0014bf432d9989ac1e7a93a8918e37b4aa9694f82fa3d86684a249f2c444394d"


Managed to get 3 different results! one matching what I got with mn4 and OpenSSL101t and the other matching what I got with the vm on Openssl102g. I think I can probably get all 3 different biblehash (if not more) on all 3 machines.

Edit: Doing some more tests, Is it normal to get these results when changing the prev block reference?


[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17079
{
  "Command": "biblehash",
  "BibleHash": "0000000000002aaa46b9dc122688a0e203a7ddec60b104c95c0f1372eb43e0dd" <= same result with block 17069
}
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17078
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"

[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17074
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"
}
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17073
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"
}
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17072
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"
}
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17071
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"
}
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17070
{
  "Command": "biblehash",
  "BibleHash": "0000000000011c6f2cd7107900e4308d6db47227d9f1753e65b9d6fe206f3072"
}
[email protected] ~ # biblepay-cli exec biblehash e0118ac9c4b5f6ec508e4bfefc38599fd55e7f79d108a560aeff9ceb0debc347 1510892191 1510890756 17069
{
  "Command": "biblehash",
  "BibleHash": "0000000000002aaa46b9dc122688a0e203a7ddec60b104c95c0f1372eb43e0dd" <= same result with block 17079

Update:

Just found something interesting which I think confirms my suspicion. Even though in most of the errors I have from the log, both biblehash1 and biblehash2 are the same, since it's computing 3 different times the biblehash, I think the one used in the if statement may actually be different from the one computed before and the one computed after, hence why it is failing the condition.

Look at this one I just found:

2017-11-17 10:03:51 ProcessNewBlock : ACCEPTED
2017-11-17 10:05:14 CheckProofOfWork(1.0): BlockHash 541a323bbf91103d90556af0e5b9143673a2cd36680fffe21bc3b7a9cbc85356, ProdChain TRUE, SSLVersion OpenSSL 1.0.1t  3 May 2016, BlockTime 1510913112.000000, PrevBlockTime 1510913025.000000, BibleHash1 00246187e1fe61cac573d808464ecbcbc67a4703fedcc1931ed761a85a50ec57, BibleHash2 00265c4ef603fb643449e68805184db17f1f0242c4a64edd402decb0e96cb0cd, TargetHash 00000000000880b2000000000000000000000000000000000000000000000000, Forensics exec biblehash 541a323bbf91103d90556af0e5b9143673a2cd36680fffe21bc3b7a9cbc85356 1510913112 1510913025 17111
2017-11-17 10:05:14 ERROR: CheckProofOfWork(1): BibleHash does not meet POW level, prevheight 17111.000000 pindexPrev 20e9f4416b8e469b23a6fde82f197342086622e9ac827e78875701d001ca3916
2017-11-17 10:05:14 ERROR: CheckBlockHeader(): proof of work failed
2017-11-17 10:05:14 ERROR: ProcessNewBlock: CheckBlock FAILED
2017-11-17 10:05:14 Misbehaving: 97.99.69.33:40000 (0 -> 5)
2017-11-17 10:05:14 UpdateTip: new best=541a323bbf91103d90556af0e5b9143673a2cd36680fffe21bc3b7a9cbc85356  height=17112  log2_work=57.818294  tx=28819  date=2017-11-17 10:05:12 progress=1.000000  cache=0.0MiB(112tx)
« Last Edit: November 17, 2017, 04:20:04 am by Alex »