Nate Rush

That works (and this is the approach uPort took in their [Meta Transactions](https://github.com/uport-project/uport-identity/blob/develop/contracts/TxRelay.sol)), but it requires an assumption that the relayer will do the right thing (and not send 2...

@djrtwo if you get a chance, I'd love another set of eyes on this bug. It's very weird and I can't figure out why it would possibly happen :D

The above bug is fixed! The fork choice is unfortunately not the same, though. Going to keep debugging + updating the spec for the algo as necessary.

@vladzamfir mentioned an O(1), or O(n) safety oracle today. Writing a note here as a reminder to ask about this. It isn't totally obvious to me how to do this,...

Another (better) solution is to reintroduce the `Justification` data structure. Here, we two options. We can have multiple `Justification`'s - one that just stores `latest_messages`, and one that also has...

Thanks for adding this. I've started work here and should be able to get up a WIP branch tomorrow. Not sure what the best trade-off is here. Seems to me...

Here's how I'm approaching it as of now: 1. When a validator checks estimate safety on some estimate for the first time, we create the directed edges in the view...

https://github.com/karlfloersch/cbc-casper/tree/feat/oracle_cache work begun here.

I think @karlfloersch mentioned that the reason the original PR was not merged in was b/c of some performance concerns. Not sure if this is an issue - but it...

Some test situations to make sure the validator does not freak out if it receives an equivocation or invalid block: 1. Invalid Block - Does not contain the correct fields....