Post
Topic
Board Announcements (Altcoins)
Re: BiblePay | Masternodes | Sanctuaries | POBH - ASIC Resistant | 10% ORPHANS
by
v1.0
on 11/03/2018, 21:48:13 UTC
Biblepay - 1.1.0.9b
Mandatory Upgrade - for Entire Network (including Sanctuaries)

Before block 35110

- Avert mining crash and relay error messages in miner to getmininginfo
- Fix PODC association error (unable to sign cpid)
- Remove logging
- Fix getnetworkhashps
- Add unbanked CPID support
- Add configurable SPM (stake-per-magnitude) UTXO requirement (pending outcome of poll)
- Remove CompetetiveMining Tithe
- Added exec search key filter (Ability to search for DCC elements by CPID - IE exec search UTXOWEIGHT ca89)
- 7 Minute block targets as of block 35110
- Fix DC Superblock Budget as of height 35110


Hi- wondering if you can help. I've been using Biblepay with its GUI program through Linux Ubuntu, and mining through an account at pool2.biblepay.org. All has been going seamlessly, until today. I upgraded my Biblepay version because last time I logged into my pool2 account it said we have to upgrade to version 1.1.0.1+ in order to keep mining. But now after the upgrade, it no longer syncs, says "no block source available". It also keeps asking me for my wallet password when I load it for "PODC updates" which I have no clue what this means.

Can you please help me resolve this, or point me to a tutorial of sorts?

Thankyou

You can cancel the password prompt, its just for PODC (Cancer mining).  
See this for cancer mining:
http://wiki.biblepay.org/Distributed_Computing_2

So, first please ensure your system time and timezone is correct.  A lot of people cant sync if the time is off by more than 2 minutes....

Then resync.



Yes, validated the system timezone and time is correct. Not resyncing or showing progress. Did I have to change something in my wallet configuration file to go along with the update? Currently it looks like:

addnode=dnsseed.biblepay-explorer.org
addnode=dnsseed.biblepay-explorer.org
gen=1
genproclimit=2
poolport=80
pool=https://pool2.biblepay.org
workerid=****(hidden)

Can you delete the chain and re-sync.

And try these instead:
addnode=node.biblepay.org
addnode=biblepay.inspect.network

Delete the chain?? Do I have to rebuild the entire chain now just because of an upgrade, or is it because of the node change you suggested? Or is it to maintain integrity because of the node change? I'm not sure how to delete the chain, I suppose I just dive into my Biblepay folder and find it there?

Thanks again- just want to make sure I'm following this correctly before I go deleting stuff!