Bible Pay

Recent Posts

Pages: 1 2 3 4 5 6 7 [8] 9 10
71
Unable to add test contact.

Fields I filled out: Company Name, Contact Name, Funding Receiving Address (I changed it from default to another one), E-Mail address. Drop Down Vendor

2018-09-28 05:11:39 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-09-28 05:11:39

************************
EXCEPTION: St13runtime_error       
JSON value is not a string as expected       
C:\crypto\biblepaytestnet\biblepay-qt.exe in Runaway exception       

2018-09-28 05:11:59


Please re-post this with every field value and user changed value existing on the screen that can allow us to reproduce the crash including what you click.

Unable to reproduce:  Unable to fix :  At this point this feature appears to work fine to us.

Also please ensure this is the latest wallet version.  Earlier than 2 versions ago, we did have a contact save issue.

72
Mining - General / Re: Ttroubles with mining
« Last post by Elight on September 28, 2018, 04:21:53 am »
Hey!

So for full Podc payouts you will need Rac via rosetta@home and RACx20 =  1700 biblepay

so for full payment you will need to have  85 RAC. (if my calculation is right)
any less then that and you will not get optimal payout via podc.

So your RAC * 20 should equal as many biblepay coins that you have.
What cpu are you mining with ?
I use Intel Quad Q8200(4x2.33GHz).
So then(when i`ll have RAC more than 85) i need to buy new coins to get optimal payout?
73
I tried SunK's recommended lowendbox service of $1 a month ... Its horrible

Sorry that happened. That's not been my experience, but support can be spotty with lowend servers sometimes. If you don't need support and can manage on your own, its been for me.

Sounds like a winner.  That is another good reason we separated the Associate from the Attach - we don't really want the associate part to fail unless they deliberately have 0 bbp to use and there is a long potential lag for a user between starting boinc and clicking associate.
I think more buttons is not helpful. I'd want to keep the "Add Me As Researcher" button only and have all the action flows from it.If they don't have an R@H account, create one and track their CPID. Give Download link with instructions to add R@H project. Crunch tasks. When s/he gets enough RAC (whether is 1 hour or 1 day or 1 week), have the pool automatically pay from the faucet. Maybe have BBP wallet check every 4 hours like PoDC updates for the RAC? Whenever there is enough BBP in the wallet, ask if they want to submit their CPID to the blockchain to receive daily PoDC payouts. IMO, it should be all behind the scene and seamless. Maybe that's too complicated to do? IDK.

Side comments:
1) Maybe WCG can fit in there somewhere too... (Display My Data needs to be checked on in Settings on the web site)
2) Form tabbing is wonky. From user name it goes to Add Researcher button instead of to password
3) R@H diagnostics show WCG, but the WCG data is not parsed out. Its all a jumbled mess from web site it seems.
74
Unable to add test contact.

Fields I filled out: Company Name, Contact Name, Funding Receiving Address (I changed it from default to another one), E-Mail address. Drop Down Vendor

2018-09-28 05:11:39 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-09-28 05:11:39

************************
EXCEPTION: St13runtime_error       
JSON value is not a string as expected       
C:\crypto\biblepaytestnet\biblepay-qt.exe in Runaway exception       

2018-09-28 05:11:59
75
Yes, I think that will be great for the UX when setting up the wallet. I shall change the guide on biblepay-central to reflect these steps when this goes into prod.

One thing comes to mind: right now there is the 'get 1000 BBP from pool' step, that ensures you have enough BBP to associate your CPID (and even have something to start staking with).

Looking at the new wallet set-up from a new user perspective, you first use the 'create and attach R@H' button. If everything goes right, you now have R@H crunching with a fresh account. Since this account doesn't have any RAC, you can't use the pools faucet yet.

So, thinking about a guide. Should the steps be:
1. Download and run BOINC
2. Use the 'create and attach R@H' button
3. Solve enough tasks to have >100 RAC + wait 24 hours just to be sure
4. Use pool faucet
5. Associate your CPID
6. Buy enough BBP for staking.

Of course, you don't HAVE to follow these steps, as long as you have enough BBP to associate your CPID. You could also use http://biblepayfaucet.com/ perhaps, but it can take a long time using that faucet to get enough BBP for the CPID association.

Anyway, people will also need to stake of course, so they will probably also have to buy BBP anyway even if they get the 1000 BBP.

Just thinking out loud about UX and how to make this proces as easy as possible...

Sounds like a winner.  That is another good reason we separated the Associate from the Attach - we don't really want the associate part to fail unless they deliberately have 0 bbp to use and there is a long potential lag for a user between starting boinc and clicking associate.

Ill start reviewing everything we changed to see if we have wrapped up what is supposed to be in the mandatory.


76
I tried SunK's recommended lowendbox service of $1 a month:
https://lowendbox.com/blog/hostbrz-vps-shared-reseller-hosting-from-2-year/

Its horrible, first day the nodes went down 15 hours in, 2nd day - they erased one server by accident, problems still not resolved.

Might be good for a test VMS, but not for a production node.

77
Production Proposals / Re: Closing the gap for BLOOM recurring expenses
« Last post by orphandefender on September 27, 2018, 05:04:41 pm »
Hi guys- It's a little more complicated than just "cutting expenses" because we can't just choose to cut the kids' food supply off or pull them out of boarding school and put them in the streets, you know what I mean? It's not as simple as a business move to do layoffs of some sort. And, unfortunately, we don't have additional funding to cover kids if they lose sponsors. Lessoned learned for the future- we need a sponsorship sustainability plan for the kids when funding is low.

Because of these risks, I'm looking into ways we can work together where it won't negatively affect the kids if there is a bearish market in the future. I also hope that our Sierra Leone kids will be weaned off sponsorships and supported by the sustainable farm by end of December. So, that will cut expenses.
78
Mining - General / Re: Ttroubles with mining
« Last post by earlzmoade on September 27, 2018, 03:00:53 pm »
Hey!

So for full Podc payouts you will need Rac via rosetta@home and RACx20 =  1700 biblepay

so for full payment you will need to have  85 RAC. (if my calculation is right)
any less then that and you will not get optimal payout via podc.

So your RAC * 20 should equal as many biblepay coins that you have.
What cpu are you mining with ?



79
Mining - General / Ttroubles with mining
« Last post by Elight on September 27, 2018, 01:54:48 pm »
Hello everyone!
At first, sorry for my language skills, I'm Ukrainian and just studying English.
At second, I have a problem with mining. All have been good when it was only PoBH mining, but problems came with PoDC.
I can't mine even 10 BBP.
Of course I set up all programs, but it doesn't work.
I have 1700 BBP in my wallet, is it enough for mining? Maybe my english skills can't let me understand how system works fully, but I read that my wallet must be filled with coins for mining.
So the question is: how much coins i need to have for effective mining?
80
Excellent!  That means the test didnt fail, great.  (Because the msgbox should show any error, even Insufficient funds).

Anywhoo,  heres what Im thinking:

Case 1:
A new biblepay user who is an existing researcher on boincstats with lots of rac.  All they do is click the Associate CPID button (thats the old button that was always there).


Case 2:
A new user who doesnt use boinc.  They click the 'Create Account & Attach project' button and that does everything Except associate the cpid with the wallet.  Then We tell them to click Associate after they get boinc running.


This way we can appeal to either group without causing duplicate DCC transactions to be sent.

Yes, I think that will be great for the UX when setting up the wallet. I shall change the guide on biblepay-central to reflect these steps when this goes into prod.

One thing comes to mind: right now there is the 'get 1000 BBP from pool' step, that ensures you have enough BBP to associate your CPID (and even have something to start staking with).

Looking at the new wallet set-up from a new user perspective, you first use the 'create and attach R@H' button. If everything goes right, you now have R@H crunching with a fresh account. Since this account doesn't have any RAC, you can't use the pools faucet yet.

So, thinking about a guide. Should the steps be:
1. Download and run BOINC
2. Use the 'create and attach R@H' button
3. Solve enough tasks to have >100 RAC + wait 24 hours just to be sure
4. Use pool faucet
5. Associate your CPID
6. Buy enough BBP for staking.

Of course, you don't HAVE to follow these steps, as long as you have enough BBP to associate your CPID. You could also use http://biblepayfaucet.com/ perhaps, but it can take a long time using that faucet to get enough BBP for the CPID association.

Anyway, people will also need to stake of course, so they will probably also have to buy BBP anyway even if they get the 1000 BBP.

Just thinking out loud about UX and how to make this proces as easy as possible...
Pages: 1 2 3 4 5 6 7 [8] 9 10