Bible Pay

Recent Posts

Pages: 1 [2] 3 4 5 6 7 8 9 10
11
Active Discussions / Re: Testnet - Test Proof of Giving
« Last post by Rob Andrews on December 15, 2018, 06:14:17 pm »
the above command isn't working for me in the debug console.

12:52:24 exec tithe
12:52:24 You must specify amount, min_coin_age (days), min_coin_amount.  IE: exec tithe 200 1 1000. (code -1)

12:52:27 exec tithe 250
12:52:27 JSON value is not a string as expected (code -1)

Good find, I just added this to the bug list.  Working on it.

12
Active Discussions / Re: Testnet - Test Proof of Giving
« Last post by Rob Andrews on December 15, 2018, 06:12:15 pm »
Is there a frequency that is observed for "tithing"? TestNet seems to be about once an hour. If I were to tithe 30 minutes after an automated send, that is considered an illegal tithe?  If the transaction is not created, it wouldn't be in the "unconfirmed" stage. Unconfirmed seems like it would encourage more confusion to new users.

No you can manually tithe as often as you want and it wont be illegal - as long as its a legal tithe.  Legal means it fits the difficulty parameters.

If it were any other way people would try to game the system by writing scripts to tithe.

The frequency is once per hour in testnet.

Im making it so you can override that in the settings next.

13
Active Discussions / Re: Testnet - Test Proof of Giving
« Last post by Rob Andrews on December 15, 2018, 06:10:48 pm »
I'm seeing PoG reward available after 6 confirmations.

Oh you are relying on the checkmark on the UI, that is just a display bug.

Coinbases are not spendable until 102 confirms.  You can look in your "unconfirmed" balance to see all your POGs arent available.

Ill look at the checkmark bug.

14
Active Discussions / Re: Testnet - Test Proof of Giving
« Last post by sunk818 on December 15, 2018, 05:25:01 pm »
So on the illegal tithe, I can say with relative certainty what I "think" is happening.  (Note that Illegal Tithe and POG Pool Recipients Invalid are mostly for logging, for us to ensure we have prevented those problems in test, and then they become very rare cases of things that arent supposed to happen in prod).

I believe due to people upgrading and being on forks, the difficulty level is not exactly the same on 3 forks.  Once we all agree on the block hash, we should re-tithe, and then watch the log for one day and see that the error has dissapeared.

To answer your question though the pool will not induct an illegal tithe.  But those will be forced on their own chain anyway, so this error should dissapear once we are synced together.

(The givers actual tithe was legal on his own chain) - just illegal on our chain.

Is there a frequency that is observed for "tithing"? TestNet seems to be about once an hour. If I were to tithe 30 minutes after an automated send, that is considered an illegal tithe?  If the transaction is not created, it wouldn't be in the "unconfirmed" stage. Unconfirmed seems like it would encourage more confusion to new users.
15
Active Discussions / Re: Testnet - Test Proof of Giving
« Last post by sunk818 on December 15, 2018, 03:13:17 pm »
the above command isn't working for me in the debug console.

12:52:24 exec tithe
12:52:24 You must specify amount, min_coin_age (days), min_coin_amount.  IE: exec tithe 200 1 1000. (code -1)

12:52:27 exec tithe 250
12:52:27 JSON value is not a string as expected (code -1)
16
Active Discussions / Re: Testnet - Test Proof of Giving
« Last post by sunk818 on December 15, 2018, 02:50:42 pm »
The POG reward is a coinbase, so it takes 120 confirms to become spendable (just like mining revenue).

On a side note, all the pool rewards for one block are contained in one transaction.

I'm seeing PoG reward available after 6 confirmations.
17
Active Discussions / Re: Testnet - Test Proof of Giving
« Last post by Rob Andrews on December 15, 2018, 12:08:42 pm »
getblockhash is correct for me.

Keep getting this:

2018-12-15 18:03:55
 Illegal tithe @height 87725.000000, max amount 296.500000  amount 296.710000 vout 1
 Illegal tithe @height 87835.000000, max amount 296.490000  amount 296.710000 vout 2
 Illegal tithe @height 87883.000000, max amount 296.930000  amount 297.150000 vout 1 ProcessNewBlock : ACCEPTED

If a tithe is illegal, maybe one can be resent as a test and if it works send it along.

Or illegal tithe should be abandoned? It keeps showing up in the logs... is that right?  I assume it'll keep showing up because the transactions can't be abandoned currently or resent?

So on the illegal tithe, I can say with relative certainty what I "think" is happening.  (Note that Illegal Tithe and POG Pool Recipients Invalid are mostly for logging, for us to ensure we have prevented those problems in test, and then they become very rare cases of things that arent supposed to happen in prod).

I believe due to people upgrading and being on forks, the difficulty level is not exactly the same on 3 forks.  Once we all agree on the block hash, we should re-tithe, and then watch the log for one day and see that the error has dissapeared.

To answer your question though the pool will not induct an illegal tithe.  But those will be forced on their own chain anyway, so this error should dissapear once we are synced together.

(The givers actual tithe was legal on his own chain) - just illegal on our chain.

18
Active Discussions / Re: Testnet - Test Proof of Giving
« Last post by sunk818 on December 15, 2018, 12:05:13 pm »
getblockhash is correct for me.

Keep getting this:

2018-12-15 18:03:55
 Illegal tithe @height 87725.000000, max amount 296.500000  amount 296.710000 vout 1
 Illegal tithe @height 87835.000000, max amount 296.490000  amount 296.710000 vout 2
 Illegal tithe @height 87883.000000, max amount 296.930000  amount 297.150000 vout 1 ProcessNewBlock : ACCEPTED

If a tithe is illegal, maybe one can be resent as a test and if it works send it along.

Or illegal tithe should be abandoned? It keeps showing up in the logs... is that right?  I assume it'll keep showing up because the transactions can't be abandoned currently or resent?
19
Active Discussions / Re: Testnet - Test Proof of Giving
« Last post by Rob Andrews on December 15, 2018, 11:56:55 am »
Ok, Testnet seems stuck at block 87697


Im surprised so few are testing - I believe we should be able to recover because the rule was our normal rejection rule for old versions; however on a side note Im starting to dislike that rule as it really shakes up the whole system - its as if its worse to require a mandatory that way than for me to add a block version field on my logging - anyway



getblockhash 87915
f042dfcb5d9265ef681ffbe1bf3577274bcdcd13411d340a37d179ca10616810

This morning looks like we got past that does yours agree?  I have two nodes running that agree.  My 3rd is not even synced halfway let me see if I can get a third up to 87915.





20
Pre-Proposal Discussion / Re: Mass Adoption for BiblePay II
« Last post by Rob Andrews on December 15, 2018, 11:53:16 am »
We will always have both,  POG will take 80% but the plan was POBH would earn 20% (block miner)

Exactly, this way solo mining pays 20% but the lions share of the pool is in-client. 

Note that I think it would be a really good idea for us to test POG in prod with POBH only (as we all agreed on so far) and write down exactly how many pool miners (in POG) we see per day - for example a pool.biblepay.org report that pulls in the exec pogpool stats in SQL so we can make a graph.  It would be very valuable to see if POG results in a daily increase in biblepay use. 

Of course we can just add pog diff to the current difficulty chart also.

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