From eb5d2a0fbe57709ae7c694c71efcbcc1b3b7df97 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ula=C5=9F=20Erdo=C4=9Fan?= <58347304+ulerdogan@users.noreply.github.com> Date: Mon, 12 Aug 2024 17:17:38 +0300 Subject: [PATCH 1/3] Update ccip-read.mdx Added `clv.eth` to L2 resolving examples --- docs/learn/ccip-read.mdx | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/docs/learn/ccip-read.mdx b/docs/learn/ccip-read.mdx index 8d43b7a8..02152a7c 100644 --- a/docs/learn/ccip-read.mdx +++ b/docs/learn/ccip-read.mdx @@ -23,6 +23,12 @@ It's already possible to deploy a resolver to a Layer 2. This is done by verifyi ENS Labs has created a toolkit called the [EVMGateway](https://github.com/ensdomains/evmgateway), which helps with trustless cross-chain data retrieval: this allows you to have, for example, your name controlled by a Resolver on Optimism or Arbitrum, with more EVM compatible chains coming soon. +An example implementation of Layer 2 resolving is: + +### clv.eth + +Clave is focused on enhancing user experience and security through a mobile wallet that leverages account abstraction and device hardware. Clave accounts come with usernames that are now stored on-chain in ZKsync Era and issued as ENS subnames such as [ulas.clv.eth](https://enstate.rs/n/ulas.clv.eth). You can read more about the implementation [here](https://blog.getclave.io/introducing-onchain-clave-usernames-with-ens). + {/* ## Primary Names on Layer 2 The process of storing primary names on Layer 2 is still under active development and more updates will be posted here as they become available. From 24bf2de73ebc35caebe78b6dc9ef1816c1dd6df9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ula=C5=9F=20Erdo=C4=9Fan?= <58347304+ulerdogan@users.noreply.github.com> Date: Mon, 12 Aug 2024 17:25:02 +0300 Subject: [PATCH 2/3] Update ccip-read.mdx Edit text --- docs/learn/ccip-read.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/learn/ccip-read.mdx b/docs/learn/ccip-read.mdx index 02152a7c..f218e3a7 100644 --- a/docs/learn/ccip-read.mdx +++ b/docs/learn/ccip-read.mdx @@ -27,7 +27,7 @@ An example implementation of Layer 2 resolving is: ### clv.eth -Clave is focused on enhancing user experience and security through a mobile wallet that leverages account abstraction and device hardware. Clave accounts come with usernames that are now stored on-chain in ZKsync Era and issued as ENS subnames such as [ulas.clv.eth](https://enstate.rs/n/ulas.clv.eth). You can read more about the implementation [here](https://blog.getclave.io/introducing-onchain-clave-usernames-with-ens). +Clave is focused on enhancing user experience and security through a mobile wallet that leverages account abstraction and device hardware. Clave accounts come with usernames that are now stored on-chain in ZKsync Era, verified with storage proofs in L1, and issued as ENS subnames such as [ulas.clv.eth](https://enstate.rs/n/ulas.clv.eth). You can read more about the implementation [here](https://blog.getclave.io/introducing-onchain-clave-usernames-with-ens). {/* ## Primary Names on Layer 2 From 569f557b0bec9911477182348c14a662c2a37371 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Ula=C5=9F=20Erdo=C4=9Fan?= <58347304+ulerdogan@users.noreply.github.com> Date: Mon, 12 Aug 2024 17:26:17 +0300 Subject: [PATCH 3/3] Update ccip-read.mdx Add link --- docs/learn/ccip-read.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/learn/ccip-read.mdx b/docs/learn/ccip-read.mdx index f218e3a7..2fe80f88 100644 --- a/docs/learn/ccip-read.mdx +++ b/docs/learn/ccip-read.mdx @@ -27,7 +27,7 @@ An example implementation of Layer 2 resolving is: ### clv.eth -Clave is focused on enhancing user experience and security through a mobile wallet that leverages account abstraction and device hardware. Clave accounts come with usernames that are now stored on-chain in ZKsync Era, verified with storage proofs in L1, and issued as ENS subnames such as [ulas.clv.eth](https://enstate.rs/n/ulas.clv.eth). You can read more about the implementation [here](https://blog.getclave.io/introducing-onchain-clave-usernames-with-ens). +Clave is focused on enhancing user experience and security through a mobile wallet that leverages account abstraction and device hardware. Clave accounts come with usernames that are now stored onchain in ZKsync Era, verified with [storage proofs](https://github.com/getclave/zksync-storage-proofs) in L1, and issued as ENS subnames such as [ulas.clv.eth](https://enstate.rs/n/ulas.clv.eth). You can read more about the implementation [here](https://blog.getclave.io/introducing-onchain-clave-usernames-with-ens). {/* ## Primary Names on Layer 2