Bible Pay

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - sunk818

Pages: 1 2 3 [4] 5 6 7 8 9 10 11 ... 24
46



07:40:41

exec boinc1




07:40:41

{
  "Command": "boinc1",
  "purse amount matched": 599938.99127,
  "purse total": 645074.51811888,
  "txid": "b52b5a341e644a68823e3076b68b918325e11a9cb0e7ae3dfa795bef8a676e5a"
}


47

It might have been setting my wallet to be a privatesend liquidity provider and all the CPK keep going elsewhere.


My biblepay.conf kept saving as Mac format after the externalprivatekey got inserted by the biblepay code. saving it back as windows (crlf) seems to triggered a gsc tramission for cameroon-one, kairos, and wcg as soon as I opened the wallet again.

48
If you feel it is easy enough to use, then it must be me. I'll sit out testing as I personally feel all these steps are too hard for me to understand and follow.  :D


It might have been setting my wallet to be a privatesend liquidity provider and all the CPK keep going elsewhere.

49
If you feel it is easy enough to use, then it must be me. I'll sit out testing as I personally feel all these steps are too hard for me to understand and follow.  :D

50
I've been following BiblePay for the last 18 months, but if I'm having a difficulty time getting this work... this does not bode well for new members. Maybe I'm just dumb... Usability is critical, but adding complexity has only made the product more difficult to use.


I DMed you my exec rac output.

51
i'm giving up. I can't get my cpid registered. tried several times now.


exec rac works but haven't gotten a podc payments for days now.

52
Production Proposals / Re: PODC TEAM REQUIREMENTS
« on: November 29, 2019, 12:26:36 AM »

I don't think it is too high at all.


https://gridcoinstats.eu/project/world%20community%20grid


Most of the top RAC "users" are pools. CharityEngine and grcpool.


Already, they are slightly split up so the RAC to BBP requirement is less.


Personally, I'd say blacklist any user above 100k RAC, but having the exponent discourage pool, people with high RAC hardware, or force you to split your cpid.


I also see BOID is another crypto BOINC pool.

53
couldn't the wallet version be enough to ban sanctuaries not on that version as well?

54
Bounty address changed to:


BKdkszSubBe9cNurd2LoBjPuaFhTL7utYw

55
InstantSend (IX) used to say 5 out of 6 confirmations. Now it is just 1 out of 6, but with the key checkbox icon in the column? I notice the transaction line continues to be blue.

56
We got 4.7 months paid for.
bbp (Biblepay) on 2019-08-30 20:53 Expires 2020-01-27 23:09 (in 149.1 days) On 2019-08-30 20:00, credit "Paymium c36c24" (144.88 days), new expiry 2020-01-27 23:09 On 2019-05-14 09:15, credit "BTC at $8000 bonus!" (8.00 days), new expiry 2019-09-05 01:57 On 2019-04-29 09:07, credit initial contribution ()



It is time to renew again. We have less than 60 days left with last payment. Will try to renew again for 6 months. Asking 350k BBP. Will convert to BTC and submit to Cryptoid Explorer. I hope everyone sees value in this explorer over Iquudus in terms of cost and features.

57
had to erasechain and delete instantsend.dat - settled on 18446. was on 18459



2019-11-26 21:41:27 UpdateTip: new best=8b1ad9df4a08823a7b1cb36c7671d21e8b549334e322ff6e1bfebfaf0e7e8170 height=18459 version=0x20000001 log2_work=46.18226809 tx=29113 date='2019-11-26 21:29:42' progress=0.258118 cache=0.1MiB(897txo) evodb_cache=0.0MiB
2019-11-26 21:41:27 CheckForkWarningConditions: Warning: Found invalid chain which has higher work (at least ~6 blocks worth of work) than our best chain.




If I had the foresight, I would have saved the old instandsend.dat and current so you could do some binary comparison.

58
other than healing and pog (or dws) which are manual transactions anyways... it makes sense to to add POOM to auto payments like WCG? If the accounting is correct and you trust the oracle data, then I don't think it should matter whether it is BOINC data or POOM data.

59
i erase the chain started over... now exec rac says


looks like I missed the one in between



"next_podc_gsc_transmission": 18552,

60
No, nothing.  If you type 'exec rac' it should reveal the height in which the daily tx goes out (automatically).

PODC_Height:


When I type exec rac, I don't see podc_height.


I see a next_podc_gsc_transmission. the block is 18347, but I think we are on 18422 (although I could be on the wrong chain).



  "next_podc_gsc_transmission": 18347,

Pages: 1 2 3 [4] 5 6 7 8 9 10 11 ... 24