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 12 13 14 ... 137
91
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).


92
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.


93
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.



94

What I want to point out is that the …200 sanc is my current sanc. The other one is the IP of my router which I have just checked that NONE of my machines (at that address) are running biblepayd and yet BOTH are enabled on the blockchain… The port 40001 isn’t even reachable for .238 and yet it appears to be still getting paid even more recently than my current .200 sanc....

Code: [Select]
$ sanc list
{
...
 },
 "51a7d0cdb93fb3377d274f1b448af3c260618eb23c145a52c6c2fc081192b4dc-1": {
   "proTxHash": "3fdfa35533185427856e07d7a966714d118c7434994b5d6a349c11558e79e290",
   "address": "45.62.239.200:40001",
   "payee": "yRKdex8fFcDyjqx618Cz4hsQcQFjp55jRg",
   "status": "ENABLED",
   "lastpaidtime": 1562191975,
   "lastpaidblock": 125601,
   "owneraddress": "yhDJCUZq19CVLiuDa4wEoY4PxWg17bZuTx",
   "votingaddress": "yhDJCUZq19CVLiuDa4wEoY4PxWg17bZuTx",
   "collateraladdress": "yMm52BQvFgjtSjHLhohQbF5zmTYkBc4JWb",
   "pubkeyoperator": "05f58c1b79e898cf31a0375ded7a8e5bb6b0e5aacb48dc79f7c87e38eb0533bdf85c610cee5cf94b79c425c20f423cc4"
 },
 "0df4d38dee8b4233d250b05dd8773ec320292d16a6b2e7c008ffb58d976a259e-1": {
   "proTxHash": "7b5c9e029fd9d220e244ab9516a6196ec98a6a5a22fab6890da2f20a80cc971c",
   "address": "64.180.194.238:40001",
   "payee": "yeVEt6ivbyJnhR96Uh7ckt9j3gy3MRDaKF",
   "status": "ENABLED",
   "lastpaidtime": 1562191896,
   "lastpaidblock": 125598,
   "owneraddress": "yfu6HiZiEEUvwd5Bt6BEzvCP2heSgguCZE",
   "votingaddress": "yfu6HiZiEEUvwd5Bt6BEzvCP2heSgguCZE",
   "collateraladdress": "yc5iiRK3bxSDRqziqMPNZ7qEHxnYzvckkH",
   "pubkeyoperator": "0bd2ef8af156182399cac5d63e6e4f79a8877d79b514791178a9ffdd54e5378f31a28522033ec0e2519027845a15ef37"
 }
}
[email protected]:~/charity/Sanctuary$ telnet 64.180.194.238 40001
Trying 64.180.194.238...
telnet: Unable to connect to remote host: Connection refused
..
[email protected]:~/charity/Sanctuary$ telnet 45.62.239.200 40001
Trying 45.62.239.200...
Connected to 45.62.239.200.


Diagnosing the problem...



95
One more thing, to test:

1) You should see -60, -10, and +15 balances for the children, since they were debited $40 to start and all 3 are provisioned now.

2)  This will be verrry tricky.  Rule 2a) Regardless of sending more than one exec sendgscc in a given superblock interval, you should only receive *one* payment per child (per superblock interval). 
Rule 2b)  If you participated in homogenized POG and or Healing, you should also receive the same regression tested amount you are used to (we should do an exec analyze height nickname, and verify the actual points->reward didn't change after adding Cameroon) (This is basically a Cameroon one regression test, to ensure we did not break Prod's POG point allocation amounts or payment amounts).


96
  "Child ID": "2c587757",100
  "Child ID": "576df3e6",50
  "Child ID": "62021cdb",25

Thx

Ok good; I have credited your 3 balances as per your payments, now when you type listchildren, you should see the actual outstanding balance as if Cameroon charged you $40.00 for each child on July 1st (its $40 per month).

So notice that your 3rd child is not fully paid.
The way this works is the API will return -999 if the child is not provisioned (that means Cameroon has not actually assigned the hex ID to a real child).  Those, whether they have negative balances or not do not get rewarded in BBP.

Next, only the people with negative balances (and provisioned children) get rewarded BBP.

So, if you do an exec sendgscc, what should technically happen is we should send a GSC tx (one tx) with 3 children in it, and, you should only be rewarded for 2 of the children (the 2 with credit balances).

So, to check the payment, check the exec leaderboard, or look in the UI leaderboard, and look in the "details" for the actual Cameroon one detail rows.  You should end up with 2,666 points (because cameroon charges us $1.33 per day).

