Messages

2626

TestNet Discussion Archive / Re: Testnet - Test Proof of Giving

« on: January 04, 2019, 09:11:51 AM »

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

Sorry for the delay; Its taking a little longer than usual; moving to daily superblocks required a larger than expected change.

Debugging now.

2627

TestNet Discussion Archive / Re: Testnet - Test Proof of Giving

« on: January 03, 2019, 07:55:40 PM »

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.

2628

TestNet Discussion Archive / Re: Testnet - Test Proof of Giving

« on: January 03, 2019, 01:46:44 PM »

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.

2629

TestNet Discussion Archive / Re: Testnet - Test Proof of Giving

« on: January 03, 2019, 01:42:31 PM »

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.

2630

TestNet Discussion Archive / Re: Testnet - Test Proof of Giving

« on: January 03, 2019, 01:40:43 PM »

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.

2631

TestNet Discussion Archive / Re: Testnet - Test Proof of Giving

« on: January 03, 2019, 12:43:09 PM »

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

2632

TestNet Discussion Archive / Re: Testnet - Test Proof of Giving

« on: January 03, 2019, 12:12:43 PM »

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.

2633

TestNet Discussion Archive / Re: Testnet - Test Proof of Giving

« on: January 03, 2019, 10:13:29 AM »

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.

2634

TestNet Discussion Archive / Re: Testnet - Test Proof of Giving

« on: January 03, 2019, 10:08:28 AM »

I have it same like MIP.
After first tithe I was on POGpool and rewards were coming, but then it suddenly stoped.
Auto tithes works, but I'm not on POGpool anymore and rewards are missing.
BTW: those rewards are really "spamy". One reward per day would be awesome.

BTW2: today it was first time that I saw someone on chat.
I left public chat window open for several hours (but i was AFK) and I have there message from ichtus220
I see that he joined and leaved chat. Interresting is that I've never see anyone else. I see only 3 nodes in my connections. It is that problem? You can see on chat only people from your connections?

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.  But yes, Ill look into a daily superblock today.

On Chat, you can actually talk to anyone on the whole network.  I think the problem is no one is using it.  I havent had much time to keep it open.  But yeah, it forwards the message through other nodes to every node.

2635

TestNet Discussion Archive / Re: Testnet - Test Proof of Giving

« on: January 03, 2019, 10:01:09 AM »

Would treating PoG like RAC be an issue?

So here's my thought.  Everyone participates in PoG and every tithe to the Foundation counts.  By contributing you get "RGC" - Recent Giving Credit.  Then a daily superblock pays out the PoG recipients like PoDC does.  So only one payment, less traffic since only one tithe a day would be necessary.

Then your tithe has a half life, and every day, is worth 50% (or some other target) of the previous day.

So, if the Team RGC is 10,000, then someone tithing 1000 would get 1000/10,0000 or 1/10th the daily reward.  The next day, that 1000 gift on Monday would still be worth 500 RCG points, and if the next day the team RCG was still 10K, they would get 1/20th the daily reward.

Granted, i still affirm working on simplifying PoDC is the optimal strategy, but I think something like this would simply the logic of PoG, reduce transactions and overall be better for the blockchain than what has been sketched out thus far.

So on this idea, I like the idea of consolidating the transactions down to one single superblock per day, as that would allow us to expand our difficulty window back to 205 blocks (IE less volatility in the Pog Diff), and of course it would reduce the spam for each wallet (which is a very good pro I think).  (I also like how we will be able to calculate payments just once per day - that I believe will work great) - that should make the system more efficient.

Honestly, the reason I originally deprioritized the idea of a superblock was because this original POG idea being an extension to our mining algorithm,
 it was originally considering the immediate tithe_weight (of the reaper of the active blockhash) and influencing the ability to solve the block. 

However, having a once per day pogpool payout sounds like a really good feature.

On the POG RAC idea, its kind of 'interesting' but Im not sure if it doesnt add more complexity to it.  Lets be real, POG is not complicated, we are down to only a couple variables (pog diff, coin difficulty parameters (age-amount-max tithe)) - and adding RAC would probably just give us a longer lifetime of a tithe.  The main problem with implementing POG RAC is then we need to keep track of a 'pog ID' and a 'pog prior RAC' (in order to calculate current rac in a decay fashion).  That is adding a lot more complexity (in contrast to sum of tithes per POG ID in one given day).  Right now we just need to capture sum of tithes over a 24 hour period.  But specifically, RAC doesnt solve the POG difficulty problem - we still need the existing POG difficulty to govern whether a tithe is legal for a certain block and we also still need our exiting tithe cap.  So it appears rac would just give users a smoother diminishing reward - but going to that requires contracts - I think we can do the daily superblock for POG without a governance contract (which is a Pro, as Ive been trying to make it so pog does not require any third party data to come to a consensus for the payment vector). 

