Testnet - Test Proof of Giving

Thanks, I did read your message and already tried, in fact I changed "MIP" to other larger lowcase nick, in case there was some issue... but it seems to keep ignoring me. And I don't know how to troubleshoot.

This is what I have now:

Code: [Select]

testnet=1
shrinkdebuglog=1
debug=true
debugmaster=true
tithe=3
nickname=mobiledev
genproclimit=1
gen=1
and then after relaunching:

Code: [Select]

pogpool
{
  "ySwRWw1EEEMyGSz4iiWVAwryXbxBTumiPG": "Amount: 879.00, Weight: 1.0000, Payment_Tier: 0, Height: 101722, NickName: randrews",
  "High Tithe": 879.3,
  "Total Tithes": 879.3,
  "Total Participants": 1,
  "POG Difficulty": 14084.597503552,
  "My Tithes": 0,
  "My Nickname": ""
}


Oh btw on the "old coins", could you please type 'titheinfo' - the "Tithability Summary: Yes/No" will show you if your coins are too young (based on the 3 diff params above it).

On the missing nickname, could you please check to see if you possibly have a 'testnet.conf' or 'biblepay.conf' in your \testnet3 directory, and rename or remove it first?  Then launch with

./biblepay-qt -conf=biblepaytest.conf

Just to ensure you dont have two copies?  I believe the code really does go key by key and may be doing something in \testnet3 if you have a 2nd config file in there.

Well you should receive 15 rewards in this current version for one tithe, as the pool contains the last 16 blocks in it, maybe diff was high when you wrote this and the remainings came in after you posted.  On that front things look OK.

I've checked it.
I have 3 tithes there and after each one there is 16 rewards what is almost (16 not 15) like you wrote.
But after 4th tithe there arent any rewards.
Then I was no able to tithe because of coin age, but I'm curious why there wasn't rewards after last tithe.
I was thinking that I'm on fork, so I've deleted my chain and resynced.
Now I've made new tithe and rewards are going well.

I've checked it.
I have 3 tithes there and after each one there is 16 rewards what is almost (16 not 15) like you wrote.
But after 4th tithe there arent any rewards.
Then I was no able to tithe because of coin age, but I'm curious why there wasn't rewards after last tithe.
I was thinking that I'm on fork, so I've deleted my chain and resynced.
Now I've made new tithe and rewards are going well.

Right, 16, I was thinking for a minute the block you tithed in didnt count, but yes it starts on the *next* block so yes 16.

Anyway, there is a positive reason for everything, so if you did not delete your chain you could type 'exec istithelegal txid' for your 4th, and it would give us the exact reason (as either it enters the pool or doesnt).

So let us know if it happens again, or in the next version.

Ok.
So here are my results:

19:22:36
exec istithelegal 1ea2e9a7470b1a15385c472e204bf7c0fc1fe78ffea9b250b67025ed821d223b

19:22:36
{
  "Command": "istithelegal",
  "Tithe_Legal": false,
  "Tithe_Age": 11.75815972222222,
  "Tithe_Spent_Coin_Amount": 50226,
  "Tithe_Amount": 227,
  "Block_diff_min_coin_age": 12.72,
  "Block_diff_min_coin_amt": 5302,
  "Block_diff_max_tithe_amt": 236,
  "Tithed_Height": 101659
}

So, it looks that my coin age was lower then expected.
But it was sent with auto tithe and I expect that autotithe didn't send coins if they didn't match criteria.
It is possible that diff change between sent and received?

Ok.
So here are my results:So, it looks that my coin age was lower then expected.
But it was sent with auto tithe and I expect that autotithe didn't send coins if they didn't match criteria.
It is possible that diff change between sent and received?

It looks like your coin_age was a little too low for it to count.
Yes, I think this can happen when the block advances between the time your miner tithed it in its eyes legally, and it was mined in n+1.

First, I think when we switch to a 205 block span, this incidence rate will drop by 90% (as volatility will drop) - right now with 16 block volatility we are highly volatile.

Second, we have a buffer in the coin to tithe 20% Less than the Max amount allowed, but we do not have a buffer for Age.  Ill go ahead and apply the 20% buffer to the auto-tithe miner only (IE just to coins tithed automatically), this will help prevent this  (IE coin must be 20% older than stated for it to auto-tithe).

Putting this in here because I thin it's related.

I setup a prod sanc yesterday, it crashed based on a gobject issue

debug log shows this:   Shouldn't this be disabled in prod currently?

Code: [Select]

