Messages

3241

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 17, 2018, 06:17:35 PM »

Will the time between blocks be about what it is right now. 32.5 hours?

Starting at block 35110, it should technically speed up to 205 blocks per day.  Lets hope we got it right this time.

3242

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 17, 2018, 02:07:56 PM »

I guess my better question is when, if ever, is it going to change from 500BBP/Mag and what will be the final determining factor in deciding how much.

In 1111, we have the SPM or SPR (stake per mag or stake per rac) indicator Spork doubles (double is like a floating point number) compiled in. 

So when this poll outcome :
http://forum.biblepay.org/index.php?topic=127.0

is known, then I sign a spork and induce it in the chain that night, and right away the sancs start honoring the new business logic rule for the next superblock.

So as an example if this poll ends of April Fools Day, and it dictates 20 bbp per rac, as of that evening, the sancs will start being influenced to create and vote on the contract using that new business logic.

3243

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 17, 2018, 01:05:20 PM »

Is the reduction in the superblock because of the tithe block?

No, the daily emission amount of 1.19 MM is what it should have been, but due to cascading superblocks, we had a bug in the initial release so we left it in for 7 superblocks while the mandatory kicked in to Fix the calculation error.  It never should have been double daily payments.

3244

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 17, 2018, 01:03:40 PM »

Block 35055 hit, shows next superblock budget as 1197260 at 35260, those look about where I was anticipating the breakdown should be initially.

What is the official word on staking for the UTXO reward component, and will that require a MN update to implement ?

Yes I agree, me too, but too bad we didn't catch it in TEST.

Hopefully this answers your question:
https://bitcointalk.org/index.php?topic=2388064.msg32447969#msg32447969

3245

Archived Proposals / Re: BiblePay & CameroonONE

« on: March 17, 2018, 07:03:10 AM »

If sanctuaries want to vote in favor of this proposal, they can use the following command:

Code: [Select]

gobject vote-many 6ca3cdfbbd557946cb776871308797406eb1a942bd866b67b4cc906c2bfa2bea funding yes
(you can check the validity in the pool of course).

If the 4000 dollars can't be collected with the requested BBP, I will add a new proposal the next round to meet the requirements to sponsor 14 children for a whole year and start our collaboration with CameroonONE in a big way!

This sounds like a reasonable cost for 14 children, that means we are technically helping 14 children for $24 a month each ($4000 / 14 / 12) = $24.

Ill be voting yes for this, Id like to expand our relationship to include Cameroon and it would be nice to see 14 more children being sponsored in our portfolio.

3246

Archived Proposals / Re: Biblepay Mass embracement campaign tour and meetups

« on: March 17, 2018, 06:18:37 AM »

Then the error seems to be a general problem per the proposal submission. We will have a look at it and see how it can be resolved.
Thank you for the feedback

Checking now... If need be we can all re-vote after this...

3247

Archived Proposals / March 2018 Compassion.com Recurring Orphan Sponsorships

« on: March 16, 2018, 05:39:37 PM »

Each month we sponsor approximately 210 orphans currently.


Rob, the lead dev charges the expense on his credit card, and keeps a copy of the receipt. 

The expenses can be viewed by navigating to Accountability.biblepay.org | Expenses and viewing the January PDF.

We have prepaid 63 childrens premiums for one month (in February 2018) meaning we are preapid with compassion by $2,394 which is a great start.

In the spirit of prepaying for 6 months in advance before sponsoring new children with compassion, I intend on using the suprlus to not only pay the $7,106 recurring invoice due on March 21 2018, but to use the excess to prepay more orphanage premiums into the future.

To see the amounts we raised in the past by selling BBP for bitcoin see this page:
 See accountability.biblepay.org | Orphans | Orphan Fundraisers.  You can audit the total by finding the sum of all fundraisers.

I am committed to using 100% of the funds received in this months proposal entirely for our orphan premiums for compassion, and anything left over 100% to the future in the form of prepayments.

I am requesting 7,500,000 BBP this month since we have a higher budget with a target sale of $19,600.


