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

Why do you think I am trying to make a FUD?  
This is my real situation...
https://i.imgur.com/5O5qPqv.jpg

After that, I found that the official explorer is consistent with the other explorer. It should be a buffering problem that lead to the latest status can't displayed in real time.

As an participant, when see that it is different from the official data, encountered problems need a query should be normal behavior

Thanks for your help and information.

Im in agreement, I definitely do not see a fork, just lag, for anyone interested you can just check the same block on each

Block 120723
http://explorer.biblepay.org/block/990846afd61dae5a3fafabc11bbeb97c860e6dc18c0ee3723a7d27306f421918
https://chainz.cryptoid.info/bbp/block.dws?120723.htm

They have the same hash

=

It looks like the explorer caught back up now

There a guy whose been working on trying to add clustering to iquidus
https://github.com/iquidus/explorer/pull/257

=

CryptoID has proven to be great, Id be fine with it being main explorer now

I believe anyone can donate Bitcoin to pay for CryptoID: https://chainz.cryptoid.info/contribute.dws?coin=bbp
And any one of us can contact their support to let them know about upgrades/etc: https://cryptoid.uservoice.com/

Someone needs to put a log in iquidis and write the timestamp ms from the php calls in main and find out where the delay is.  It could be a mysql index missing, or a mishandled call to biblepaycore, or an error trap lag, etc.  Id do it if I had more time but I have other irons.

I agree chainz seems completely worth it- hopefully we can keep paying for that as we go forward and work on our other important issues instead of fighting with iquidis's lags.

One more thing, we should tell the users:  a delayed block count is not a different road if its on the same chain LOL. 

But explorer.biblepay.org is not forked, as I see its diff is > 12,000 on it.  So I just want to clarify he was alluding to a fork, and we have not been forking after POG (ever - not once).

I think the explorer is lagged behind by 40+ minutes
http://explorer.biblepay.org/
https://chainz.cryptoid.info/bbp/

I remoted in, everything looks okay,
I did find a 49GB log file for mongodb and reset it

I can try stopping everything, maybe doing a fresh reboot of the server, and then start everything back up again,
I think Iquidus explorer just isnt that great, the chainz one is awesome

Hi Eternalenvoy,

I just took a look at your last 17 posts, and I believe all 17 are inaccurate.

We had only ONE fork in BiblePay, and that was back at block 105,000 (which, remind you we asked the exchanges to shut down while we disabled POG and reorganized to POBH).

So I'm going to give you the benefit of the doubt, that you have bad machines and a personally bad experience on your end (which is very hard to believe that it could be spread out over that time period - and it is in contrast to my experience with BBP sancs).

Our diff has been over 20,000 and we have not had a fork for 15,000 blocks and we only had ONE (not 16).  The masternodes are NOT confused where they are, as we are on decentralized with a flavor of POW called POBH (not a staking algorithm that is hard to come to consensus).

Please be more careful about what you post in the future - check that it is entirely accurate - as it appears you are trying to spread FUD here.

(IE you would say "I seem forked again personally" not "it seems forked again") - as we were not forked before - and I recall replying to you and saying that in the reply - therefore you should already know we weren't forked 'before'.

getblockhash 120695

4bdaaa2623a8c128d537393e1d66a457e4e1c2d126edf282fc2052cc2b9bef2c

It seems forked again?

MY MN 1  "blocks": 120659,
MY MN 2  "blocks": 120680,

Official Explorer blocks = 120667

https://chainz.cryptoid.info/bbp/ show blocks = 120690



which is the right road?

Slovakia, if you want to post here again just send me a PM with the apology for:

- Calling us a scam
- Calling me an orphan fund thief
- Swearing

If you explain that you were wrong about these things, and also Repent and tell us you will never do these things again, I will restore access.

God Bless You,
Rob

*** BIBLEPAY EVOLUTION UPGRADE INFORMATION ***

June 2nd, 2019 - After Height 123,000 - At this height, we would like the entire network (users and sanctuaries to upgrade).  Note:  Do not upgrade before block 123,000 if you are a sanctuary - as Evo governance is not compatible with this monthly superblock.   Regular miners may upgrade before 123,000, but please do not upgrade your controller wallet before 123,000 except for testing only (as the Evo controller wallet will not be compatible with BiblePay Classic sanctuaries).  At height 123,000 our exchanges will go into maintenance.  (Note:  the mandatory Evo cutover height is 123,200).

