 Show Posts
|
|
Pages: « 1 [2] 3 4 5 6 »
|
Hoping someone will find this helpful for setting up a wallet in Windows 10 - https://www.youtube.com/watch?v=jlwEkgyO-zU Please subscribe and like if it is helpful. I plan on doing another for setting up PoDC2.0 I'm not great at making videos but am gonna try getting members of my team collecting soon and it is easier to follow when you have a visual. |
|
|
|
Not sure if Feeding America fits into the "efficient" charity threshold... but they spend 76% on Programs relative to overhead and $30 is spent to raise $100. https://www.charitywatch.org/charities/feeding-americaI bring this up because Swagbucks is offering 1000 swagbucks back (each SB is worth $0.01, so $10) if you donate a minimum of $18. Just need to find offers that scale better and can apply to many for an extended period of time (like match offers, etc to amplify giving).  Just make sure you set up an account with Swagbucks before trying to use the offer though. |
|
|
|
|
Just a heads up in case anyone has issues.
World Community Grid: Planned Maintenance on Friday, January 24, 2020
We are updating the operating system on our servers on Friday, January 24, beginning at 17:00 UTC.
1/23/2020 4:45:12 PM ·
|
|
|
|
|
I got 4 work units on the same device. I do have about 30 devices that are currently pulling work from another project waiting for WCG. This batch is 100. If it goes well, per the thread I linked, they will release more batches. If things go well, he also said this would be a longer running BETA than normal since MCM has never supported this platform before. Basically, this is positive news for Android (wallet) users as there are currently no other Android work available unless SCC suddenly releases something.
|
|
|
|
Same problem on another machine. Upgrading from 1.4.8.5 to 1.4.8.7
Rebuild in progress, and after I'm pretty sure wallet will crash.
Also, if you have been, please avoid killing the biblepay-qt process from task manager, please do not do that. That is a big no no in crypto. If you kill the wallet without gracefully exiting, you will corrupt all of your databases - both berkeley DB and the underlying blocks and chainstate and wallet and you will be in for nothing but trouble in the future. I've had a good 1 year run now with the same database and no corruption simply by exiting from the menu. - Just to clarify - that is not a crash. That is a notification that you have a corrupt database file. (A crash is an unhandled exit in the program, this was handled). Mine did this when upgrading. When I started rebuilding, I let it do its thing. Came back hours later and the wallet had closed itself. Launched again and it started rebuilding all over again without prompting. It seems to have worked fine after that. Just wanted to add my experience in case it is a mass thing. My wallet was properly exited using the file menu. I just ran the update over the old. This was on Windows 10 64 bit. |
|
|
|
Sunk, wasn't this the bug Rob said he was fixing in the next version? IIRC you just had to restart the wallet and it would show correct.
I think the restart of the wallet (or entire system) with exec rac not showing the link: https://bitcointalk.org/index.php?topic=2388064.msg53470948The specific issue is that a CPID can't associate when it is not part of team BiblePay. The ^1.6 requirement works for non-BBP team but the current workflow seems to require you join team BiblePay (in version 1.4.8.4) then change to another team. Well, mine was associated back in PoDC 1.0, so not sure if that was a reason why it worked in 2.0. Otherwise, I've never been a member of team BBP and I believe that is the version I used to associate. Restarting the client would show it correctly being associated. |
|
|
|
|
Sunk, wasn't this the bug Rob said he was fixing in the next version? IIRC you just had to restart the wallet and it would show correct.
|
|
|
|
1) Strictly on the part about the 'exec rac' switching from the 37Mil requirement over to 'not being linked', that is a bug in this first version, but note, its not the kind of bug affecting PODC or payments (its a client glitch on the display purposes only). You can get around it by rebooting the client or waiting four hours (then exec rac will work again). Im trying to get that fixed as a leisure asap. 2) So Im looking at your coinage reqs. Since you arent on team bbp, thats why the req is so high (37 mil). Yes, we are supposed to put you in the leaderboard with a commensurate low reward, but I see we have a minimum threshhold (I honestly dont remember doing that, but for now we have it because its the consensus for the sancs). So here is how the two step phase works: On Non-Team BBP, we check your req, and 54000 rac reqs 37Mil in coin-age. Then we reduce your minimum RAC req (after we see you didnt make it), to 4368 RAC. Then we see if you have a coin age of 667,501 BBP (but you didnt meet that), so that explains why you are not in the leaderboard. Note, that if you send out a GSC, you will show up in the leaderboard in about 5-7 blocks, as long as you satisfy the req. So if possible, if you join team BBP, what would happen is the req would drop to 53.9K for 4368 (after missing the first) and you would be in the leaderboard. This also explains why you have not received podc rewards (you must be in the leaderboard to get podc rewards). OK, so since I won't switch teams (as I am a team captain) then my only option is to set up an Exchange account and purchase more Biblepay to meet the minimum requirements which isn't going to happen either. I don't trust the current exchanges. So, I guess what I need to know now is how to turn off PoDC so that I'm not wasting my BBP with GSC transmissions that won't ever pan out a return. I also see this as an issue that will most likely occur with many BOINC contributors that may be tempted to create wallets. It should also be explained better in the wiki as this seems to be a "dead zone" of sorts. Also, since there is no Android (or mobile) work to crunch at WCG right now (for a few months now actually) and no ETA on when it will return (scientists have not said when SCC will have work again and WCG has no official plans for Android work on the other sub projects) then isn't it a moot point right now to have a low RAC stipulation for unbanked? Maybe a note needs added to the wiki for this as well. 1) 10-4 on WCG lacking the mobile app. Thank you. 10-4 on the wiki guide. And the dead area on unjoining a project. 2) As far as a moot point for unbanked, I think its a two part deal. MIP is working on making the 'sendgscc wcg' work on the mobile. But yes once he finishes, we will have a challenge to deal with. We'll have to make a post on the WCG threads and ask them if *any* sub projects will ever return for android? If they say no we might as well stop working on that MIP, until we have a better idea. I think its certainly a good feature to have; we should have a coin that is friendly to third world countries who have no bank accounts. Back when our price was higher we calculated that mobile research was enough to live on in a third world country (food only). 3) To unjoin please type: 'exec unjoin wcg'. That should stop the daily gsc transmission. 4) As far as trust, I don't have any reason to not trust SX personally. One way you can minimize the risk is not keeping any latent digital asset on an exchange overnight - just make small trades (IE 100K bbp) and take it out immediately, then repeat etc. Thanks Rob. As of right now Smash Childhood Cancer (SCC) is supposed to return. They just haven't given an ETA. That is the only sub project with Android apps left. People keep asking in the forums but aren't getting much hope on a new app coming down the pipeline for Android. Allegedly there are two more climate based sub projects in the works but not much has been stated on these and it has been stated that they won't have Android work as it is not suitable for those devices. WCG doesn't actually develop the apps. The scientists that bring their research to WCG is responsible for all of that and they won't open their code to the public for additional help. This is one of the reasons why they have only ever had one GPU application which ended 2 years worth of work in like 6 months. I agree it would be nice to have one for small mobile devices. I actually have ~30 devices on my shelf that are dedicated to DC. Right now, they are working on Universe@home due to the lack of good Bio/Medical projects that support Android and have work for them. |
|
|
|
Yesterday running exec rac got me:  { "Command": "rac", "cpid": "1bb993deb5284d5f357c6ef05d8eddb2", "CPK": "BSzYoSHeQGwAGseo12gq67KdL56AhVSoEV", "next_podc_gsc_transmission": 166357, "team_name": "Unknown", "external_purse_total_coin_age": 1789.596875000001, "coin_age_percent_required": 0.99, "NOTE!": "Coins must have a maturity of at least 5 confirms for your coin*age to count. (See current depth in coin control).", "WARNING!": "BiblePay requires staking collateral to be stored in your Christian-Public-Key (External Purse) to be available for GSC transmissions. You currently do not have enough coin age in your external purse. This means your PODC reward will be reduced to a commensurate amount of RAC. Please read our PODC 2.0 guide about sending bankroll notes to yourself. ", "coin_age_required": 37331261.2988052, "wcg_id": 338542, "rac": 54018.86 } 21:53:52  However today when I run it I get: exec rac 21:53:52  { "Command": "rac", "cpid": "1bb993deb5284d5f357c6ef05d8eddb2", "temporary_cpid": "1bb993deb5284d5f357c6ef05d8eddb2", "Error": "Your CPID is linked to your CPK, but we are unable to find your research records in WCG; most likely because you are not in team BiblePay yet.", "Step 1": "Log into your WCG account at 'worldcommunitygrid.org' with your WCG E-mail address and WCG password.", "Step 2": "Click Settings | My Profile. Record your 'Username' and 'Verification Code' and your 'CPID' (Cross-Project-ID).", "Step 3": "Click Settings | Data Sharing. Ensure the 'Display my Data' radio button is selected. Click Save. ", "Step 4": "Click My Contribution | My Team. If you are not part of Team 'BiblePay' click Join Team | Search | BiblePay | Select BiblePay | Click Join Team | Save.", "Step 5": "NOTE: After choosing your team, and starting your research, please give WCG 24 hours for the CPID to propagate into BBP. In the mean time you can start Boinc research - and ensure the computer is performing WCG tasks. ", "Step 6": "From our RPC console, type, exec associate your_username your_verification_code", "Step 7": "Wait for 5 blocks to pass. Then type 'exec rac' again, and see if you are linked! ", "Step 8": "Once you are linked you will receive daily rewards. Please read about our minimum stake requirements per RAC here: wiki.biblepay.org/PODC" } I am not on team BiblePay. According to the documentation I do not have to be. Is this accurate or is it limited to team BiblePay and Gridcoin? https://wiki.biblepay.org/PODC_SetupI can see that I have now sent out 3 GSC transmissions in the wallet but have not received any payouts for contributions to WCG. Before asking, I have contributed to WCG non-stop for 12 years. My RAC is fully established by now. I am aware that coin age may be a factor, but wasn't sure if that is the case since the reply mentioned not being part of the team. I will also add that I do allow stats exporting. 1) Strictly on the part about the 'exec rac' switching from the 37Mil requirement over to 'not being linked', that is a bug in this first version, but note, its not the kind of bug affecting PODC or payments (its a client glitch on the display purposes only). You can get around it by rebooting the client or waiting four hours (then exec rac will work again). Im trying to get that fixed as a leisure asap. 2) So Im looking at your coinage reqs. Since you arent on team bbp, thats why the req is so high (37 mil). Yes, we are supposed to put you in the leaderboard with a commensurate low reward, but I see we have a minimum threshhold (I honestly dont remember doing that, but for now we have it because its the consensus for the sancs). So here is how the two step phase works: On Non-Team BBP, we check your req, and 54000 rac reqs 37Mil in coin-age. Then we reduce your minimum RAC req (after we see you didnt make it), to 4368 RAC. Then we see if you have a coin age of 667,501 BBP (but you didnt meet that), so that explains why you are not in the leaderboard. Note, that if you send out a GSC, you will show up in the leaderboard in about 5-7 blocks, as long as you satisfy the req. So if possible, if you join team BBP, what would happen is the req would drop to 53.9K for 4368 (after missing the first) and you would be in the leaderboard. This also explains why you have not received podc rewards (you must be in the leaderboard to get podc rewards). OK, so since I won't switch teams (as I am a team captain) then my only option is to set up an Exchange account and purchase more Biblepay to meet the minimum requirements which isn't going to happen either. I don't trust the current exchanges. So, I guess what I need to know now is how to turn off PoDC so that I'm not wasting my BBP with GSC transmissions that won't ever pan out a return. I also see this as an issue that will most likely occur with many BOINC contributors that may be tempted to create wallets. It should also be explained better in the wiki as this seems to be a "dead zone" of sorts. Also, since there is no Android (or mobile) work to crunch at WCG right now (for a few months now actually) and no ETA on when it will return (scientists have not said when SCC will have work again and WCG has no official plans for Android work on the other sub projects) then isn't it a moot point right now to have a low RAC stipulation for unbanked? Maybe a note needs added to the wiki for this as well. |
|
|
|
|
Coin age is not the same as BiblePay total. So 1 BBP in your wallet untouched for 3 days is 3 days worth of coin age. At least that is how I understand it. And yes this is an issue for DC'ers and requiring such an up front amount to get started. I am not a large DC'er and I don't have the amount needed as I only have a little over 100k BBP total to work with.
|
|
|
|
Yesterday running exec rac got me:  { "Command": "rac", "cpid": "1bb993deb5284d5f357c6ef05d8eddb2", "CPK": "BSzYoSHeQGwAGseo12gq67KdL56AhVSoEV", "next_podc_gsc_transmission": 166357, "team_name": "Unknown", "external_purse_total_coin_age": 1789.596875000001, "coin_age_percent_required": 0.99, "NOTE!": "Coins must have a maturity of at least 5 confirms for your coin*age to count. (See current depth in coin control).", "WARNING!": "BiblePay requires staking collateral to be stored in your Christian-Public-Key (External Purse) to be available for GSC transmissions. You currently do not have enough coin age in your external purse. This means your PODC reward will be reduced to a commensurate amount of RAC. Please read our PODC 2.0 guide about sending bankroll notes to yourself. ", "coin_age_required": 37331261.2988052, "wcg_id": 338542, "rac": 54018.86 } 21:53:52  However today when I run it I get: exec rac 21:53:52  { "Command": "rac", "cpid": "1bb993deb5284d5f357c6ef05d8eddb2", "temporary_cpid": "1bb993deb5284d5f357c6ef05d8eddb2", "Error": "Your CPID is linked to your CPK, but we are unable to find your research records in WCG; most likely because you are not in team BiblePay yet.", "Step 1": "Log into your WCG account at 'worldcommunitygrid.org' with your WCG E-mail address and WCG password.", "Step 2": "Click Settings | My Profile. Record your 'Username' and 'Verification Code' and your 'CPID' (Cross-Project-ID).", "Step 3": "Click Settings | Data Sharing. Ensure the 'Display my Data' radio button is selected. Click Save. ", "Step 4": "Click My Contribution | My Team. If you are not part of Team 'BiblePay' click Join Team | Search | BiblePay | Select BiblePay | Click Join Team | Save.", "Step 5": "NOTE: After choosing your team, and starting your research, please give WCG 24 hours for the CPID to propagate into BBP. In the mean time you can start Boinc research - and ensure the computer is performing WCG tasks. ", "Step 6": "From our RPC console, type, exec associate your_username your_verification_code", "Step 7": "Wait for 5 blocks to pass. Then type 'exec rac' again, and see if you are linked! ", "Step 8": "Once you are linked you will receive daily rewards. Please read about our minimum stake requirements per RAC here: wiki.biblepay.org/PODC" } I am not on team BiblePay. According to the documentation I do not have to be. Is this accurate or is it limited to team BiblePay and Gridcoin? https://wiki.biblepay.org/PODC_SetupI can see that I have now sent out 3 GSC transmissions in the wallet but have not received any payouts for contributions to WCG. Before asking, I have contributed to WCG non-stop for 12 years. My RAC is fully established by now. I am aware that coin age may be a factor, but wasn't sure if that is the case since the reply mentioned not being part of the team. I will also add that I do allow stats exporting. |
|
|
|
|
I'm not trying to cause friction but legitimately asking. Is our focus on PoDC now moved away from cancer research? Out of WCG's remaining six sub projects, only two are cancer focused. One hasn't had work for months. Should we fairly say the focus has shifted to a general humanitarian goals instead? I want to say the stats exports let you track by a sub project level and so could be tied to those if desired. However I don't know if that is also on a user level or just team level.
Just so others are aware, one sub project (only one with Android work) hasn't had work in months with no ETA in sight. Two sub projects with small quantities to go around. Fah2 has work but mip and mcm seem to have the largest amount available at any given time. Also for those unaware, mip is very heavy on L3 cache. Rule of thumb is run no more than one mip work unit per 4mb cache that your CPU has or your performance will suffer a good deal.
|
|
|
|
Rob, Togo, & Sunk, it appears that my wallet is back in business and I even associated my CPK for PoDC 2.0. Thanks again for the suggestions and assistance. You guys have been busy. Don't forget to rest and enjoy the holidays.  |
|
|
|
Thanks Togo. Giving that a try now.
Looking at our 4 dns servers, I see the problem, apparently when we switched to dynamic ports, we no longer listen on 40,000 by default in these core nodes. I just updated all 4 to use the 40,000 default ports. Please try now. Also please ensure your system time is correct. Nothing changed over night. Just restarted the client but nothing yet. I will check back when the family is done with opening gifts. This can be fixed in minutes... We just need you to confirm that your system time and timezone is correct, and post your IP, and then I can check the DNS1 log and unban you. Or you can add an addnode like they suggested. DNS1-4 is working. I actually already posted in previous posts that the time/date were correct. (yes I manually sync'd it to verify) I have also posted adding the nodes as both Togo and Sunk suggested. So, I guess all that is left is my IP address. Currently it is 107.77.210.51 Edit: I want to say it was Sunk that posted about this site earlier, but they have a faucet with BBP that new users could utilize for setting up PoDC. https://freefaucet.io/login/register.php?r=cl3dkde3mhcz2yj It is a small amount each time but it is something to get started. We can certainly debug this because weve been through this end to end, it can only be one of about 10 things. Could you please try this first: rm banlist.dat. rm debug.log (I ensured our banlist.dat was cleared on our first dns1 node, so your IP is not blocked). First just start the node. If no connections: addnode dns1.biblepay.org onetry If still no connections, try restarting again with "-erasechain=1". Just to be sure there is no data in there being passed off on other nodes (bad blocks). If still no connection could you please post the log snippet - that should show the reason you cant connect. One last thing to try ./biblepay-qt -connect=dns1.biblepay.org And: telnet dns1.biblepay.org 40000 I confirm the seed node is running and listening and synced, etc. I am using windows 10 if that helps. Here is the odd part. I removed the nodes to start clean and now it seems to be connecting on its own. (unless you had actually de-banned the ip already) I will see how it goes and report back from there. Thanks for taking the time to assist thus far. Oh OK, yes, although I did remove our banlist.dat and reboot dns1, I was just thinking what probably happened. You probably banned the main external nodes, because when you deleted banlist.dat, you found a connection. So all, lets remember this for next time: We should remove our own banlist.dat first, then restart. I had already deleted banlist.dat prior and it was still doing it. This time I just deleted the addnodes from my config file and it started working. |
|
|
|
Thanks Togo. Giving that a try now.
Looking at our 4 dns servers, I see the problem, apparently when we switched to dynamic ports, we no longer listen on 40,000 by default in these core nodes. I just updated all 4 to use the 40,000 default ports. Please try now. Also please ensure your system time is correct. Nothing changed over night. Just restarted the client but nothing yet. I will check back when the family is done with opening gifts. This can be fixed in minutes... We just need you to confirm that your system time and timezone is correct, and post your IP, and then I can check the DNS1 log and unban you. Or you can add an addnode like they suggested. DNS1-4 is working. I actually already posted in previous posts that the time/date were correct. (yes I manually sync'd it to verify) I have also posted adding the nodes as both Togo and Sunk suggested. So, I guess all that is left is my IP address. Currently it is 107.77.210.51 Edit: I want to say it was Sunk that posted about this site earlier, but they have a faucet with BBP that new users could utilize for setting up PoDC. https://freefaucet.io/login/register.php?r=cl3dkde3mhcz2yj It is a small amount each time but it is something to get started. We can certainly debug this because weve been through this end to end, it can only be one of about 10 things. Could you please try this first: rm banlist.dat. rm debug.log (I ensured our banlist.dat was cleared on our first dns1 node, so your IP is not blocked). First just start the node. If no connections: addnode dns1.biblepay.org onetry If still no connections, try restarting again with "-erasechain=1". Just to be sure there is no data in there being passed off on other nodes (bad blocks). If still no connection could you please post the log snippet - that should show the reason you cant connect. One last thing to try ./biblepay-qt -connect=dns1.biblepay.org And: telnet dns1.biblepay.org 40000 I confirm the seed node is running and listening and synced, etc. I am using windows 10 if that helps. Here is the odd part. I removed the nodes to start clean and now it seems to be connecting on its own. (unless you had actually de-banned the ip already) I will see how it goes and report back from there. Thanks for taking the time to assist thus far. |
|
|
|
Thanks Togo. Giving that a try now.
Looking at our 4 dns servers, I see the problem, apparently when we switched to dynamic ports, we no longer listen on 40,000 by default in these core nodes. I just updated all 4 to use the 40,000 default ports. Please try now. Also please ensure your system time is correct. Nothing changed over night. Just restarted the client but nothing yet. I will check back when the family is done with opening gifts. This can be fixed in minutes... We just need you to confirm that your system time and timezone is correct, and post your IP, and then I can check the DNS1 log and unban you. Or you can add an addnode like they suggested. DNS1-4 is working. I actually already posted in previous posts that the time/date were correct. (yes I manually sync'd it to verify) I have also posted adding the nodes as both Togo and Sunk suggested. So, I guess all that is left is my IP address. Currently it is 107.77.210.51 Edit: I want to say it was Sunk that posted about this site earlier, but they have a faucet with BBP that new users could utilize for setting up PoDC. https://freefaucet.io/login/register.php?r=cl3dkde3mhcz2yj It is a small amount each time but it is something to get started. |
|
|
|
Still not connecting to any peers. And yes the date and time are correct. Can't waste any more time today trying to get the latest client to work. May have another go tomorrow. It is just frustrating to have to fight this every time we have a big upgrade.
I would say: * quit biblepay wallet * erase everything in your biblepay folder except for wallet.dat and biblepay.conf (that includes all the folders including blockchain, san, llmq, etc) * restart biblepay wallet and sync from height 0 This is actually what I have been trying to do. It won't connect to ANY peers to even start sync'ing from height 0.... You might be banned because of the fork... so you might try going https://chainz.cryptoid.info/bbp/#!network Under nodelist for the latest version 1484, you can try adding the nodes manually addnode=109.157.126.30 addnode=13.59.180.68 addnode=134.101.7.88 addnode=14.231.206.198 addnode=144.202.56.183 addnode=148.59.174.210 addnode=149.28.215.112 addnode=155.138.228.109 addnode=155.138.236.76 addnode=155.207.70.146 addnode=155.207.70.25 addnode=155.207.70.27 addnode=155.207.70.38 addnode=155.207.70.44 addnode=155.207.70.79 addnode=155.207.70.82 addnode=155.207.70.84 addnode=155.207.70.86 addnode=155.207.72.71 addnode=155.207.72.86 addnode=157.230.152.110 addnode=157.230.175.49 addnode=159.203.96.171 addnode=167.86.74.98 addnode=173.180.116.201 addnode=173.238.232.163 addnode=178.143.24.140 addnode=178.170.72.149 addnode=178.170.72.154 addnode=178.170.72.155 addnode=18.224.246.84 addnode=195.201.116.198 addnode=202.97.251.251 addnode=210.13.84.226 addnode=212.237.30.143 addnode=216.116.134.129 addnode=216.116.134.64 addnode=217.112.36.195 addnode=218.250.191.216 addnode=24.133.137.158 addnode=36.70.45.47 addnode=37.228.244.204 addnode=37.229.154.194 addnode=38.240.19.34 addnode=45.62.235.218 addnode=45.77.165.14 addnode=45.77.74.143 addnode=47.189.52.131 addnode=52.42.102.242 addnode=68.58.243.174 addnode=71.135.70.180 addnode=76.170.58.128 addnode=81.213.176.213 addnode=85.216.245.90 addnode=89.36.217.238 addnode=95.105.188.255 addnode=95.216.127.253 addnode=95.216.127.254 addnode=95.216.252.101 addnode=95.217.67.252 addnode=95.217.97.210 addnode=95.217.97.214 addnode=95.217.97.220 addnode=95.217.97.234 addnode=98.115.175.151 addnode=99.27.120.250 addnode=dns1.biblepay.org addnode=dns2.biblepay.org addnode=dns3.biblepay.org addnode=dns4.biblepay.org I added those already from Togo's suggestion. I guess my client will just have to wait as my IP isn't something I can force a change of. |
|
|
|
|
