Topic: BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes) - page 383. (Read 243454 times)

Yikes, praying for sure. Just a few months ago during the dam break in Kenya there was some concern that one of the girls my wife and I sponsor outside of BBP was affected, and she was out of touch for a worrisome amount of time. Luckily, she was eventually found safe. Prayers going up now for Juneyssi.

This is good, proactive analysis/correction and positive updates. Thanks Rob.

I just got a call from Compassion about Juneyssi Yalile Cabrera Gonzalez,


with very bad news.

She was caught up as a victim in the middle of the Civil Unrest in Nicaragua, and is missing.

They are keeping an eye out for her and the local church compassion office is still open and helping other orphans.

Please add her to your prayers.  I will add a prayer to our wallet now.

I'm on a train in the next hours and have a bad internet connection, so debugging is hard:

Right now, a lot of solutions on purepool are rejected because of wrong block height ( I can't see what the wrong height is, sadly)
But Purepool is on the same chain as the main explorer and biblepay-central explorer:
http://explorer.biblepay.org:3001/block/46fa6d70eb63c52cc683619ef2952a7e7ae04aff935eb8d17fd9b152d87c54dd

Is it likely that so many users are on a different chain right now?

Togo- also add that we receive one Personal letter per month from each orphan and keep electronic copies.  Its obviously apparent that we sponsor the stated number of children.

I argue that we are more transparent than Enron.  We have electronic copies of everything that reconciles.  This is better than certified accountants that falsify things for wall street.

Btw, pool.biblepay.org is our alternative POBH pool, you can always try it and see if it helps you with reliability.

Since you are one of our devs, if your client crashes more than once in 6 months, I recommend you run valgrind on it and give us the line # so we can fix it if its crashing in such an "ugly" way .

So I saved the blockchain from one of my sanctuaries that forked last week (I guess this was about 7 days ago) and I did some detailed analysis on the issue and found the exact root cause.

We had a block at 63829 that was marked invalid by a certain percentage of the network, and this caused a fork to appear.  On the nodes that marked the block as bad, I confirmed that our "feature" we added (calling reconsiderblock 205 times) actually fails to unmark the bad block as good, hence the reason the node stays in that state no matter what is done (you can move the chain back 1000 blocks, you can manually type reconsiderblock blockhash with the known bad block, etc, but the chainstate persistently keeps the block in its 'dirty' ~BLOCK_FAILED_MASK state, meaning that reconsiderblock does not actually unset our state in practice.  This also explains why an entire resync of the chain is necessary to allow the client to go down the fork with the higher work.

So for the short term solution, I added a feature that detects a fork (I verified that it would have detected the case of 63829 in this case), and erases the entire chainstate and blocks and restarts the wallet in QT.    This is just to provide resilience for now during our next release so that no manual intervention is required (since this appears to only happen a couple times a year).

The longer term solution is for me to find out why 63829 was marked bad to begin with and prevent forks.  This might be impossible as forks occasionally appear on all chains.  We can also look into ways to roll the chain back more gently for the long term solution (IE clear the failed mask state). 

Yeah I guess, thank you.

Thanks Light, hope you can fix it soon.

MIP, he is spamming to get his signature advertisement into the thread...

Mhh, the biblepay client crashed in an ugly way and another job filled the disk with error logs after that. I needed to reindex the blockchain to recover the biblepay client.

Hope it can fix everything automaticly, if not then I will look at it in more detail tomorrow

Yes, PurePool is down again. Hope @Lichtsucher con get it back on track.

Yes. I confirm. Everything is stopped in
Yes. I confirm. Everything is stopped in PurePool
Guys, I started mining BBP 1 month ago and since I started I have had a lot of headaches due to PurePool instability. When I see a problems I don’t know if the problem is with my wallet or with the pool. Very frustrating...
This is not motivating new comers to stay with BBP.

I saw that you are looking for new miners and purepool is perfect (easy and clean) but you need to improve stability.

Im moving now from heat mining to PODC but I would recommend you to stabilize PurePool for the new commers to stay.

Just checked my miner and can confirm.
Just getting connectionrefusederror

@Lichtsucher, the PurePool is not founding blocks since yesterday 9pm. (more than 12 hours ago).
It was stable for some time but It is stuck again. Could you please have a look?

Thank you!

Do your research right and don't just drop a templated one-line post.

All masternode coins (not "tokens" by the way) accumulate a 75-90% fall on average. Biblepay only a 50%.

Steps on how to use the 2nd CPU Science Research Project BiblePay Supports:

World Community Grid (WCG)

1. Create Account
https://www.worldcommunitygrid.org/join.action#signup
NOTE: Use exact same email address as used for Rosetta@home

QUESTION: Does a user have to create a Rosetta@home account first if first starting?


2. Join Team BiblePay
https://www.worldcommunitygrid.org/team/viewTeamInfo.do?teamId=JRD1XTFK92
Click blue "Join Team" button


3. Add Project to PC
BOINC Manager >> Tools >> Add Project >>> World Community Grid
>>> Next >>> Enter Username and Password from Step 1

QUESTION: It may take 24 hours for Rosetta@home and World Community Grid CPID's to sync into one CPID?

=

REFERENCES: https://bitcointalksearch.org/topic/m.34438501

QUESTION: If Rosetta@home and World Community Grid are both added, do they share 50% each of CPU? Is there a way to change percentage?

===

Please let me know if the above is correct

===

WCG BiblePay Team
https://www.worldcommunitygrid.org/team/viewTeamInfo.do?teamId=JRD1XTFK92

WCG Projects:
- Microbiome Immunity Project
- Smash Childhood Cancer
- OpenZika
- Help Stop TB
- FightAIDS@Home
- Outsmart Ebola Together
- Mapping Cancer Markers

===

And by doing WCG, you can also be rewarded in Byteball
https://medium.com/byteball/computing-for-good-again-3795336bdaed
https://wiki.byteball.org/WCG_distribution

1st professional step from BBP team .. hallelujah

Couple of thoughts, these are just my opinions and not the canon belief of the coin, but I think could spawn some good discussion.

On the thought of removing the Team BiblePay requirement to PoDC.  I understand we would gain more users, but I fear we would alienate our current mining base.  I'm pretty sure without the team requirement it will be harder to show our value to the scientific community.  Sure, we can show how many people get BBP and user BOINC, but we could no longer claim those as our unique users.  While we've not been able to capitalize on the potential PR value of Team BiblePay yet, I think it is there.

We have enough exchanges: With the addition of Cryptobridge and the upcoming addition of Coinexchange, in addition to SouthXchange, QIEX and C-Cex, we have enough markets to provide stability.  Sure, the last two have had some issues, but the first two should provide enough market stability.  The only other exchanges we should be courting would be top 40 exchanges and many of those don't accept paid listings so for all practical purposes, I think we are where we need to be with that.

I do believe we need to seriously consider two moderate changes to the coin.

The first is to remove the Dark Gravity Wave component from the PoDC and Sanctuary payments and keep it solely for the PoBH (heat mining) payments.  This would still protect against an influx of hash rate, but would allow investors to have a more dependable ROI for Sanctuaries.  In the last month I've seen payments range from approximately 3900 to approximately 4600.  This is a variation of nearly 20%, and adds too much complexity to the coin, skews the potential maximum emissions and I believe would be of benefit to change.  It would also make Sanctuaries and PoDC miners get equal rewards, whereas right now, PoDC gets more in a day than the collective sum of winning Sanctuaries.  In short, give the lucky Sanctuary 38.5% of the current block maximum, rather than the DGW Modified value.

The second is put a lower cap on the emission, preventing it from going below 200 BBP per block (before accounting for the budgetary parameters).  This would mean no max supply, but would only add approximately 7% to the current theoretical maximum every 50 years.  This would send a message that 1) we intended to be around more than 50 years and 2) Will still be supporting our charities and having a workable budget.

While we could discuss either of these points further down the line, I think considering them now, while we're still relatively young, would be best.