Now heres where it gets tricky.  We never reward a user more than $1.33 per day even if we have only a partial superblock.
So knowing the output of exec price yields a BBP price of $.000507 per USD, the wallet will automatically arrive at what is called a daily sponsorship cap.
You can get this value by typing exec dailysponsorshipcap.

Knowing the sponsorshipcap, it will reward you about 2500 bbp or so (I forget the exact #) in rewards per child.

So once you get your rewards, please do the math and see if your two children paid you $2.66 today? 
Remember in testnet, we have 4 blocks per day, so you will end up with 4* the amount in 24 hours.

I believe people who leave their miner off will end up being shorted (so they have to actually mine) in order for a gsc transmission to go out every day and get the daily reward back.


97
Listchildren shows the 3 are “not provisioned yet”.....

Ok, good.  Please paste the 3 hex-child-id codes for your children (this simulates you notifying cameroon by paying by paypal or check) and give me an amount you want credited to your cameroon account in USD?


98
Old sanc that I resurrected  is 45.62.239.400. Same exact server.

Strange, it was on the blockchain even though the server was off or running something else and once on didn’t need the controller wallet at all.

Maybe you can verify if it was receiving rewards previously since as far as i know the same server was deployed on mainchain.

Great to have you join; So I do see the 45.62.239.200 (not 400) but I see this 200 was paid @ 125356.
Yes I do see oncoapop1 owed 65% of the kitty in the leaderboard.

If you want to help me test cameroonone, please join the 'cameroon-one' exec join cameroon-one, then 'sponsorchild authorize' then send me the child ID and the amount you want to send a fake check in for and Ill credit your cameroon one account in testnet. 

EDIT: Actually could you go ahead and sponsor 3 children?  This way we can see if MIP gets 1 payment, randrews2 gets 2 payments and oncoapop1 gets 3 payments?

PS:  Yeah, I think you made it through without resyncing because since you were off, you didnt violate any consensus rules and after you upgraded, you synced as normal forward.  Btw, the reason you didnt need to restart the server is the other sancs didnt POSE ban you yet (plus, in dip3 mode, they restart automatically - the dash devs removed the start button etc and integrated the auto-start logic into dip3).  But Ive seen some of our sancs get POSE banned in Prod - I had to restart some of mine a few times.  The main difference should be that we wont have to manually click start, they will go down, we will fix the sancs problem, then they will autostart in this version (in prod).




99
All linux & mac binaries are ready. I am back mining again.

And on Cameroon-One, I forgot to mention, and its OK you have already sponsored a child (we will add a test to ensure this is in order for the next version), but please also do this MIP:

exec join cameroon-one

You must be a member of the campaign for the sancs to "see you" in the campaign.


100
Does everyone agree with this hash:

10:11:38

getblockhash 124999


10:11:38

250787d6b1cf87b15f69bf3009eccc56017270b7142d7d4960b6a1281350a3b2


* Note that you may have to resync as we are now in pure dip3 mode.


101
BiblePay
1.4.5.6 - Mandatory Upgrade for TestNet

- Fix sanctuary split issue (Require ABN fees to be added into total block fees)

102
BiblePay
1.4.5.5 - Mandatory upgrade for TestNet

- Require proto_version 70735 in testnet
- Remove log spam
- Dont allow people to tithe more than 500 inputs
- Fix bug in Deterministic Payment comparison (appears to be confined to coins with very high satoshi scales - like us)
- Make govobj ddos more unique (allows devs to debug govobj propagation issues)


Hey all - please don't upgrade yet - I see one more problem that needs addressed.

Im working on it.


103
BiblePay
1.4.5.5 - Mandatory upgrade for TestNet

- Require proto_version 70735 in testnet
- Remove log spam
- Dont allow people to tithe more than 500 inputs
- Fix bug in Deterministic Payment comparison (appears to be confined to coins with very high satoshi scales - like us)
- Make govobj ddos more unique (allows devs to debug govobj propagation issues)

104

Hmm, actually no one is mining right now due to some very strange error in the log.  Checking.

Ok, the problem in testnet turned out to be a division error in our branch only.  It was not a Dash or Biblepay development error, its an error rooted in floating point math that is only exploited in a chain with very high Satoshi scale like us.


The new version will be out in an hour.



105
Now I think I don't have enough ABN weight so I'm not mining and no blocks are being mined.


00:09:27

exec getabnweight


00:09:27

{
  "Command": "getabnweight",
  "version": 1.2,
  "weight": 26756016.61004648,
  "total_required": 17733092
}


Hmm, actually no one is mining right now due to some very strange error in the log.  Checking.



Pages: 1 2 3 4 5 6 [7] 8 9 10 11 12 13 14 ... 137