So in light of this, I think it would be in our best interests to look into a daily POG superblock.  The biggest requirement for this is it requires me to allocate funds from the daily heat mining budget for the superblock (IE only reaper rewards are issued block to block) and that 'pogpool portion' is paid in the actual superblock daily.

Whats nice about testnet is we will see this in action 4 times per day as soon as we test, so we should be able to sort this out pretty quickly.

2636

TestNet Discussion Archive / Re: Testnet - Test Proof of Giving

« on: January 03, 2019, 09:47:39 AM »

I seem to be in the right chain but still have problems to see my nickname in pogpool and the chat shows blank

Code: [Select]

pogpool
{
  "ySwRWw1EEEMyGSz4iiWVAwryXbxBTumiPG": "Amount: 637.00, Weight: 1.0000, Payment_Tier: 0, Height: 101505, NickName: randrews",
  "High Tithe": 637.2,
  "Total Tithes": 637.2,
  "Total Participants": 1,
  "POG Difficulty": 10206.64793502028,
  "My Tithes": 0,
  "My Nickname": ""
}

Also I can't tithe but I think this is because my coins are not old enough at current diff level (2-3 days).

Oh, ok I remember something now - when your nickname is not set up (IE its empty) Chat does Not work - it needs a name to work.

On your nickname, I think I know the problem - Im not sure if you saw my prior message, but please create a biblepaytest.conf here:
~/.biblepaycore/biblepaytest.conf


If you place:  nickname=yyyy
testnet=1
tithe=N

In there, you should then be able to reboot and see the nickname in 'pogpool'?

Start program like this:
./biblepay-qt -conf=biblepaytest.conf

2637

TestNet Discussion Archive / Re: Testnet - Test Proof of Giving

« on: January 02, 2019, 07:14:47 PM »

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

2638

TestNet Discussion Archive / Re: Testnet - Test Proof of Giving

« on: January 02, 2019, 02:44:20 PM »

So, no more "tranches"? More payments but smaller amounts? How much we tithe / pool tithe is the percentage we get back? Sort of like my rac / team rac?

Ironically, I found a thing with the "tiers" that I dont think anyone likes (so this is sort of an accidental blessing that cures this problem).  If you get unlucky and leave your miner tithing in the old way, you can continually get placed in a busy tier (IE one with high tithes) and actually lose money the old way.

In the new way there are no more tiers- and everyone gets paid every block.  This is a little more spammy, in that we will probably have 1000 recipients per block in prod (when we grow bigger), but we can fix that later as it is not a problem for our wallet to handle this currently.

So now, the ROI will be much more accurate.  If you tithe continually, you will be assured a profit (and not a crapshoot).

We will test this out in a little bit; but from the design, you should always make at least 50% profit.

I think the faster turnover of diff (every 16 blocks) will be a very positive thing also as it will make the system much more active. 

2639

TestNet Discussion Archive / Re: Testnet - Test Proof of Giving

« on: January 02, 2019, 08:53:24 AM »

Hey All,

So from a very high level, POG seems to be "relatively good", but I have an uneasy feeling about one issue. 
When we removed the training wheels, I noticed we always had a smaller chain with less work competing with the main chain - IE we were more apt to form a fork.  We had about one fork per day, yet we recovered.   I don't think this is normal.

In light of this, I will need to make some changes to POG - most likely changes that deal with shortening the POG duration down from 205 blocks to 16.  I'm thinking what we might do is simplify POG in a way where the wallet takes a look at the last 16 blocks to determine POG difficulty (in contrast to 205), and inside those 16 blocks, it creates a map of who is in the pool (IE who legally tithed), and we pay every pool participant in the next block.

This should give the POG participant the benefit of receiving less volatile reward amounts per tithe (IE not waiting for a payment tier to occur).

The main benefit of this for the core wallet is it will theoretically be more efficient (IE less lookback calculations) and also less prone to fork risk (as during every block connect, the wallet looks at its prior 16 block indexes).

So in light of this please pause testing and Ill prioritize this to the highest level and be back asap with a new version.

2640

TestNet Discussion Archive / Re: Testnet - Test Proof of Giving

« on: January 02, 2019, 08:43:39 AM »

where is problem?

So the problem is half bug half understanding.

Take a look at your prior screenshots, and see how you have no coins old enough to tithe?  (IE tithability = NO) in the one shot, and the amount?  Thats the "actual problem".

But I see when you tried to send 200, it created a txid of 00000000000000000000000, thats a bug.

Will fix today.

Thanks.