From 6d534a3ec0258aa7b1873b706a40b3715f81598d Mon Sep 17 00:00:00 2001 From: Hack666r Date: Fri, 31 Jan 2025 22:24:24 +0100 Subject: [PATCH] typo in the 19.md --- ensips/19.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ensips/19.md b/ensips/19.md index cce0e42..d47190e 100644 --- a/ensips/19.md +++ b/ensips/19.md @@ -66,7 +66,7 @@ Below is a step-by-step resolution process of ENS reverse resolution. A dapp mus 8) If the primary name is not the empty string, go to step 11. 9) If `name` is an empty string, and `coinType` is not 0, set `reverseName = '[address].default.reverse'` and `coinType = 0` and go to step 5. 10) Otherwise, no primary name exists for this account on this chain; halt and display the address instead. -11) If the dapp finds an ENS name, it MUST then check the forward resolution. This can be done by using the resolution processs in [ENSIP-10](https://docs.ens.domains/ensip/10). When constructing the ENSIP-10 `resolve()` calldata, encode a call to `addr(bytes32 node, uint256 coinType)`. Set `resolvedAddress` to the result of calling `resolve` on the resolver with this calldata. +11) If the dapp finds an ENS name, it MUST then check the forward resolution. This can be done by using the resolution process in [ENSIP-10](https://docs.ens.domains/ensip/10). When constructing the ENSIP-10 `resolve()` calldata, encode a call to `addr(bytes32 node, uint256 coinType)`. Set `resolvedAddress` to the result of calling `resolve` on the resolver with this calldata. 12) If `resolvedAddress == address`, the dapp considers the Primary Name valid, and can now show this instead of the address within the application. 13) If `resolvedAddress != address` the dapp considers the Primary Name invalid and MUST show the address instead.