# EPF6 - Week 4

## Overview
- Mapped out and ran sim tests to prepare project proposal for submission
- Began research on the codebase and how to contribute to the migration process

## Main points
- Obtained insights from Lodestar team on Discord about migration status and potential points of integration with Kurtosis
- Started to outline potential TODOs for contributing to the migration process
- Submitted and solicited feedback on my project proposal
- Began deep-dive into ethereum-package and Lodestar codebase to better formulate migration scope and requirements
- Mapped out the code of the simulation tests
- Successfully initiated sim tests from github workflow

## Learnings & Outcomes
- Learned how to start sim tests (Command:`yarn workspace @chainsafe/lodestar test:sim:multifork`) and successfully ran ([multifork test](https://github.com/ChainSafe/lodestar/blob/unstable/packages/cli/test/sim/multiFork.test.ts) output shown below)
- Seems likely that Kurtosis will (after migration) need to be able to be initiated from a github action as well

## Week 5 TODOs
- Participate in weekly Lodestar core dev standup
- Submit project proposal and collect feedback
- Explore structure of current `kurtosis.yml` and `kurtosis_sim_test_config.yaml` to understand the difference in the type of tests being run versus test-sim.yml

### Useful resources checked

[GitHub sim tests](https://github.com/ChainSafe/lodestar/tree/unstable/packages/cli/test/sim) from [Lodestar documentation](https://chainsafe.github.io/lodestar/contribution/testing/simulation-tests/)

[Lodestar multifork test](https://github.com/ChainSafe/lodestar/blob/unstable/packages/cli/test/sim/multiFork.test.ts)