fix(docs): fetch network into ASI network

pages/concepts.mdx

@@ -72,7 +72,7 @@ import { AgentsIcon, AgentverseIcon ,FetchNetwork, LedgerIcon} from "src/icons/m
     icon: FetchNetwork,
     data: [
       {
-        title: "Introducing the Fetch Network",
+        title: "Introducing the ASI Network",
         path: "/concepts/fetch-network/intro-fetch-network",
       },
       {

pages/concepts/_meta.json

@@ -5,5 +5,5 @@
   },
   "agent-services": { "title": "Agentverse", "timestamp": true },
   "ai-engine": { "title": "AI Engine", "timestamp": true },
-  "fetch-network": { "title": "Fetch Network", "timestamp": true }
+  "fetch-network": { "title": "ASI Network", "timestamp": true }
 }

pages/concepts/ai-engine/ai-engine-personalities.mdx

@@ -11,7 +11,7 @@ The [AI Engine ↗️](/concepts/ai-engine/ai-engine-intro) stands as the heart
     1. **User input**: the user provide instructions via [DeltaV ↗️](/concepts/ai-engine/deltav) which facilitates smooth interaction with the AI Engine.
     2. **Understanding the request**: the AI Engine employs LLMs to analyze the user's request, grasping the intent and identifying the necessary actions.
     3. **Function delegation**: based on the analysis, the AI Engine breaks down the user's request into executable functions.
-    4. **Agent coordination**: the AI Engine then orchestrates a network of agents registered on the Fetch Network to execute those functions, ultimately achieving the initial user's objective.
+    4. **Agent coordination**: the AI Engine then orchestrates a network of agents registered on the ASI Network to execute those functions, ultimately achieving the initial user's objective.
 
 AI Engine personalities are not primarily about user experience or preference. Instead, they represent different versions or iterations of the AI Engine itself, each with its own set of features and capabilities.
 

pages/concepts/fetch-network/_meta.json

