Messages

1

Active Discussions / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: Today at 10:18:43 am »

i had 286k bbp in external purse

now
07:53:53


Code: [Select]

{
  "Command": "rac",
  "cpid": "e7c056024cd3b781edd5af37965c652c",
  "CPK": "yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "wcg_teamid": 35006,
  "next_podc_gsc_transmission": 16297,
  "team_name": "Biblepay",
  "researcher_nickname": "capulo",
  "researcher_country": "SLOVAKIA",
  "total_wcg_boinc_credit": 69294160.40000001,
  "total_wcg_points": 485059122.8000001,
  "external_purse_total_coin_age": 363319.7254050925,
  "coin_age_percent_required": 0.7400380137787291,
  "coin_age_required": 265237.210701367,
  "wcg_id": 1066130,
  "rac": 14860.263202
}
so yesterday there must been about 100k coin age at wcg-gsc transmission time
but only 59bbp was taken

b88b8b5480f1ff6311c2fed1bc26052739b5aa19848f981501af0d5a00046580
Status: 167 confirmations, broadcast through 5 nodes
Date: 14. 11. 2019 11:21
Source: GSC-Transmission
Total debit: -59.27710240 tBBP
Total credit: 59.27710240 tBBP
Transaction fee: -0.03533000 tBBP
Net amount: -0.03533000 tBBP

Code: [Select]

Transaction ID: b88b8b5480f1ff6311c2fed1bc26052739b5aa19848f981501af0d5a00046580
Output index: 0
Transaction total size: 3526 bytes

Height: 16094
Difficulty: 34.61
Time: 11-14-2019 10:24:56
Subsidy: 3839.5479

Debit: -1457.48153815 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Debit: -3.27032000 tBBP
Credit: 5.92771024 tBBP
To: yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k 5.0000 BBP
Credit: 5.92771024 tBBP
To: yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k 5.0000 BBP
Credit: 5.92771024 tBBP
To: yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k 5.0000 BBP
Credit: 5.92771024 tBBP
To: yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k 5.0000 BBP
Credit: 5.92771024 tBBP
To: yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k 5.0000 BBP
Credit: 5.92771024 tBBP
To: yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k 5.0000 BBP
Credit: 5.92771024 tBBP
To: yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k 5.0000 BBP
Credit: 5.92771024 tBBP
To: yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k 5.0000 BBP
Credit: 5.92771024 tBBP
To: yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k 5.0000 BBP
Credit: 5.92771024 tBBP
To: yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k 5.0000 BBP
Credit: 1457.03486575 tBBP
To: ycPcPQ9bh45xUvMeBSHprdhvbKjTVxqTQX 1457.0000 BBP
btw why total credit debit is only 59 when there is credit/debit of 1457bbp also?

i'll see today in 3 hrs what happens...

1) Could you please put long pastes inside code tags - thanks.
2) The reason you see a 1457 bbp debit, is because we broke the 1457 bbp bill from your external purse, and made the debits.  The credit back is your change.
(This happens in all tx's).

3)  I agree that it looks like you had coin-age on that day, but the wallet only saw 1457 bbp available to spend.  It thought you had "8 total" in coin-age at that exact time, from looking at the transaction I can see, that for WCG, we thought you had 8 total coin age available.


So, I believe the only problem we have is finding out why you had 8 in its view (instead of 335,000).

I have a hypothesis, how many minutes earlier was your transmission before WCG?

I have a feeling we don't detect the correct coin-age for 5 confirms *after* any gsc transmission.
I say this because I sent one manually, and then my 'exec rac' was wrong for 5 blocks.

So, I think you found a nice bug we can fix!

Anyone want to confirm that is the case for one manually?  Just sent a cameroon one then look at exec rac.

2

Active Discussions / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: Today at 10:09:45 am »

who owns the external purse? do we have access to it?


if we don't send a gscc daily, do we stop earning rewards? what do you think about a 7 day average? this way, even if we miss a day, we'll still earn rewards? I thought you mentioned something about 7 days, but I forgot what that was about...

On the 7 day idea, I think its too risky for daily mining rewards.  With the daily budget we require the coin-age to be staked within the last 205 blocks of the contract.  Moving to 7 days, then we have to make sancs assess different ranges than the daily contract reward range.  Doesn't sound possible without redesigning our entire GSC system.

3

Active Discussions / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: Today at 10:05:19 am »

soo, coin age was not spent


13:42:52