June 2nd through June 9th 2019 - After height 123,000 - At this time we would like all sanctuaries to upgrade to Evo in non-deterministic mode.  Since we have changed our lockup requirements to 4,500,001 per sanctuary, we ask you to re-lock every sanctuary in your cold wallet, start them, and test them (verify they are started and in the sanctuary list).

June 10th 2019 - At height 124,400 - At this height our exchanges will come back online.

July 2nd 2019 - After height 129,150 - At this time we would like all sanctuaries to upgrade to deterministic mode (using the upgradesanc RPC command, to be explained in detail).  This height is after our June superblock pays out.  (The reason we require a two-step upgrade is to preserve backward compatibility during the month of June with classics block structure).  

August 2nd 2019 - After height 135,300 - We enable Dip3 (deterministic Sancs) meaning we no longer support non-deterministic sancs on the network.  All non-upgraded sancs after this height will not be paid rewards.

Since we will be upgrading to Evo in only 13 days we really need to test Evo in prod from the pool perspective on all pools.

In testnet two of us tested pool mining in prod against purepool & pool.biblepay and they passed.


Pool owners: Please test Evo in prod as a pool server, but do it in a way where you can roll back if it doesn't work.

EDIT: Pools - you can post messages here to confirm its working:
https://forum.biblepay.org/index.php?topic=391.msg6053#msg6053

You were probably good then - the blocks have moved up since we started diagnosing, so just go back to the old block and type:

getblockhash 119916

e7addba62252b412d5b7a9433cd1802dbbcfd8687ff9432e4ca8da090e4a8ff1


Just see if your nodes still match that hash, if they do, everything is OK.

I have completely deleted biblepaycore folder and reindex , all my masternode is showing 119940 now.. different with official explorer and same with SXC & https://chainz.cryptoid.info/bbp/

Im seeing all nodes are on the 11916 chain above, please check to see if deleting your banlist.dat works.

No problem man, but I find it hard that we have a fork because our diff has been above 10K for quite a while (and we only have POBH on right now).

Could you please tell me more about the nodes that are forked, can you check those nodes and look at the Peers list and see if you have any banned peers?  Could be a regional issue.

In the mean time Ill run my sanc report - this shows the conglomerated diff and block on more than 50 nodes so its usually good to see the total health of the network (for me).

Thank you for your information.

It seem the "right" block  is 119928
Southxchange and https://chainz.cryptoid.info/bbp/ also showing "119928"
However, Official Explorer  is 119917 ...

Different nodes display different blocks "119893" "119912"  "119914" , it seems have several forked.

ATTN all Proposal Creators and Devs:

Please add your proposal within 3-4 days if possible as I need to see what will be left for Compassion and add it early - as it will be a very hectic end of month with the Evo upgrade coming up.


Regarding Evo:  It looks like our mandatory upgrade will occur system-wide after this monthly superblock pays out (that will be approx. June 2nd).  I'll post the detailed upgrade plan asap.


Note to Devs:
Someone created some FUD on the discord a while back saying something to the extent that I was hogging the entire IT budget and that I would choose to hog the remaining budget for Compassion and not pay the devs.  Both of these statements are false.  I want the devs to know that I encourage you to add your proposals early and NOT wait for me to enter a proposal.  And, I realize we may go OVER the IT budget while our price is low.  Its to be expected that we might have a couple million extra BBP going to the devs during our lean times.  The main point I want to communicate is although we can't afford the full proposal for one dev, you can add a proposal that is capped at a reasonable amount.  For example if your payroll is normally 3 mil you can enter 1 mil being cognizent to share the rest with the other devs, but certainly I would rather see it entered and be overbudget in IT than to not be paid.  Our orphans are equally important but we will all take a hit together and reduce by 60% or so until the economic conditions improve.  So please, enter your proposals now.

Here is one way:

https://chainz.cryptoid.info/bbp/


I believe we have this hash (high diff):


getblockhash 119916

e7addba62252b412d5b7a9433cd1802dbbcfd8687ff9432e4ca8da090e4a8ff1

May I know where can check the block is "right" road?
I checked my MNs is different with explorer...

Since masternodes.online is not listed BBP .. anyone knows have another monitoring website?

Forum.biblepay.org is back up!