Search content
Sort by
Showing 19 of 19 results by haladez
Re: BiblePay | 10% to Orphan-Charity | POBH CPU | Sanctuaries (Masternodes)
Same here, must be a glitch with the BBP daemon. Will come back up soon. Solo miners, enjoy this brief session of luck 
I was worrying already that I might be on a fork since I got 8 blocks within the last 6 hours.
Thats awesome, just for reference what kind of HPS are you running solo mining?
About 197k hps with a Ryzen 1700X with 32 genproclimit.
Re: BiblePay | 10% to Orphan-Charity | POBH CPU | Sanctuaries (Masternodes)
Same here, must be a glitch with the BBP daemon. Will come back up soon. Solo miners, enjoy this brief session of luck
I was worrying already that I might be on a fork since I got 8 blocks within the last 6 hours.
Re: BiblePay | 10% Charity | POW/POBH CPU Mining *novel* | Sanctuaries
Is the CryptoBridge wallet halted until the Evo update? (It says wallet update when you try to deposit/withdraw)
I believe the last news was that they wanted 0.25 BTC to upgrade wallet again
I wasn't too active the last months
Re: BiblePay | Masternodes | Sanctuaries | POBH - ASIC Resistant | 10% ORPHANS
Wallet Crash wise, Id advise everyone having issues to Clean and Reindex their wallets:
https://www.reddit.com/r/BiblePay/comments/7nmvm8/how_to_update_clean_wallets/
and also delete debug.log file if it is large
Windows:
- Open File Explorer: %appdata%/BiblePayCore
- Delete blocks and chainstate folders
- Delete banlist, fee_estimates, governance, mncache, netfulfiled and peers .dat files
- Delete debug.log
- In Wallet do Tools >> Wallet Repair >> Rebuild index
https://www.reddit.com/r/BiblePay/comments/7nmvm8/how_to_update_clean_wallets/
and also delete debug.log file if it is large
Windows:
- Open File Explorer: %appdata%/BiblePayCore
- Delete blocks and chainstate folders
- Delete banlist, fee_estimates, governance, mncache, netfulfiled and peers .dat files
- Delete debug.log
- In Wallet do Tools >> Wallet Repair >> Rebuild index
I've tried that and it doesn't work unfortunately.
I have reinstalled it completely and still get this in the debug file:
Code:
2018-05-31 15:50:29 GUI: Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt. You must
reimplement QApplication::notify() and catch all exceptions there.
2018-05-31 15:50:29
************************
EXCEPTION: N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_16bad_lexical_castEEEEE
bad lexical cast: source type value could not be interpreted as target
C:\Program Files\BiblepayCore\biblepay-qt.exe in Runaway exception
exceptions from an event handler is not supported in Qt. You must
reimplement QApplication::notify() and catch all exceptions there.
2018-05-31 15:50:29
************************
EXCEPTION: N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_16bad_lexical_castEEEEE
bad lexical cast: source type value could not be interpreted as target
C:\Program Files\BiblepayCore\biblepay-qt.exe in Runaway exception
Re: BiblePay | Masternodes | Sanctuaries | POBH - ASIC Resistant | 10% ORPHANS
My wallet (1.0.2.2) didn't open and the loading window disappeared without any notice after ~5 minutes, repeatedly.
Then I installed 1.0.2.4 and I get
I tried deleting everything but my wallet.dat, I tried using an "empty" wallet.dat and reinstalling.
I can open my wallet, it asks for the PODC password, and after a while it crashes with above error message.
Debug:
Then it seems to work for a while, and after some blocks it says:
(end of debug)
Then I installed 1.0.2.4 and I get
Quote
a fatal error occurred. BiblePay can no longer continue safely and will quit.
I tried deleting everything but my wallet.dat, I tried using an "empty" wallet.dat and reinstalling.
I can open my wallet, it asks for the PODC password, and after a while it crashes with above error message.
Debug:
Code:
2018-05-30 20:23:40 ProcessNewBlock : ACCEPTED
2018-05-30 20:23:53 GUI: Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt. You must
reimplement QApplication::notify() and catch all exceptions there.
2018-05-30 20:23:53
************************
EXCEPTION: N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_16bad_lexical_castEEEEE
bad lexical cast: source type value could not be interpreted as target
C:\Program Files\BiblepayCore\biblepay-qt.exe in Runaway exception
2018-05-30 20:24:30 ProcessMessages(addr, 30003 bytes): CHECKSUM ERROR nChecksum=c3f0869d hdr.nChecksum=1641cf83
2018-05-30 20:24:34 UpdateTip: new best=00000b0ef8301f9a0d30aa0aa0e5ce947257717c1459f5cfb3f9c50881161b3f height=226 log2_work=25.937256 tx=231 date=2017-07-25 08:18:50 progress=0.001235 cache=0.1MiB(227tx)
2018-05-30 20:24:34 ProcessNewBlock : ACCEPTED
2018-05-30 20:23:53 GUI: Qt has caught an exception thrown from an event handler. Throwing
exceptions from an event handler is not supported in Qt. You must
reimplement QApplication::notify() and catch all exceptions there.
2018-05-30 20:23:53
************************
EXCEPTION: N5boost16exception_detail10clone_implINS0_19error_info_injectorINS_16bad_lexical_castEEEEE
bad lexical cast: source type value could not be interpreted as target
C:\Program Files\BiblepayCore\biblepay-qt.exe in Runaway exception
2018-05-30 20:24:30 ProcessMessages(addr, 30003 bytes): CHECKSUM ERROR nChecksum=c3f0869d hdr.nChecksum=1641cf83
2018-05-30 20:24:34 UpdateTip: new best=00000b0ef8301f9a0d30aa0aa0e5ce947257717c1459f5cfb3f9c50881161b3f height=226 log2_work=25.937256 tx=231 date=2017-07-25 08:18:50 progress=0.001235 cache=0.1MiB(227tx)
2018-05-30 20:24:34 ProcessNewBlock : ACCEPTED
Then it seems to work for a while, and after some blocks it says:
Code:
2018-05-30 20:26:34 UpdateTip: new best=000005f863c8814a6d408724612a4c3b6094a5efe37c14fc2b97b49a9cbe844b height=364 log2_work=27.507559 tx=392 date=2017-07-26 06:57:02 progress=0.002096 cache=0.1MiB(368tx)
2018-05-30 20:26:34 ProcessNewBlock : ACCEPTED
2018-05-30 20:26:35 CDBEnv::EnvShutdown: Error 22 shutting down database environment: Invalid argument
2018-05-30 20:26:34 ProcessNewBlock : ACCEPTED
2018-05-30 20:26:35 CDBEnv::EnvShutdown: Error 22 shutting down database environment: Invalid argument
(end of debug)
Re: BiblePay | Masternodes | Sanctuaries | POBH - ASIC Resistant | 10% ORPHANS
Because the system rounds 5% or less of UTXO down to 0%, and rounds the rest up to the next 10%. So to get 100% UTXO you need 20 BBP * RAC * .901. In User BBP's case that would mean 1,301,683 * 20 * .901 = 23,456,327.66.
This has been discussed repeatedly, and while I personally think the system needs tweaked just a bit, that is the way it is currently coded to work and has been since PoDC Staking began.
This has been discussed repeatedly, and while I personally think the system needs tweaked just a bit, that is the way it is currently coded to work and has been since PoDC Staking began.
I think we should make the steps smaller, like every 1 or 2%.
That way you can get (tiny) rewards with little amounts of BBP and yet require more than 90.1% to get the full reward, in this case 99.1%
I know, even though we have officially 202 blocks per day, Alex pointed out that we have historically Always had 150 due to the nature of the bible hash algorithm. So, technically, the main pool is getting 33%, but still, its been dropping lately, not increasing.
Doesn't that mean the block times have been wrong the entire time?
If I recall correctly, this was pointed out some months ago as well that our block times are around 10 minutes on average instead of 7 minutes like intended.
So let me get this straight? BBP is now favoring big mining ops over everyone else?
Before that it was an arbitrary limitation that could be bypassed by running multiple instances.
So honest people with strong CPUs would get significantly less than people who were using the bypass.
I gotta admit that I simply couldn't be bothered to set up multiple clients.
Now it just takes your raw CPU power again.
I still don't understand one thing, if HPS is used for pool payouts (as is displayed in the block distribution page), what purpose does HPS2 have and why is the leaderboard sorted by HPS2 by default?
I know HPS2 has something to do with shares submitted and luck, but is it used in the pool calculation for payouts or not? If it is used, then why is it not displayed in the block distribution page and HPS is displayed instead?
I know HPS2 has something to do with shares submitted and luck, but is it used in the pool calculation for payouts or not? If it is used, then why is it not displayed in the block distribution page and HPS is displayed instead?
HPS2 is used for pool payouts, that's why the leaderboard is sorted by it.
My HPS varies a lot from my HPS2 and is usually completely wrong.
HPS2 is at 37k right now while my HPS is only 2.5k
(yesterday it was around 19k)Is the pool on the main chain?
I think I got the issue resolved since my test withdraw appeared on my wallet.
Looks like the difficulty spiked to 10
---
Block explorer seems to be on a different chain.
http://biblepay.inspect.network/
I think I got the issue resolved since my test withdraw appeared on my wallet.
Looks like the difficulty spiked to 10
---
Block explorer seems to be on a different chain.
http://biblepay.inspect.network/
I reset your password to Null, so try logging in with empty, then changing it.
The page doesn't react at all when I leave the password empty.
I think someone else reported the same login issue with the new website.
It works now, thanks.
Pool UPDATE:
In order to find out if a Vultr Win 2012 R2 server can run a pool, I have shut down pool2.biblepay.org, and migrated pool.biblepay.org to Vultr.
Lets see how the performance is overnight and this will tell us if this particular config will be able to be cloned.
I still can't login on the normal pool.biblepay.org page, I'm getting this error:In order to find out if a Vultr Win 2012 R2 server can run a pool, I have shut down pool2.biblepay.org, and migrated pool.biblepay.org to Vultr.
Lets see how the performance is overnight and this will tell us if this particular config will be able to be cloned.
Invalid Username or Password
Any idea how long the wallet on c-cex is hung in maintenance? Been a couple days now.
If someone generated a deposit adress before that, can they still deposit coins?
I guess we can expect a dump when the maintenance is done. I'm hesitating to buy right now.