diff --git a/docs/learn/ccip-read.mdx b/docs/learn/ccip-read.mdx
index 8d43b7a8..2fe80f88 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 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
 
 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.