{

Code: [Select]

  "Command": "rac",
  "cpid": "e7c056024cd3b781edd5af37965c652c",
  "CPK": "yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "wcg_teamid": 35006,
  "next_podc_gsc_transmission": 16297,
  "team_name": "Biblepay",
  "researcher_nickname": "capulo",
  "researcher_country": "SLOVAKIA",
  "total_wcg_boinc_credit": 69335182.63,
  "total_wcg_points": 485346278.41,
  "external_purse_total_coin_age": 441222.8717592593,
  "coin_age_percent_required": 0.7435678336035351,
  "coin_age_required": 323666.9061727702,
  "wcg_id": 1066130,
  "rac": 17319.571826
}

but i'm now in leader table with wcg

Transaction ID: e3b4dcc778bb7676fac56af17b2ff47c3053e2f8892093e199263ef8c9f99a9c

seems like bbp (and coin age) was taken from normal wallet addres and sent to CPK address
is this ok?

"seems like bbp (and coin age) was taken from normal wallet addres and sent to CPK address
is this ok?"
getrawtransaction e3b4dcc778bb7676fac56af17b2ff47c3053e2f8892093e199263ef8c9f99a9c 1

->  Why do you say it wasnt taken from your CPK external purse?  Looking at the vin of the transaction (i pasted above), its from your yi* address.  So it appears it was taken from your external purse.

->  Yes, coin age was spent.  You can type 'exec sentgscc' to see each time the coin-age was spent.

->  The only problem I see here, is why didn't we send your GSCC out yesterday if you had 330K coin age *at that time*?  That looks like a legitimate problem; I will be checking this next.

4

Active Discussions / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: Today at 09:52:08 am »

who owns the external purse? do we have access to it?


if we don't send a gscc daily, do we stop earning rewards? what do you think about a 7 day average? this way, even if we miss a day, we'll still earn rewards? I thought you mentioned something about 7 days, but I forgot what that was about...

You own the external purse; its your Christian-public-key (private key) pair - so you can still access it via coin-control and send things into and out of it.

If you don't send a gscc for that day for cameroon-one or kairos, you would not get the reward.  As explained for WCG in one of the prior posts, if you are unbanked, you dont need to send the daily wcg.  But if you have > 250 rac, you do need to send the wcg.

I dont think I ever mentioned a 7 day average, cant recall anything about that.

5

Active Discussions / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: November 14, 2019, 08:04:22 pm »

BiblePay TestNet
1.4.7.2-Mandatory Upgrade for TestNet

- Add Howey verbiage to exec dws.  Rename all instances of ROI to DWU (Dynamic Whale Units).  Ensure burn errors are bubbled to the user immediately.  Ensure burns that exceed the daily limit are checked correctly and reported correctly.  Make the whale icon appear on DWS rewards.
- Ensure the CPID RAC is updated on all sancs every 14 blocks (if it changes) - this ensures a consistent GSC contract for WCG.
- Ensure the user is enrolled in Kairos or Cameroon-One before allowing sponsorship
- Fix tinyformat error
- Encrypt the WCG verification code

** This is the Windows release.  Its 3 AM in Spain so lets wait til tomorrow for the compiles.  You can still self-compile tonight.  **

6

Active Discussions / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: November 14, 2019, 07:54:20 pm »

i happens automaticaly about 14h ago together with kairos and cameron

yes i dont have coin age now, in this case no reward? i think it will be some lower % as in podc1

it did only 59bbp in tx, so is it works this way? if i dont have enough coinage, then only do update with small bbp amount and no reward? until i will have coin age?

Well lets clarify this to make it easier to understand.
Lets say your CPID is 10,000 RAC, and we require 1 mil of coin-age. 
And in your external purse, you have exactly 500,000 of coin-age at the wcg-gsc-transmission-height available.
We would automatically use all of your coin-age, and, we would set you up with about 5,000 RAC.
So yes, you would get your tx in, and you would get about half the reward.

But, a person with only 59 bbp would fall below the minimum (I think of 1 RAC), and get nothing because the math would not reverse engineer all the way down to 1RAC.

So the main goal is to keep the external purse filled with coin-age for the midday block.
Now one more tip I remember, we did add code to ensure Kairos and Cameroon-One do not use much coin age and do not tithe.  So when you drill into those, you should see the absolute minimum spent in coin age from the purse.

The key to that requires doing the exec bankroll first to have some extra small bills around (in the external purse).

BTW:

You can type 'exec rac' to see the condition you are in.  The % of coin-age available comes out of that command now.

7

Active Discussions / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: November 14, 2019, 07:49:21 pm »

** DYNAMIC WHALE STAKING UPDATE **

Due to a change in the structure of each burn, we have to start the burns over.  (IE the old ones are now going to be unrecognized).
So please after you upgrade, please re-burn new DWSs.

8

Active Discussions / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: November 14, 2019, 04:57:04 pm »

i can see myself in leaderboard for kairos and cameron but not for wcg hmm

Just check your wallet and see if you sent the 'exec sendgscc wcg' out at the last height, or manually.
Ive been watching mine and mine went out automatically I believe it was 04:20AM.


