I see there was a problem with the deploy, par for the course today!  Bad IT day, Bad.

Please grab it now!

Full deploy successful this time.

Please ensure your sanctuaries are started.  We have payments coming up in only 25 blocks.

That is our next huge milestone.

This is not a valid question.  In order to ask an IT question, you must provide information.

BiblePay - 1.0.6.8c
Mandatory Upgrade


- Disable tithe blocks at #21565
- Ensure Sanctuary payments can go live at #21600
- Increment mandatory protocol version to 70911

- Superblocks start at block #30001
- Proposals and Budgets went live at block #21551


** This is the windows release.  Please upgrade to 1068 if you have not.  Linux upgraded 4 hours ago **

Pool is back up!  We're back in business.

Sorry, had to babysit ( a real baby )..

Updating pool now.


Windows has been deployed.


Go ahead and start upgrading windows.

I will release the manifest in 10 minutes.


Yes, we are rolling again.  Thanks for the help on the linux side. 

Yes, 1.0.6.8b is ready now.

Alex is finally mining the tithe block.

Please upgrade to 1068b - I think we finally will put this behind us.

We moved the masternode payments up 40 blocks.


Ill post manifest after we mine the next 2 blocks.

Windows is still delayed by 3 more hours.

Alright guys, we made a little progress in slack and decided to move to Plan B.

The last tithe height is just too close to masternode start, and in addition, weve already mined up to 21559, so we found it easier on everyone instead of asking people to roll back the chain and deal with errors, to move our last tithe block forward 1 block (then there will be no errors).

So, I apologize for all the inconvenience today.   Now this means we need all the linux users to upgrade to 1.0.6.8.


After that, it should allow us to mine forward on the linux side.


Windows 1.0.6.8 is compiling now.


Thanks.

Could we please have a few Prod users download the windows version 1067c now.

Lets see if we make it through the tithe block at 21350 that is giving us trouble...

Alex and I have been testing two scenarios on linux, but those are our Plan B solutions.

Please help us move the chain forward.

Please be patient we are working as fast as possible in slack...  Testing the new version.

We have a plan B if this fails.

Lets wait until the pool is on 1067 and synced, then we can look at the actual guid.

Nothing is lost in the blockchain, No, not lost, ever.

Only coins mined on a fork are lost.  Or coins deposited to an exchange on a fork.

That should be OK if one controller has multiple masternodes; lets verify 100 payments after we get back up. 


So after you upgrade your linux box, the last few blocks in the chain are bad because the tithe was paid at that height.

Go ahead and click OK to let it rebuild the block index.


Alex and I are working on this now to ensure we resync up to 21551.  This upgrade only talks to other nodes of the same protocol version, hence the reason it is not going smoothly.

We are working it out now.

Please wait two more hours for the windows update.

Oh unfortunately we need to update every single node in our system, the pool, the masternodes, everything .

Yes.

BiblePay - 1.0.6.7
Mandatory Upgrade

- Disable tithe blocks at #21550
- Ensure Sanctuary payments can go live at #21551
- Increment mandatory protocol version to 70911
- Sanctuary payments went live at block #21551
- Superblocks start at block #30001
- Proposals and Budgets went live at block #21551


** This is the linux release.  Please upgrade now and lets get the chain rolling on the right fork.

Windows will be available in 4 hours.  **

Its the tithe block causing a problem.  (They were left in and designed to stop right before superblocks start, but are interfering with the masternode payments).



Sorry for the inconvenience.  We need another mandatory upgrade.




It will be ready for linux in 15 minutes, then windows in 4 hours.  Please be ready to upgrade.

Im taking a look - I think its the tithe block. 

I did deliberately keep the tithe block going til Superblocks start... but the problem is masternode payments cant be made at the same time a tithe block is made. 

We may need to disable the tithe block, checking...

Please review:

Please contact us if you'd like to add BiblePay to masternodes.online


Listing advantages
- Accurate stats and comparison tool for investors
- Free Masternode monitoring for BBP MN holders
- Daily of exposure to 1000s of visitors on fastest growing masternodes site
- Page dedicated to your coin's detailed stats
- Daily Twitter broadcasts of top % gainers
- Coin included in popular telegram bot

Our Listing bounty ~.125 BTC - payable in BBP.

All my best!

Cryptosandwich
Communications for masternodes.online & NODEshare.in






If good, someone please enter a proposal.

Thanks!

Yeah, Im working on #1 now.  Im thinking of finishing after 21550 because this requires one more tweak.
Youll see a higher HPS now in the pool in the mean time.

The biggest issue with the diff is there is some botnet still mining on an old version and they are not upgrading.  So our diff dropped with the mandatory upgrade.  Now with lower diff, we have a higher payout per block.  So now you are all reaping the benefits.

I just lowered the pool fee 1% down to 7% - as the pool gets closer to the black, Im lowering it each step of the way.

At block 21550, its hard to tell, if these botnets will upgrade or not.  

EDIT:  Im only making this comment based on the Chinese emails Im receiving and Alex is getting hit with a lot of Chinese translation results in the BX.  Im thinking maybe they do not know to upgrade.

Yes, after upgrading the sanctuaries should say EXPIRED or UPGRADE_REQUIRED, then just do a start-many again.