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

[SVK Noko]

Maybe wrong question. But... where is our dev when everybody has problem with fork, wallet, masternode, mining ... after mandatory update???

[slovakia]

fork is problem of noobs=   -reindexing helped always

wallet is updated

MNs working excellent

who got problem with mining?


MIP must update 1185b to package of PPA


its ok for you TOM?

[secoccular]

fork is problem of noobs=   -reindexing helped always

wallet is updated

MNs working excellent

who got problem with mining?


MIP must update 1185b to package of PPA


its ok for you TOM?

I know as of today, purepool seems to be operating on a fork. So, for some of us, mining is not working at the moment.

[MIP]

1.1.8.5b is already in Ubuntu Launchpad. (PPA repository)

Remember that it just adresses a crash in a RPC (console) command , so it doesn't make any difference to 1.1.8.5 in terms of chain consensus .

[bible_pay]

Maybe wrong question. But... where is our dev when everybody has problem with fork, wallet, masternode, mining ... after mandatory update???

Ive been working on biblepay....

[bible_pay]

ROBERT thanks you that you deleted my account on your pool ... excellent
facepalm

i had bbp on pool-wallet  

I don't delete random accounts in the pool, but you got my message via e-mail saying I've been helping you correct?  What about the e-mail that I sent saying I was restoring the account and the reason you got deleted?

Do you want to inform everyone ... that you are in contact ... and things are getting resolved...

[bible_pay]

I shut down PODC few days ago. And leave wallet online with 1% CPU mining on pool.biblepay.org... And after few days i got it..

Please check your wallet with the "getblockhash" commands we posted earlier to see if you are on a fork. As already said, this symbol means that you found a block on your own, which is theoretically possible, but with 1% CPU highly unlikely.

Btw: the main pool also seems to be on the wrong chain, it constantly changes the given information like "coins mined", "offline workers" etc. and also seems to be quite unresponsive.

I believe we were being attacked today.  I took pool2 down to give us a chance to take a look at this.

I'm working on finding the performance problem now.

[bible_pay]

It seems like there are several problems right now. Most of my ARMs are on the apparently correct chain, but I just updated two of them to 1185b and this version does not seem to find peers at all.

Also the PODC update system seems corrupt. The pool superblock view shows 0 for a lot of CPIDs and if I look up my CPID here:
https://forum.biblepay.org/tools/podcstatus.php?cpid=7c9264559fef3c1c689ee9fc3ff42494
it says my last PODC update was on 01/31, whereas my controller wallet constantly keeps sending them (mininmum 6 times yesterday alone). Strangely enough I received a PODC payment just a couple of hours ago.  

Also, my Sanc says "expired", but I received a payment for it just 3 hours ago ...
[Edit]: nevermind, this one also was on a wrong chain ...


@MIP: where do you see this "chainwork" information?

Using getblockchaininfo command.

You might find all sorts of inconsistencies depending on where you look at (and the fork where that tool is at the moment).

Also, as there seems to be some issues with the DNS seed servers, sync gets harder (it also happened to some users with the Android wallet a couple of weeks ago)

The reason the 6 dns seeds are down is my sanctuary host went down and these seeds might need updated (depending on how bad the outage is) but its still going on right now.

Oh thats horrible that we had android users out of sync also!  Man, we are providing terrible service to our users.  Maybe it will get worse before it gets better.

On the 'horrible inconsistencies' you might find, yes, if there are two chains, depending on which one you look at you will see an entirely different view.

In the mean time, MIP one thing you might help with is see if getchaintips shows the two competing chain hashes - you can do a 'reconsiderblock hash' on the chain with more work on one of your nodes that is out of sync, and see if it syncs to the top.  That would tell us if that paritcular node has a bad block in its chain (in its view).

[bible_pay]

Regarding this fork and choosing between the two chains, the diff is so close between the two the wallet is having a hard time choosing one or the other.

One thing I have discovered is chain B is 99% 1.1.8.5 while chain A is mostly the older, non upgraded wallets.

So for a rule of thumb to get us out of this, I recommend doing this from each of your nodes:

exec versionreport

If the report shows > 90% 1.1.8.5 nodes, you are on the right chain.
If the report shows more than a couple lines of info, please rm blocks, rm chainstate and restart the wallet.

If you are not sure, please re-index.

I think after we do this we will resolve the fork.

[bible_pay]

Regarding the 5 dns seeds being bad, I just updated all 5 to point to 5 good nodes at vultr (who didnt go down) however give it about an hour to update (as all 5 are upgrading now).

[bible_pay]

Expenses and Revenue updated for this month. 

Thanks Gunde for the 500K+ tithe!  It went directly to compassion.

[togoshigekata]

Is this the chain with most work?

Code:

getblockhash 99412
24f6698013663e200ef1d4810aa2ce9ef92ce482fbcbc21513bce258b483eb11

Also everyone here is how to update and reindex:
https://www.reddit.com/r/BiblePay/comments/7nmvm8/how_to_update_clean_wallets/

[sunk818]

Who is on 1147?


19:42:29

exec versionreport


19:42:30

{
  "Version": "Popularity,Percent %",
  "1147": "1; 0.49%",
  "1185": "204; 99.51%"
}

[sunk818]

Nope, I mean "-resync". It's two levels "above" rescan (which only scans the blockchain without changing it) and one level above reindex (which uses already existing block files). It automatically deletes all blockchain-related files and re-downloads it completely.

First I've heard of the -resync option. Is it part of Bitcoin? Its not part of DASH as far as I can find. Do you know what coin offers this option?

[bible_pay]

Is this the chain with most work?

Code:

getblockhash 99412
24f6698013663e200ef1d4810aa2ce9ef92ce482fbcbc21513bce258b483eb11

Also everyone here is how to update and reindex:
https://www.reddit.com/r/BiblePay/comments/7nmvm8/how_to_update_clean_wallets/

Yes that's the one with exec versionreport 1.1.8.5.  (Thats the one we want to be on through block 100,000).

All my sancs on this chain now.  Looks like fork is almost worked out.

[bible_pay]

Who is on 1147?


19:42:29

exec versionreport


19:42:30

{
  "Version": "Popularity,Percent %",
  "1147": "1; 0.49%",
  "1185": "204; 99.51%"
}

1 bbp'er won't hurt but will get lost after block 100,000 hits.

[bible_pay]

I believe the pool problems are resolved, please email me if anyone finds a pool problem.

[slovakia]

1.1.8.5b is already in Ubuntu Launchpad. (PPA repository)

Remember that it just adresses a crash in a RPC (console) command , so it doesn't make any difference to 1.1.8.5 in terms of chain consensus .

after upgrade,still crashed

[fenin0018]

Hi everyone! I have allready not update to last mandatory but I think Im mining in fork. Or just Purepool is down? How do I update the wallet on linux? What are the comands to do so?
Thanks!

[lalexcross]

Hi everyone, so in upgrade from 1.1.7.9 to 1.1.8.5 I lost more or less 190.000 BBP ..

What I need to do ?

Thanks
Ale