BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

[sunk818]

You deleted the roadmap without asking.  I said I forgave you.  Wasnt I really nice about it?

It was not deleted. It was renamed, and it was very easy to revert back to previous version. That's what wikis are for. No, you were a real jerk about it. You used the word "incensed" to describe how you felt.

The difference is we dont need to attack each other disrespectfully.  If I have a problem with you or your code Ill mention it respectfully.  Thats all Im asking.

What are you smoking? When we bring potential issues with PoG you would dismiss them and proudly declare PoG is production ready. The only way you listen is by showing you how weak your code is. Why do you think you had three mandatories in a matter of weeks?

[bible_pay]

You deleted the roadmap without asking.  I said I forgave you.  Wasnt I really nice about it?

It was not deleted. It was renamed, and it was very easy to revert back to previous version. That's what wikis are for. No, you were a real jerk about it. You used the word "incensed" to describe how you felt.

The difference is we dont need to attack each other disrespectfully.  If I have a problem with you or your code Ill mention it respectfully.  Thats all Im asking.

What are you smoking? When we bring potential issues with PoG you would dismiss them and proudly declare PoG is production ready. The only way you listen is by showing you how weak your code is. Why do you think you had three mandatories in a matter of weeks?

Sun, I think you should consider supporting another community - you obviously are not aligned with helping us here or exercising Christian values by being so mean spirited.

This is your last warning; Im banning you if you are disrespectful to any of us here at BiblePay again.

[bible_pay]

** BiblePay Update **


So MIP and I have made a lot of progress finding the two issues we have.  One is the data that entered the pogpool during certain recent blocks that caused memory corruption to affect a field in a block, this caused some of our fully synced nodes to throw a errors while syncing lower heights, so another words we have to fix both of these issues and fully sync the chain to know for sure that we killed both bugs.  

As far as the mandatory itself goes, we have most of it coded to switch over to POW.  I need to test this in testnet locally with a few nodes and then we will create a release.

Im really shooting for having one ready by 9PM CST US time tonight, but it may be a challenge, or it may be a little early if we are lucky.

We should be on block 107,000 or so by now, and the cutover height is set to 107,001 (since we are changing our consensus rules in this next release).

[bible_pay]

Daemonko, you are on the ban list. 

No, despite the small group of mean-spirited people (note the list of 5 at the bottom of the OP post), we will not give up and we will make it through this hard time with perseverance.

I predict an increase in sponsored orphans by the end of the year.

[capulo]

so what is block number after which podc will stops working?
just to know when to stop machines...

[bible_pay]

so what is block number after which podc will stops working?
just to know when to stop machines...

Block 107,000.  But please stop now - as the new client is not going to issue another PODC superblock.

[sunk818]

Two of my clients never crashed. Was on 106841 for the longest time stuck with invalid block header.

Now, I got this and they are syncing from block 0 again.

I wonder if this is good news.

Code:

2019-03-13 21:02:06 UpdateTip: new best=4357fa1294055f68b2eaf429f9ab35b917339c92a2cc89d8c2cb21e067dc9e5a  height=106610  log2_work=59.187575  tx=903826  date=2019-03-11 21:30:00 progress=0.995655  cache=0.9MiB(1070tx)
2019-03-13 21:02:06 CheckForkWarningConditions: Warning: Found invalid chain at least ~6 blocks longer than our best chain.
Chain state database corruption likely.
2019-03-13 21:02:06
 ERROR: Found invalid chain with higher work (ChainState database corruption likely)
2019-03-13 21:02:07
 ** Erasing Chain and Rebooting Wallet Now **

[bbptoshi]

I think the Retiring PODC vote should continue as intended, if 80 more blocks to go.

[bible_pay]

I think the Retiring PODC vote should continue as intended, if 80 more blocks to go.

A) Governance did not stop; its still running.
B) We passed block 107,000 a couple hours ago (I had a rigged up client and saw block 107,004 go by)

[bible_pay]