All orphanage coins are spent on orphan expenses at compassion.com and Rob will 'tip' in a little extra to ensure Gods money is put to use for Gods children.

3248

Archived Proposals / February 2018 IT Expenses (Payroll)

« on: March 16, 2018, 05:29:50 PM »

To partially fund some of my own programming hours, I would like to submit Github commits for the core biblepay wallet from Nov 1 2017 through Nov 30 2017:

Commits on Nov 29, 2017
1.0.6.3-Mandatory Upgrade - TESTNET  …

@biblepay
biblepay committed on Nov 29, 2017
 
Commits on Nov 20, 2017
1.0.6.2-Leisure  …

@biblepay
biblepay committed on Nov 20, 2017
 
Commits on Nov 17, 2017
1.0.6.1b-Leisure (Highly Recommended Upgrade)  …

@biblepay
biblepay committed on Nov 17, 2017
 
1.0.6.1-TESTNET  …

@biblepay
biblepay committed on Nov 17, 2017
 
Commits on Nov 16, 2017
1.0.6.0-Testnet-Leisure  …

@biblepay
biblepay committed on Nov 16, 2017
 
Commits on Nov 15, 2017
1.0.5.9b-Leisure  …

@biblepay
biblepay committed on Nov 15, 2017
 
1.0.5.9-Leisure-Testnet  …

@biblepay
biblepay committed on Nov 15, 2017
 
Commits on Nov 13, 2017
1.0.5.8c-Testnet  …

@biblepay
biblepay committed on Nov 13, 2017
 
1.0.5.8b-TestNet  …

@biblepay
biblepay committed on Nov 13, 2017
 
Commits on Nov 12, 2017
1.0.5.8-Testnet-Leisure  …

@biblepay
biblepay committed on Nov 12, 2017
 
1.0.5.7-Leisure  …

@biblepay
biblepay committed on Nov 12, 2017
 
1.0.5.6b-TESTNET  …

@biblepay
biblepay committed on Nov 12, 2017
 
Commits on Nov 11, 2017
1.0.5.6-TESTNET-Leisure Upgrade  …

@biblepay
biblepay committed on Nov 11, 2017
 
Commits on Nov 9, 2017
1.0.5.4b (TESTNET) - Leisure Upgrade  …

@biblepay
biblepay committed on Nov 9, 2017
 


For a grand total programming time of (40 hrs per week * 4 weeks) = 160 hours @ 40.00 per hour = $6,400.00

Also, I would like to expense the following IT expenses for Biblepay:

Zinc, Exchange, SSL for wiki.biblepay.org, and resource upgrade for biblepay.org for Wordpress ($313.08):
Receipts:
http://pool.biblepay.org/SAN/expenses/ITExpensesBiblePayFeb2018.pdf


For a Grand Total Proposal of :  $6,713.08
Equaling:

?6713/.002930 = 2,291,126 BBP


Thank you for your consideration.

3249

Archived Proposals / Re: New Exchange Proposal - Add new Biblepay Exchange

« on: March 16, 2018, 05:16:36 PM »

Alright I'll do it. But I don't have enough BBP left on my pool account.

Rob, could you by any chance arrange that I can deposit BBP into my pool-address?

I added 3K to your Balance just in case.

Brilliant guys, sure lets work on a google doc.

It is nice to have a standard centralized tracking status on these exchanges.

3250

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 16, 2018, 12:11:43 PM »

Yeah payment came through today so that is good and there have been no futher interruptions in the PoDC Updates which was the root issue.

One question, in a case like this when I don't bring my RAC to the equation, does that effectively mean that everyone else gets a slightly higher reward since the overall Team RAC is effectively lower for that superblock?

Yes very good question.

So yes, the superblock always shoots for a (fraction less than) 1000 magnitude, and attempts to use up 99.9% of the daily superblock budget, for payments within the contract.

So if someone has UTXO Weight = 0 or TaskWeight = 0, it ends up being More for the rest of the gang. 

3251

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 16, 2018, 07:53:51 AM »

