BiblePay | 10% to Orphan-Charity | RANDOMX MINING | Sanctuaries (Masternodes)

[bible_pay]

I borrowed the upcoming 250,000 reward from the next superblock and added it to the pool.

Now the pool is rewarding a 1200 BBP letter writing bounty.

Please, take advantage of this and write some letters for us!

All:  Please keep an eye on what people are writing and PM me or email me if you see any abuse.
The most common abuse is this:
Someone creates multiple accounts, copies and pastes the content to be the same, and upvotes their own letter.
I have fraud detection 1.0 in to detect the illegal upvoting but please keep an eye on it anyway as I dont want low quality content making it to compassion.

I will be removing the pool letter writing fee penalties later today.

[noxpost]

I borrowed the upcoming 250,000 reward from the next superblock and added it to the pool.

Now the pool is rewarding a 1200 BBP letter writing bounty.

Please, take advantage of this and write some letters for us!

All:  Please keep an eye on what people are writing and PM me or email me if you see any abuse.
The most common abuse is this:
Someone creates multiple accounts, copies and pastes the content to be the same, and upvotes their own letter.
I have fraud detection 1.0 in to detect the illegal upvoting but please keep an eye on it anyway as I dont want low quality content making it to compassion.

I will be removing the pool letter writing fee penalties later today.

So I've been thinking about this quite a bit lately, and trying to come up with a suggestion that could help remove the roadblocks to the kids getting letters. We know that the basic interaction steps are:
1) Write letter
2) Get letter approved (upvoted)

Now, currently there is a letter bounty, which is fine, and may incentivize people to get step 1 done. Step 2 has been more problematic, as seen by the posts today.

While it would potentially be possible to have a penalty and/or bounty associated with vote-related activity, I had another thought....

What if we allowed someone when writing a letter to "bid" the bounty that they wanted? The higher the bounty, the more upvotes they would need to get sent. Myself, I am not writing letters for the bounties so much as I think it is important that the letters be written/sent - so I would personally have a very low bounty and my letters would be more likely to be sent.

It isn't a perfect system - there could still be some low-quality letters that get created, or maybe we need to have a minimum # of votes no matter what (I'll be honest, I started off with a proposal to weight votes based on the voter's activity and it turned into something like a Proof-of-Stake system, which I didn't like)... I am not sure that this is the final solution, but it might be worth the discussion.

[thesnat21]

DONE!  I added the narrative hint to that page.

Perhaps you can add a "Back Button", or option to vote from the detail view?

I like the full view of the letter better, but its a bit of a pain to go back to the list to actually vote.  either solution would be helpful.

[616westwarmoth]

is there any problem with rosetta tasks again? all my computers have insufficient tasks amount

I've not noticed it on my end and while the available tasks are a bit below average on the server, https://boinc.bakerlab.org/rosetta/server_status.php shows 2026 unsent Rosetta tasks and 13234 Rosetta Mini tasks so you shouldn't be having an issue.

My test machines are supposed to arrive tomorrow and I'll split them evenly between WCG and R@h so in a few days should have a good baseline for what is to be expected between the two for determining a fair RAC equivalent.  But in the meantime, you might consider throwing some power at WCG as a hedge.  The R@h project we're tending to be in the 15% work performed range (we solved 13% of the work units overall yesterday), whereas if we did a comparable amount of work at WCG (roughly 5M RAC) we'd be around 3-5% (although right now we're less than 1%).  That is to say the WCG project can handle the influx much better than R@h can.

Sadly, my instances were terminated before I could get any accurate data. I don't have any similar machines at my disposal anymore and sadly I cannot afford to start again at this point.

So far I've got 2 smaller machines that have been up for a week and are showing mid 2300 under host average credit (in BOINC), and the two identical machines to those were showing 3800 RAC.

I did fire up four identical heavier computers last night ,two on R@h and two on WCG, it will take until the end of the weekend to begin to get meaningful data from those.

