diff --git a/pages/concepts.mdx b/pages/concepts.mdx index 23c56788d..de8ce34e4 100644 --- a/pages/concepts.mdx +++ b/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", }, { diff --git a/pages/concepts/_meta.json b/pages/concepts/_meta.json index 65b7dfe58..98d675932 100644 --- a/pages/concepts/_meta.json +++ b/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 } } diff --git a/pages/concepts/ai-engine/ai-engine-personalities.mdx b/pages/concepts/ai-engine/ai-engine-personalities.mdx index fb76601bb..3a228ed39 100644 --- a/pages/concepts/ai-engine/ai-engine-personalities.mdx +++ b/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. diff --git a/pages/concepts/fetch-network/_meta.json b/pages/concepts/fetch-network/_meta.json index 25e555241..4a9656a0b 100644 --- a/pages/concepts/fetch-network/_meta.json +++ b/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": { diff --git a/pages/concepts/fetch-network/almanac.mdx b/pages/concepts/fetch-network/almanac.mdx index c08345c9a..aeae52e8b 100644 --- a/pages/concepts/fetch-network/almanac.mdx +++ b/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. 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. diff --git a/pages/concepts/fetch-network/intro-fetch-network.mdx b/pages/concepts/fetch-network/intro-fetch-network.mdx index 3f69d2ced..3c2c70387 100644 --- a/pages/concepts/fetch-network/intro-fetch-network.mdx +++ b/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. \ No newline at end of file +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. \ No newline at end of file diff --git a/pages/concepts/fetch-network/ledger/intro.mdx b/pages/concepts/fetch-network/ledger/intro.mdx index 7c9b4b715..144b3584a 100644 --- a/pages/concepts/fetch-network/ledger/intro.mdx +++ b/pages/concepts/fetch-network/ledger/intro.mdx @@ -8,7 +8,7 @@ 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. 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. @@ -16,7 +16,7 @@ The fetchhub [mainnet ↗️](/concepts/fetch-network/ledger/validators#test-net 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. -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 diff --git a/pages/concepts/fetch-network/ledger/validators.mdx b/pages/concepts/fetch-network/ledger/validators.mdx index 268d342cb..168947ae2 100644 --- a/pages/concepts/fetch-network/ledger/validators.mdx +++ b/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 diff --git a/pages/concepts/fetch-network/native-and-erc20-fet-tokens.mdx b/pages/concepts/fetch-network/native-and-erc20-fet-tokens.mdx index 6bbdd68b3..72e35bfa4 100644 --- a/pages/concepts/fetch-network/native-and-erc20-fet-tokens.mdx +++ b/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). diff --git a/pages/concepts/introducing-fetchai.mdx b/pages/concepts/introducing-fetchai.mdx index 9b2b41f72..c2ac3e2dc 100644 --- a/pages/concepts/introducing-fetchai.mdx +++ b/pages/concepts/introducing-fetchai.mdx @@ -8,19 +8,19 @@ import DarkDecentralisedNetwork from 'src/images/concepts/ai-agents/Dark_decentr # Introducing Fetch.ai: pioneering an AI powered decentralized digital economy -**Fetch.ai** is developing a platform to enable the development of an AI empowered decentralized digital economy. _Agents_ are programs that can make choices on their own for individuals, companies, and devices. Agents are the actors, and the heart of Fetch.ai ecosystem. +**Fetch.ai** is developing a platform to enable the development of an AI empowered decentralized digital economy. _Agents_ are programs that can make choices on their own for individuals, companies, and devices. Agents are the actors, and the heart of the ASI ecosystem. Agents are flexible problem solvers, capable of not just completing tasks but also tackling difficult issues across several domains. Agents have the adaptability to handle different activities inside the decentralized economy, whether it's improving supply chain logistics, maintaining solid record-keeping systems, executing computational tasks, or enabling buying and selling interactions. They might even book a hotel room for you. -We couple agents with AI-Engine, the AI system that understands human input and turns that into actionable events empowered by agents in the network. AI-engine is an intelligence system which create dynamic agent workflows. Agentverse offers cheap agent hosting and the Fetch Network provides an open layer of trust. +We couple agents with AI-Engine, the AI system that understands human input and turns that into actionable events empowered by agents in the network. AI-engine is an intelligence system which create dynamic agent workflows. Agentverse offers cheap agent hosting and the ASI Network provides an open layer of trust. These services make up the core architecture of Fetch.ai ### The architecture -**Agents**, **Agentverse**, **AI Engine**, and **Fetch network**. +**Agents**, **Agentverse**, **AI Engine**, and **ASI network**. -Agents register to Almanac so that they can be discovered in the network by other agents. Agents may register their functions to Agentverse so that AI-Engine can index these agents so that they can be called by AI-Engine. The Fetch network offers a layer of truth and trust by inherently being open. +Agents register to Almanac so that they can be discovered in the network by other agents. Agents may register their functions to Agentverse so that AI-Engine can index these agents so that they can be called by AI-Engine. The ASI network offers a layer of truth and trust by inherently being open. Check out the official [uAgents Python package ↗️](https://pypi.org/project/uagents/) and start developing your ideas using this library! @@ -147,7 +147,7 @@ Check out the [uAgents Framework installation guide ↗️](/guides/agents/getti ### Core concepts #### Addresses -Agents are identified by **two types of addresses**, serving as identifiers for each agent within the Fetch.ai Ecosystem: +Agents are identified by **two types of addresses**, serving as identifiers for each agent within the ASI Ecosystem: 1. **uAgent Address**: the primary agent identifier; it allows it to interact with other agents, exchange messages, and participate in decentralized network activities @@ -191,7 +191,7 @@ The exchange protocol uses a standardized `HTTP 1.1 POST /submit` endpoint for m #### Almanac contract, registering, searching and discovery -The [Almanac ↗️](/references/contracts/uagents-almanac/almanac-overview) contract is an important component in Fetch.ai Ecosystem. It operates as a blockchain-based repository where agents register, exchange information and establish communication. Registration in the Almanac is mandatory so that agents can participate in remote interactions and become discoverable through the [Agentverse Explorer ↗️](/concepts/agent-services/agent-explorer). +The [Almanac ↗️](/references/contracts/uagents-almanac/almanac-overview) contract is an important component in ASI Ecosystem. It operates as a blockchain-based repository where agents register, exchange information and establish communication. Registration in the Almanac is mandatory so that agents can participate in remote interactions and become discoverable through the [Agentverse Explorer ↗️](/concepts/agent-services/agent-explorer). Agents keep their registrations up-to-date within certain block limits to ensure the accuracy and relevance of their data. Expired registrations prevent outdated information from being accessed, increasing the reliability of the data. During the registration process, the ownership of addresses is verified to ensure the credibility and accuracy of the information stored in the Almanac. @@ -328,7 +328,7 @@ This time, the output will be: ### Printing agent's addresses -Sometimes, we just need to see what a value looks like. We can quickly do so in Python by using the `print()` in-built function. As we have mentioned earlier, every AI Agent is identified by two addresses within the uAgents Framework: **uAgent** and **Fetch Network** addresses. We have showed above how to check for an uAgent address using the `agent.address` method of the `Context` class. Let's now print them in the console to see their differences using the `print()` function: +Sometimes, we just need to see what a value looks like. We can quickly do so in Python by using the `print()` in-built function. As we have mentioned earlier, every AI Agent is identified by two addresses within the uAgents Framework: **uAgent** and **ASI Network** addresses. We have showed above how to check for an uAgent address using the `agent.address` method of the `Context` class. Let's now print them in the console to see their differences using the `print()` function: @@ -361,7 +361,7 @@ The output of the above would look similar to: ``` uAgent address: agent1qww3ju3h6kfcuqf54gkghvt2pqe8qp97a7nzm2vp8plfxflc0epzcjsv79t - Fetch network address: fetch1454hu0n9eszzg8p7mvan3ep7484jxl5mkf9phg + ASI network address: fetch1454hu0n9eszzg8p7mvan3ep7484jxl5mkf9phg ``` diff --git a/pages/guides/agents/advanced/register-in-almanac.mdx b/pages/guides/agents/advanced/register-in-almanac.mdx index f1f4a3c91..fbab453ca 100644 --- a/pages/guides/agents/advanced/register-in-almanac.mdx +++ b/pages/guides/agents/advanced/register-in-almanac.mdx @@ -45,7 +45,7 @@ Make sure you have read the following resources before going on with this guide: -2. Open your terminal and `registration.py` file in an editor of your choice. Let's start by importing the `Agent` class from the `uagents` library to create our Agent. This function will check if you have enough tokens to register in the Almanac contract, if not it will add testnet tokens to your `Fetch Network address`. Then, create an agent, `alice`, you need to provide the `name`, `seed`, `port` and `endpoint` parameters to correctly run it! The code will look similar to the following: +2. Open your terminal and `registration.py` file in an editor of your choice. Let's start by importing the `Agent` class from the `uagents` library to create our Agent. This function will check if you have enough tokens to register in the Almanac contract, if not it will add testnet tokens to your `ASI Network address`. Then, create an agent, `alice`, you need to provide the `name`, `seed`, `port` and `endpoint` parameters to correctly run it! The code will look similar to the following: - If you see a message saying **"We couldn't find this agent address on Fetch Network"** you will need to wait for some time (around 5 minutes) until the protocols are uploaded successfully on the Fetch Network and your agent is retrievable. + If you see a message saying **"We couldn't find this agent address on ASI Network"** you will need to wait for some time (around 5 minutes) until the protocols are uploaded successfully on the ASI Network and your agent is retrievable. Once your agent is retrieved correctly, you will see a box depicting it within the **My Agents** tab. Click on it and head over to the **Deploy** tab and click on **+ New Function**. Here, you can now provide the needed details for your Agent Function in the dedicated fields. Remember to provide detailed descriptions for what your **Agent Function** does and the **Fields** for data Models expected. understanding of Functions fields descriptions. diff --git a/pages/guides/agents/getting-started/fet-token-for-agents.mdx b/pages/guides/agents/getting-started/fet-token-for-agents.mdx index feb1ae2dc..fab0b7d24 100644 --- a/pages/guides/agents/getting-started/fet-token-for-agents.mdx +++ b/pages/guides/agents/getting-started/fet-token-for-agents.mdx @@ -31,7 +31,7 @@ For long-term storage goals, you can enhance security by integrating your ASI Wa You can download and use the uAgents library to create autonomous Agents capable of interacting with other Agents in a decentralized environment. Check out this guide [here ↗️](/guides/agents/getting-started/installing-uagent) to get started with Agents development. -In order to get your Agent up and running within the Fetch.ai ecosystem, you will need to retrieve the Agent's address and fund it with FET tokens to make it correctly register within the network. +In order to get your Agent up and running within the ASI Ecosystem, you will need to retrieve the Agent's address and fund it with FET tokens to make it correctly register within the network. When creating your account, it is crucial to securely store your [seed phrase ↗️](/guides/agents/getting-started/seedphrase). The seed phrase is essential for accessing your Agent's identity and controlling any funds it holds. Treat it with the highest level of security to prevent unauthorized access! @@ -84,7 +84,7 @@ should be as simple as withdrawing native FET, by selecting the Fetch.ai Mainnet exchanges do not support Native FET, and you will need to use the [token bridge](https://token-bridge.fetch.ai/), luckily we have [a guide for that too](/guides/fetch-network/how-to-convert-fet-to-and-from-erc20) -Check out the following resources for more information on Agents and how these integrate within the Fetch Ecosystem and perform operations using FET tokens: +Check out the following resources for more information on Agents and how these integrate within the ASI Ecosystem and perform operations using FET tokens: - [Agents - uAgents Framework ↗️](/guides/agents/getting-started/whats-an-agent) - [The Agentverse ↗️](/concepts/agent-services/agentverse-intro) diff --git a/pages/guides/agents/getting-started/getting-uagent-address.mdx b/pages/guides/agents/getting-started/getting-uagent-address.mdx index 7f8f842bb..568407aab 100644 --- a/pages/guides/agents/getting-started/getting-uagent-address.mdx +++ b/pages/guides/agents/getting-started/getting-uagent-address.mdx @@ -4,13 +4,13 @@ import { CodeGroup, CodeSegment, DocsCode, GithubCodeSegment } from "../../../.. ## Introduction -Agents within the Fetch Ecosystem are characterized by different addresses. These can allow the agent to perform different actions, including sending messages or interacting with the [Almanac contract ↗️](/references/contracts/uagents-almanac/almanac-overview). +Agents within the ASI Ecosystem are characterized by different addresses. These can allow the agent to perform different actions, including sending messages or interacting with the [Almanac contract ↗️](/references/contracts/uagents-almanac/almanac-overview). It is possible to distinguish between two different types of addresses: - - `uAgent address`: this address identifies the agent within the Fetch Network. It's similar to a username within a chat platform, allowing other agents to discover and communicate with that specific agent by querying that agent's information from the Almanac contract. + - `uAgent address`: this address identifies the agent within the ASI Network. It's similar to a username within a chat platform, allowing other agents to discover and communicate with that specific agent by querying that agent's information from the Almanac contract. - - `Fetch network address`: this address is linked to the agent's wallet on the Fetch.ai network. It is essential to perform multiple functionalities like holding cryptocurrency, interacting with the [Fetch Ledger ↗️](/concepts/fetch-network/ledger/intro) and performing secure transactions. This address is needed to register an agent to the [Almanac ↗️](/concepts/fetch-network/almanac) contract. Note, you must ensure the agents has enough funds available to perform operations in the Fetch Network, however this is all done automatically and no funds are currently required. + - `ASI network address`: this address is linked to the agent's wallet on the ASI network. It is essential to perform multiple functionalities like holding cryptocurrency, interacting with the [Fetch Ledger ↗️](/concepts/fetch-network/ledger/intro) and performing secure transactions. This address is needed to register an agent to the [Almanac ↗️](/concepts/fetch-network/almanac) contract. Note, you must ensure the agents has enough funds available to perform operations in the ASI Network, however this is all done automatically and no funds are currently required. If you want to retrieve the address of an agent, you can either use the `print()` function and specify which of the above addresses you wish to print out, or by calling the `.address()` or `.wallet.address()` methods using the `agent` object to retrieve specific information. @@ -98,9 +98,9 @@ The output would be as follows: INFO: [alice]: Starting server on http://0.0.0.0:8000 (Press CTRL+C to quit) ``` -## Print Fetch network address +## Print ASI network address -You can print the `Fetch network address` related to your agent in the following way: +You can print the `ASI network address` related to your agent in the following way: 1. Let's create a Python script, and name it: @@ -124,7 +124,7 @@ You can print the `Fetch network address` related to your agent in the following -2. As before, we first need to import the `Agent` class from the `uagents` library to create an Agent, `alice`. Then, using the `print()` function, we will print the related `Fetch Network address`: +2. As before, we first need to import the `Agent` class from the `uagents` library to create an Agent, `alice`. Then, using the `print()` function, we will print the related `ASI Network address`: - Local Agents can communicate and interact with other Agents and Functions connected to the Agentverse and Fetch Network through a Mailbox. For more information on Mailbox and how to connect local Agents and their Functions to the Agentverse, have a look at these guides: + Local Agents can communicate and interact with other Agents and Functions connected to the Agentverse and ASI Network through a Mailbox. For more information on Mailbox and how to connect local Agents and their Functions to the Agentverse, have a look at these guides: - [Agent Mailbox ↗️](/guides/agents/intermediate/mailbox). - [Hosted, Local, and Mailbox Agents ↗️](/guides/agents/intermediate/agent-types). diff --git a/pages/guides/agents/intermediate/options-for-running-local-agents.mdx b/pages/guides/agents/intermediate/options-for-running-local-agents.mdx index d75c39471..7c4f742a8 100644 --- a/pages/guides/agents/intermediate/options-for-running-local-agents.mdx +++ b/pages/guides/agents/intermediate/options-for-running-local-agents.mdx @@ -124,7 +124,7 @@ We can now run our Agent with the following command: `python agent_endpoint.py` ## Run a local Agent using a Mailbox -Through the **Agentverse** you can set up [Mailboxes ↗️](/guides/agents/intermediate/mailbox) for your local Agents, allowing them to communicate with other Agents registered on the Fetch Network without the need to be constantly online and without requiring your constant presence to operate. +Through the **Agentverse** you can set up [Mailboxes ↗️](/guides/agents/intermediate/mailbox) for your local Agents, allowing them to communicate with other Agents registered on the ASI Network without the need to be constantly online and without requiring your constant presence to operate. ### Local Agent setup diff --git a/pages/guides/agents/quickstart.mdx b/pages/guides/agents/quickstart.mdx index 012f0bf31..5cc2fb147 100644 --- a/pages/guides/agents/quickstart.mdx +++ b/pages/guides/agents/quickstart.mdx @@ -323,6 +323,6 @@ Open two terminal windows, each one for an Agent, and then run the scripts separ ## Reach out to the Team! -Excellent! You are now ready to start exploring the concepts and resources available to start developing your agents on the Fetch Network! if you're keen to skip the more code focused guides, the best next steps would be exploring how [Agents communicate with other Agents ↗️](/guides/agents/intermediate/communicating-with-other-agents). +Excellent! You are now ready to start exploring the concepts and resources available to start developing your agents on the ASI Network! if you're keen to skip the more code focused guides, the best next steps would be exploring how [Agents communicate with other Agents ↗️](/guides/agents/intermediate/communicating-with-other-agents). Note that our Team is available on [Discord ↗️](https://discord.gg/fetchai) for any additional inquiry. diff --git a/pages/guides/agentverse/agentverse-functions/registering-agent-coin-toss.mdx b/pages/guides/agentverse/agentverse-functions/registering-agent-coin-toss.mdx index e2e910611..ed52a2e5a 100644 --- a/pages/guides/agentverse/agentverse-functions/registering-agent-coin-toss.mdx +++ b/pages/guides/agentverse/agentverse-functions/registering-agent-coin-toss.mdx @@ -9,7 +9,7 @@ import { CodeGroup, CodeSegment, DocsCode, GithubCodeSegment } from "../../../.. In the [Agentverse Functions: register your Functions on the Agentverse! ↗️](/guides/agentverse/registering-agent-services) guide, you have gotten familiar with the creation of an agent that can be registered as a Function and then be used in [DeltaV ↗️](/concepts/ai-engine/deltav). - Check out the [Functions ↗️](/guides/agents/intermediate/agent-functions) guide for additional information needed for Agent Functions and their registration on the Agentverse and Fetch network. + Check out the [Functions ↗️](/guides/agents/intermediate/agent-functions) guide for additional information needed for Agent Functions and their registration on the Agentverse and ASI network. diff --git a/pages/guides/fetch-network/asi-wallet/companion-app.mdx b/pages/guides/fetch-network/asi-wallet/companion-app.mdx index f38d119c0..a939a5fa9 100644 --- a/pages/guides/fetch-network/asi-wallet/companion-app.mdx +++ b/pages/guides/fetch-network/asi-wallet/companion-app.mdx @@ -2,7 +2,7 @@ ## Introduction -Within the Fetch Network, an essential tool is the **Companion App** which works similarly to any block explorer, thus offering the opportunity for users to navigate and analyze the Fetch.ai blockchain network data and related information. +Within the ASI Network, an essential tool is the **Companion App** which works similarly to any block explorer, thus offering the opportunity for users to navigate and analyze the Fetch.ai blockchain network data and related information. You can access the Companion App [here ↗️](https://companion.fetch.ai/fetchhub-4/blocks). diff --git a/pages/guides/fetch-network/intro-fet-token.mdx b/pages/guides/fetch-network/intro-fet-token.mdx index df568499b..97c8c12aa 100644 --- a/pages/guides/fetch-network/intro-fet-token.mdx +++ b/pages/guides/fetch-network/intro-fet-token.mdx @@ -42,7 +42,7 @@ For long-term storage goals, you can enhance security by integrating your ASI Wa You can download and use the uAgents library to create autonomous Agents capable of interacting with other Agents in a decentralized environment. Check out this guide [here ↗️](/guides/agents/getting-started/installing-uagent) to get started with Agents development. -In order to get your Agent up and running within the Fetch.ai ecosystem, you will need to retrieve the Agent's address and fund it with FET tokens to make it correctly register within the network. +In order to get your Agent up and running within the ASI ecosystem, you will need to retrieve the Agent's address and fund it with FET tokens to make it correctly register within the network. When creating your account, it is crucial to securely store your [seed phrase ↗️](/guides/agents/getting-started/seedphrase). The seed phrase is essential for accessing your Agent's identity and controlling any funds it holds. Treat it with the highest level of security to prevent unauthorized access! @@ -95,7 +95,7 @@ should be as simple as withdrawing native FET, by selecting the Fetch.ai Mainnet exchanges do not support Native FET, and you will need to use the [token bridge](https://token-bridge.fetch.ai/), luckily we have [a guide for that too](/guides/fetch-network/how-to-convert-fet-to-and-from-erc20) -Check out the following resources for more information on Agents and how these integrate within the Fetch Ecosystem and perform operations using FET tokens: +Check out the following resources for more information on Agents and how these integrate within the ASI Ecosystem and perform operations using FET tokens: - [Agents - uAgents Framework ↗️](/guides/agents/getting-started/whats-an-agent) - [The Agentverse ↗️](/concepts/agent-services/agentverse-intro) diff --git a/pages/guides/fetch-network/re-delegating-staked-fet-token.mdx b/pages/guides/fetch-network/re-delegating-staked-fet-token.mdx index f357380d5..dc1d1c1ef 100644 --- a/pages/guides/fetch-network/re-delegating-staked-fet-token.mdx +++ b/pages/guides/fetch-network/re-delegating-staked-fet-token.mdx @@ -16,7 +16,7 @@ There may be different reasons why you might choose to re-delegate and redistrib 1. **Increase the decentralization and therefore security of the network.** - For the Fetch network to be as secure as possible, there should not be a large concentration of stakes (e.g. more than 33% of the delegated FETs) staked within only a small number of (e.g. 10) validators. If you see this is currently the case and that you have also contributed to it by delegating your stakes with one of those validators, you may want to consider redistributing your stakes to some of the other validators. + For the ASI network to be as secure as possible, there should not be a large concentration of stakes (e.g. more than 33% of the delegated FETs) staked within only a small number of (e.g. 10) validators. If you see this is currently the case and that you have also contributed to it by delegating your stakes with one of those validators, you may want to consider redistributing your stakes to some of the other validators. 2. **Reduce your staking risks.** diff --git a/pages/guides/fetch-network/setting-up-a-multisig.mdx b/pages/guides/fetch-network/setting-up-a-multisig.mdx index f629d9a13..a156315f3 100644 --- a/pages/guides/fetch-network/setting-up-a-multisig.mdx +++ b/pages/guides/fetch-network/setting-up-a-multisig.mdx @@ -2,7 +2,7 @@ ## What is a Multisig account? -A multisig account, within the Fetch Network, possesses a unique key that necessitates multiple signatures for transaction authorization. This feature serves to enhance account security and mandates the agreement of multiple parties for transaction execution. Multisig accounts are established by defining: +A multisig account, within the ASI Network, possesses a unique key that necessitates multiple signatures for transaction authorization. This feature serves to enhance account security and mandates the agreement of multiple parties for transaction execution. Multisig accounts are established by defining: * The threshold number of signatures necessary. * The public keys implicated in the signing process.