I just found I missed last POBH payment for block 53505. Is there a way to know why? Nothing changed since block 53300 and I have several PODC updates.
From the pool website, the rosseta leaderboard only has the lastest block. Is there a way to check the block 53505?
Easiest way is to check on biblepay-central.org. There is a history of PODC payments, PODC updates etc. The payments are not quite accurate, but give a good idea.  Imho the phrase should be the payment history is generally 95% accurate or higher. The history snapshot is taken from one sanctuarys view of the network. There is a chance that a new cpid, or a cpid that had a change in magnitude was not viewed as part of the consensus at the time the history snapshot was taken. But in general it should be 95% accurate or higher. So missing some payment is normal? My wallet just had incoming transaction and PODC updates since block 53300. It is an old cpid. Nothing changed. What do you mean a change in magnitude? When will it happen to an old cpid? I was referring to the accuracy of the historical info, not your individual case. If you give us your cpid, we can try 'exec utxoreport cpid' and look for gaps. |
|
|
|
|
All outbound orphan letters to compassion, bloom and cameroon one have been sent.
|
|
|
|
I just found I missed last POBH payment for block 53505. Is there a way to know why? Nothing changed since block 53300 and I have several PODC updates.
From the pool website, the rosseta leaderboard only has the lastest block. Is there a way to check the block 53505?
Easiest way is to check on biblepay-central.org. There is a history of PODC payments, PODC updates etc. The payments are not quite accurate, but give a good idea. Imho the phrase should be the payment history is generally 95% accurate or higher. The history snapshot is taken from one sanctuarys view of the network. There is a chance that a new cpid, or a cpid that had a change in magnitude was not viewed as part of the consensus at the time the history snapshot was taken. But in general it should be 95% accurate or higher. |
|
|
|
** Huge News for Mac **
We are now fully supporting the Mac OS! Web site being updated now with mac download link: https://www.biblepay.org/biblepaycore.dmgPlease test this on various mac flavors! Great job MIP for making this happen! MIP is debugging MacOSX in house and making releases.
|
|
|
|
Ive submitted us for a slot for a Bitcointalk Banner Ad again,
I think we have a higher chance of not getting rejected this time
Why do you think so? Theymos is notorious for rejecting projects which he personally doesn't like, under that bizarre excuse that "it's an ICO". I researched a bit and found out about other coins which had the same fate as BiblePay - they got rejected with that same reason, and they are of course not ICOs. And he doesn't respond anymore after that, for example if you try to say that it's not an ICO, or anything for that matter. I can't believe he can get away with that, it's like he's trying to a find a rule which the ad would break, and maybe the ICO rule is not provable or something. While betting and gambling ads are completely fine with him, where people lose money. They are in fact running right now. I don't have high hopes that he will approve the ad this time around, because he will remember that he already rejected it. But in any case, my advice is to clearly write in big letters that BiblePay is not an ICO, that it's a 1-year old project! In fact I would put that in the first sentence as the header of the post - that way he can't miss it and can't say that it's an ICO again. its classic/same way when owners of 3 big exchanges wrote me that BBP is scam..... its same ... im tried to ask if they can list us for btc/etg  No - I don't believe that the top 3 exchanges said we were a scam. Please give me the contact info and let me verify this, and/or take up communication with them. I believe you made this up. |
|
|
|
so I bought some BBP on SouthExchange to stake more BBP to get a higher reward.
BBP is a side hobby for me and we support Compassion kids on our own, but I've gotta say there's no easy way to figure this stuff out for someone new. Now granted I have two rigs with many GPUs running and I can mine about anything, but Biblepay has to make it cryptic.
For one, my RAC is 1607, the console knows that, so why doesn't the wallet show me how much BBP I need to stake to get 100% UXTO awards?
found this on another thread: Stake 20 BBP per RAC and you will receive : (YOUR_RAC/TEAM_RAC) x SUPERBLOCK_REWARD x 0.7.
So why not add something to give a suggested stake level to the wallet... it could be to the far right of the Available balance.
So I changed my utxoamount=36321 (was 5539) in the biblepay.conf and exec stakebalance still shows: 5539. I shut the wallet down and restarted so I'm guessing it takes time, but how much I can't seem to locate.
So if the utxoamount= still needs to be in the .conf file then why isn't the wallet smart enough to autostake the max amount available? Or why can't it stake at 75% of available balance if someone doesn't want to stake it all?
ETA: after 30 to 40 mins my stakebalance is now 36321.
You can type 'exec totalrac' to find out how much UTXO is required. You can comment out 'utxoamount' and 'utxooverride' in the config. When its not present, we automatically stake the "UTXO Target" amount (from exec totalrac) in the PODC Update. |
|
|
|
Security is actually more reliant on the distinct CPID, not on copies of it. I never said it was frowned on to run multiple wallets.
My point is if you want to run multiple heat mining wallets, you can set a simple switch.
What is frowned on is not understanding blockchain programming, and what I mean by that is the ignorance of proposing a bad solution that bloats the chain. Remember, most of us are not developers (let alone blockchain developers). So, know in advance, we may make suggestions not fully knowing the intricacies or even the background knowledge of this blockchain fully works. > My point is if you want to run multiple heat mining wallets, you can set a simple switch. I wish there was a way to could keep our main wallet.dat on one machine only, but still be able to mine on mutiple computers. Having to copy wallet.dat to multiple machines is a security concern for me. Instead of securing one machine, I know how to worry about x number of computers that have the same wallet.dat Doesn't the masternode have some sort of mechanism to secure/lock funds and not require you to have the wallet on the same computer as the masternode? Not a problem, I am all for making the wallet smart enough to act more like an iPhone (IE improve our ease-of-use features). And not against supporting the n+1 wallets intelligently. The issue was how it was approached. If a feature request is made in a very respectable way, it will receive all the credit and explanation. If otoh, the user is demanding, or rude, or assumptions are made (without simply asking others how something works first), a person comes across as a know it all, and disrespects the lead dev, etc, then things will go south quickly. As far as not copying the wallet, you could dump the private key for the Rosetta pay to public key address, and import that key into the submachines. Im not currently thinking of a graceful way to heat mine on the sub machines without doing that. We get too much benefit from requiring the distinct CPID to be signed with magnitude than to change that feature. |
|
|
|
** ASIAN COMMUNITY ALERT **
Please see this gem that Linda from QIEX translated for us: https://pool.biblepay.org/Docs/BiblePay_WhitePaper_Chinese.pdfPlease let us know if there are any fundamental errors, or if it is good the way it is. If its good we can use it on the upcoming new website! This is instrumental in expanding our presence in China!
|
|
|
|
I do think the 2nd wallet sending partial stake reports should be looked at and addresed in the wallet.
The primary is smart enough to handle it, the secondary is missing a piece.
No - the 2nd - N+ wallets should have utxooverride=-1 set in the configs. Let not try to make up rules on how things should work without blockchain programming knowledge. Our ecosystem was designed for One controller wallet. If people are insisting to mine with the same CPID on more than one, then they need to set a config switch. "Having a backup wallet that can do PODC updates is security, and should not be frowned on." That is actually a good point. It would be good to have some redundancy, especially if you're a large miner. Don't know if it's technically possible though? Security is actually more reliant on the distinct CPID, not on copies of it. I never said it was frowned on to run multiple wallets. My point is if you want to run multiple heat mining wallets, you can set a simple switch. What is frowned on is not understanding blockchain programming, and what I mean by that is the ignorance of proposing a bad solution that bloats the chain. Jaap I have to delete your last post as you quoted snats disrespectful attitude, sorry. TheSnat, if you aren't going to respect the community here I think you should find somewhere else to troll your belligerent attitude, thanks. |
|
|
|
I do think the 2nd wallet sending partial stake reports should be looked at and addresed in the wallet.
The primary is smart enough to handle it, the secondary is missing a piece.
No - the 2nd - N+ wallets should have utxooverride=-1 set in the configs. Let not try to make up rules on how things should work without blockchain programming knowledge. Our ecosystem was designed for One controller wallet. If people are insisting to mine with the same CPID on more than one, then they need to set a config switch. |
|
|
|
I think one issue is the net upvotes required were changed to 10 from 7 a little while back when the corrupt person was copy-pasting.
But the easiest thing to do is if you give me the "added" timestamp of one of the letters that is not paid yet, and let me specifically check one. Then I can check the actual business logic. Note that if it says 'approved=0' that would explain why you were not paid yet (approved get set to 1 after 10 net upvotes are hit).
I plan on adding an indicator that shows how much of the 500K bounty we spent on letter rewards somewhere on the front page so we know when we need a proposal for a refill.
Hmmm, yes on the 'please wait until next month' we were checking for any letters you wrote even if sent; to make this easier I changed it to letters written within 30 days that have not been sent (up to 3), please try now.
So I wrote three new letters, but one of them is not showing up in the list for some reason, although it must be in the system because it says I need to wait until next month to write any more letters. Also, increasing the upvotes required to 10 may backfire a bit as it doesn't seem like many people vote on the letters. I also agree with Jaap that it would be great to be able to our own past letters so we can keep track of which orphans we've written to and try to write to them again if we can. Yes, I agree that would be a good feature. I think we can make that happen. We have one more high priority feature however that Luke and Jaap brought to my attention that is not in the pool yet: We need a grand total paid per month for Charity, this helps people write blogs, and we need a feature that allows non Compassion Charity expenses to be added to the pool for total accountability. Ill jump on these 3 features asap. In the meantime, you had a blank letter stuck in the system; cleared; please try again. |
|
|
|
Is it possible that there is a problem with the payout of the letter-writing bounty? I've written six letters in may (using two accounts), and as far as I can see, only one or two of those letters have received payout and one letter is still in the 'outgoing letters' section. I would be strange if the other three letters were downvoted, since I think that they were good quality letters (with photos attached to them). Also, when I try to write a letter now, a box pops up saying 'outbound letter exceeded - Sorry, please wait until next month to write more letters'. On both my accounts, the outbound letter counter says '3', so that's right, but I've written the letters in May, so it should have been reset by now, right? On the letter: is it possible to see the letters you have sent? It would be good documentation for myself to have an archive of which children I sent what  Hi Jaap, I think one issue is the net upvotes required were changed to 10 from 7 a little while back when the corrupt person was copy-pasting. But the easiest thing to do is if you give me the "added" timestamp of one of the letters that is not paid yet, and let me specifically check one. Then I can check the actual business logic. Note that if it says 'approved=0' that would explain why you were not paid yet (approved get set to 1 after 10 net upvotes are hit). I plan on adding an indicator that shows how much of the 500K bounty we spent on letter rewards somewhere on the front page so we know when we need a proposal for a refill. Hmmm, yes on the 'please wait until next month' we were checking for any letters you wrote even if sent; to make this easier I changed it to letters written within 30 days that have not been sent (up to 3), please try now. |
|
|
|
I started running BOINC on an Android device a couple of days ago.
It shows up in Your Computers at my boinc.bakerlab.org account, user name zthomasz.
It has crunched some Rosetta tasks (Avg Credit 65, Total Credit 673) but it is not in the Rosetta Unbanked Report at pool.biblepay.org.
Is there anything I need to do to get it listed on at the pool?
First please ensure it is part of team Biblepay. Next, decide if you want it to share your existing CPID (IE if you have other PCs associated with your wallet and want to add the phone on to that existing cpid). If you do, just ensure the e-mail matches your other machines e-mail, and then all machines + this phone will tally to your controller wallet magnitude. If you are sure you want to make it an unbanked phone, with its own distinct CPID, then you can log into the pool, and click Account | Associate Unbanked Device. Once that is done you should show up in the unbanked report after ~ 6 confirms or so. I have BOINC running on Windows PCs and Linux servers using the same CPID and associated with the same wallet. If I want my Android device to be Unbanked, I just attach it to a new Rosetta account with a new CPID. Do I need to associate the new CPID/Android with a new BBP wallet, or can I use the same wallet that I use for my Windows/Linux devices? You need to associate it with your account in the pool, but you can use a receive-address from one of your current wallets. (There is a guide on the new website btw ) Thanks, I knew that. My question is ... Do I need to associate the new CPID/Android with a new BBP wallet, or can I use the same wallet that I use for my Windows/Linux devices? Wiki guide: To associate the Researchers CPID with Biblepay, perform the following steps: Ensure you have an account with Rosetta@Home, and a CPID Launch Biblepay Click on the Distributed Computing Association Tab from the home page of the wallet Populate "Rosetta@Home" in the Project Name by choosing it from the drop down Populate your Rosetta@Home UserName in the UserName field Populate your Rosetta@Home Password in the Password field Click AssociateWhen you associate an unbanked CPID with a receiving address using the pool, it actually sets up the core wallet to receive payments to that address as long as that CPID only has ARM RAC (and is a distinct CPID). So you do not need a new wallet to do this. (Note: the payments do not come from the pool, this is just a service for convenience since an unbanked user may not have a PC). So as long as this CPID is ARM only, you can use an existing receiving address and not hose your home machines research income. NOTE: Here is the actual warning, of when you can hose your research: If you build up some rac on CPID X (using non arm PC devices), and associate CPID X from the pool 10 days later, since we only allow the Last instance of the CPID to be honored in the chain, you have now effectively deleted your home PC CPID and its RAC. So you would effectively Cut off your income and your unbanked income would not work either (since you have PC RAC - making it technically fail the unbanked test). To unravel this you would just need to re-associate your CPID X at home on a PC (outside of the pool). The pool is just for ARM-only cpids. |
|
|
|
So your CPID is in the chain and it cant send a podcupdate, interesting. Alright please see if downgrading actually solves it; I only have 1.1.1.9, which should be OK for this, here is the link: https://pool.biblepay.org/downloads/biblepaycore-1.1.1-win64.exeI'll check further into the problem. Before you downgrade please try this and tell me if it solves it so we know the problem: Boot wallet Wait 5 mins Type exec getboincinfo (Verify the CPID is present) Type exec podcupdate (Verify you dont see the error that no cpids exist that you saw before) Then do: (This means you start the miner *after* exec getboincinfo was called) setgenerate true 5 (or whatever number) getmininginfo Tell me if it mines. I think the problem is that 'exec getboincinfo' has to be run before 'setgenerate true X'. If that is the case its a race condition that needs a line of code during boot to fix 1.1.2.6. Yep, that's exactly it! What I did: 1. Stop wallet. 2. Change to "gen=0" in config 3. Start wallet, wait shortly. 4. exec getboincinfo was successful 5. exec podcupdate was successful (!) 6. setgenerate true 4 7. getmininginfo showed no errors (!) Nice troubleshooting. btw: it's almost midnight, I'm going to bed now.  Thanks a lot for the debugging guys. So it looks like it was a race condition based on the logic also (caused by moving those prayers to the background thread). Ok, Im testing the fix now, Ill have 1.1.2.7 out there before midnight tonight. Anyone who was testing 1.1.2.6 and had mining problems, please upgrade to 1.1.2.7. The race condition should be fixed now... Note in 1.1.2.7 getmininginfo will show something to the effect of "Loading CPIDs" until the wallet is warmed up. Sorry about the inconvenience. |
|
|
|
So your CPID is in the chain and it cant send a podcupdate, interesting. Alright please see if downgrading actually solves it; I only have 1.1.1.9, which should be OK for this, here is the link: https://pool.biblepay.org/downloads/biblepaycore-1.1.1-win64.exeI'll check further into the problem. Before you downgrade please try this and tell me if it solves it so we know the problem: Boot wallet Wait 5 mins Type exec getboincinfo (Verify the CPID is present) Type exec podcupdate (Verify you dont see the error that no cpids exist that you saw before) Then do: (This means you start the miner *after* exec getboincinfo was called) setgenerate true 5 (or whatever number) getmininginfo Tell me if it mines. I think the problem is that 'exec getboincinfo' has to be run before 'setgenerate true X'. If that is the case its a race condition that needs a line of code during boot to fix 1.1.2.6. Yep, that's exactly it! What I did: 1. Stop wallet. 2. Change to "gen=0" in config 3. Start wallet, wait shortly. 4. exec getboincinfo was successful 5. exec podcupdate was successful (!) 6. setgenerate true 4 7. getmininginfo showed no errors (!) Nice troubleshooting. btw: it's almost midnight, I'm going to bed now. Thanks a lot for the debugging guys. So it looks like it was a race condition based on the logic also (caused by moving those prayers to the background thread). Ok, Im testing the fix now, Ill have 1.1.2.7 out there before midnight tonight. |
|
|
|
I don't see a problem with 1.1.2.6, this looks to be on your end.
Classic IT response.. I'll sit back and watch if others encounter issues. edit2: Same message on testnet with a "clean" install and associated cpid. ... Let me check into this... I dont see a problem with 1.1.2.6, Im still mining after 24 hours. To diagnose this in prod, first type: exec datalist dcc;YYYY 365 Where YYYY equals the first 4 chars of your CPID. Paste the results here. Step 2: Type 'exec podcupdate' and paste the results here. I'm sure the other person who had the problem resolved itself after the prayers were memorized. The high cpu usage during 15 seconds after the GUI loads is just the prayers being memorized in the background. You should leave the machine on for at least 10 minutes of mining to see if the errors clear. Wallet has been running for hours, but no POBh possible. {
"DataList": "DCC;7C92",
"4559FEF3C1C689EE9FC3FF42494 (03-07-2018 20:01:05)": "7c9264559fef3c1c689ee9fc3ff42494;BNetxsZfjyNfW73Kvsh5AYLHENpEHcR3qh;BNetxsZfjyNfW73Kvsh5AYLHENpEHcR3qh;1981794;IIN5nTV5xxNV9tflryvwAcWzvf9WyxKPUx1XxpKGl1tgOZQ3uXzDIxPgjxxTtUIyZXHa1TMzDuTFcPDS7cl/U10=;0"
}{
"Command": "podcupdate",
"PODCUpdate": "Unable to find any CPIDS. Please try exec getboincinfo."
}Thx for looking into this. In the meantime: is there an archive with the old 1.1.2.4 win64-install? I'd like to go back to that for the time being... So your CPID is in the chain and it cant send a podcupdate, interesting. Alright please see if downgrading actually solves it; I only have 1.1.1.9, which should be OK for this, here is the link: https://pool.biblepay.org/downloads/biblepaycore-1.1.1-win64.exeI'll check further into the problem. Before you downgrade please try this and tell me if it solves it so we know the problem: Boot wallet Wait 5 mins Type exec getboincinfo (Verify the CPID is present) Type exec podcupdate (Verify you dont see the error that no cpids exist that you saw before) Then do: (This means you start the miner *after* exec getboincinfo was called) setgenerate true 5 (or whatever number) getmininginfo Tell me if it mines. I think the problem is that 'exec getboincinfo' has to be run before 'setgenerate true X'. If that is the case its a race condition that needs a line of code during boot to fix 1.1.2.6. |
|
|
|
I don't see a problem with 1.1.2.6, this looks to be on your end.
Classic IT response.. I'll sit back and watch if others encounter issues. edit2: Same message on testnet with a "clean" install and associated cpid. ... Let me check into this... I dont see a problem with 1.1.2.6, Im still mining after 24 hours. To diagnose this in prod, first type: exec datalist dcc;YYYY 365 Where YYYY equals the first 4 chars of your CPID. Paste the results here. Step 2: Type 'exec podcupdate' and paste the results here. I'm sure the other person who had the problem resolved itself after the prayers were memorized. The high cpu usage during 15 seconds after the GUI loads is just the prayers being memorized in the background. You should leave the machine on for at least 10 minutes of mining to see if the errors clear. Wallet has been running for hours, but no POBh possible. {
"DataList": "DCC;7C92",
"4559FEF3C1C689EE9FC3FF42494 (03-07-2018 20:01:05)": "7c9264559fef3c1c689ee9fc3ff42494;BNetxsZfjyNfW73Kvsh5AYLHENpEHcR3qh;BNetxsZfjyNfW73Kvsh5AYLHENpEHcR3qh;1981794;IIN5nTV5xxNV9tflryvwAcWzvf9WyxKPUx1XxpKGl1tgOZQ3uXzDIxPgjxxTtUIyZXHa1TMzDuTFcPDS7cl/U10=;0"
}{
"Command": "podcupdate",
"PODCUpdate": "Unable to find any CPIDS. Please try exec getboincinfo."
}Thx for looking into this. In the meantime: is there an archive with the old 1.1.2.4 win64-install? I'd like to go back to that for the time being... So your CPID is in the chain and it cant send a podcupdate, interesting. Alright please see if downgrading actually solves it; I only have 1.1.1.9, which should be OK for this, here is the link: https://pool.biblepay.org/downloads/biblepaycore-1.1.1-win64.exeI'll check further into the problem. |
|
|
|
I've found a very interesting concept which could be useful in the times during and after The Great Tribulation: PoHW (Proof of Human Work)https://bitcointalk.org/index.php?topic=4459113@Rob, I think you may like this concept. I wonder if something along those lines could be in BiblePay someday. I read it and have read similar ideas in the past, but the problem still appears to be the actual verification process can be hacked in opensource software. It's an interesting concept though. |
|
|
|
|
Show Posts