NextPogRevenue 50694.078759
NextPogRevenue 50694.078759
NextPogRevenue 50694.078759
NextPogRevenue 50694.078759
NextPogRevenue 50694.078759
NextPogRevenue 50694.078759
NextPogRevenue 50694.078759

Also, watchman crashed:

Code: [Select]

Traceback (most recent call last):
  File "bin/watchman.py", line 244, in <module>
    main()
  File "bin/watchman.py", line 191, in main
    perform_biblepayd_object_sync(biblepayd)
  File "bin/watchman.py", line 24, in perform_biblepayd_object_sync
    GovernanceObject.sync(biblepayd)
  File "lib/models.py", line 78, in sync
    golist = biblepayd.rpc_command('gobject', 'list')
  File "lib/biblepayd.py", line 42, in rpc_command
    return self.rpc_connection.__getattr__(params[0])(*params[1:])
  File "/home/mn2/.biblepaycore/watchman/venv/lib/python2.7/site-packages/bitcoinrpc/authproxy.py", line 139, in __call__
    response = self._get_response()
  File "/home/mn2/.biblepaycore/watchman/venv/lib/python2.7/site-packages/bitcoinrpc/authproxy.py", line 179, in _get_response
    http_response = self.__conn.getresponse()
  File "/usr/lib/python2.7/httplib.py", line 1121, in getresponse
    response.begin()
  File "/usr/lib/python2.7/httplib.py", line 438, in begin
    version, status, reason = self._read_status()
  File "/usr/lib/python2.7/httplib.py", line 402, in _read_status
    raise BadStatusLine(line)
httplib.BadStatusLine: ''


This is 1.1.7.5 from the mainnet PPA

edit:

ran again and got this in the debug.log

Code: [Select]

