Quick question about the pool: I tried to withdraw some BBP from there, chose the amount, clicked "send" and received the usual e-mail. However, when I click on the link in there, I always get redirected to a page with a single sentence: "Please wait until January 1, 2021 before withdrawing more than 1001 BBP."Since when is this restriction enabled? What is the purpose of it? Why is this not stated as soon as you want to withdraw it from the pool? It would be nice if you could either remove this restriction OR increase the percentage of the auto-withdraw. Because right now my coins keep piling up on the pool and it is really tedious to pull them off there in 1k batches. ![Wink](https://bitcointalk.org/Smileys/default/wink.gif) Hi Dave, I'm committed to making it work properly. For higher security however, I do feel we should work on auto-withdraws first. Do you have that feature enabled? I will work with you to ensure it either works or figure out what error it failed with. The raising of the withdrawal limit is secondary - I confirm, this limit was added recently due to what appeared to be someone making a hacking attempt.
|
|
|
I could not get auto withdraw to work when I tried months ago
Never seen the 1k limit though
Try purepool , you get paid daily and your wallet address is your user id. No registration required
Wait, let's not give up on pool.biblepay either - I say that it is unacceptable to have a non-working mission critical feature in Prod. This is the first time I heard that auto-withdrawals don't work. (Note that I have an email address right on the pool contact page - and nothing was sent).
|
|
|
Short-term we talked about it merging with POBH. The long term goal was to replace PODC.
Just to clarify... You can't merge PoG with PoBH (PoW) because PoG is a daily superblock now. Perhaps I misunderstood and you meant the economics are siphoning from PoBH? After being in testnet, I've changed my mind and see sharing the PoDC with PoG makes more sense now. With GridCoin (GRC) pool and that guy from Turkey being the biggest BOINCers, I don't even see PoDC participants being aligned with Christian values. So, the sooner we can get off PoDC safely, the better. After the team requirement went away, there was no marketing angle being able to say a Christian coin was helping to cure cancer. Now I feel like the messaging like seoccular says is to say to BiblePay is about promoting Christian values. Whether that is tithing, giving to charities (compassion, bloom, kairos), or something else... as long as it aligns with defined Christian values, it allows BiblePay to be more agile and test out innovative and/or novel technologies without deviating from the "Christian values" angle. Thanks Sun, I appreciate your thoughts that take Christianity into consideration in the total mission. I can say also that I love how philanthropic the BOINC community is in giving distributed computing time. But I also feel that we as a community are capable of spreading the Gospel to masses and might have painted ourselves in a corner by appealing to a small segment of the available miners. It will be very interesting to see if we can appeal to a few new users per day that feel like coming back daily to visit Christian spaces and evangelize to their friends.
|
|
|
** BIBLEPAY POOL UPDATE **
Please disregard this message; we have decided to continue pool.biblepay.org and pool2.biblepay.org.
|
|
|
Unbanked test, always something is wrong, enough, You live in a world of fantasy
"true","2019-01-08T10:55:56","PODC Payment","","BMdmVJtfYU9TtgF7TRSXzsK9Wh2teweijB","442.19000000","e3aca59824320db1f679f32f211adc8d3ae349c423c788aaad0e7c6a0764365a-000" "true","2019-01-06T10:34:30","PODC Payment","","BMdmVJtfYU9TtgF7TRSXzsK9Wh2teweijB","434.75000000","763fecf4d7f6a5eab47345e6ab428c9cb7ec69ff738bea875e92c1855ebce9b4-000"
Could you elaborate? Showing a list of data doesn't tell us what is wrong ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) You really don`t see what is wrong? 1) Is this you? https://www.biblepay-central.org/en/podc/user/2013113/Your RAC is varied as you add & remove machines. That is to be expected. 2) What everyone thus far has missed is that your PoDC payment is not daily. There are gaps in payment. Now, if someone can explain why you are missing payments... Rob thinks it might be due to a masternode behind a VPN that is unable to download the distributed computer files from Rosetta & WCG. This explains intermittent payout... I don't really know. Either way, PoDC payment for unbanked is unreliable lately. 3) And the reason for WCGRAC being 0 is because of planned maintenance today. https://www.worldcommunitygrid.org/forums/wcg/viewthread_thread,41333Thanks Sun! My eyes got crosseyed looking at a wall of data ![Wink](https://bitcointalk.org/Smileys/default/wink.gif) Rob has been looking into the missed unbanked payments, every time there has been one he has looked at the logs in his masternode and seen the data. The suspicion is a few masternodes are unable to pull the data so when it's their "turn" they don't include it, but we are trying to see if there is something else going on. Since as of yet we have been unable to re-produce it, it is difficult to fix. Ok, so to summarize the users feel like PODC (non-unbanked) has been extremely reliable, but we had about 4 missed unbanked payments in a month - due to our hypothesis of maybe the creation sanc is behind a VPN, or has strict firewall rules in place. Now that things are clearing up in testnet (for POG) this should allow for some time to either add trace information to the gov. obj and/or investigate querying the actual unbanked list from the chain. I think we can take a look at this within the next few days as it appears to be the next highest priority github. EDIT: As far as testnet goes we had a very good test run this last release - it appears POG is now working in testnet.
|
|
|
Checkmate, too many changes. Stability was the key to success, not change. Good luck Rob ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) ) PODC has been over 99% stable. One two hour change only affected a cosmetic output for a couple hours (which is just for reference, not for superblock creation). To re-clarify the sanctuaries take care of contract creation AND payments.
|
|
|
Unbanked test, always something is wrong, enough, You live in a world of fantasy
"true","2019-01-08T10:55:56","PODC Payment","","BMdmVJtfYU9TtgF7TRSXzsK9Wh2teweijB","442.19000000","e3aca59824320db1f679f32f211adc8d3ae349c423c788aaad0e7c6a0764365a-000" "true","2019-01-06T10:34:30","PODC Payment","","BMdmVJtfYU9TtgF7TRSXzsK9Wh2teweijB","434.75000000","763fecf4d7f6a5eab47345e6ab428c9cb7ec69ff738bea875e92c1855ebce9b4-000"
Could you elaborate? Showing a list of data doesn't tell us what is wrong ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) You really don`t see what is wrong? Is it that the payments have been going down since November? Well, if that was true we would have complaints. A few unbanked payments using a completely different system isnt equal to "down since September".
|
|
|
now it looks good alsowith 'exec totalrac' only problem is that it sent podcupdate with only roseta stats, which is almost 0 for me ![Smiley](https://bitcointalk.org/Smileys/default/smiley.gif) so i need to resend it again manualy It should be reliable again now, we had a configuration change.
|
|
|
** BIBLEPAY POOL UPDATE **
We have increased the size of the pool server and consolidated both pool.biblepay.org and pool2.biblepay.org into one site. Anyone using the " https://pool2.biblepay.org" configuration: Please switch over to pool.biblepay.org. Performance should not be impacted negatively. SUMMARY: Pool2.biblepay.org has been shut down.
|
|
|
Totalrac pulls from a bbp pool API, and is only a "rough guess" try the podcstatus script, if it matches then we have an issue
No, totalrac pulls from the API, but it is the from the last WCG rac export (not a rough guess). Thats the same info that is used to create each superblock.
|
|
|
You can now read inbound letters from Cameroon-One in the pool.
We just received one from Fuhni.
|
|
|
Your cpid was in my sanc1's contract on all 3 of the blocks, therefore the unbanked code is working correctly. My theory is the sanc that created these 4 contracts is behind a VPN (or has HTTP blocked), and is therefore not downloading the unbanked report. The only way we can tell for sure is if we add a couple hours of code into the sanc contract (and a mandatory sanc upgrade), this would populate the governance object with additional details (as to what unbanked info was pulled). I just added a github issue for this potential podc sanc contract enhancement.
|
|
|
Missed unbanked PoDC payments for 1/4, 1/2, 12/27, and 12/25.
I show more than 10 unbanked cpids were voted in on the blocks above, except I dont see a PODC superblock that fell on 12-25 (we had one on 12/24 and then 12/26) CPID?
|
|
|
1.1.7.7 - Leisure Upgrade
- Added WIN exit handler (in getboincmetrics during initialization) - Test to see if this stops crashing in Win10 Home (be sure to set boincmetrics=0 first)
|
|
|
As promised the pool now honors inbound letters from Kairos. To see them click Orphans | Inbound Letters, and when the charity is <> Compassion, click "View".
|
|
|
Happy new year BBP team! I will wish you all a very good year. As I understand, we are planning to drop BOINC in the near future, and POG, which replace it, will not use CPU power. so, is this means that BBP will no longer be attractive to the CPU mining community ? I own ~30 CPU mining stations, using BOINC. I see I have no alternative to used them in BBP, but to switch them to a different coin ![Sad](https://bitcointalk.org/Smileys/default/sad.gif) We will still be a CPU mined coin. But, I understand that the extra 29 rigs would not be necessary. For now we still have PODC though, we still need to run a baseline on POG user count changes.
|
|
|
Does it crash always or occasionally?
I would say "always". I tried it 3 times in a row and then now another 2 times and it crashed all 5 times. Obviously the number of tries is very small, but at least I would say the crashes are very frequent. Can anyone else beside MIP try it on Windows? I didn't change anything in my OS since the previous version I had (which was 1.1.6.9b). I'm running 1175 on prod and three instances on testnet also 1175. No issues. windows 10 64-bit pro. I can reproduce crash on windows 10 64-bit home. application starts then just exits. so, this may be specific to windows 10 64-bit home, as I can't reproduce on win 10 64-bit pro. from debug.log 2018-12-31 20:22:12 MinerSleep 325.000000 2018-12-31 20:22:12 ** Started 1.000000 BibleMiner threads. ** 2018-12-31 20:22:12 Genesis Hash 3b4431310395638c0ed65b40ede4b110d8da70fcc0c2ed4a729fb8e4d78b4452 2018-12-31 20:22:12 init message: Done loading 2018-12-31 20:22:12 GUI: Platform customization: "windows" 2018-12-31 20:22:12 1 addresses found from DNS seeds 2018-12-31 20:22:12 dnsseed thread exit 2018-12-31 20:22:13 GUI: PaymentServer::LoadRootCAs: Loaded 211 root certificates 2018-12-31 20:28:06 I'll see if I can dig up anything in Event Viewer > Windows Logs > Applications: Fault bucket 2035543438252503376, type 4 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: biblepay-qt.exe P2: 1.0.1.7 P3: 5685c180 P4: StackHash_8dde P5: 10.0.17134.471 P6: 7e614c22 P7: c0000374 P8: PCH_B1_FROM_ntdll+0x000000000009B4F4 P9: P10: Attached files: These files may be available here: C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_biblepay-qt.exe_d0cea5e9f3db56a2da25c9b87a21142dfdb2ff_0c644e00_1a1ead24 Analysis symbol: Rechecking for solution: 0 Report Id: a01bc275-1d2d-4c5a-9dfe-45d9ce6e6300 Report Status: 268435456 Hashed bucket: 83819d716955aef0dc3fb3f8e9eaf150 Cab Guid: 0 Fault bucket 129518852071, type 5 Event Name: FaultTolerantHeap Response: Not available Cab Id: 0 Problem signature: P1: biblepay-qt.exe P2: 1.0.1.7 P3: 5685C180 P4: ffffbaad P5: P6: P7: P8: P9: P10: Attached files: These files may be available here: Analysis symbol: Rechecking for solution: 0 Report Id: be3fa363-96db-43ad-ae53-b374a5bd645c Report Status: 268435456 Hashed bucket: 60d544181622a84597aaa5b932a4ef1f Cab Guid: 0 ~~~ biblepay-qt.exe Stopped working 12/31/2018 12:28:15 PM All Users 0xc0000374 A heap has been corrupted. StackHash_8dde 10.0.17134.471 C:\Program Files\BiblepayCore\biblepay-qt.exe 15,210 C:\Users\All Users\Microsoft\Windows\WER\ReportArchive\AppCrash_biblepay-qt.exe_d0cea5e9f3db56a2da25c9b87a21142dfdb2ff_0c644e00_1a1ead24\Report.wer It might be due to the way we handle our masking of the flashing boinc command window - not being compatible with win10 Home - I'll jump in and add a switch right now to allow you to disable that feature and then you guys can tell us if it fixes it. This will take a while to compile; hang on. 1.1.7.6 is out there, anyone who crashed on Win10-home will you please test to see if the problem was the initializing boinc windows? Please add this to the config file: boincmetrics=-1 (-1 means dont try at all, 0 is the default, and 1 means try the legacy way (IE visible command prompt windows)).
|
|
|
|