You can type 'exec sendgscc wcg' right now and then wait a few blocks and then see yourself also.

Let me know if you dont and if you sent it and the txid, and Ill research if something went wrong.

Could be that you didnt have enough coin-age for your huge rac?

9

Active Discussions / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: November 14, 2019, 03:39:18 pm »

what should i see? i did exec join and sendgscc then... and after 1 day:

21:09:04

listchildren


21:09:06

{
  "List Of": "POOM Children",
  "Charity": "cameroon-one",
  "Child ID": "6d9e2b38",
  "CPK": "yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Biography": "https://biblepay.cameroonone.org/bios/6d9e2b38.htm",
  "Balance": -44,
  "Notes": "Good job, nothing due!",
  "---------": "--------------------------------------------------",
  "Charity": "kairos",
  "Child ID": "ad7ec463",
  "CPK": "yi74isEFVicF8wkXHrC1jaoMRWuX2tkU1k",
  "Biography": "https://kairoschildrensfund.com/bios/ad7ec463.htm",
  "Balance": -60,
  "Notes": "Good job, nothing due!",
  "---------": "--------------------------------------------------"
}

btw is there some command to list all my whale stakes?

Great, this is good that you can see your balance(s).  But, after you do the 'exec sendgscc kairos', you should see yourself in the leaderboard.  To see that click Leaderboard | Details.  You will see a breakout next to kairos and a separate one next to cameroon-one.  (Or the leaderboard command).


On the whale stakes, that is a good idea.  All we have so far is 'exec dwsquote 1' which shows *all* the stakes.  Let me add a couple more things to the list I posted on Suns replay:

- Ability to see the Whale icon when you *receive* a stake - this was programmed but is broken
- Ability to list your own whale stakes
- Fix the 5mil limit error
- Reject the whale stake in the RPC, and show the error message now
- Add the anti-howey language
- Allow 48 hours for whale stake maturity (in contrast to 24 hours)

** NOTE:  I received my first two whale stake payments.  Note everyone:  the way the system works, its paying 48 hours later (not 24 hours later).  Keep that in mind.  Im going to update the RPC text **  Another thing:  The whale is missing in this version, on the payments.

10

Active Discussions / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: November 14, 2019, 03:35:57 pm »

Says the burn was successful, but gets rejected. The messaging is not clear. Ideally, no mempool creation should be created IMO.

Code: [Select]

   11:04:52    exec dws 1000000 1 1

    11:04:52    {
  "Command": "dws",
  "Staking Amount": 1000000,
  "Duration": 1,
  "Reclaim Date": "11-15-2019 19:04:52",
  "Return Address": "yTXhgST2JwaPM8XRwMng4fBZzgubx76cRB",
  "ROI %": "90.6013",
  "Results": "Burn was successful.  You will receive your original BBP back on the Reclaim Date, plus the stake reward.  Please give the wallet an extra 24 hours after the reclaim date to process the return stake.  ",
  "TXID": "ab5c992590f07e67d85d9495b91a943bd785aefa973cf17630cc76f818dbf3a8"
}




VerifyDynamicWhaleStake::REJECTED, Sorry, our daily whale commitments of 118557.355695 are higher than the acceptable maximum of 5000000.000000, please wait until tomorrow.AcceptToMemoryPool::Dynamic Whale Burn rejected 5b5ff5efda6d9b4cf110e2bb977f297347924429339ab8e34f9cd0cf2d2d6507
2019-11-14 19:05:50 CommitTransaction(): Transaction cannot be broadcast immediately,


Right, we should be pre-testing this and rejecting it on the screen.  Ill fix this next.

Although I see 2 problems:  I believe we allow 5mil a day, so it should not have rejected 118K.  Ill look into that also.

Also, Ill add the Anti-Howey changes (DWS Units instead of ROI), and, a warning that as you burn the coins you are not promised a return at all.  Etc.  Something to make it clear that BBP is not promising an increase in value, but the opposite, we are warning you of a loss if you use this feature, etc.

11

Active Discussions / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: November 14, 2019, 03:33:11 pm »

on mac i got on command line saying..


  ****TINYFORMAT ERROR****
    err="tinyformat: Not enough conversion specifiers in format string"
    fmt="
VerifyDynamicWhaleStake::REJECTED, Burn time out of bounds."


****TINYFORMAT ERROR****
    err="tinyformat: Not enough conversion specifiers in format string"
    fmt="
VerifyDynamicWhaleStake::REJECTED, Burn time out of bounds."

Ok, I found this on my node also, and fixed the problem for the next release; it turns out its not too important for now so it can wait for the next release.

12

Production Proposals / Re: Dynamic Whale Staking

