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

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.

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.

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.

1.1.6.7 - Mandatory Upgrade (TestNet)** Note: This mandatory will only disconnect old versions, but will not hard fork so as to keep the chain running smoother** Forensically we now have more specific logging with the version in the POG message

- Fixed 'exec tithe' to allow just amount- Added low and high estimated ROI to 'exec titheinfo'. Note: The ROI is based on: Daily_POW_Rewards / TitheCap, divided by 2. The divided by 2 is assuming the miner spends half of the profit on electricity.- Removed non-biblepay-team warning in exec getboincinfo- Fixed the PODC Reward and POG Reward "clock" symbol to require 120 confirms in the UI transaction list- NEW USER SETTINGS: Made the wallet Not tithe automatically by default, unless the 'tithe=1' setting is set (or user uses the one-click mining configuration setup).Possible settings:Missing = Wallet will not auto tithetithe=0 or -1 Wallet will not auto tithetithe=1 : Wallet will tithe automatically according to default network SPORK (once per 4 hours in prod, once per hour in testnet)tithe=NN : Enter any number in minutes above 2, and the wallet will tithe this often