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

sunk818

full member

Activity: 1176

Merit: 111

Quote from: bible_pay on March 13, 2019, 09:45:20 PM

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

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: sunk818 on March 13, 2019, 09:03:12 PM

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.

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

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

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: bbptoshi on March 13, 2019, 09:29:46 PM

Quote from: sunk818 on March 13, 2019, 09:03:12 PM

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.

bbptoshi

copper member

Activity: 39

Merit: 0

Quote from: sunk818 on March 13, 2019, 09:03:12 PM

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.

sunk818

full member

Activity: 1176

Merit: 111

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

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

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 **

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: bbptoshi on March 13, 2019, 05:36:06 PM

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)

bbptoshi

copper member

Activity: 39

Merit: 0

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

sunk818

full member

Activity: 1176

Merit: 111

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 **

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: capulo on March 13, 2019, 03:54:17 PM

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.

capulo

newbie

Activity: 491

Merit: 0

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

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

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.

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

** 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

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: sunk818 on March 13, 2019, 02:26:32 PM

Quote from: bible_pay on March 13, 2019, 02:18:25 PM

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.

Quote from: bible_pay on March 13, 2019, 02:18:25 PM

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.

sunk818

full member

Activity: 1176

Merit: 111

Quote from: bible_pay on March 13, 2019, 02:18:25 PM

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.

Quote from: bible_pay on March 13, 2019, 02:18:25 PM

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?

thesnat21

jr. member

Activity: 490

Merit: 4

Quote from: bible_pay on March 13, 2019, 02:21:17 PM

I made the assumption that our LIMITED_STRING was enough to prevent any effects of memory corruption, and for that I apologize to everyone.
In the future we wont base any production code on any untrusted user entered field ever again.

In my mind, the most effect the nickname could have had in the map was : Swear word (and we added code to remove those) and length, sorry guys.

In Evolution we will check every outside entry point in the smart contract processor.

I appreciate the candor, and yes not trusting any user input is a great default state.. (intentionally or not User's are most often the cause of systems going awry)

I'll admit I didn't consider special characters having an impact either..

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: dave_bbp on March 13, 2019, 01:39:15 PM

Quote from: bible_pay on March 13, 2019, 11:56:17 AM

Quote from: thesnat21 on March 13, 2019, 09:30:33 AM

Quote from: bible_pay on March 13, 2019, 09:12:55 AM

Quote from: vahtis on March 13, 2019, 07:56:31 AM

Quote from: bible_pay on March 13, 2019, 07:37:05 AM

Who is PoG @('_')@ Monkey?

Same address has used also StopCrashingBiblePay nick.
I remember seeing this at least yesterday.

Thanks.

So far we have found a corrupted scriptPubKey on the PoG Monkey record.

All exchanges are disabled.

From what I can see preliminarily, the bad POG record is causing the core client to go into a condition where it ends up corrupting the reply messages to other nodes exacerbating the problem for people who are trying to resync.

Let me continue to do more testing. Most likely we will need a mandatory upgrade release with a safer/more stable environment while we wait for Evolution. We may have to disable POG and move to POBH temporarily, we're checking.

Waiting to see the outcome of this.. If you have to drop POG temporarily, how does this affect the PODC vote?

The PODC retirement vote is winning by 100, so we only have 80 more blocks before it would be retired anyway.

Nothing changes... as far as that goes. The governance module should come back up and we will see if any changes are occuring to that vote over the next 10 days (IE governance does not go away).

The only thing that changes is blocks pay 50-50 to POW - Sanctuary (IE 5000 to POW/5000 to Sanc after governance escrow %) for a while, until Evolution.

Wait, WHAT?
Sorry, but this is ridiculous. May I remind you that the proposal was not just simply "retire PODC?" but actually "retire PODC in favour of POG?"! So by all that is right, if you now make the (rushed) decision to simply bury POG for good, then this whole proposal/vote has no more legitimacy whatsoever!

So what you're saying now is, we not only give up on POG (which more and more seems to have been in beta stage at best), but also simultaneously bury the ONE system that has worked for more than a year now? And we're going back to our good old trusty botnet-mining?

I hate to say it, but I'm afraid as soon as any exchange is gonna open up our trading again (that is if there is still an exchange patiently enough ...) this coin will dump hard. Sad

Dave, We arent saying it that way. The point is Prod is down due to a malfunction in POG, and reliability and security are paramount now.

What I am saying is the vote for PODC retired PODC at the cutover height. Next comes POW mining and stability.

Evolution will be ready in testnet within 10 days.
We will have green features in the smart contract within 20 days after that date. Just help us make a good product.

I'm not risking a fix to POG right now because I cant risk an unstable Prod environment during the interim between now and the Evo release.

None of this was done on purpose; this is something we have to go through for stability.

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: thesnat21 on March 13, 2019, 12:44:03 PM

Quote from: bible_pay on March 13, 2019, 11:52:59 AM

"StopCrashingBiblePay", that is such a Christian way to be Sun. It figures it was you as you are hiding behind being Christian but not acting like one.

Thanks for taking our chain down Sun; thats one thing Ive always disliked is hackers in prod.

I do think this should have been tested in testnet early on (special characters etc in the text fields). I am curious how this is different than tx message strings(Would this have a similar effect).

I cannot say it was malicious (with intent to crash the chain), I suspect it was only a matter of time before someone/something did this.

I do think we can add some tests to testnet next time around with this knowledge.

I made the assumption that our LIMITED_STRING was enough to prevent any effects of memory corruption, and for that I apologize to everyone.
In the future we wont base any production code on any untrusted user entered field ever again.

In my mind, the most effect the nickname could have had in the map was : Swear word (and we added code to remove those) and length, sorry guys.

In Evolution we will check every outside entry point in the smart contract processor.

bible_pay

full member

Activity: 1176

Merit: 215

Jesus is the King of Kings and Lord of Lords

Quote from: ?? on ??

I admit I'm human and weak at times. It happens to all of us. Being able to admit your vulnerability and work on your shortcomings, makes you a stronger person in Faith. I hope you can do the same and relate to all of us in a way that earns respect and shows you as a spiritual and sacrificial leader.

The same group is here for BBP sun, Jaap took a sabatical, and as you can see Togo is still here. Luke started working doubles at work.

Please take your negative attitude away from this forum.

Im not hiding my mistakes Sun! I admit there are flaws in POG, why do think Im fixing it?

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.

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

Topic: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 196. (Read 243436 times)