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 - Rob Andrews

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

22:56:00

exec getabnweight 125000


22:56:00

{
  "Command": "getabnweight",
  "version": 2.6,
  "weight": 1253818517.638646,
  "total_required": 28852642,
  "weight 125000.00": 132255.1786689815,
  "total_required 125000.00": 67455
}


I'm using my "normal" mainnet mining wallet but this is different to what I see using 1.4.4.3

Code: [Select]
22:56:24

exec getabnweight 125000


22:56:24

{
  "Command": "getabnweight",
  "version": 1.2,
  "weight": 23305003.67273147,
  "total_required": 1861636,
  "weight 125000.00": 146982.5912037037,
  "total_required 125000.00": 23121
}

v1.2 didnt have the 500 tx limit, but 2.6 does; 2.6 sorts by coin-age.

Lets see if these two things shed light on it:

exec getabnweight 125000 1

And

exec createabn 125000


See if they use the coins as expected.  If no error occurs in exec createabn, you should be able to abn mine.


If you really want to see if 2.6 is accurate, try this:

exec createabn 10000000
See if it makes an ABN with a weight of 10 million?

(audited_weight: 10mm)

47
mining in prod... I see weird stuff in abninfo and poolinfo5:

Code: [Select]
20:37:10

getmininginfo


20:37:10

{
  "blocks": 132344,
  "currentblocksize": 1000,
  "currentblocktx": 0,
  "difficulty": 5764.798569706667,
  "errors": "",
  "pooledtx": 0,
  "chain": "main",
  "genproclimit": 1,
  "networkhashps": 554920.0413722472,
  "hashps": 0,
  "minerstarttime": "07-17-2019 18:19:34",
  "hashcounter": 0,
  "pooledtx": 0,
  "chain": "main",
  "biblepay-generate": true,
  "poolinfo1": "",
  "poolinfo2": "",
  "poolinfo3": "",
[b]  "abninfo": "No block to mine... Please wait... 1563388615; ",
  "poolinfo5": "Internal ABN: Invalid 1563388480; ",
[/b]  "gsc_errors": "low abn weight 0",
  "poolmining": false,
  "pool_url": "",
  "required_abn_weight": 125000
}

While 1.4.4.3 says "Unable to create ABN..."

So if you send a big GSC out, sometimes you have to wait 5 confirms to get your ABN weight back.
Could you please paste your exec getabnweight 125000?


48
BiblePay
1.4.5.9 - Leisure Upgrade

- Commit 1441-1442 prod changes to Develop
- Miner now has all the abn/turnkey features prod does - please test mining against Prod


49
Code: [Select]
23:05:00

listchildren


23:05:01

{
  "List Of": "Cameroon-One Children",
  "Child ID": "abaad3ec",
  "CPK": "yWK9ckFhU1ihDSDLAZggNFTwypg6Bi3C23",
  "Biography": "https://cameroonone.org/biblepay/abaad3ec.htm",
  "Balance": -10,
  "Nickname": "MIP",
  "Child ID": "0f83ef0c",
  "CPK": "yWK9ckFhU1ihDSDLAZggNFTwypg6Bi3C23",
  "Biography": "https://cameroonone.org/biblepay/0f83ef0c.htm",
  "Balance": -999,
  "Notes": "This child is not provisioned yet.",
  "Nickname": "MIP"
}

Executed the sendgscc
And I see myself in the leaderboard

Are you happy with the amount you are receiving per day (for Cameroon), and non Cameroon POG rewards?

Next, we need to test non abn and abn and pool and non-pool mining (I think it would be prudent to test all the combinations).

