Merge remote-tracking branch 'origin/main' into eip-5559-v2

README.md

@@ -2,15 +2,13 @@
 
 ## Overview
 
-"
 The Ethereum Name Service (ENS) has revolutionized the way we interact with the blockchain by replacing complex addresses with human-readable domain names like "myname.eth". However, ENS faces scalability and cost challenges that hinder its widespread adoption. The External Resolver project offers an innovative solution to overcome these obstacles by combining established patterns such as ERC-3668, EIP-5559, ENSIP-10, and ENSIP-16.
 
 At its core, a "resolver" is a crucial component of ENS that translates human-readable domain names into relevant blockchain information, such as wallet addresses, public keys, and custom records. The "resolution" process is fundamental for making domain names usable in decentralized applications (dApps) and wallets.
 
 The External Resolver takes the concept of resolution further by allowing ENS data to be stored and managed off-chain. This drastically reduces transaction costs, improves network scalability, and enables more advanced features like larger and more complex data records.
 
 This project not only makes ENS more efficient and cost-effective but also opens up a world of possibilities for developers and users, expanding the potential of ENS as a foundational infrastructure for Web3. By providing a comprehensive reference implementation for off-chain storage and management, the External Resolver empowers the community to innovate and build upon the ENS ecosystem.
-"
 
 ## Objectives
 
@@ -153,6 +151,20 @@ To run the External Resolver project in its entirety, you'll need to complete th
     npm run client read
     ```
 
+##### Migrations
+
+This repository relies on migrations to manage the database schema. To create a new migration, run the following command:
+
+```bash
+npm run gateway migration:create --name=<migration_name>
+```
+
+To apply the migration, run the following command:
+
+```bash
+npm run migration:generate -- -n <migration_name>
+```
+
 #### Layer 2 Setup
 
 1. Deploy the contracts to the local Arbitrum node (follow the [Arbitrum's local node setup tutorial](https://docs.arbitrum.io/run-arbitrum-node/run-local-dev-node)):