Perform the following steps: Run using invalid block and transaction tests using blockchain_test_engine Verify exception messages returned in the validation_error field of the engine_newPayloadVX response If a client returns any of the following three exceptions:Invalid Receipt Trie Hash Invalid State Root Hash Invalid Gas Used It is highly likely that there's a combination of the three fields which would result in the client accepting the invalid block.
4/14/2025Could you walk us through your changes? Could you explain how these changes affect the clients and what changes do they have to do on their clients to process them? Could you explain why you chose to implement these format changes and what's the benefit of them over the previous format? What was your approach to understanding the repository/tests? Bonus (Maybe too specific?): What do you think are the advantages of producing tests per "process name" as compared to the full epoch and why do you think this approach was chosen in the first place? Is there anything you would do to improve the test generation?
4/2/2025Hi ! As discussed in the interview, a next step in the recruitment process, we'd like to ask you to work on a take-home assignment. This assignment is based on the consensus-specs repository which would be the main focus of the position you are applying to: Build the consensus-specs and run tests. Write a new test based on any of the existing tests that you find interesting. Open a PR to the consensus-specs repo with the new test. Include in the PR some ideas of potential improvements to the repository and, specifically, improvements to the tests and/or tests framework.
2/21/2025[STEEL - February 2025] Prague Devnet-6 EELS and EEST integration Hiring EELS & EEST in the EIP Process EOF Testing - Prague Devnet-6 Specs and Testing On February 13th, EELS made their first release that follows the new versioning scheme to mark the specification of Prague's Devnet-6, which is the same finalized spec that will make it to Mainnet:
2/18/2025