update domai nname

README.md

@@ -4,14 +4,14 @@
 <br />
 
 <p align="center">
-  <a href="https://ethfollow.xyz" target="_blank" rel="noopener noreferrer">
-    <img width="275" src="https://docs.ethfollow.xyz/logo.png" alt="EFP logo" />
+  <a href="https://efp.app" target="_blank" rel="noopener noreferrer">
+    <img width="275" src="https://docs.efp.app/logo.png" alt="EFP logo" />
   </a>
 </p>
 <br />
 <p align="center">
   <a href="https://pr.new/ethereumfollowprotocol/api"><img src="https://developer.stackblitz.com/img/start_pr_dark_small.svg" alt="Start new PR in StackBlitz Codeflow" /></a>
-  <a href="https://discord.ethfollow.xyz"><img src="https://img.shields.io/badge/chat-discord-blue?style=flat&logo=discord" alt="discord chat" /></a>
+  <a href="https://discord.efp.app"><img src="https://img.shields.io/badge/chat-discord-blue?style=flat&logo=discord" alt="discord chat" /></a>
   <a href="https://x.com/efp"><img src="https://img.shields.io/twitter/follow/efp?label=%40efp&style=social&link=https%3A%2F%2Fx.com%2Fefp" alt="x account" /></a>
 </p>
 

astro.config.ts

@@ -6,7 +6,7 @@ import { defineConfig } from 'astro/config'
 import spotlightjs from '@spotlightjs/astro'
 import starlightLinksValidator from 'starlight-links-validator'
 