PreRelease for Linux
BiblePay - 1.1.9.9d
Mandatory Upgrade

- Remove POG in Prod to prevent external attack vectors
- Fix boost::lexical cast error during syncing
- Transition to POBH POW mining only after block 107,000
- Fix difficulty reading on overview and getmininginfo


** This is a pre-release if anyone wants to test on self-compiled nodes **

[sunk818]

I've tried 10 times now on three different Windows 10 PCs. Always stuck at block 33620 if I start from scratch. Get this error about coinbase pays too much at height 33620. Is this happening to anyone else? Just want to verify if its just me or other people are experiencing the same thing...

Code:

2019-03-14 01:47:24 UpdateTip: new best=24d50f20dd30a407fb1eddc85c580a6df0430cc6c814925e6036e6a248bc97af  height=33619  log2_work=58.865086  tx=125414  date=2018-03-08 23:02:13 progress=0.071044  cache=19.4MiB(69179tx)
2019-03-14 01:47:24 ProcessNewBlock : ACCEPTED
2019-03-14 01:47:24 coinbase pays too much at height 33620.000000 (actual=2666049.488200 vs limit=765636.976632), exceeded superblock max valueHeight 33620.000000, Amount 2666049.488200
ERROR: ConnectBlock(biblepay): coinbase pays too much at height 33620.000000 (actual=2666049.488200 vs limit=765636.976632), exceeded superblock max value
2019-03-14 01:47:24 InvalidChainFound: invalid block=923225d2991b267b3bd98df07d08cf1a979cdd03991e2af523f2bb3f8c196dff  height=33620  log2_work=58.865088  date=2018-03-08 23:18:09
2019-03-14 01:47:24 InvalidChainFound:  current best=24d50f20dd30a407fb1eddc85c580a6df0430cc6c814925e6036e6a248bc97af  height=33619  log2_work=58.865086  date=2018-03-08 23:02:13
2019-03-14 01:47:24 ERROR: ConnectTip(): ConnectBlock 923225d2991b267b3bd98df07d08cf1a979cdd03991e2af523f2bb3f8c196dff failed
2019-03-14 01:47:24 InvalidChainFound: invalid block=923225d2991b267b3bd98df07d08cf1a979cdd03991e2af523f2bb3f8c196dff  height=33620  log2_work=58.865088  date=2018-03-08 23:18:09
2019-03-14 01:47:24 InvalidChainFound:  current best=24d50f20dd30a407fb1eddc85c580a6df0430cc6c814925e6036e6a248bc97af  height=33619  log2_work=58.865086  date=2018-03-08 23:02:13
2019-03-14 01:47:24 ProcessNewBlock : ACCEPTED

[bbptoshi]

I've tried 10 times now on three different Windows 10 PCs. Always stuck at block 33620 if I start from scratch. Get this error about coinbase pays too much at height 33620. Is this happening to anyone else? Just want to verify if its just me or other people are experiencing the same thing...

Code:

