{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/1bbe6c14c9784dce861307fb8b8a2d1d\" frameborder=\"0\" width=\"1664\" height=\"1248\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":1248,"width":1664,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":1248,"thumbnail_width":1664,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/1bbe6c14c9784dce861307fb8b8a2d1d-00001.gif","duration":164.16,"title":"Using Resolver to Move ENS Text Records on a Different Chain 📝","description":"Hey there! In this Loom, I'm going to show you how we can use Resolver to move ENS text records on a different chain. We've expanded the resolver field to offer you the option to apply one of the off-chain resolvers, like the one we're using. We'll pick \"noces\" as our resolver and set a new resolver that is now resolving and storing the record on the Knois chain instead of Ethereum. We'll wait a bit until the transaction passes, and then we'll set a new record, \"my new text.\" We'll do a CCIP read to get the record, but we'll get a response code not found because we haven't created the record yet. So, we'll create the record by doing an L2 transaction using a little script that I've prepared. Once the transaction is included, we can open the link to notice and see our transaction for 15 seconds. Hope you find this helpful!"}