Search content
Sort by
Showing 6 of 6 results by JennyR
Re: BiblePay | 10% Charity | POW/PODC | CPU Mining *new* | Sanctuaries
pathetic BBP, irational nonsense, revolting waste...
Nehemiah 4
Re: BiblePay | 10% Charity | POW/PODC | CPU Mining *new* | Sanctuaries
So here is something that goes against what the naysayers are saying:
Out of all those masternode coins on GIN, according to my conversation with TTS, we would be the first Evolution based coin to upgrade after Dash according to our testnet schedule (IE Evo is only 6 days away from being tested in testnet at biblepay). If we are so "worthless" then why are we first? (Hmmm... ) Maybe its because we are actually competent, yes we don't look good when we are stuck in a ditch, but as Christians we should help each other out of the ditch.
And I just want everyone to know that got banned, I will forgive you and not hold a grudge, if you repent for your past behavior and send me an e-mail or a PM with a true repentant heart. Then I would have mercy and remove you from the ban list.
Great job, Rob and everyone who pitched in.
Matt 6:11-15; Rom 5:8
Re: BiblePay | 10% Charity | POW/PODC | CPU/Cancer Mining | Sanctuaries
1.2.0.1 - BiblePay - Mandatory Upgrade
- Disable sanctuary payment verification until a future spork is activated
- Disable sanctuary payment verification until a future spork is activated
MacOS version ready
Ubuntu PPAs currently building (will take a few hours)
And thank you too, MIP, for all you do. May the Lord reward your efforts!
Re: BiblePay | 10% Charity | POW/PODC | CPU/Cancer Mining | Sanctuaries
Ok it makes a little more sense now, I believe I see the lions share of the problem (IE bigger than reorganizing).
Ive got two nodes that dont agree here, both consider one of the forks valid but node 2 is following a shorter chain.
Looking at the log on node2, it feels the list of sanctuaries is different than node1. Another words, it has a view of sanctuary payments that differs from other parts of our network.
So basically the sanctuary payment is enforced with a hard rule - and this can cause a fork. We need to either A) Sync all the sancs, or B) Temporarily not enforce that sancs get paid properly.
Ill work on B at a network level now.
Sancs: Please try to sync to the top so your data can synchronize.
Ive got two nodes that dont agree here, both consider one of the forks valid but node 2 is following a shorter chain.
Looking at the log on node2, it feels the list of sanctuaries is different than node1. Another words, it has a view of sanctuary payments that differs from other parts of our network.
So basically the sanctuary payment is enforced with a hard rule - and this can cause a fork. We need to either A) Sync all the sancs, or B) Temporarily not enforce that sancs get paid properly.
Ill work on B at a network level now.
Sancs: Please try to sync to the top so your data can synchronize.
We will need to know what the "top" is.. I have 3 different chains i'm seeing
Ive confirmed we need a mandatory upgrade for the entire network to turn off the switch, then we sync to the top, the top stays the top, then in a couple days we will re-enable the spork.
So for now, please disregard my comment about the Top.
The new version will be out in less than one hour.
Thanks for everyones patience.
One other reason this happened is we have GIN hosting a fair amount of Sancs and they are on the old chain (as I really dont want to have them upgrade until we are synced) - exacerbating the problem. (Their sancs are not in agreement with heights from 1199 sancs, so no masternode winners can be calculated yet).
Thank you, Rob for your hard work. May the Lord grant you strength and His Holy Spirit to bring stability in this critical time. We need all of us to work together. May you bear the fruit of His Spirit, Gal 5:22-23 as a witness to our Risen Saviour.
Re: BiblePay | 10% Charity | POW/PODC | CPU/Cancer Mining | Sanctuaries
We have next fork now, its the end.
Same here,
Different machines show different fork blocks after update to 1.1.9.9g version.
After such a long time, it still failed to return on the right block, which is worrying.
I gave some power on correct chain(about 40% all), we must waiting ....
wchich one is correct, i have wallets on blocks 107049, 107076 and 107021
107076 in most cases
few wallets unable to connect peers
good question ... hard to say which is the "real" chain at this point
Please try not to quote banned members posts, thanks.
Sir, I dont know who is banned or not. I just have the same problem.
Captain, the ship is in a storm and we are ALL in it. Please give us clear and concise instructions what to do when our wallets show different block counts even after multiple restarts. Where can we find the latest correct hash of the main kosha chain updated in real time, please?
We need your help and direction in times like this, Sir, to steady the ship. May God speed you! We await your instructions....
Thanks Jenny - please do this:
- Wait 10 minutes for me to issue the global command to my sancs
- cd %appdata%\biblepaycore
- rm banlist.dat
- rm blocks -r
- rm chainstate -r
- Restart wallet
The theory is that by removing the banlist, we will see each others nodes.
Thanks,
Rob
Aye, aye, captain! Thank you.
Re: BiblePay | 10% Charity | POW/PODC | CPU/Cancer Mining | Sanctuaries
We have next fork now, its the end.
Same here,
Different machines show different fork blocks after update to 1.1.9.9g version.
After such a long time, it still failed to return on the right block, which is worrying.
I gave some power on correct chain(about 40% all), we must waiting ....
wchich one is correct, i have wallets on blocks 107049, 107076 and 107021
107076 in most cases
few wallets unable to connect peers
good question ... hard to say which is the "real" chain at this point
Please try not to quote banned members posts, thanks.
Sir, I don’t know who is banned or not. I just have the same problem.
Captain, the ship is in a storm and we are ALL in it. Please give us clear and concise instructions what to do when our wallets show different block counts even after multiple restarts. Where can we find the latest correct hash of the main kosha chain updated in real time, please?
We need your help and direction in times like this, Sir, to steady the ship. May God speed you! We await your instructions....