2019-03-14 01:47:24 UpdateTip: new best=24d50f20dd30a407fb1eddc85c580a6df0430cc6c814925e6036e6a248bc97af  height=33619  log2_work=58.865086  tx=125414  date=2018-03-08 23:02:13 progress=0.071044  cache=19.4MiB(69179tx)
2019-03-14 01:47:24 ProcessNewBlock : ACCEPTED
2019-03-14 01:47:24 coinbase pays too much at height 33620.000000 (actual=2666049.488200 vs limit=765636.976632), exceeded superblock max valueHeight 33620.000000, Amount 2666049.488200
ERROR: ConnectBlock(biblepay): coinbase pays too much at height 33620.000000 (actual=2666049.488200 vs limit=765636.976632), exceeded superblock max value
2019-03-14 01:47:24 InvalidChainFound: invalid block=923225d2991b267b3bd98df07d08cf1a979cdd03991e2af523f2bb3f8c196dff  height=33620  log2_work=58.865088  date=2018-03-08 23:18:09
2019-03-14 01:47:24 InvalidChainFound:  current best=24d50f20dd30a407fb1eddc85c580a6df0430cc6c814925e6036e6a248bc97af  height=33619  log2_work=58.865086  date=2018-03-08 23:02:13
2019-03-14 01:47:24 ERROR: ConnectTip(): ConnectBlock 923225d2991b267b3bd98df07d08cf1a979cdd03991e2af523f2bb3f8c196dff failed
2019-03-14 01:47:24 InvalidChainFound: invalid block=923225d2991b267b3bd98df07d08cf1a979cdd03991e2af523f2bb3f8c196dff  height=33620  log2_work=58.865088  date=2018-03-08 23:18:09
2019-03-14 01:47:24 InvalidChainFound:  current best=24d50f20dd30a407fb1eddc85c580a6df0430cc6c814925e6036e6a248bc97af  height=33619  log2_work=58.865086  date=2018-03-08 23:02:13
2019-03-14 01:47:24 ProcessNewBlock : ACCEPTED

Me too, my latest block is always 33619.

[bible_pay]

I've tried 10 times now on three different Windows 10 PCs. Always stuck at block 33620 if I start from scratch. Get this error about coinbase pays too much at height 33620. Is this happening to anyone else? Just want to verify if its just me or other people are experiencing the same thing...

Code:

2019-03-14 01:47:24 UpdateTip: new best=24d50f20dd30a407fb1eddc85c580a6df0430cc6c814925e6036e6a248bc97af  height=33619  log2_work=58.865086  tx=125414  date=2018-03-08 23:02:13 progress=0.071044  cache=19.4MiB(69179tx)
2019-03-14 01:47:24 ProcessNewBlock : ACCEPTED
2019-03-14 01:47:24 coinbase pays too much at height 33620.000000 (actual=2666049.488200 vs limit=765636.976632), exceeded superblock max valueHeight 33620.000000, Amount 2666049.488200
ERROR: ConnectBlock(biblepay): coinbase pays too much at height 33620.000000 (actual=2666049.488200 vs limit=765636.976632), exceeded superblock max value
2019-03-14 01:47:24 InvalidChainFound: invalid block=923225d2991b267b3bd98df07d08cf1a979cdd03991e2af523f2bb3f8c196dff  height=33620  log2_work=58.865088  date=2018-03-08 23:18:09
2019-03-14 01:47:24 InvalidChainFound:  current best=24d50f20dd30a407fb1eddc85c580a6df0430cc6c814925e6036e6a248bc97af  height=33619  log2_work=58.865086  date=2018-03-08 23:02:13
2019-03-14 01:47:24 ERROR: ConnectTip(): ConnectBlock 923225d2991b267b3bd98df07d08cf1a979cdd03991e2af523f2bb3f8c196dff failed
2019-03-14 01:47:24 InvalidChainFound: invalid block=923225d2991b267b3bd98df07d08cf1a979cdd03991e2af523f2bb3f8c196dff  height=33620  log2_work=58.865088  date=2018-03-08 23:18:09
2019-03-14 01:47:24 InvalidChainFound:  current best=24d50f20dd30a407fb1eddc85c580a6df0430cc6c814925e6036e6a248bc97af  height=33619  log2_work=58.865086  date=2018-03-08 23:02:13
2019-03-14 01:47:24 ProcessNewBlock : ACCEPTED

Me too, my latest block is always 33619.

Dumb question, but is this definitely 1.1.9.9?

I'm just about to release Windows 1199, I suppose we can fix this small bug as a leisure.

[bible_pay]

BiblePay - 1.1.9.9d
Mandatory Upgrade



- Remove POG in Prod to prevent external attack vectors
- Fix boost::lexical cast error during syncing
- Transition to POBH POW mining only after block 107,000
- Fix difficulty reading on overview and getmininginfo


** Mac/PPA's compiling by MIP **

[bible_pay]

