Bible Pay

Read 20408 times

  • sunk818
  • Sr. Member

    • 340


    • 12
    • April 24, 2018, 02:02:20 PM
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #180 on: November 16, 2019, 04:43:20 PM »
Please add true to the end and it should force it in.


I wonder if there's value in always forcing it true. Seems like a point of confusion to use true or not. Any harm in making it the default?


  • Rob Andrews
  • Administrator

    • 2284


    • 30
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #181 on: November 16, 2019, 06:39:08 PM »
Will someone please test unbanked, to ensure you get auto payments each day and dont need to post a stake?

Im going to start a 2nd cpid soon but havent got around to it.

You just need to lower your rac down to below 250 and above 1.



  • sunk818
  • Sr. Member

    • 340


    • 12
    • April 24, 2018, 02:02:20 PM
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #182 on: November 17, 2019, 09:47:08 AM »
What happens if we send funds to DWS but don't get it back? For example, in this last situation we lost all the test tBBP. Is there a way to recover in case of catastrophe?


  • Rob Andrews
  • Administrator

    • 2284


    • 30
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #183 on: November 17, 2019, 11:44:16 AM »
What happens if we send funds to DWS but don't get it back? For example, in this last situation we lost all the test tBBP. Is there a way to recover in case of catastrophe?

1) Yes we lost the tBBP, but thats because the test format changed; in prod that would never happen.  Obviously, we would not release the change without a smooth cutover between ended payments and new payments in prod.
2) As far as the question though, if there is a technical glitch or for some reason, the payment is not paid back, it would be lost.  There is no mechanism in BBP for it to re-send it if the sancs don't send it to you on the due date.  To clarify though, I originally planned on making the algo detect 'unpaid items that need paid today' and then I realized that adds risk.  Right now the sancs are forced to pay things that are due from a certain block range; and the only risk would be the GSC contract fails that day.  BBP only risks sending out a max of 5mil per day.  If I started adding in the "possibility" of missing a day and sending 2* the amount that opens us up to way too much capital risk.  I think 5mil deflating is manageable, since our great deflation lowers this continually.  And allowing 5 mil per day in burns is good enough for most of us etc.  So at this point I feel the simplicity is safer than the riskiness of adding complexity and capital risk.  I will continue to explore other options for prod, such as 'longer term maturing coinbases and timed transactions', but those are not guaranteed to work for this use case.

  Its currently a use-at-your-own-risk feature, and this way it passes the Howey test also.

« Last Edit: November 17, 2019, 11:58:34 AM by Rob Andrews »


  • Rob Andrews
  • Administrator

    • 2284


    • 30
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #184 on: November 17, 2019, 11:46:54 AM »
Will someone please test unbanked, to ensure you get auto payments each day and dont need to post a stake?

Im going to start a 2nd cpid soon but havent got around to it.

You just need to lower your rac down to below 250 and above 1.

I started an unbanked CPID; waiting for RAC to increase.

I noticed that on brand new WCG CPIDs, we cant associate them right away because there is a delay on the WCG side.  Ill see if I can detect the condition and maybe we can add one more result code - something at least explaining the expected amount of time to wait between a new account and the time the 'associate' will actually work.   I emailed IBM about it - from the boinc side I can see the CPID, from the WCG side - their XML api returns 'name does not exist' but from the WCG web page the name does exist.  I also will re-clarify what we need to do about the data export reqs.  Im still not 100% sure if we need to demand the radio button be set to export stats or not.



  • Rob Andrews
  • Administrator

    • 2284


    • 30
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #185 on: November 17, 2019, 12:02:58 PM »
I got my DWS rewards last night, but there is no whale icon.  So if you are looking for yours look for smart-contract-reward.

Ill look into this issue.


  • Rob Andrews
  • Administrator

    • 2284


    • 30
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #186 on: November 17, 2019, 12:17:23 PM »

I wonder if there's value in always forcing it true. Seems like a point of confusion to use true or not. Any harm in making it the default?
Yes, harm because forcing it negates the path of code that explains common reasons it failed, like username already taken, etc.
Force=true is only for reassociations already in the chain.



  • Rob Andrews
  • Administrator

    • 2284


    • 30
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #187 on: November 17, 2019, 02:12:30 PM »
I got my DWS rewards last night, but there is no whale icon.  So if you are looking for yours look for smart-contract-reward.

Ill look into this issue.