« on: November 14, 2019, 03:24:32 pm »

DWS feels like PoG v1. Along with spending your coin age you send your coins to a burn address. After the wait period, you get a reward. It doesn't feel that different from PoG v1 except the "burned" funds leave your wallet temporarily.

The drastic difference however is in POG, you have control over your coins and each day, you can crash our market or spend the coins.

With burning otoh, you lose control of your coins and burn them, and therefore make our coins rarer for the period that our money supply shrinks.

So this type of ecosystem what we would hope for is new buyers buy into biblepay, our price rises, they burn the coins, they get a refund later plus a reward, and by then we have even more users.  So its sort of an ecosystem with an impetus for popularity, if it works out.

13

Active Discussions / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: November 13, 2019, 04:41:27 pm »

Sorry.... it should say “allows us to contribute without officially joining”...

One of your payment comments made me thing of a pretty interesting idea for 'decentralizing orphans'.  If we had an array of orphan keys, and remember at the very beginning, we used to give every10th block reward to charity, (the miner mined it but didnt get a reward), it would be intersting if we considered rotating through a list of orphan keys, and rewarding the orphan address with the mining reward - and then giving the key to one of our charities.  Then we would have an algorithm that rotates, and requires the charity to keep a bio under the same name as the key.  (This would prove to us the sponsorship actually exists - and a page with stats to show the orphan is current by public key).    We would make it so we could automatically revoke or replenish a key by Sanctuary vote, so that the sancs still had control over the decision making process.  Then also the core wallet could expand and contract its key exposure as necessary to limit each orphan to $40 per month in BBP etc.    Just another concept to put under our belt for the future.   The idea that wins is probably the one that is trusted the most by the cryptocommunity at large, and scales well.

14

Active Discussions / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: November 13, 2019, 04:27:04 pm »

Did you do a ‘exec join cameroon-one’ ?
And a ‘exec join kairos’? I noticed that it allows us to contribute to the gscc project with having officially joined it and hence you won’t receive rewards for it.

Yeah, I confirm we dont check to see if a user is enrolled when we allow them to sponsor a child , lol, but they will quickly find out when they are not getting paid.  Ill make a note to do something about that.

15

Active Discussions / Re: TestNet - PODC 2.0 (Proof of Distributed Computing)

« on: November 13, 2019, 04:25:00 pm »

good note

04b236ea $20 (underpayment) - shows 20 balance (but I paid $40 using `exec paysponsorship cameroon-one 04b236ea 40 authorize`)
f89f5a15   $40 (correct payment)  - shows 0 balance

d6ac6919 $25 (correct payment) - shows 0 balance
5cf71b44  $50 (overpayment) - shows -25 balance
8e697449 $20 (underpayment) - shows 15 balance

Code: [Select]

{
 
 "Charity": "kairos",
 "Child ID": "8e697449",
 "CPK": "yejTJcE9cSHMfC6H3ncbURt9MWPYc2kWPv",
 "Biography": "https://kairoschildrensfund.com/bios/8e697449.htm",
 "Balance": 15,
 "Notes": "Child sponsorship is due.",
 "---------": "--------------------------------------------------"
}

sendgscc cameroon-one

Code: [Select]

{
 "Results": true
}

sendgscc kairos

Code: [Select]

{
 "Results": true
}


Code: [Select]

{
   "ac
     "ca0c14fe20735d0e73a469ce71e23d2ad89a8ad347a421eb61f3f2c24e07aca7",
     "04cd725198564fdd947095f17ffe09d751f55935ea189c695501176d121385e7",
     "9605a0be9a4080b1b3a4a9ced399d60a9585dbe27490f16dbab189bf5c3d42f4"
   ],
   "time": 1573651276,
   "timereceived": 1573651276,
   "abandoned": false
 },


1) In Prod, we do recommend the paysponsorship, so there is a complete record of the payment.  And its up to kairos or cameroon to actually apply the balance.
But in the fake environment in testnet, I rely on what you guys tell me to apply; so the applied payments don't count the paysponsorship payments.
Although Im glad you tried to send them, because that helps test the actual usage of the spork (for the receive address).  As a matter of fact if I can get Kairos to create an account here, we will need to have him review that to post payments; so when we get to that phase Ill check with him and see if he can run the report on his end that shows what users have paid through that command.
So please just verify the payments were applied that you asked me to manually apply .

2) As far as the stuck outgoing transaction, that can happen if your wallet tried to double spend, not sure why it would, and that is very very rare.  The best advice I have for that is to restart the wallet with -zapwallettxes=1, verify the tx outbound is no longer stuck.  Then re-send it.  BBP is always either on your end or on the receiver end, but not lost.  In a nutshell, this failed outbound tx didn't cause any problems for our gsc's or our WCG testing though.