I've tried 10 times now on three different Windows 10 PCs. Always stuck at block 33620 if I start from scratch. Get this error about coinbase pays too much at height 33620. Is this happening to anyone else? Just want to verify if its just me or other people are experiencing the same thing...

Code:

2019-03-14 01:47:24 UpdateTip: new best=24d50f20dd30a407fb1eddc85c580a6df0430cc6c814925e6036e6a248bc97af  height=33619  log2_work=58.865086  tx=125414  date=2018-03-08 23:02:13 progress=0.071044  cache=19.4MiB(69179tx)
2019-03-14 01:47:24 ProcessNewBlock : ACCEPTED
2019-03-14 01:47:24 coinbase pays too much at height 33620.000000 (actual=2666049.488200 vs limit=765636.976632), exceeded superblock max valueHeight 33620.000000, Amount 2666049.488200
ERROR: ConnectBlock(biblepay): coinbase pays too much at height 33620.000000 (actual=2666049.488200 vs limit=765636.976632), exceeded superblock max value
2019-03-14 01:47:24 InvalidChainFound: invalid block=923225d2991b267b3bd98df07d08cf1a979cdd03991e2af523f2bb3f8c196dff  height=33620  log2_work=58.865088  date=2018-03-08 23:18:09
2019-03-14 01:47:24 InvalidChainFound:  current best=24d50f20dd30a407fb1eddc85c580a6df0430cc6c814925e6036e6a248bc97af  height=33619  log2_work=58.865086  date=2018-03-08 23:02:13
2019-03-14 01:47:24 ERROR: ConnectTip(): ConnectBlock 923225d2991b267b3bd98df07d08cf1a979cdd03991e2af523f2bb3f8c196dff failed
2019-03-14 01:47:24 InvalidChainFound: invalid block=923225d2991b267b3bd98df07d08cf1a979cdd03991e2af523f2bb3f8c196dff  height=33620  log2_work=58.865088  date=2018-03-08 23:18:09
2019-03-14 01:47:24 InvalidChainFound:  current best=24d50f20dd30a407fb1eddc85c580a6df0430cc6c814925e6036e6a248bc97af  height=33619  log2_work=58.865086  date=2018-03-08 23:02:13
2019-03-14 01:47:24 ProcessNewBlock : ACCEPTED

Looking at 1.1.9.9 a little closer, it definitely allows you to sync from 0.  (We might have had a bug in 1198 that we didnt even know of).

Please try with the latest windows client.

[sunk818]

Looking at 1.1.9.9 a little closer, it definitely allows you to sync from 0.  (We might have had a bug in 1198 that we didnt even know of).

Please try with the latest windows client.

I don't know how to compile Windows binary so I rely on biblepay.org/wallet

I tried with Ubuntu WSL to make exe binary, but couldn't figure it out.

So, I'm using 1198.

[bible_pay]

Looking at 1.1.9.9 a little closer, it definitely allows you to sync from 0.  (We might have had a bug in 1198 that we didnt even know of).

Please try with the latest windows client.

I don't know how to compile Windows binary so I rely on biblepay.org/wallet

I tried with Ubuntu WSL to make exe binary, but couldn't figure it out.

So, I'm using 1198.

That one wont work after 106,999 though (mandatory upgrade).
Windows is out (see above).

[MIP]

BiblePay - 1.1.9.9d
Mandatory Upgrade



- Remove POG in Prod to prevent external attack vectors
- Fix boost::lexical cast error during syncing
- Transition to POBH POW mining only after block 107,000
- Fix difficulty reading on overview and getmininginfo


** Mac/PPA's compiling by MIP **

MacOS version is also ready
PPAs will take 2-4 hours

[bible_pay]

Pool.biblepay.org coming up now... Testing it....

[SEO_Account]

So is everyone stuck on 107030?

getblockhash 107030 f17997e81295b768dc801e8d3a3ca15f7e14dc3161dfec45c32da25d0876b7b5