danny
danny
Absolutely. In the issue, I should note that this is for when other clients implement the casper spec.
`decimal10` support in web3.py is currently a blocker https://github.com/ethereum/web3.py/issues/700
`eth-abi` library is waiting on decision to be made on whether vyper is going to keep decimal10 or just move to support fixedNxM https://github.com/ethereum/vyper/issues/566
If we want "View" to be more pure in the sense that it is in the spec paper, we could have a Node or Client that has the View and...
Fixing the seed might be useful for testing the random implementation, but we want validators to be able to make more interesting decisions than build on random shard(s) and want...
@naterush More details need to be fleshed out. Just wanted to get this up before you dive into memoization tonight.
This looks good. A couple of questions: - Should the view be responsible for creating/maintaining edges or should the Oracle? I like the idea of the oracle maintaining the cache...
Honestly, looks like a great start. We can debate design on the other side On Tuesday, October 17, 2017, Nate Rush wrote: > Here's how I'm approaching it as of...
I'm down to help get prepared. We are currently tied to the vyper version commit right after the big eth-tester merge. What else has changed since then?
Cool. I'm planning on converting (almost) all of our `int128`s to `uint256` so that should fix that issue.