@devs: and the first shit-effect became visible.
Out of 4 bounty submissions only 3 went through the supernode, causing me to lose one bounty-announcement-fee of 10 XEL.
Since bounty announcements do not go through supernodes (only the bounties themselves), it becomes sort of a gamble - we have to get it fixed somehow. We need an idea to move from "best effort" to "guaranteed submission", at least in a form that people do not lose deposits randomly.
Also, we need a way to "set the network" into maintenance mode to ensure an upgrade. Maybe we could allow the guard nodes to submit a "force update" transaction, causing the entire network to only relay regular transactions and nothing work related before an update has been made? This will not shut down the network since the basic functions are still "alive"? But then, what do we do with open work, pending bounty announcements, etc?
We need some answers
At least this works: Due to the "lost" bounty submission, the work author made 10 XEL with forfeited deposits ;-) (Actually, the text is misleading, because currently forfeited bounties go to some central account)