[orbis]

2) On the DMG, please check out the gitian-build and the apple dependencies required to build the DMG file.  We are looking for a volunteer that wants to build the DMG after every release.

I'm happy to help if it doesn't require an Apple Developer account and it can be done free. I have MacBook so I can compile stuff if you help me getting set up with the environment.

Thanks!  I was just talking to MIP and he has to buy an apple developer license for the iPhone (for our upcoming iPhone mobile wallet that he is creating), and hes buying a MAC today, so he just volunteered that Most Likely, he will be able to become our config manager for MAC, and create a DMG build script for us! 

THANKS MIP!

Wau... this is great...
This is going to be perfect with wallets on Android/IOS.
Now I'm waiting for wallet import option and it will be awesome.
Thanks MIP.

[bible_pay]

DONE!  I added the narrative hint to that page.

Perhaps you can add a "Back Button", or option to vote from the detail view?

I like the full view of the letter better, but its a bit of a pain to go back to the list to actually vote.  either solution would be helpful.

Updated Feature (IE Bug Fix):
Now you can click on the Breadcrumb trail for "Letters".  (This is the original design idea for usability, but the breadcrumb still is not fully implemented).

First, you will have to Log Off.  Then Log back on.  Then the new breadcrumb system will load.  Now you can click on a letter, and then the breadcrumb.

NOTE:  Users of the pool can also open two windows and put one on each monitor....

[capulo]

are we stuck? one block before payout

edit: we are going again but quite a bit long block

[bible_pay]

are we stuck? one block before payout

The problem was the long string error (IE net7biosfailure) that we fixed a few days ago.

Apparently the fix is not running on all sancs yet, and since only 64% have upgraded to 1119 so far, the sancs are having a hard time propagating that contract.
More specifically though, I see that we now have 381 CPIDs, and we are now officially over the govobj size limit per day, so what is happening is the nodes running prior to 1119 are not forwarding the contract around (IE it is just blowing their buffer), and more specifically, those particular nodes can't heat mine the contract (because they dont have it).

So we basically need to quickly step-up our effort to release 1.1.2.0, and also, ensure all sancs are on 1.1.1.9+.

I have some changes today that Anton pushed in for the Bezaleel theme- let me merge those in and test them and make a release.


 

[znffal]

Hi all,

Please comment and upvote this reddit post to help convince NextExchange to list us!


https://www.reddit.com/r/NEXTexchange/comments/8d9ye2/details_of_a_coin_under_consideration_biblepay_bbp/

Thanks

[kyxap]

Hello. It is possible information on the price for masternode? Thank you in advance. I think now is the best time to buy.

[znffal]

Hello. It is possible information on the price for masternode? Thank you in advance. I think now is the best time to buy.

Sanctuary Escrow Requirement: 1,550,001 BBP

[bible_pay]

BiblePay - v1.1.2.2
Leisure upgrade for Exchanges
Note: All users and Sanctuaries must be on version 1.1.2.1+
(Required to propagate PODC contracts properly)


- Merged in Anton G's Hand-of-God icon updates (and splash screen update)
- 1.1.2.1 fixed the WCG rounding error and also extended the max govobj size to allow 32,767 CPIDs

[tmike]

BiblePay - v1.1.2.2
Leisure upgrade for Exchanges
Note: All users and Sanctuaries must be on version 1.1.2.1+
(Required to propagate PODC contracts properly)


- Merged in Anton G's Hand-of-God icon updates (and splash screen update)
- 1.1.2.1 fixed the WCG rounding error and also extended the max govobj size to allow 32,767 CPIDs

The windows wallet on biblepay.org is still 1.1.1.9.

[bible_pay]

BiblePay - v1.1.2.2
Leisure upgrade for Exchanges
Note: All users and Sanctuaries must be on version 1.1.2.1+
(Required to propagate PODC contracts properly)


