Actually, in my scheme you would be able to submit PoW submissions with 0 XEL, just no bounty submissions. SO you would have to keep PoW'ing until you have enough for the bounty deposit fee.
Well, that is cool, but I'm still not so sure about the proposition...
(EDIT: Note that while it is assumed that watching for PoW certs should be "pointless" I'm afraid that it isn't, as I'll illustrate later. Wink)
Im really interested ....
I think that some of the assumed distinctions between PoW and PoB are problematic. This is directly related to the "really interesting" attacks.
I'll have to re-check one of my remaining (DoS) attacks (which I've been calling the "max backtrack attack") against the parser. Although I suspect that this change will prevent a node from being knocked out entirely by the attack, I also suspect that the attack could still be used to "temporarily hang" a node. (Short version explanation: use the production order of the parser to craft "worst case parse time" expressions and then spam them at a node.)
... and even more! Thanks for everything so far!!
Turns out that this is probably far less interesting. With the current repo state, most of these manifest as java stack exception. About the most that I can "hang" the parser right now is 3-7 second at a time. (
i7@2.5Ghz, sun "jre 8") Not sure if that is a problem. Noticed heap GC got a little crazy though, so it might be that it could still be tuned into a combination problem.