NextPogRevenue 50694.078759 CGovernanceObject::IsCollateralValid -- Couldn't find opReturn 045038724b047ba1908bc557777a5c5ae04703230449d1707865b6$
    CTxIn(COutPoint(188a03b6449ca0bc55e6080dffe79eb3ce82ab29a8fa058c25cd12eb56ba13a2, 1), scriptSig=4730440220609c612a0d1bc0, nSequence=429496729$
    CTxOut(nValue=5.00000000, scriptPubKey=6a20be8b2d169ab6657870d1490423)
    CTxOut(nValue=350.70471391, scriptPubKey=76a914c9a8aec4fae6853343f451e6)

2019-01-03 18:44:47 MNGOVERNANCEOBJECT -- Governance object is invalid - Couldn't find opReturn 045038724b047ba1908bc557777a5c5ae04703230449d1707$
    CTxIn(COutPoint(188a03b6449ca0bc55e6080dffe79eb3ce82ab29a8fa058c25cd12eb56ba13a2, 1), scriptSig=4730440220609c612a0d1bc0, nSequence=429496729$
    CTxOut(nValue=5.00000000, scriptPubKey=6a20be8b2d169ab6657870d1490423)
    CTxOut(nValue=350.70471391, scriptPubKey=76a914c9a8aec4fae6853343f451e6)


...(IE coin must be 20% older than stated for it to auto-tithe).

Does it mean to us increasing diff by 20%?
Because now we have problems with coinage, not with +20%

Does it mean to us increasing diff by 20%?
Because now we have problems with coinage, not with +20%

What do you mean?

Edit: You had a problem with coin_age, it was too low in your illegal tithe.

Edit2:  No it will not mean increase in diff - it just means the miner would wait longer before tithing it.
If the age required is 10 days, it would wait until it had found 12 days of coin age before tithing.  Better than complaints that we lost peoples money.

A user can always tithe manually however against the current diff level.

Putting this in here because I thin it's related.

I setup a prod sanc yesterday, it crashed based on a gobject issue

debug log shows this:   Shouldn't this be disabled in prod currently?

Code: [Select]

NextPogRevenue 50694.078759
NextPogRevenue 50694.078759
NextPogRevenue 50694.078759
NextPogRevenue 50694.078759
NextPogRevenue 50694.078759
NextPogRevenue 50694.078759
NextPogRevenue 50694.078759

Also, watchman crashed:

Code: [Select]

Traceback (most recent call last):
  File "bin/watchman.py", line 244, in <module>
    main()
  File "bin/watchman.py", line 191, in main
    perform_biblepayd_object_sync(biblepayd)
  File "bin/watchman.py", line 24, in perform_biblepayd_object_sync
    GovernanceObject.sync(biblepayd)
  File "lib/models.py", line 78, in sync
    golist = biblepayd.rpc_command('gobject', 'list')
  File "lib/biblepayd.py", line 42, in rpc_command
    return self.rpc_connection.__getattr__(params[0])(*params[1:])
  File "/home/mn2/.biblepaycore/watchman/venv/lib/python2.7/site-packages/bitcoinrpc/authproxy.py", line 139, in __call__
    response = self._get_response()
  File "/home/mn2/.biblepaycore/watchman/venv/lib/python2.7/site-packages/bitcoinrpc/authproxy.py", line 179, in _get_response
    http_response = self.__conn.getresponse()
  File "/usr/lib/python2.7/httplib.py", line 1121, in getresponse
    response.begin()
  File "/usr/lib/python2.7/httplib.py", line 438, in begin
    version, status, reason = self._read_status()
  File "/usr/lib/python2.7/httplib.py", line 402, in _read_status
    raise BadStatusLine(line)
httplib.BadStatusLine: ''


This is 1.1.7.5 from the mainnet PPA

edit:

ran again and got this in the debug.log

Code: [Select]

NextPogRevenue 50694.078759 CGovernanceObject::IsCollateralValid -- Couldn't find opReturn 045038724b047ba1908bc557777a5c5ae04703230449d1707865b6$
    CTxIn(COutPoint(188a03b6449ca0bc55e6080dffe79eb3ce82ab29a8fa058c25cd12eb56ba13a2, 1), scriptSig=4730440220609c612a0d1bc0, nSequence=429496729$
    CTxOut(nValue=5.00000000, scriptPubKey=6a20be8b2d169ab6657870d1490423)
    CTxOut(nValue=350.70471391, scriptPubKey=76a914c9a8aec4fae6853343f451e6)

2019-01-03 18:44:47 MNGOVERNANCEOBJECT -- Governance object is invalid - Couldn't find opReturn 045038724b047ba1908bc557777a5c5ae04703230449d1707$
    CTxIn(COutPoint(188a03b6449ca0bc55e6080dffe79eb3ce82ab29a8fa058c25cd12eb56ba13a2, 1), scriptSig=4730440220609c612a0d1bc0, nSequence=429496729$
    CTxOut(nValue=5.00000000, scriptPubKey=6a20be8b2d169ab6657870d1490423)
    CTxOut(nValue=350.70471391, scriptPubKey=76a914c9a8aec4fae6853343f451e6)


On the POGRevenue, I deliberately added that to print it to the log and not to the screen - just so I could see the value in advance for sanity sake.  I just took out the logging for prod for the next version.

On the POGRevenue, I deliberately added that to print it to the log and not to the screen - just so I could see the value in advance for sanity sake.  I just took out the logging for prod for the next version.

On watchman, could you try running it again and see if it recovered?  There are a lot of Error conditions in watchman that are picked up on the next run (it runs every 5 mins).

On the Collateral being invalid in prod, that is normal.  Thats due to someone creating a proposal without aged collateral.  That just wont be a valid governance object, so that is OK.

On watchman, could you try running it again and see if it recovered?  There are a lot of Error conditions in watchman that are picked up on the next run (it runs every 5 mins).

On the Collateral being invalid in prod, that is normal.  Thats due to someone creating a proposal without aged collateral.  That just wont be a valid governance object, so that is OK.

Thanks i'll give it another go... it crashed again when I tried to enable, maybe 3rd times the charm?

1.1.7.7 - Leisure Upgrade
Mandatory Upgrade for TestNet


- MIP added WIN exit handler (in getboincmetrics during initialization) - Test to see if this stops crashing in Win10 Home (be sure to set boincmetrics=0 first)
- Moved exec tithe and exec titheinfo to : tithe and titheinfo
- Added a spork to allow us to add or remove POG training wheels (allows devs to attempt to verify forks)
- Added nickname to 'titheinfo' (Allows user to see config is being recognized)
- Modified POG to only look back 16 blocks (prevent forks)
- POG 24 hour tithes is now based on the last 16 blocks extrapolated out to 24 hours

Having hard time finding peers again. No problems on 1175. 1177 only one wallet found peers. Rest at 0 peers for several hours.

Having hard time finding peers again. No problems on 1175. 1177 only one wallet found peers. Rest at 0 peers for several hours.

Please wait about an hour, 1178 is almost out.

On watchman, could you try running it again and see if it recovered?  There are a lot of Error conditions in watchman that are picked up on the next run (it runs every 5 mins).

On the Collateral being invalid in prod, that is normal.  Thats due to someone creating a proposal without aged collateral.  That just wont be a valid governance object, so that is OK.

Strange not sure what the deal was but seems ok now, sorry false alarm

Please wait about an hour, 1178 is almost out.

I shut down all my clients a while ago based on Rob's message earlier.