danny
danny
Note, this was previously pointing to the wrong contract. The link has been updated to the correct contract.
@hrishikeshio Vyper LLL rather than high level Vyper. LLL is an intermediary between vyper and bytecode.
Although we would forgo some built-in support, I personally prefer @mratsim's format due to the ability to define a multi-field type and test multiple values per type. Also, adding `test_suite`...
@mratsim I modified the chain test format to conform to your proposed format with `fork`, `test_suite` and `test_cases`. I think it generally makes sense to support multiple `test_cases` per eth2.0...
That is the intention @terenc3t. It will probably live at ethereum/eth2.0-tests and you will be able to add it into your repo as a submodule (just like eth1.0 clients do...
Here's the repo, but we don't have anything to put it in until we decide on some testing formats :) https://github.com/ethereum/eth2.0-tests
@mratsim, Paul and I were discussing that in light of the tests he has generated, maybe all test cases don't deserve a name. Instead make the test cases a list...
described the general format in more detail in this PR https://github.com/ethereum/eth2.0-specs/pull/39
@karlfloersch @vbuterin @ChihChengLiang Requesting your comments on the above issue.
The thing about validators having different clocks is that the Network doesn't care. That delay is based on whatever the time is in `Network`, not what the time is in...