- Merged in Anton G's Hand-of-God icon updates (and splash screen update)
- 1.1.2.1 fixed the WCG rounding error and also extended the max govobj size to allow 32,767 CPIDs

The windows wallet on biblepay.org is still 1.1.1.9.

It was updated 3 minutes ago.

[zthomasz]

BiblePay - v1.1.2.2
Leisure upgrade for Exchanges
Note: All users and Sanctuaries must be on version 1.1.2.1+
(Required to propagate PODC contracts properly)


- Merged in Anton G's Hand-of-God icon updates (and splash screen update)
- 1.1.2.1 fixed the WCG rounding error and also extended the max govobj size to allow 32,767 CPIDs

The windows wallet on biblepay.org is still 1.1.1.9.

It was updated 3 minutes ago.

Will you check that windows wallet link ... I just downloaded / installed and it shows 1119.

[tmike]

BiblePay - v1.1.2.2
Leisure upgrade for Exchanges
Note: All users and Sanctuaries must be on version 1.1.2.1+
(Required to propagate PODC contracts properly)


- Merged in Anton G's Hand-of-God icon updates (and splash screen update)
- 1.1.2.1 fixed the WCG rounding error and also extended the max govobj size to allow 32,767 CPIDs

The windows wallet on biblepay.org is still 1.1.1.9.

It was updated 3 minutes ago.

Hmmm, I just downloaded the 64 bit version and it's still 1.1.1.9. Maybe something is wrong with my computer, although the file size is the same as before.

[616westwarmoth]

BiblePay - v1.1.2.2
Leisure upgrade for Exchanges
Note: All users and Sanctuaries must be on version 1.1.2.1+
(Required to propagate PODC contracts properly)


- Merged in Anton G's Hand-of-God icon updates (and splash screen update)
- 1.1.2.1 fixed the WCG rounding error and also extended the max govobj size to allow 32,767 CPIDs

The windows wallet on biblepay.org is still 1.1.1.9.

It was updated 3 minutes ago.

Hmmm, I just downloaded the 64 bit version and it's still 1.1.1.9. Maybe something is wrong with my computer, although the file size is the same as before.

Yes, file shows as version 1.1.1.9 in Properties-Details and shows 18,300 KB in size which is identical to the other 1.1.1.9 file I have in the folders.

[SVK Noko]

BiblePay - v1.1.2.2
Leisure upgrade for Exchanges
Note: All users and Sanctuaries must be on version 1.1.2.1+
(Required to propagate PODC contracts properly)


- Merged in Anton G's Hand-of-God icon updates (and splash screen update)
- 1.1.2.1 fixed the WCG rounding error and also extended the max govobj size to allow 32,767 CPIDs

The windows wallet on biblepay.org is still 1.1.1.9.

It was updated 3 minutes ago.

Hmmm, I just downloaded the 64 bit version and it's still 1.1.1.9. Maybe something is wrong with my computer, although the file size is the same as before.

Yes, file shows as version 1.1.1.9 in Properties-Details and shows 18,300 KB in size which is identical to the other 1.1.1.9 file I have in the folders.

Same here

Installed 1.1.2.2 (according to description on website) win version, but its still 1.1.1.9. No comment.

[Cryptoalt1990]

Hi Bible_pay,

It looks like the staking bug isn't actually fixed?

https://www.biblepay-central.org/en/podc/user/1995180/

He has a RAC of 184,677, stake of 3,388,035 and he is still getting a 100% UTXO weight.  Shouldn't he at least stake 3,693,540 to get 100% UTXO weight?

[znffal]

Hi Bible_pay,

It looks like the staking bug isn't actually fixed?

https://www.biblepay-central.org/en/podc/user/1995180/

He has a RAC of 184,677, stake of 3,388,035 and he is still getting a 100% UTXO weight.  Shouldn't he at least stake 3,693,540 to get 100% UTXO weight?

184677*20*0.9=3324186 so he is ok