Ok whale icon fixed, will be in the next release.



  • capo
  • Newbie

    • 44


    • 2
    • March 11, 2018, 07:02:14 AM
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #188 on: November 18, 2019, 05:05:09 AM »
i cleaned up my cpk address so i had only 1x 1m coins there, but then at time of automatic gsc sends, it takes whole 1m for kairos and then nothing for wcg... :) so whole coin age was spent on nothing and not saved for wcg..
is it possible to reorder somehow that wcg will goes first?


  • Rob Andrews
  • Administrator

    • 2284


    • 30
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #189 on: November 18, 2019, 09:27:38 AM »
i cleaned up my cpk address so i had only 1x 1m coins there, but then at time of automatic gsc sends, it takes whole 1m for kairos and then nothing for wcg... :) so whole coin age was spent on nothing and not saved for wcg..
is it possible to reorder somehow that wcg will goes first?

Well to be entirely honest with you, I think that will do damage.  Since we will have 4 campaigns (Kairos, cameroon, wcg and maybe healing) I think it will still be key for the user to use bankroll command, if they have any type of massive RAC like you.

So as long as we do the bankroll, what will happen is Kairos or Cameroon *will* pick the smallest bill and only use one bill.  It is already programmed to pick the smallest coin age for each GSC transmission as possible.

So in this case I think the best answer is for all of us to run exec bankroll knowing that we may have more than one tx per night.


EDIT:

However we can reorder them also.  Remind me in prod if I forget, we do have control of the iteration order; in Prod when we set the spork, we can set it to : WCG (0), then Cameroon-One (1) ... etc.   Yes, no problem.

« Last Edit: November 18, 2019, 09:29:57 AM by Rob Andrews »


  • sunk818
  • Sr. Member

    • 340


    • 12
    • April 24, 2018, 02:02:20 PM
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #190 on: November 18, 2019, 01:33:16 PM »
None of my dynamic whale staking went through on the latest version. I don't know if all the slots are filled up already...?




I also could start the chain fresh and BBP would crash every time around 12k. I don't know if it was peers on old versions, but I kept getting invalid block errors. I thought we had mandatory, but I kept seeing 1.4.7.2 and 1.4.7.3 peers. Even testnet1.biblepay.org was on 1.4.7.2.


  • Rob Andrews
  • Administrator

    • 2284


    • 30
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #191 on: November 18, 2019, 02:45:49 PM »
None of my dynamic whale staking went through on the latest version. I don't know if all the slots are filled up already...?




I also could start the chain fresh and BBP would crash every time around 12k. I don't know if it was peers on old versions, but I kept getting invalid block errors. I thought we had mandatory, but I kept seeing 1.4.7.2 and 1.4.7.3 peers. Even testnet1.biblepay.org was on 1.4.7.2.

Could you please explain what you mean by "none went through"? 
(On a side note, now we show the user immediately if it is going to fail right in the rpc, you will receive a nice error message now).  I just burned one: successful.
You are probably running the pre 1.4.7.4 version; if you run an old version it tries to use the "old" dws format which is no good. 

In the mean time, Ill try to sync from zero on the latest version to verify it can sync.

Yes, also, 1.4.7.4 only sync with its peers; and the sancs must be on 1.4.7.4 too.  Was MIPs binary released yet?  Or are you on windows, it could be my issue? 

« Last Edit: November 18, 2019, 02:48:55 PM by Rob Andrews »


  • Rob Andrews
  • Administrator

    • 2284


    • 30
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #192 on: November 18, 2019, 03:42:05 PM »
None of my dynamic whale staking went through on the latest version. I don't know if all the slots are filled up already...?




I also could start the chain fresh and BBP would crash every time around 12k. I don't know if it was peers on old versions, but I kept getting invalid block errors. I thought we had mandatory, but I kept seeing 1.4.7.2 and 1.4.7.3 peers. Even testnet1.biblepay.org was on 1.4.7.2.


Ok, I confirm the crash during sync from zero.  So, I debugged this issue and indeed we have a bug.

The fix is checked in.

We will release a leisure fix for this bug.

On the dws burn issue, I believe the answer on that is to just ensure the version is 1.4.7.4+. 




  • Rob Andrews
  • Administrator

    • 2284


    • 30
    • June 05, 2017, 08:09:04 PM
    • Patmos, Island Of
    more
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #193 on: November 18, 2019, 03:59:45 PM »
BiblePay - TestNet
1.4.7.5 - Leisure Upgrade


- Fix crash during sync from zero reported by Sun
- Add extra DWS BL rule to prevent stakes from exceeding 5 mil on any future date (in addition to 5 mil in new burns per day)
- Check in POBH R&D class for MIP and the GPU contractor
- Add help message notes in exec associate to explain the missing steps
- Show the whale icon on Received stakes

« Last Edit: November 18, 2019, 07:56:00 PM by Rob Andrews »


  • sunk818
  • Sr. Member

    • 340


    • 12
    • April 24, 2018, 02:02:20 PM
Re: TestNet - PODC 2.0 (Proof of Distributed Computing)
« Reply #194 on: November 18, 2019, 08:10:43 PM »

Some Dynamic Whale Stake took but not all.