Thanks for all the insight.  I PM'ed because the debug log contained some things I thought would not be ideal to share.

Great, did you get the payment?

Wait I guess I can type 'exec leaderboard', ,   "e7ae6abd6284b05f3fd5f7c780e60bc7": 21.30465742430721,
Alright congratulations, your back in!

So with West as a guineapig, remember how dangerous it is to fall out of the superblock, it could take up to 48 hours to be in the next one again, due to the sanctuary voting process.

This is a double edged sword, as some benefit from it while others are penalized - its a blessing overall that it requires work to be paid (IE leaving the controller running 24-7).

This saves up more rewards for the persistent.

3252

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 16, 2018, 07:51:41 AM »

Just got my first unbanked payment from the pool! 

http://explorer.biblepay.org:3001/address/BNfb6uMyeAHDwZs538gzxS2k2iqbz8NWQj

Thats awesome!  I guess the mandatory upgrade has propagated through the supermajority of the sancs.  (I saw this morning 67% of the general network had upgraded to 1.1.1.1), a much quicker response time than we had when the bot-net dragged us down.  Now do you all see why I called it a bot-net and have a dark view of the prior ecosystem?  They installed our software on so many machines they were not even able to upgrade it , and that caused us to have a very dangerous ecosystem, in that we have no control over our own software rules.  And this has little to do with being "powerful" it has everything to do with being "cutting edge" and "nimble".  If we want quarterly releases with cool new features, so we can work our way up the coinmarketcap ladder, its essential to have a network that can upgrade during mandatories.  Now these mining orgs have to come out in the light and expose themselves.  They can upgrade the single controllers easily now. 

3253

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 15, 2018, 02:33:46 PM »

Sent you a PM Rob, did not receive a Superblock payment again.

I sent a PM to West explaining I believe his PODC update crossed while the last superblock contract was generated with him in it - IE his elements were not picked up by 51% of the sancs until after the 1am contract.

The current pool contract has him in it. 

These Pool superblocks are usually what are going to be voted in guys.

Meaning that the primary goal is to work hard to ensure your UTXO weight, task weight, and magnitude are populated in the current pool Superblock   report.

3254

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 15, 2018, 02:25:34 PM »

Yes to the above. I've been receiving regular rewards. What i meant was I downloaded 1.1.1.1 to test after reading warmoth's note. As soon as I noticed something odd with the behaviour, I immediately downgraded to 1.1.0.9b and it was fine. Was just wondering if there's a problem with 1.1.1.1 and perhaps podc updates?

No problems have been reported with 1111, and 1111 is a mandatory so downgrading to 1109 would fork your chain.

3255

TestNet Discussion Archive / Re: BIBLEPAY -TESTNET TESTING THREAD-Proof-Of-Distributed-Computing(Cancer Research)

« on: March 15, 2018, 11:05:50 AM »

Yes, they were and after un-hidding them and issuing a podcupdate I got this:

Code: [Select]

  "Command": "podcupdate",
  "PODCUpdate": "Processed (129) over 1 CPID(s) successfully."

I suppose this is good My TaskWeight also  became 100 from 0, but UTXWeight is still 0.

What does the amount that I choose to stake represent? Is this amount lost or is it just symbolic?
If it isn't lost, then I suppose that I have to raise it to 50001+, right?

Thank you for your time!

So the utxoamount represents how much out of your wallet you will stake for Cancer research, and its not lost, it comes back to you right away.
They are voting in 20 BBP per RAC right now, so to be safe just estimate what your RAC will be by typing 'exec getboincinfo' take a look at your RAC and estimate your future RAC value, and multiply that * 20.  Then use that as your stake amount (or higher .  Then you should see an increase in UTXOAmount after 6 blocks of confirms after the exec podcupdate was executed.

Good luck man.


EDIT: Btw for anyone who unhides the machines, boinc obfuscates all personal information like domain name, machine name, IP, etc, it re-names this info "computer1, computer2" etc, so we do not gain any personal info other than the OS type, proc count, speed, processor type, and memory.