They are send from GUI with version 1163.
I did not see any error messages until I had no more aged coins. Until that I was able to send as many times as I wanted. I cannot recall seeing minimum diff in red.
I just reproduced this behavior and I can pump my tithes up in a very short time.
OK good to know. So as of yesterday, I logged a couple things that could be bugs (the tithes not entering - sometimes - even though you didnt receive an error in the gui) and another one: I believe our version of dash has a limited memory of utxo age; and I have a suspicion that some nodes are seeing a different memory utxo set - this is all really technical so what I need to do for the next version is create our own BBP map of these, so there is no chance of this "difference" and I believe this will also kill the possibility of a tithe not entering when it meets the parameters. (On a side note I plan on adding a transaction fee to donations that increases by 1 bbp per donation - and giving that to the miner - I think this would stave off single block tithe attacks. Although I do want to clarify to everyone, a legal tithe is a legal tithe, so dont get the idea that when one hogs a block they are doing something bad - if the coins are aged its legal - what Im trying to do is discourage it and make it financially unfeasible for someone to want to hog a single block and raise diff up for everyone at once by a massive amount).
Just to clarify on the fee: It makes no difference what address or wallet # you tithe from, it would be like this: Miner checks global memory pool, how many tithes on bbp network in this block? If < 10, no extra fee to tithe. If > 10, the tithe fee is 1 bbp for tithe #11, 2 bbp for tithe #12, ... etc. Next block we start over at 0 again. Also the tithing fees goes to the reaper. The giver loses the tx fee. This discourages tithe attacks by one "hog".
Recent Posts
manpage for repository creation and user configuration details.