-const SITE_URL = 'https://docs.ethfollow.xyz/'
+const SITE_URL = 'https://docs.efp.app/'
 
 // https://astro.build/config
 export default defineConfig({
@@ -33,7 +33,7 @@ export default defineConfig({
       },
       social: {
         github: 'https://github.com/ethereumfollowprotocol',
-        discord: 'https://discord.ethfollow.xyz',
+        discord: 'https://discord.efp.app',
         'x.com': 'https://x.com/efp'
       },
       locales: {
@@ -201,7 +201,7 @@ export default defineConfig({
         },
         {
           label: 'Forum',
-          link: 'https://forum.ethfollow.xyz/'
+          link: 'https://forum.efp.app/'
         },
         {
           label: 'Discord',
@@ -269,15 +269,15 @@ export default defineConfig({
           attrs: {
             name: 'twitter:domain',
             property: 'twitter:domain',
-            content: 'ethfollow.xyz'
+            content: 'efp.app'
           }
         },
         {
           tag: 'meta',
           attrs: {
             name: 'twitter:url',
             property: 'twitter:url',
-            content: 'https://ethfollow.xyz'
+            content: 'https://efp.app'
           }
         },
         {

package.json

@@ -51,7 +51,7 @@
     "typed-query-selector": "^2.11.0",
     "typescript": "^5.3.3"
   },
-  "homepage": "https://docs.ethfollow.xyz",
+  "homepage": "https://docs.efp.app",
   "sideEffects": false,
   "private": true
 }

src/content/docs/api/Token/metadata.mdx

@@ -4,9 +4,11 @@
 ---
 
 #### /token/metadata/\:token_id
-Get NFT metadata for a specified token id 
+
+Get NFT metadata for a specified token id
 
 #### Sample Query
+
 ```sh
 curl https://api.ethfollow.xyz/api/v1/token/metadata/4
 ```
@@ -17,7 +19,7 @@ curl https://api.ethfollow.xyz/api/v1/token/metadata/4
   "name": "EFP List #4",
   "description": "Ethereum Follow Protocol (EFP) is an onchain social graph protocol for Ethereum accounts.",
   "image": "https://api.ethfollow.xyz/api/v1/token/image/3",
-  "external_url": "https://ethfollow.xyz/3",
+  "external_url": "https://efp.app/3",
   "attributes": [
     {
       "trait_type": "User",
@@ -53,4 +55,4 @@ curl https://api.ethfollow.xyz/api/v1/token/metadata/4
     }
   ]
 }
-```
+```

src/content/docs/api/Users/ens.mdx

@@ -4,12 +4,15 @@
 ---
 
 ### /users/\:addressOrENS/ens
-Get the ENS data of a user by their address or ENS name. 
+
+Get the ENS data of a user by their address or ENS name.
 
 #### Path Parameters
+
 - `addressOrENS` (string): The address or ENS name of the account.
 
 #### Sample Query
+
 ```sh
 curl https://api.ethfollow.xyz/api/v1/users/brantly.eth/ens
 ```
@@ -32,9 +35,9 @@ curl https://api.ethfollow.xyz/api/v1/users/brantly.eth/ens
       "location": "USA",
       "name": "Brantly Millegan",
       "org.telegram": "brantlymillegan",
-      "url": "https://ethfollow.xyz/"
+      "url": "https://efp.app/"
     },
     "updated_at": "2024-09-18T03:40:58.807Z"
   }
 }
-```
+```

src/content/docs/api/intro.mdx

@@ -15,10 +15,10 @@ If you are a developer, you are free to use this endpoint to retrieve EFP data.
 
 ### Commonly used endpoints
 
-- [User Stats](https://docs.ethfollow.xyz/api/users/stats/): the follower and following counts of a particular user
-- [User Following](https://docs.ethfollow.xyz/api/users/following/): list of the accounts a particular user follows
-- [User Followers](https://docs.ethfollow.xyz/api/users/followers/): list of the accounts that follow a particular user
-- [User ENS data](https://docs.ethfollow.xyz/api/users/ens/): the ENS data for a particular user
+- [User Stats](https://docs.efp.app/api/users/stats/): the follower and following counts of a particular user
+- [User Following](https://docs.efp.app/api/users/following/): list of the accounts a particular user follows
+- [User Followers](https://docs.efp.app/api/users/followers/): list of the accounts that follow a particular user
+- [User ENS data](https://docs.efp.app/api/users/ens/): the ENS data for a particular user
 
 ### Self-hosting
 
@@ -29,20 +29,18 @@ You may also fork EFP's Indexer/API source code and deploy yourself.
 
 ### KV cache
 
-The API uses Cloudflare KV storage to cache some endpoint's responses.  When one of these 
-endpoints is called the cache is checked and if there is no record the data is fetched from 
-the database.  If a cached record is found it is returned immediately.  All cache records 
-are set to expire 5 minutes after they are created. 
+The API uses Cloudflare KV storage to cache some endpoint's responses. When one of these endpoints is called the cache is checked and if there is no record the data is fetched from the database. If a cached record is found it is returned immediately. All cache records are set to expire 5 minutes after they are created.
 
-The cached record for each of these endpoints can be refreshed by adding `cache=fresh` to the
-query params.  For example:
+The cached record for each of these endpoints can be refreshed by adding `cache=fresh` to the query params. For example:
 
 Get the cached record
+
 ```sh
 curl https://api.ethfollow.xyz/api/v1/lists/1/details
 ```
 
 Get latest data and reset the cached record
+
 ```sh
 curl https://api.ethfollow.xyz/api/v1/lists/1/details?cache=fresh
 ```

src/content/docs/design/glossary.mdx

@@ -3,79 +3,105 @@ title: Glossary
 ---
 
 **Account** (or **Ethereum account**)
->An EVM account. There are no "EFP accounts".
+
+> An EVM account. There are no "EFP accounts".
 
 **Account Metadata**
-> EFP provides an Account Metadata contract that allows users to set EFP-related metadata specific to their Ethereum account, such as identifying the Primary List for that Ethereum account. (see [Account Metadata](https://docs.ethfollow.xyz/design/account-metadata/))
+
+> EFP provides an Account Metadata contract that allows users to set EFP-related metadata specific to their Ethereum account, such as identifying the Primary List for that Ethereum account. (see [Account Metadata](https://docs.efp.app/design/account-metadata/))
 
 **Address** (or **Ethereum address**)
->An EVM address (e.g. 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045). There are no "EFP addresses".
+
+> An EVM address (e.g. 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045). There are no "EFP addresses".
 
 **Block**
->A standard tag that means neither the user nor the blocked account should see each other’s activity in a relevant app; lists with this tag are not included in Followers count, even if the list tags the account with other tags; if both “block” and “mute” tags are present, “block” takes precedence. (see [Tags](https://docs.ethfollow.xyz/design/tags/))
+
+> A standard tag that means neither the user nor the blocked account should see each other’s activity in a relevant app; lists with this tag are not included in Followers count, even if the list tags the account with other tags; if both “block” and “mute” tags are present, “block” takes precedence. (see [Tags](https://docs.efp.app/design/tags/))
 
 **EFP app**
->Web app that enables someone to create and manage a List on EFP. (see [EFP website](https://ethfollow.xyz/))
+
+> Web app that enables someone to create and manage a List on EFP. (see [EFP website](https://efp.app/))
 
 **Ethereum Follow Protocol** (or **EFP**)
->An onchain social graph protocol for Ethereum accounts. The protocol whose docs you are currently reading. (see [EFP website](https://ethfollow.xyz/))
+
+> An onchain social graph protocol for Ethereum accounts. The protocol whose docs you are currently reading. (see [EFP website](https://efp.app/))
 
 **Ethereum Name Service** (or **ENS**)
->A distributed, open, and extensible naming system based on the Ethereum blockchain. EFP is designed to complement ENS, and the EFP web app makes extensive use of ENS for names, avatar, and other profile data. (see [ENS website](https://ens.domains/))
+
+> A distributed, open, and extensible naming system based on the Ethereum blockchain. EFP is designed to complement ENS, and the EFP web app makes extensive use of ENS for names, avatar, and other profile data. (see [ENS website](https://ens.domains/))
 
 **Followers**
->The total number of Primary Lists that follow a particular Ethereum account, excluding lists that tag them with "block" or "mute".
+
+> The total number of Primary Lists that follow a particular Ethereum account, excluding lists that tag them with "block" or "mute".
 
 **Following**
->The total number of Ethereum accounts followed by a list, excluding accounts tagged with "block" or "mute".
+
+> The total number of Ethereum accounts followed by a list, excluding accounts tagged with "block" or "mute".
 
 **List**
->An NFT in the EFP List Registry and its accompanying List Storage Location data.
+
+> An NFT in the EFP List Registry and its accompanying List Storage Location data.
 
 **List Metadata**
->Metadata for a list, stored alongside List Records in a list's List Storage Location, that specifies the Ethereum accounts set for the roles Manager and User.
+
+> Metadata for a list, stored alongside List Records in a list's List Storage Location, that specifies the Ethereum accounts set for the roles Manager and User.
 
 **List Number**
->The token ID for the NFT that represents a list.
+
+> The token ID for the NFT that represents a list.
 
 **List Ops** (or **List Operation**)
->The same as a **List Record**; An operation performed on an EFP List, such as appending a list record (for following a particular Ethereum account, unfollowing, tagging, untagging).
+
+> The same as a **List Record**; An operation performed on an EFP List, such as appending a list record (for following a particular Ethereum account, unfollowing, tagging, untagging).
 
 **List Records**
->The set of list operations stored at your List Storage Location. (see [List Records](https://docs.ethfollow.xyz/design/list-records/))
+
+> The set of list operations stored at your List Storage Location. (see [List Records](https://docs.efp.app/design/list-records/))
 
 **List Registry**
->An Ethereum ERC-721 contract where the NFT represents ownership of a particular list.
+
+> An Ethereum ERC-721 contract where the NFT represents ownership of a particular list.
 
 **List Settings**
->A term used in the EFP app that refers to a variety of settings for a list, including: the list's List Storage Location; whether the list is set as a Primary List; the Ethereum accounts set for the roles Owner, Manager, and User.
+
+> A term used in the EFP app that refers to a variety of settings for a list, including: the list's List Storage Location; whether the list is set as a Primary List; the Ethereum accounts set for the roles Owner, Manager, and User.
 
 **List Storage Location**
->Where the records for a list are stored. (see [List Storage Location](https://docs.ethfollow.xyz/design/list-storage-location/))
+
+> Where the records for a list are stored. (see [List Storage Location](https://docs.efp.app/design/list-storage-location/))
 
 **Manager**
->The Ethereum account that can edit a list's records. By default when a list is created, all three roles (Owner, Manager, and User) are set as the Ethereum account that created the list. Typically, all three roles remain the same account, but they can be changed to be different. (see [Roles](https://docs.ethfollow.xyz/design/roles/))
+
+> The Ethereum account that can edit a list's records. By default when a list is created, all three roles (Owner, Manager, and User) are set as the Ethereum account that created the list. Typically, all three roles remain the same account, but they can be changed to be different. (see [Roles](https://docs.efp.app/design/roles/))
 
 **Mute**
-> A standard tag that means the user shouldn’t see the muted account’s activity in a relevant app, but the muted account might still be able to see the user’s activity; lists with this tag are not included in Followers count, even if the list tags the account with other tags; if both “block” and “mute” tags are present, “block” takes precedence. (see [Tags](https://docs.ethfollow.xyz/design/tags/))
+
+> A standard tag that means the user shouldn’t see the muted account’s activity in a relevant app, but the muted account might still be able to see the user’s activity; lists with this tag are not included in Followers count, even if the list tags the account with other tags; if both “block” and “mute” tags are present, “block” takes precedence. (see [Tags](https://docs.efp.app/design/tags/))
 
 **Mutuals**
->Ethereum accounts that an Ethereum account follows who follow them back.
+
+> Ethereum accounts that an Ethereum account follows who follow them back.
 
 **Owner**
->The Ethereum account that ultimately controls a List. By default when a list is created, all three roles (Owner, Manager, and User) are set as the Ethereum account that created the list. Typically, all three roles remain the same account, but they can be changed to be different. (see [Roles](https://docs.ethfollow.xyz/design/roles/))
+
+> The Ethereum account that ultimately controls a List. By default when a list is created, all three roles (Owner, Manager, and User) are set as the Ethereum account that created the list. Typically, all three roles remain the same account, but they can be changed to be different. (see [Roles](https://docs.efp.app/design/roles/))
 
 **Primary List**
->The one list an Ethereum account has confirmed to represent who they follow. While an Ethereum account may have roles in more than one list, an Ethereum account can only have one Primary List. Only Primary Lists count as Followers. (see [Account Metadata](https://docs.ethfollow.xyz/design/account-metadata/))
+
+> The one list an Ethereum account has confirmed to represent who they follow. While an Ethereum account may have roles in more than one list, an Ethereum account can only have one Primary List. Only Primary Lists count as Followers. (see [Account Metadata](https://docs.efp.app/design/account-metadata/))
 
 **Social Graph**
->The sum total of relationships between Ethereum accounts held in EFP, counting only Primary Lists. Any list that is not set as a Primary List is not included.
+
+> The sum total of relationships between Ethereum accounts held in EFP, counting only Primary Lists. Any list that is not set as a Primary List is not included.
 
 **Tag**
->A Tag is a string associated with a List Record in an EFP list. Tags only count for an account if that account is also followed by the user, otherwise they're not counted. List Records can have zero or more tags. A few tags are standardized with specified semantics. Users may also set custom tags. (see [Tags](https://docs.ethfollow.xyz/design/tags/))
+
+> A Tag is a string associated with a List Record in an EFP list. Tags only count for an account if that account is also followed by the user, otherwise they're not counted. List Records can have zero or more tags. A few tags are standardized with specified semantics. Users may also set custom tags. (see [Tags](https://docs.efp.app/design/tags/))
 
 **Top8** (or, **Top 8**)
->The tag "top8" means the account should appear in the user's "Top 8" in UIs that support it. If a user has more than eight followed accounts with the "top8" tag, then only show the eight most recent should be included in a "Top 8" displayed in a UI. (see [Tags](https://docs.ethfollow.xyz/design/tags/))
+
+> The tag "top8" means the account should appear in the user's "Top 8" in UIs that support it. If a user has more than eight followed accounts with the "top8" tag, then only show the eight most recent should be included in a "Top 8" displayed in a UI. (see [Tags](https://docs.efp.app/design/tags/))
 
 **User**
->The Ethereum account for whom the list is intended; the Ethereum account that is following the Ethereum accounts in the list. By default when a list is created, all three roles (Owner, Manager, and User) are set as the Ethereum account that created the list. Typically, all three roles remain the same account, but they can be changed to be different. (see [Roles](https://docs.ethfollow.xyz/design/roles/))
+
+> The Ethereum account for whom the list is intended; the Ethereum account that is following the Ethereum accounts in the list. By default when a list is created, all three roles (Owner, Manager, and User) are set as the Ethereum account that created the list. Typically, all three roles remain the same account, but they can be changed to be different. (see [Roles](https://docs.efp.app/design/roles/))