@@ -1,6 +1,6 @@
 {
   "intro-fetch-network": {
-    "title": "Fetch Network Introduction",
+    "title": "ASI Network Introduction",
     "timestamp": true
   },
   "native-and-erc20-fet-tokens": {

pages/concepts/fetch-network/almanac.mdx

@@ -2,7 +2,7 @@ import { Callout } from 'nextra/components'
 
 # The Almanac
 
-The **Almanac** contract is a critical component within the Fetch.ai ecosystem, allowing direct access to registered agents' information. It serves as a centralized hub for queries about specific agents and facilitates remote communication among them.
+The **Almanac** contract is a critical component within the ASI ecosystem, allowing direct access to registered agents' information. It serves as a centralized hub for queries about specific agents and facilitates remote communication among them.
 
 Agents must register within the Almanac to enable remote interactions and be found via the [Agentverse Marketplace ↗️](/concepts/agent-services/agent-explorer). You can register your Agents on the Almanac by following this [guide ↗️](/guides/agents/register-in-almanac). You can also explore the [Communicating with other agents ↗️](/guides/agents/communicating-with-other-agents) guide to understand how Agents leverage the Almanac to communicate remotely.
 
@@ -24,7 +24,7 @@ Agents offer the flexibility of being designated as either public or private dur
 
 A [protocol ↗️](/references/uagents/uagents-protocols/agent-protocols), within the uAgents Framework, establish the rules and message structures governing AI Agent interactions. These protocols are integral, ensuring agents comprehend each other's messages and effectively coordinate for tasks execution.
 
-Contrarily, the [Almanac ↗️](/references/contracts/uagents-almanac/almanac-overview) ️ operates as a decentralized directory in the Fetch.ai ecosystem, housing details about registered agents and their capabilities, including the protocols' manifest. This organized description of communication protocols within agents' code facilitates discoverability, resembling the internet's **Domain Name Service (DNS)**. Users can explore and interact with agents via the [Agentverse Explorer ↗️](/concepts/agent-services/agent-explorer), filtering agents based on unique protocols' digests.
+Contrarily, the [Almanac ↗️](/references/contracts/uagents-almanac/almanac-overview) ️ operates as a decentralized directory in the ASI ecosystem, housing details about registered agents and their capabilities, including the protocols' manifest. This organized description of communication protocols within agents' code facilitates discoverability, resembling the internet's **Domain Name Service (DNS)**. Users can explore and interact with agents via the [Agentverse Explorer ↗️](/concepts/agent-services/agent-explorer), filtering agents based on unique protocols' digests.
 
     <Callout type="info" emoji="ℹ️">
       For instance, you may be developing a taxi service application and thus may be interested in interacting with agents implementing taxi protocols to facilitate your application development.

pages/concepts/fetch-network/intro-fetch-network.mdx

@@ -1,12 +1,12 @@
-# The Fetch Network
+# The ASI Network
 
 ## Introduction
 
-The **Fetch Network** represents the foundation of the Fetch.ai Ecosystem as it enables the decentralized digital economy driven by [Agents ↗️](/guides/agents/getting-started/whats-an-agent), [AI Engine ↗️](/concepts/ai-engine/ai-engine-intro), [Agentverse ↗️](/concepts/agent-services/agentverse-intro) and [DeltaV ↗️](/concepts/ai-engine/deltav). The Network provides integration with Fetch blockchain technology and ensures security, transparency, and scalability of transactions, and enhanced trust across the overall Ecosystem.
+The **ASI Network** represents the foundation of the ASI Ecosystem as it enables the decentralized digital economy driven by [Agents ↗️](/guides/agents/getting-started/whats-an-agent), [AI Engine ↗️](/concepts/ai-engine/ai-engine-intro), [Agentverse ↗️](/concepts/agent-services/agentverse-intro) and [DeltaV ↗️](/concepts/ai-engine/deltav). The Network provides integration with blockchain technology and ensures security, transparency, and scalability of transactions, and enhanced trust across the overall Ecosystem.
 
 ### The Almanac Contract
 
-The [Almanac Contract ↗️](/concepts/fetch-network/almanac) is an important component within the Fetch Network. It connects together Agents, the Agentverse, and the AI Engine by working as decentralized registry and allowing for agents discoverability and coordination. Whenever agents are registered in the Almanac, they become accessible across the entire Fetch Ecosystem, allowing the AI Engine to dynamically locate and engage with them based on users' or agents' requests and queries. This ensures the accurate and reliable execution of objectives, as the Almanac supports the AI Engine in identifying and deploying the most appropriate agents for any given function being requested for execution, amongst all those registered agents in the Agentverse and Fetch Network.
+The [Almanac Contract ↗️](/concepts/fetch-network/almanac) is an important component within the ASI Network. It connects together Agents, the Agentverse, and the AI Engine by working as decentralized registry and allowing for agents discoverability and coordination. Whenever agents are registered in the Almanac, they become accessible across the entire ASI Ecosystem, allowing the AI Engine to dynamically locate and engage with them based on users' or agents' requests and queries. This ensures the accurate and reliable execution of objectives, as the Almanac supports the AI Engine in identifying and deploying the most appropriate agents for any given function being requested for execution, amongst all those registered agents in the Agentverse and ASI Network.
 
 The Almanac facilitates remote communication between agents but also provides a layer of trust and verification, ensuring that accurate and up-to-date information is available at all times for everybody. By maintaining an organized directory of agents and their functions, the Almanac empowers the AI Engine to coordinate complex multi-agent workflows efficiently.
 
@@ -16,18 +16,18 @@ The [Fetch Name Service (FNS) ↗️](/guides/agents/advanced/name-service) is a
 
 ### Fetch Ledger
 
-The [Fetch Ledger ↗️](/concepts/fetch-network/ledger/intro) is an additional central component of the Fetch Network. It provides a secure, decentralized, and transparent record of all transactions and data exchanges that take place within the Fetch Ecosystem itself. The Ledger uses the [FET token ↗️](/concepts/fetch-network/native-and-erc20-fet-tokens) to facilitate transactions, agent interactions, and smart contracts execution, but it also to ensure that the integrity and efficiency of the Network is maintained.
+The [Fetch Ledger ↗️](/concepts/fetch-network/ledger/intro) is an additional central component of the ASI Network. It provides a secure, decentralized, and transparent record of all transactions and data exchanges that take place within the ASI Ecosystem itself. The Ledger uses the [FET token ↗️](/concepts/fetch-network/native-and-erc20-fet-tokens) to facilitate transactions, agent interactions, and smart contracts execution, but it also to ensure that the integrity and efficiency of the Network is maintained.
 
 ### Jenesis
 
-An additional tool is [Jenesis ↗️](/guides/fetch-network/jenesis/getting-started); it simplifies the development and deployment of smart contracts and decentralized applications (i.e., dApps) on the Fetch Network and other CosmWasm-enabled platforms. Jenesis offers a streamlined environment for developers that reduces the complexity of building blockchain-based solutions and accelerates the deployment of decentralized services and applications.
+An additional tool is [Jenesis ↗️](/guides/fetch-network/jenesis/getting-started); it simplifies the development and deployment of smart contracts and decentralized applications (i.e., dApps) on the ASI Network and other CosmWasm-enabled platforms. Jenesis offers a streamlined environment for developers that reduces the complexity of building blockchain-based solutions and accelerates the deployment of decentralized services and applications.
 
 ### CosmPy
 
-As a complementary tool to the above ones, [CosmPy ↗️](/guides/fetch-network/cosmpy/install) is a Python-based library that facilitates interactions with Cosmos SDK-based blockchains, including the Fetch Network. CosmPy provides developers with a straightforward way to manage blockchain transactions, write and test smart contracts but also interact with agents; all within the familiar Python environment.
+As a complementary tool to the above ones, [CosmPy ↗️](/guides/fetch-network/cosmpy/install) is a Python-based library that facilitates interactions with Cosmos SDK-based blockchains, including the ASI Network. CosmPy provides developers with a straightforward way to manage blockchain transactions, write and test smart contracts but also interact with agents; all within the familiar Python environment.
 
 ### Conclusions
 
-These components together constitute the backbone structure of the Fetch Network. These tools are essential in enabling a decentralized economy of autonomous Agents and AI-driven Agent Functions. By leveraging the Fetch Ledger, Almanac Contract, FNS, Jenesis, and CosmPy, the Fetch Network focuses on creating an environment where agents can autonomously manage tasks, interact with each other, and create value in a secure and scalable way.
+These components together constitute the backbone structure of the ASI Network. These tools are essential in enabling a decentralized economy of autonomous Agents and AI-driven Agent Functions. By leveraging the Fetch Ledger, Almanac Contract, FNS, Jenesis, and CosmPy, the ASI Network focuses on creating an environment where agents can autonomously manage tasks, interact with each other, and create value in a secure and scalable way.
 
-The FET token empowers the Fetch Ecosystem, providing the economic incentive and governance framework necessary for the sustainability and evolution of the Network itself. The token acts both as the medium of exchange and the incentive structure for participants, while supporting the Network's governance and staking mechanisms.
+The FET token empowers the ASI Ecosystem, providing the economic incentive and governance framework necessary for the sustainability and evolution of the Network itself. The token acts both as the medium of exchange and the incentive structure for participants, while supporting the Network's governance and staking mechanisms.

pages/concepts/fetch-network/ledger/intro.mdx

@@ -8,15 +8,15 @@ A **ledger** refers to a decentralized and distributed digital book that records
 
 Within this context, the **Fetch Ledger** developed by Fetch.ai constitutes the underlying infrastructure for various decentralized applications and contracts. It employs a consensus mechanism where [validators ↗️](/concepts/fetch-network/ledger/validators) are responsible for validating transactions and creating new blocks in the [blockchain ↗️](/concepts/fetch-network/ledger/validators#overview-blockchains-consensus-and-validators). The ledger utilizes Fetch native cryptocurrency, FET, which is used for various activities within the network, including transaction fees and staking. The ledger also supports features such as [multi-signature keys ↗️](/guides/fetch-network/ledger/cli/multisig-keys), allowing users to control [keys ↗️](/guides/fetch-network/ledger/cli/keys) in different configurations.
 
-The fetchhub [mainnet ↗️](/concepts/fetch-network/ledger/validators#test-network-testnet-vs-main-network-mainnet) forms the core of the Fetch.ai ecosystem. In here, you will find all information to setup your client and connect on the network.
+The fetchhub [mainnet ↗️](/concepts/fetch-network/ledger/validators#test-network-testnet-vs-main-network-mainnet) forms the core of the ASI ecosystem. In here, you will find all information to setup your client and connect on the network.
 
     <Callout type="info" emoji="ℹ️">
       Head over to our [guides ↗️](/guides) section and get yourself started with the ledger [installation ↗️](/guides/fetch-network/ledger/installation) and different executable operations. Also, you can checkout our [GitHub repository ↗️](https://github.com/fetchai/fetchd) to further enhance your understanding of these topics.
 
       You can also visit the [references ↗️](/references) section for further information on ledger related topics, including [active networks ↗️](/references/ledger/active-networks) specifications, [ledger versions ↗️](/references/ledger/versions), and the [Command Line Interface (CLI) ↗️](/guides/fetch-network/ledger/cli/intro) section for guidance on how to install and configure the `fetchd` client and perform different operations within the ledger using the CLI.
     </Callout>
 
-This documentation covers the things you need to know in order to prepare yourself and start developing on the Fetch network.
+This documentation covers the things you need to know in order to prepare yourself and start developing on the ASI network.
 
 ## Test networks
 

pages/concepts/fetch-network/ledger/validators.mdx

@@ -54,7 +54,7 @@ We can distinguish between:
 
 ## Set up a validator node
 
-If you are willing to set up a validator node on the Fetch network, visit our dedicated [guide ↗️](/guides/fetch-network/ledger/setup-validator-node).
+If you are willing to set up a validator node on the ASI network, visit our dedicated [guide ↗️](/guides/fetch-network/ledger/setup-validator-node).
 
 ### Hardware requirements
 

pages/concepts/fetch-network/native-and-erc20-fet-tokens.mdx

@@ -1,10 +1,10 @@
 ## Native and ERC-20 FET tokens
 
-The Fetch.ai (FET) token is the utility token and the key medium of exchange on the Fetch.ai network. FET can be used to pay for services in the Fetch ecosystem and network transaction fees. Users can also choose to stake FET to participate in securing the network via its Proof-of-Stake (PoS) consensus mechanism and earn rewards in return for contributing to [validator ↗️](/concepts/fetch-network/ledger/validators) nodes.
+The Fetch.ai (FET) token is the utility token and the key medium of exchange on the Fetch.ai network. FET can be used to pay for services in the ASI ecosystem and network transaction fees. Users can also choose to stake FET to participate in securing the network via its Proof-of-Stake (PoS) consensus mechanism and earn rewards in return for contributing to [validator ↗️](/concepts/fetch-network/ledger/validators) nodes.
 
-The Fetch.ai team initially developed the FET utility token on an [ERC-20 contract ↗️](https://etherscan.io/token/0xaea46A60368A7bD060eec7DF8CBa43b7EF41Ad85) on the Ethereum network while finishing the work on the Fetch.ai native main network (Main-net). This helped developers across the world get their hands on the FET tokens earlier and kickstart the process of developing innovative solutions within the Fetch.ai ecosystem. FET, as an ERC-20 token on the Ethereum contract has never been Fetch.ai's end game because the Ethereum chain does not offer the degree of scalability needed by the kinds of applications the Fetch.ai ecosystem aims for.
+The Fetch.ai team initially developed the FET utility token on an [ERC-20 contract ↗️](https://etherscan.io/token/0xaea46A60368A7bD060eec7DF8CBa43b7EF41Ad85) on the Ethereum network while finishing the work on the Fetch.ai native main network (Main-net). This helped developers across the world get their hands on the FET tokens earlier and kickstart the process of developing innovative solutions within the ASI ecosystem. FET, as an ERC-20 token on the Ethereum contract has never been Fetch.ai's end game because the Ethereum chain does not offer the degree of scalability needed by the kinds of applications the ASI ecosystem aims for.
 
-With the launch of the Fetch.ai Mainnet, the native FET became available. This meant that users operating on the Fetch.ai network no longer needed to hold any token (e.g. ETH or BTC) associated with any other network. It is only the native FET token that fuels the Fetch.ai ecosystem and its applications.
+With the launch of the Fetch.ai Mainnet, the native FET became available. This meant that users operating on the Fetch.ai network no longer needed to hold any token (e.g. ETH or BTC) associated with any other network. It is only the native FET token that fuels the ASI ecosystem and its applications.
 
 ERC-20 FET tokens are still in circulation and currently co-exist with native FET tokens and can be [transferred from one to the other ↗️](/guides/fetch-network/how-to-convert-fet-to-and-from-erc20) easily on the Fetch.ai network. All of the ERC-20 FET tokens will ultimately become native FET tokens, but in the foreseeable future both will live side by side. FET tokens can be purchased from different [centralized or decentralized exchanges ↗️](https://coinmarketcap.com/currencies/fetch/#Markets).