Can we please sync to prod in .14, and have a few of us test against the pool in PROD (as testnet doesn't have a pool setup currently).

We have develop version 1.4.5.9 coming out now; lets build this version first, release it, then continue testing the mining.


50
I'm back here with latest testnet in MacOS.

I see this


Code: [Select]
01:10:30

listchildren


01:10:31

{
  "List Of": "Cameroon-One Children",
  "Child ID": "abaad3ec",
  "CPK": "yWK9ckFhU1ihDSDLAZggNFTwypg6Bi3C23",
  "Biography": "https://cameroonone.org/biblepay/abaad3ec.htm",
  "Balance": -999,
  "Notes": "This child is not provisioned yet.",
  "Nickname": "MIP"
}

OK, and as you know, in Testnet I am running the mock API to apply debits and credits to the childs balances, but in Prod, CameroonOne will be running the API (from their own domain).

So I posted a $50.00 payment for child abaad3ec. 

Go ahead and do a listchildren now and see if you have a -10$ balance (this is because you have a debit of $40 for July orphanage charges minus a $50 payment).

Then do an execgscc and wait 6 blocks and see if the child payment is showing in your leaderboard "details".

Do you understand the 'exec dailysponsorshipcap'?  This shows the max amount we pay per child per day in the GSC contract (we use the daily BBP price quote - found in exec price - and of course the daily GSC paymentlimit - to calculate the quorums dailysponsorshipcap).

Oncoapp has 3 children, you have 1 and I have 2.  So Ill do an exec sendgscc, and we should see 6 children over 3 participants in the leaderboard we can reverse engineer. (Click Details).

OK, I sent an exec gscc, I see Oncoapp & I in there, now we need you.  Btw, the reason you are not in cameroon one as of yet today is because your child was not provisions (nor had a credit balance - until Cameroon receives the check or the paypal making your balance a credit balance!).



51
BiblePay
1.4.5.8-Leisure Upgrade

- Merge in 1.4.4.1 prod changes -> develop
- Fix ABN create error (insufficient funds)
- Fix BiblePay Miner ABN crash-windows 64 crash issue

52
Please check your coin control, and see if select all results in a tx size > 100K.  If so, unselect all, then select some repeatedly - and send them to yourself.
Repear until your total stash < 100K in size.

Then wait 6 confirms then do exec sendgscc.

I see we made this automatic in our prod branch, and somehow, this got borked in testnet; I will have a commit within 24 hours to fix this issue.


53
I am ready to do some tests but I don't know if I'm doing something wrong

Code: [Select]
00:16:32

exec sendgscc


00:16:32

{
  "Command": "sendgscc",
  "Error!": "CreateGSCTransmission::Fail::(Create Transaction) Insufficient funds.CreateGSCTransmission::Fail::(Create Transaction) Insufficient funds."
}

I have like 27M so plenty of funds.

Please check your coin control, and see if select all results in a tx size > 100K.  If so, unselect all, then select some repeatedly - and send them to yourself.
Repear until your total stash < 100K in size.

Then wait 6 confirms then do exec sendgscc.


54
So I just sent a few gsccs.

Clicking on GUI leaderboard, clicking on DETAILS, check out randrews3.  I have two cameroon one orphans.  I am being paid 5550.46 (two children of 1334 points each).  So far this version looks good.  (Even though I sent out 10 gsccs).  My pog is 607,553.  Ill do exec analyze.


55
Thank you, both.

Wallets currently syncing....


I have an update on the POSE issue (this is the unreachable sanc being paid issue).

So I have fully researched this.  In our prod environment (non-deterministic sancs, running in the .13 branch), the POSE (proof of service) is achieved by having sanctuaries send MNPINGs around the network.  This is similar to the bitcoin PING packet, meaning that our network knows when a sanctuary fails to reply to MNPINGS, they start falling behind in the payment queue and start getting POSE banned.  I know in prod, if I stop a sanc for over a couple hours, my sanc will move to NEW_START_REQUIRED (I just had to restart two in that state today).

However, you rightly point out that in the .14 branch, our sancs just keep getting paid.  So the reason for this is Dash is retiring all non-deterministic-messages to simplify the codebase.  We are running in a state where we are expected to turn on LLMQ soon.

In .14, when LLMQ is off, sancs constantly get rewarded.  When LLMQ is enabled, each sanc is required to participate in a quorum within a certain amount of time (IE about 1-24 hours depending on the size of the quorum).

So the answer to this concern is for now lets overlook it until we enable LLMQ.  Then let us regroup and test this POSE ban functionality to ensure your non reachable sancs do get POSE banned.

Moving on to Cameroon One, Im still very excited about this feature.  Lets see if this latest version fixed the payment issue?




56
The binaries appear not to have been complied yet? What is the proper command to pull from the develop branch on github? The usual command errors out.

Sorry but I’m not a coder and not familiar with these basic commands....

I released Windows last night, but MIP is in the mountains and he releases linux, but I have received word the binaries are now deployed.

Regarding manual pull, try this:
cd ~/biblepay-evolution-develop (or where your develop branch is)
cd src
git pull origin develop
make

(This assumes you built it once before from source).

If not you have to do this whole thing first including building depends:
https://github.com/biblepay/biblepay-evolution/blob/master/BuildBiblePay.txt

Then just pull the develop branch (with the above git commands) and recompile develop.

(I keep develop in a separate directory so I can have both in separate states).



57
BiblePay
1.4.5.7 - Mandatory Upgrade for TestNet

- Fix bug in Cameroon-One reward (restrict reward to one payment per day)
- Add Sanctuary POSE ban punishment on Sancs who are offline (see masternodelist : posescore column for POSE ban level; when service level drops below .50, node moves to POSE_BAN state and stops receiving payments)
- Add BBPSocket class (this is for a non-blocking TCP connection with timeout for future use)
- Added notes to getchaintips function explaining our unique situation on DIP1 & CSV bits states

58
1. Tithe normally via Cameroon-One

Code: [Select]
{
 "Prominence": "Details",
 "CAMEROON-ONE: yS9YaCFpQuE6xpBrTvUbnPyJgwaXZep8C8 [N/A], Pts: 1333.00": "0.27%",
 "CAMEROON-ONE: yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe [N/A], Pts: 0.00": "0.00%",
 "CAMEROON-ONE: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 2667.00": "0.55%",
 "POG: yS9YaCFpQuE6xpBrTvUbnPyJgwaXZep8C8 [N/A], Pts: 3022707.00": "53.72%",
 "POG: yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe [N/A], Pts: 634626.00": "11.28%",
 "POG: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 0.00": "0.00%",
 "Healing": "Diary Entries",
 "Prominence": "Totals",
 "ALL: yS9YaCFpQuE6xpBrTvUbnPyJgwaXZep8C8 [N/A], Pts: 3024040.00, Reward: 502530.690": "53.990%",
 "ALL: yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe [N/A], Pts: 634626.00, Reward: 104974.110": "11.280%",
 "ALL: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 2667.00, Reward: 5083.390": "0.550%”
}

2. spam exec sendgscc

3. cli exec analyze 127852 oncoapop1

Code: [Select]
{
 "Command": "analyze",
 "Totals": "CAMEROON-ONE|yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt|2667|0.00546183|oncoapop1|2668\nPOG|yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt|0|0.00000000|oncoapop1|664505\n",
 "0": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127747.00, TXID: 48e194fa86c3c3765b8e99d21a7817265ad2178174c3af2fd2ec4481953f0240, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 436515.4894, Donation: 0.0000, UserTotal: 2666.67",
 "1": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127829.00, TXID: 60e6383ad2a46c1562b22bc8f363ad48c51be907b20f1ce8b6b3a5329b0285d8, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 472618.7650, Donation: 0.0000, UserTotal: 5333.33",
 "2": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127831.00, TXID: 09bdcb818fb26f7889730feb9af7a3be49f119cb822f885525d9cdecc76ec13d, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 1170573.1598, Donation: 0.0000, UserTotal: 8000.00",
 "3": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127831.00, TXID: e643dcf61c8666ec77f481f32041e98bec0f0357005599f1dffddfe7c089661d, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 244234.6203, Donation: 0.0000, UserTotal: 10666.67",
 "4": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127831.00, TXID: ba5dbc1954e23ca44c821317515c55d895dbe117a97f19fa8260ac276bed23d1, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 16135.2207, Donation: 0.0000, UserTotal: 13333.33",
 "5": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127831.00, TXID: 60b7a3124d9d75aa2024a67ce4a29bcecd2d7e8adb55014227c88acb89c5b7fa, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 495451.5158, Donation: 0.0000, UserTotal: 16000.00",
 "6": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127832.00, TXID: 9884b452e0d6cabd512b82ba0a01d6aeebd434d5ee5be4d5bed9577d7ff6e5e3, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 815893.8629, Donation: 0.0000, UserTotal: 18666.67",
 "7": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127832.00, TXID: 4ea1df741b02ec30a16cf8fdce9b4c8ade28d7b4558b9289b0864014092b5c58, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 637133.8471, Donation: 0.0000, UserTotal: 21333.33",
 "8": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127835.00, TXID: 1aa871659405b4a96e3d747d2da820b974d5e9d59d474ca787b67d5a259797ac, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 1163778.4370, Donation: 0.0000, UserTotal: 24000.00"
}

4. now after spamming, I check leaderboard

Code: [Select]
{
 "Prominence": "Details",
 "CAMEROON-ONE: yS9YaCFpQuE6xpBrTvUbnPyJgwaXZep8C8 [N/A], Pts: 1333.00": "0.27%",
 "CAMEROON-ONE: yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe [N/A], Pts: 0.00": "0.00%",
 "CAMEROON-ONE: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 2667.00": "0.55%",
 "POG: yS9YaCFpQuE6xpBrTvUbnPyJgwaXZep8C8 [N/A], Pts: 3022707.00": "53.72%",
 "POG: yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe [N/A], Pts: 634626.00": "11.28%",
 "POG: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 0.00": "0.00%",
 "Healing": "Diary Entries",
 "Prominence": "Totals",
 "ALL: yS9YaCFpQuE6xpBrTvUbnPyJgwaXZep8C8 [N/A], Pts: 3024040.00, Reward: 502530.690": "53.990%",
 "ALL: yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe [N/A], Pts: 634626.00, Reward: 104974.110": "11.280%",
 "ALL: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 24000.00, Reward: 5083.390": "0.550%”
}

5. great - i accumulate points but the rewards are capped as intended to 5083.90 BBP

6. Now I POG

Code: [Select]
"41": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127843.00, TXID: ff01da633701ff62bd850a5958969c51170a0921bbc72656b1c40c1966f08e5e, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 102796.3848, Donation: 0.0000, UserTotal: 112000.00",
 "42": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127856.00, TXID: e92787cdc0a272fa2fb0a6583aba692a90c85f9b1d8de5efb846dbeeac3ef110, NickName: oncoapop1, Points: 6944111.09, Campaign: POG, CoinAge: 322317.0851, Donation: 10000.0000, UserTotal: 7056111.09",
 "43": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127856.00, TXID: ec831148c8372acf8dbd9ff85b85ab4071537fd157d37b546f7bf40e714d1047, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 82046.5779, Donation: 0.0000, UserTotal: 7058777.76”,

7. POG calculation

CoinAge x (tithe)^1/3
322,317 x (10,000)^1/3 = 322,317 x 21.5443469003 = 6,944,108
6,944,108 /  7,608,615 (ie total POG points, add POG from leaderboard) = 91.2% of POG reward ( 617671.74 BBP) = 563,726.68 BBP
plus CAMEROON ONE 5083.90

Total 568,810.58 BBP

Code: [Select]
{
 "Prominence": "Details",
 "CAMEROON-ONE: yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe [N/A], Pts: 0.00": "0.00%",
 "CAMEROON-ONE: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 2667.00": "0.55%",
 "POG: yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe [N/A], Pts: 615907.00": "5.30%",
 "POG: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 6944111.00": "59.70%",
 "Healing": "Diary Entries",
 "Prominence": "Totals",
 "ALL: yUNSEjjtC9pdeHp4spswdFWh1npfV5Jvqe [N/A], Pts: 615907.00, Reward: 49285.700": "5.300%",
 "ALL: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt [oncoapop1], Pts: 7058778.00, Reward: 560760.880": "60.250%"
}

8. Well = 568,810 BBP (calculated as in (7), based on my understanding) vs 560,760 BBP (reported by leadboard)- that 8,050 BBP difference is more than my Cameroon reward!

Issues
A. points in exec analyze are incorrect for Cameroon one as it is not supposed to accumulate, it is correct on leaderboard for Cameroon-one but NOT total (see 2, this is may be confusing)
B. points in leaderboard Totals are not accurate since it sums incorrectly accumulating Cameroon-One points and hence no value above the cap.
C. There appears to be a discordance in manually calculated vs leaderboard reported rewards which may be significant, if my understanding is correct.


Issues
A. points in exec analyze are incorrect for Cameroon one as it is not supposed to accumulate, it is correct on leaderboard for Cameroon-one but NOT total (see 2, this is may be confusing)
->  Great, correct, this was a bug, the Cameroon points were accumulating.  Fixed in next version.



B. points in leaderboard Totals are not accurate since it sums incorrectly accumulating Cameroon-One points and hence no value above the cap.
->  Correct, Bug.  Fixed in next version.

C. There appears to be a discordance in manually calculated vs leaderboard reported rewards which may be significant, if my understanding is correct.
->  As long as the discord affects Cameroon One only, as what I observed in unit test earlier was POG was still correct - but Cameroon was accumulating.  So lets test again tomorrow and spam it again, and see if we got it.




The next version also addresses POSE bans (for penalizing offline sancs).


59
Fiat calculations

1. $1.33 per child per day = $2.66 for two children
2. BBP = 2.66 / 0.000502405947 = 5,294 BBP (we used 5083.90 in last calculation but it is close enough)
3. Sorry I do not understand what the dailysponsorshipcap is and how to apply it in this case.

Values used to calculate the points received:

Code: [Select]
exec dailysponsorshipcap
{
 "Command": "dailysponsorshipcap",
 "cap": 0.00273612097317169
}
exec price
{
 "Command": "price",
 "consensus_price": 0,
 "qt_phase": 0,
 "qt_prior_phase": 0,
 "qt_future_phase": 0,
 "qt_enabled": true,
 "cur_price": "0.000502405947",
 "BBP/BTC": "0.000000045000",
 "BTC/USD": 11164.5766
}

Excellent summary above;  luckily, we are in agreement in all points, so the code I checked in for the next version addresses exactly those things.  Ill comment deeper on it.

As far as fiat,  so the wallet converts the $1.33 into a corresponding maximum Prominence % level, in reference to the entire total contract for the day.  So, since our GSC contract is about 950K per day, it converts $1.33 to a prominence cap level in percentage terms, so that you can take the daily sponsorship cap %, and multiply it * the daily superblock value like this:

950,000 (daily superblock GSC contract value ) * .00273 (sponsorship cap) = 2593 bbp.
This is the amount the wallet will reward for one child (about $1.33 per day).

So yes you got that one and it seems to be working correctly.  We should see about 5200 bbp for 2 children at this price level and contract level.  Of course QT and deflation in the future will lower this figure, but we will know as it happens, as our getgovernanceinfo will show the next daily budget etc.


60
POG calculation
CoinAge x (tithe)^1/3
4,021,756 x (1,300)^1/3 = 4,021,756 x 10.9139288 = 43,893,155
plus 2,666=43,895,821 (close enough)

Within superblock (height 127415-127256 = 159 blocks), send another gscc +2666 points
Usertotal = 43,898,493

Perhaps I didn’t understand it but this means that I was awarded points TWICE WITHIN the same superblock….

also the price function does not appear to work and I cannot see if the fiat is correct.


Code: [Select]

cli exec analyze 127426 oncoapop1
{
 "Command": "analyze",
 "Totals": "CAMEROON-ONE|yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt|2667|0.00687494|oncoapop1|2668\nPOG|yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt|43893160|0.64629026|oncoapop1|44145110\n",
 "0": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127256.00, TXID: cd1a328f8316753e2899b8447db915c74f49105971f1cea144afba924115d64c, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 34196721.3301, Donation: 0.0000, UserTotal: 2666.67",
 "1": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127399.00, TXID: ab31c0f4818188b1dd8e3ae9ad8d76514dd8750401ba603f2d45c3000f33b240, NickName: oncoapop1, Points: 43893160.43, Campaign: POG, CoinAge: 4021756.1531, Donation: 1300.0000, UserTotal: 43895827.10",
 "2": "User: yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt, Diary: , Height: 127415.00, TXID: 3c99a32dfc1d984f2030bcfe21fb6cf9344a79d9b1243ead698e3947c580a99c, NickName: oncoapop1, Points: 2666.67, Campaign: CAMEROON-ONE, CoinAge: 4711.9792, Donation: 0.0000, UserTotal: 43898493.76",
 "3": ""
}

cli listchildren
{
 "List Of": "Cameroon-One Children",
 "Child ID": "2c587757",
 "CPK": "yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt",
 "Biography": "https://cameroonone.org/biblepay/2c587757.htm",
 "Balance": -60,
 "Nickname": "oncoapop1",
 "Child ID": "576df3e6",
 "CPK": "yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt",
 "Biography": "https://cameroonone.org/biblepay/576df3e6.htm",
 "Balance": -10,
 "Nickname": "oncoapop1",
 "Child ID": "62021cdb",
 "CPK": "yfqGyVvuyidYytq5o2QvN1VdVeXtH9Lrkt",
 "Biography": "https://cameroonone.org/biblepay/62021cdb.htm",
 "Balance": 15,
 "Nickname": "oncoapop1"
}

Cameroon points  - only count negative balances (ie we are up-to-date with the payments?) = 2
points awarded = 2,666 (CORRECT)

exec dailysponsorshipcap
{
 "Command": "dailysponsorshipcap",
 "cap": 0.003436608621582211
}

cli exec price
{
 "Command": "price",
 "consensus_price": 0,
 "qt_phase": 0,
 "qt_prior_phase": 0,
 "qt_future_phase": 0,
 "qt_enabled": true,
 "cur_price": "0.000000000000",
 "BBP/BTC": "0.000000000000",
 "BTC/USD": 0
}



1) I am still working on the POSE issue (regarding the nodes that were non-reachable) - we will have a release to analyze and mitigate.

2) Regarding exec price, there was a missing spork; fixed.  Now you can do the exec price.

3)  Regarding your exec analyze 127426 oncoapop1 results, I see you were paid only once per orphan (1333 points * 2 active orphans = 2666 points) in superblock for 127426.  I like how your points analysis almost matches exactly for the legacy POG point rewards compared to actual rewards, I believe that confirms the POG points, but please lets check the next superblock with that formula also.
  As far as double payments,  we have a superblock once every 6 hours in Testnet, so when you receive your *next* 2666 points it should be at *a higher height*.  You should be able to see this in exec analyze, because the cutoff will be clear, each new superblock height should reward you with payments for 2 children.

EDIT:  Oh, sorry, I see you do have two rows for one height... Interesting.  We specifically coded against that scenario.  OK, I will check this out now.

Thanks.



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