Nice.. so, that is used like a "signature"... blocks without that expected 0.001 fee attached are obviously running free in the wild, on the wrong chain, or attempting to 51% attack? Since they would not have that fee? (Not sure if it is "given/handed-out", or if it is "programmed/auto-reward" in the code.)
Still, nice.
Adding 0.001 to all my found blocks.
JK.
Also, add a "mandatory update" notice... Might even want a specific thread for that, "just the client wallet". For wallet related issues, as opposed to "Aircoin" as a whole.
Possible thread title:
[INFO] AIRcoin mandatory wallet update (v0.3.x) and wallet issues.
Forking, node-failure, setup, transactions... you know... basic wallet issues. (Would delete old replies there as handled, to keep the off-topic crap down. Also as it updates to new versions.)
P.S. You should make wallets look for a "mandatory update" flag... If it sees the flag, it stops mining, or auto-rejects the blocks found so it never submits them. (As opposed to still submitting blocks to the others with outdated wallets, which would accept them. Also, as opposed to new wallets just rejecting the old wallets submitted blocks, which would cause a fork, as the old wallets continue to run in one isolated group.)
The flag would have to have a hashed version increment, tied to the seed, so it could not be "faked", which would stall the network by disabling miners everywhere with a fake mandatory update flag. Incremental is fine, does not need to have an actual version number, as it would not change with each version, just be worked into code/wallets that are new, when a "forced update" is required. Which would also stop any prior old versions from running.
Eg,
V0.3.1
MU#1V0.3.2
MU#1V0.3.3
MU#2 <- First actual mandatory update
V0.3.4
MU#2V0.4.1
MU#2 <- Not forced, still compatible (down to V0.3.3)
V0.4.2
MU#3 <- Oops, not as compatible as you thought, same as v0.4.1, but forced flag set now.
etc..
Also... have you disabled the LTC version-update warning..
that will annoy everyone in the future if you did not. When LTC updates, your wallet may start complaining to "update your LTC wallet".