Add Substrate EVM adapter milestone 2

deliveries/substrate_evm_adapter_2.md

@@ -0,0 +1,33 @@
+# Milestone Delivery :mailbox: Substrate EVM Adapter, MS2
+
+**The delivery is according to the official [milestone delivery guidelines](https://github.com/w3f/Grants-Program/blob/master/docs/Support%20Docs/milestone-deliverables-guidelines.md).**
+
+* **Application Document:** [Substrate EVM Adapter](https://github.com/w3f/Grants-Program/blob/master/applications/substrate-evm-adapter.md)
+* **Milestone Number:** 1
+
+**Context** (optional)
+
+This milestone's main goal was to be able to expand an ETH RPC adapter capabilities to be able to write into the chain. This involved writing a pallet that converts incoming RPC requests into runtime calls that Substrate runtime understands.
+
+**Deliverables**
+
+| Number | Deliverable | Link | Notes/Specification |
+| -----: | ----------- | ------------- | ------------- |
+| **0a.** | License | [License](https://github.com/subclone/subeth/blob/main/LICENSE) | MIT |
+| **0b.** | Documentation | [Documentation](https://github.com/subclone/subeth/blob/main/INSTRUCTIONS.md) | We will provide both **inline documentation** of the code and a basic **tutorial** that explains how a user can (for example) spin up one of our Substrate nodes and send test transactions, which will show how the new functionality works. |
+| **0c.** | Testing and Testing Guide | [Tests](https://github.com/subclone/subeth/blob/main/chain/pallets/evm-adapter/src/tests.rs) | Core functions will be fully covered by comprehensive unit and integration tests to ensure functionality and robustness. In the guide, we will describe how to run these tests. |
+| **0d.** | Docker | [Docker](https://github.com/subclone/subeth/blob/main/chain/Dockerfile) | We will provide a Dockerfile(s) that can be used to test all the functionality delivered with this milestone. |
+| **0e.** | Article | [Article](https://medium.com/@subclone/subeth-bridging-ethereum-tools-to-substrate-chains-dfd81547d802) | I will publish an article that explains the complete lifecycle and future plans of the project |
+| 1. | EVM Adapter Pallet | [evm-adapter](https://github.com/subclone/subeth/tree/main/chain/pallets/evm-adapter) | We will create a pallet that will be responsible for bridging the gap between the ETH RPC adapter and the Substrate chain. It will have the ability to dispatch FRAME calls, opt-in possibility to execute EVM bytecode, and handle account mapping. Another main responsibility of the pallet will be handling signature verification. Some parts of this pallet can be inspired from `frontier`'s pallet `pallet-ethereum` but needs refinement and some modification. |
+| 2. | Substrate Node | [Template node](https://github.com/subclone/subeth/tree/main/chain) | We will create a Substrate node that has two runtimes: with and without the `pallet-evm`. Both will contain `evm-adapter` pallet, but only the one with `pallet-evm` will be able to execute EVM bytecode. This will demonstrate two main use-cases of this pallet. |
+| 3. | MVP Demo DApp | [Simple dApp](https://github.com/subclone/subeth/tree/main/simple-dapp) | We will provide a small EVM DApp that demonstrates the integration of the pallet and RPC adapter. This will be a basic web page that can sign and send custom extrinsic with Metamask, read the state of Substrate pallets. |
+| 4. | `docker-compose` | [docker-compose](https://github.com/subclone/subeth/blob/main/docker-compose.yml) | We will provide a `docker-compose` file that will run the whole project. |
+
+**Additional Information**
+
+`smoldot` support is currently experimental in `subxt` and in general `smoldot` is pretty unstable as a real time RPC node.
+
+Some known limitations and issues:
+
+- When using a light client it might crash from time to time, causing the light client to be banned from the network but it will try to reconnect after timeout. This issue is not observed when remote RPC node is used.
+- The adapter is not able to handle all the edge cases of the ETH RPC, but it should be able to handle the most common ones.