Bible Pay

Recent Posts

Pages: [1] 2 3 4 5 6 7 8 ... 10
1
I guess team Gridcoin, Byteball and Neumannium Labs would be the ones I see right off the bat.  Right now the BOINC percentage that is winning is 100%, which I think is entirely counter-productive.  Even though I'm very much against removing the team requirement, I do think that if we do, 90% of the reward to non-team members is enough to give an incentive for people to join our team but not penalize people too much for keeping with their old team.  That being said, even 100% reward is unlikely to trigger in my mind more than a 2-4M coin surge in demand, followed by a routine surge in supply as non-interested miners sell off the coin as they earn them.

Agreed, and if we are blocking other Crypto's from participating it is taking the audience away.
2
I am going back to our free website for now https://kairoscf.wordpress.com. SSL isn't working at kcf.winnegor.org, and chrome doesn't like that. We can't afford SSL for now.

Good to know. I'll update the links :)
3
I am going back to our free website for now https://kairoscf.wordpress.com. SSL isn't working at kcf.winnegor.org, and chrome doesn't like that. We can't afford SSL for now.
4
I guess team Gridcoin, Byteball and Neumannium Labs would be the ones I see right off the bat.  Right now the BOINC percentage that is winning is 100%, which I think is entirely counter-productive.  Even though I'm very much against removing the team requirement, I do think that if we do, 90% of the reward to non-team members is enough to give an incentive for people to join our team but not penalize people too much for keeping with their old team.  That being said, even 100% reward is unlikely to trigger in my mind more than a 2-4M coin surge in demand, followed by a routine surge in supply as non-interested miners sell off the coin as they earn them.
5
So I added some more handling to the area of "ancestor not found".  I found a bug in Contact Add - fixed - will be in the next testnet version.

Im working on automating BOINC setup for brand new cancer miners. 

Let's pause for a little bit until the next version is ready, then we can test all this together.

6
Production Proposals / Re: Proposal - listing BBP on GIN MN platform
« Last post by jmmc on September 20, 2018, 12:23:41 pm »
I have good news - BiblePay was just listed on Gin platform so we can save some listing budget here.
Feel free to host BiblePay Sanctuaries on GIN if you like - https://p.gincoin.io/#!/
7
Oh one more thing I just remembered, if anyone does receive that 'block has no ancestor' and crash, you can also make a copy of your testnet chainstate and blocks folders, and zip it and send to me, or simply keep it in order to have it to reproduce the error again in valgrind.

8
Sure, it should be easy as the defaults usually work.  Once you have valgrind installed, depending on how you launch biblepay (IE either "./biblepay-qt" or "./biblepayd") replace that string with this:

cd ~/biblepay
valgrind ./biblepay-qt

For example would start the QT wallet with valgrind running.  You can put all your normal parameters after the ./biblepay-qt also.  It might be easier to pipe the output to a log file since the log would be long (like  >vallog.txt) etc.  If you dont pipe to a log you can scroll back through the end of the trace and see functions and line numbers.  We usually need the last stack trace (the whole section to see how it was called).  Since some functions call other functions etc.

Very clear explanation. Thanks!
9
Sorry, I already -reindexed it :(

But I've installed valgrind in case it ever happens again. Can't seem to get it working in all my noobness though... Could you tell me what specific command I should use?
Sure, it should be easy as the defaults usually work.  Once you have valgrind installed, depending on how you launch biblepay (IE either "./biblepay-qt" or "./biblepayd") replace that string with this:

cd ~/biblepay
valgrind ./biblepay-qt

For example would start the QT wallet with valgrind running.  You can put all your normal parameters after the ./biblepay-qt also.  It might be easier to pipe the output to a log file since the log would be long (like  >vallog.txt) etc.  If you dont pipe to a log you can scroll back through the end of the trace and see functions and line numbers.  We usually need the last stack trace (the whole section to see how it was called).  Since some functions call other functions etc.

10
Production Proposals / Re: Compensation for Jaap's work with BiblePay
« Last post by jaapgvk on September 20, 2018, 07:44:46 am »
Jaap,

New proposal should be a new thread so things don't get confused :)

Well, I purposely link to the specific posts (not the thread itself) in my proposals, so I thought it wouldn't be confusing. But if people find this confusing, I will start a new thread for every proposal in the future :)
Pages: [1] 2 3 4 5 6 7 8 ... 10