In other words, XEL should probably always fill *all* input memory with random values, taken from a deterministic generated sequence derived from something miner-specific, and work/bounty solution certificates should include the position in the stream which gives the corresponding inputs, for validation.
Questions?
Great overview...This clarified some of my questions. However, you mentioned that the adding a signature wont help POB. My understanding is that POB also included a hash of the inputs, so if this hash was simply extended to include both a miner specific signature along with the inputs would that solve this issue without changing the current logic around the use of inputs?
Edit: I think I understand now....you are saying that the hash wont get propegated so unless the inputs are unique to me anyone can steal it....that sux :-)