-
Notifications
You must be signed in to change notification settings - Fork 9
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat(docs): Minor updates from Feb review (#1179)
Co-authored-by: Joshua Croft <[email protected]> Co-authored-by: Felix Nicolae Bucsa <[email protected]>
- Loading branch information
1 parent
56ddfe6
commit 4c22168
Showing
17 changed files
with
548 additions
and
125 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -791,4 +791,7 @@ apimessage | |
getmodels | ||
runtype | ||
CUDOS | ||
HD | ||
HD | ||
teckstack | ||
i1 | ||
i2 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -68,5 +68,6 @@ | |
"eslint-plugin-unicorn": "^48.0.1", | ||
"tailwindcss": "^3.3.3", | ||
"typescript": "^4.9.5" | ||
} | ||
}, | ||
"packageManager": "[email protected]+sha512.da9dc28cd3ff40d0592188235ab25d3202add8a207afbedc682220e4a0029ffbff4562102b9e6e46b4e3f9e8bd53e6d05de48544b0c57d4b0179e22c76d1199b" | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,13 @@ | ||
import { Callout } from 'nextra/components' | ||
|
||
# Almanac contract, registering, searching and discovery | ||
|
||
The [Almanac ↗️](/references/contracts/uagents-almanac/almanac-overview) contract is a decentralised register of all agents that are available in the system. Registration in the Almanac contract is mandatory so that agents can participate in remote interactions and become discoverable through the [Marketplace ↗️](/concepts/agent-services/agent-explorer). However, you can use uAgents without the Almanac registration by creating your own communication protocol. | ||
|
||
Agents keep their registrations up-to-date within defined block times 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. | ||
|
||
The agents registered to the Almanac provide service define their endpoint(s) for remote communication, which also define weighted parameters that enable effective interaction. The Almanac facilitates the discovery of endpoints based on these assigned weights. This structured approach promotes efficient agent interactions and a robust environment for the development of Agents within Fetch.ai's decentralized network. | ||
|
||
<Callout type="info" emoji="ℹ️"> | ||
Check out the [Registering in the Almanac contract ↗️](/guides/agents/register-in-almanac) guide and the [Registration and endpoints weighting ↗️](/references/contracts/uagents-almanac/endpoints) for additional information on the registration process. | ||
</Callout> |
92 changes: 92 additions & 0 deletions
92
pages/guides/agents/getting-started/fet-token-for-agents.mdx
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,92 @@ | ||
import { Callout } from 'nextra/components' | ||
|
||
# Getting Started with FET Token for Agent development | ||
|
||
<Callout type="info" emoji="💡️"> | ||
This is currently a work in progress and may be subject to further updates and revisions. | ||
</Callout> | ||
|
||
## Introduction | ||
|
||
The FET token was created to facilitate payments in an Agentic ecosystem, these are micro payments to one another which traditional currencies do not support. FET tokens are used for agent Almanac registration, and wider contract interactions. | ||
|
||
## Acquiring FET Tokens | ||
|
||
Exchanges are the simplest way to get FET tokens. | ||
|
||
Visit a trusted exchange such as Coinbase or Binance. You may need to create an account, which will involve you | ||
passing [KYC ↗️](https://www.gov.uk/government/publications/know-your-customer-guidance/know-your-customer-guidance-accessible-version). Once your account is enabled, you can buy FET token. You can buy this with most global | ||
currencies, just check on the exchange which currencies they accept. | ||
|
||
## Storing FET | ||
|
||
Ideally you would be sending this FET to your agent to transact on the network. However, if you'd like greater | ||
security or accessibility. | ||
|
||
For short-term storage goals, the ASI Wallet is an excellent choice; it provides direct functionalities for daily activities such as staking and interacting with Agents. | ||
|
||
For long-term storage goals, you can enhance security by integrating your ASI Wallet with a hardware wallet like Ledger, offering robust protection for your assets. Follow this guide [here ↗️](/guides/fetch-network/asi-wallet/asi-wallet-hardware-connection-guide) if you wish to set up the ASI Alliance extension wallet with a Ledger hardware wallet. | ||
|
||
## How to transfer tokens to your Agents | ||
|
||
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. | ||
|
||
<Callout type="info" emoji="ℹ️"> | ||
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! | ||
</Callout> | ||
|
||
### Getting your Agent address to send tokens to your Agent | ||
|
||
The following Python script demonstrates how to create and initialize an Agent using the `uagents` and `cosmpy` libraries, to connect it to the Fetch.ai Mainnet, and retrieve its address and balance information: | ||
|
||
```py copy filename="agent_address_and_balance.py" | ||
from uagents import Agent, Context | ||
import cosmpy | ||
|
||
from cosmpy.aerial.client import LedgerClient, NetworkConfig | ||
|
||
agent = Agent(name="alice", seed="", port=8000, test=False, endpoint=["http://localhost:8000/submit"]) | ||
|
||
@agent.on_event("startup") | ||
async def introduce_agent(ctx: Context): | ||
ctx.logger.info(f"ASI network address:{agent.wallet.address()}") | ||
ledger_client = LedgerClient(NetworkConfig.fetch_mainnet()) | ||
address: str = agent.wallet.address() | ||
balances = ledger_client.query_bank_all_balances(address) | ||
ctx.logger.info(f"Balance of addr: {balances}") | ||
|
||
if __name__ == "__main__": | ||
agent.run() | ||
|
||
``` | ||
|
||
**You must update the seed value, and store it safely. Losing this value will lose you your tokens.** | ||
|
||
In the code example above an Agent named `alice` is initialized with a specified `name`, `port`, `endpoint`, and `seed` | ||
parameters. When the Agent starts up, it logs the wallet address and queries the balance using the `LedgerClient` connected to the Fetch.ai Mainnet. Finally, the script runs the Agent, which processes the `startup` event and retrieves the balance, allowing the Agent to interact with the Fetch.ai network. | ||
|
||
Once you run the above Agent script, you will see your Agent address and balance printed out. You will see something similar to the following output: | ||
|
||
``` | ||
INFO: [alice]: Registration on Almanac API successful | ||
INFO: [alice]: Registering on almanac contract... | ||
INFO: [alice]: Registering on almanac contract...complete | ||
INFO: [alice]: Agent inspector available at https://agentverse.ai/inspect/?uri=http%3A//127.0.0.1%3A8000&address=agent1qdxdrwqek4pt9xt8kggcxus0zm54d4vgdznrs6y5acn26paphervwfj7pdd | ||
INFO: [alice]: Starting server on http://0.0.0.0:8000 (Press CTRL+C to quit) | ||
INFO: [alice]: ASI network address:fetch1ujr7wyuvza7uwnkr3usv53hjlwjvu8s7l06vzf | ||
INFO: [alice]: Balance of addr: [] | ||
``` | ||
|
||
You can now use this address to transfer your purchased FET tokens from the exchange to this Agent's address. This | ||
should be as simple as withdrawing native FET, by selecting the Fetch.ai Mainnet network when withdrawing. Some | ||
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: | ||
|
||
- [Agents - uAgents Framework ↗️](/guides/agents/getting-started/whats-an-agent) | ||
- [The Agentverse ↗️](/concepts/agent-services/agentverse-intro) | ||
- [AI Engine ↗️](/concepts/ai-engine/ai-engine-intro) | ||
- [DeltaV ↗️](/concepts/ai-engine/deltav) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.