## Case 1
-The first option is to create a `HTTP Server` connection that handles incoming requests from a REST API. In this scenario, the REST API communicates with the AEA and requests are handled by the `HTTP Server` connection package. The REST API should send CRUD requests to the `HTTP Server` connection (`fetchai/http_server:0.23.3`) which translates these into Envelopes to be consumed by the correct skill.
+The first option is to create a `HTTP Server` connection that handles incoming requests from a REST API. In this scenario, the REST API communicates with the AEA and requests are handled by the `HTTP Server` connection package. The REST API should send CRUD requests to the `HTTP Server` connection (`fetchai/http_server:0.23.4`) which translates these into Envelopes to be consumed by the correct skill.
## Case 2
-The second option is to create a front-end comprising a stand-alone `Multiplexer` with a `P2P` connection (`fetchai/p2p_libp2p:0.27.2`). In this scenario the Agent Communication Network can be used to send Envelopes from the AEA to the front-end.
\ No newline at end of file
+The second option is to create a front-end comprising a stand-alone `Multiplexer` with a `P2P` connection (`fetchai/p2p_libp2p:0.27.3`). In this scenario the Agent Communication Network can be used to send Envelopes from the AEA to the front-end.
\ No newline at end of file
diff --git a/docs/connection.md b/docs/connection.md
index b1fe507bae..66f1bb641b 100644
--- a/docs/connection.md
+++ b/docs/connection.md
@@ -36,7 +36,7 @@ The developer needs to implement four public coroutines:
- The `receive` coroutine is continuously called by the AEA framework. It either returns `None` or an envelope. The `receive` coroutine must implement the logic of data being received by the agent, and if necessary, its translation into a relevant protocol.
-The framework provides a demo `stub` connection which implements an I/O reader and writer to send and receive messages between the agent and a local file. To gain inspiration and become familiar with the structure of connection packages, you may find it useful to check out `fetchai/stub:0.21.1`, `fetchai/http_server:0.23.3` or `fetchai/http_client:0.24.3` connections. The latter two connections are for external clients to connect with an agent, and for the agent to connect with external servers, respectively.
+The framework provides a demo `stub` connection which implements an I/O reader and writer to send and receive messages between the agent and a local file. To gain inspiration and become familiar with the structure of connection packages, you may find it useful to check out `fetchai/stub:0.21.2`, `fetchai/http_server:0.23.4` or `fetchai/http_client:0.24.4` connections. The latter two connections are for external clients to connect with an agent, and for the agent to connect with external servers, respectively.
### Primary methods to develop - sync connection interface
diff --git a/docs/contract.md b/docs/contract.md
index 477d0cb33f..7186ef47fd 100644
--- a/docs/contract.md
+++ b/docs/contract.md
@@ -18,9 +18,9 @@ Interacting with contracts in almost all cases requires network access. Therefor
-In particular, the `fetchai/ledger:0.21.2` connection can be used to execute contract related logic. The skills communicate with the `fetchai/ledger:0.21.2` connection via the `fetchai/contract_api:1.0.0` protocol. This protocol implements a request-response pattern to serve the four types of methods listed above:
+In particular, the `fetchai/ledger:0.21.3` connection can be used to execute contract related logic. The skills communicate with the `fetchai/ledger:0.21.3` connection via the `fetchai/contract_api:1.0.0` protocol. This protocol implements a request-response pattern to serve the four types of methods listed above:
-- the `get_deploy_transaction` message is used to request a deploy transaction for a specific contract. For instance, to request a deploy transaction for the deployment of the smart contract wrapped in the `fetchai/erc1155:0.23.2` package, we send the following message to the `fetchai/ledger:0.21.2`:
+- the `get_deploy_transaction` message is used to request a deploy transaction for a specific contract. For instance, to request a deploy transaction for the deployment of the smart contract wrapped in the `fetchai/erc1155:0.23.2` package, we send the following message to the `fetchai/ledger:0.21.3`:
``` python
contract_api_msg = ContractApiMessage(
@@ -37,7 +37,7 @@ contract_api_msg = ContractApiMessage(
Any additional arguments needed by the contract's constructor method should be added to `kwargs`.
-This message will be handled by the `fetchai/ledger:0.21.2` connection and then a `raw_transaction` message will be returned with the matching raw transaction. To send this transaction to the ledger for processing, we first sign the message with the decision maker and then send the signed transaction to the `fetchai/ledger:0.21.2` connection using the `fetchai/ledger_api:1.0.0` protocol. For details on how to implement the message handling, see the handlers in the `erc1155_deploy` skill.
+This message will be handled by the `fetchai/ledger:0.21.3` connection and then a `raw_transaction` message will be returned with the matching raw transaction. To send this transaction to the ledger for processing, we first sign the message with the decision maker and then send the signed transaction to the `fetchai/ledger:0.21.3` connection using the `fetchai/ledger_api:1.0.0` protocol. For details on how to implement the message handling, see the handlers in the `erc1155_deploy` skill.
CosmWasm based smart contract deployments
@@ -45,7 +45,7 @@ This message will be handled by the `fetchai/ledger:0.21.2` connection and thenfetchai/default:1.1.3 protocol which satisfies the following protobuf schema:
+fetchai/default:1.1.4 protocol which satisfies the following protobuf schema:
``` proto
syntax = "proto3";
@@ -121,7 +121,7 @@ message DefaultMessage{
fetchai/default:1.1.3 protocol. The protobuf schema is given above.
+fetchai/default:1.1.4 protocol. The protobuf schema is given above.
-
diff --git a/docs/ledger-integration.md b/docs/ledger-integration.md
index 755c096077..27fae94d5d 100644
--- a/docs/ledger-integration.md
+++ b/docs/ledger-integration.md
@@ -146,7 +146,7 @@ Stargate World is our stable, public testnet for the Fetch Ledger v2. As such, m
You can access more details on docs section.
-The configurations can be specified for the `fetchai/ledger:0.21.2` connection.
+The configurations can be specified for the `fetchai/ledger:0.21.3` connection.
## CosmWasm supporting chains
diff --git a/docs/logging.md b/docs/logging.md
index 35ac27615f..52cd984351 100644
--- a/docs/logging.md
+++ b/docs/logging.md
@@ -22,13 +22,13 @@ aea_version: 0.6.0
fingerprint: {}
fingerprint_ignore_patterns: []
connections:
-- fetchai/stub:0.21.1
+- fetchai/stub:0.21.2
contracts: []
protocols:
-- fetchai/default:1.1.3
+- fetchai/default:1.1.4
skills:
-- fetchai/error:0.18.3
-default_connection: fetchai/stub:0.21.1
+- fetchai/error:0.18.4
+default_connection: fetchai/stub:0.21.2
default_ledger: fetchai
required_ledgers:
- fetchai
diff --git a/docs/ml-skills.md b/docs/ml-skills.md
index a69f5cf55f..1bc8124f25 100644
--- a/docs/ml-skills.md
+++ b/docs/ml-skills.md
@@ -106,7 +106,7 @@ Follow this approach when using the `aea` CLI.
First, fetch the data provider AEA:
``` bash
-aea fetch fetchai/ml_data_provider:0.32.2
+aea fetch fetchai/ml_data_provider:0.32.3
cd ml_data_provider
aea install
aea build
@@ -119,19 +119,19 @@ The following steps create the data provider from scratch:
``` bash
aea create ml_data_provider
cd ml_data_provider
-aea add connection fetchai/p2p_libp2p:0.27.2
-aea add connection fetchai/soef:0.27.3
-aea add connection fetchai/ledger:0.21.2
-aea add skill fetchai/ml_data_provider:0.27.3
+aea add connection fetchai/p2p_libp2p:0.27.3
+aea add connection fetchai/soef:0.27.4
+aea add connection fetchai/ledger:0.21.3
+aea add skill fetchai/ml_data_provider:0.27.4
aea config set --type dict agent.dependencies \
'{
"aea-ledger-fetchai": {"version": "<2.0.0,>=1.0.0"}
}'
-aea config set agent.default_connection fetchai/p2p_libp2p:0.27.2
+aea config set agent.default_connection fetchai/p2p_libp2p:0.27.3
aea config set --type dict agent.default_routing \
'{
- "fetchai/ledger_api:1.1.3": "fetchai/ledger:0.21.2",
- "fetchai/oef_search:1.1.3": "fetchai/soef:0.27.3"
+ "fetchai/ledger_api:1.1.4": "fetchai/ledger:0.21.3",
+ "fetchai/oef_search:1.1.4": "fetchai/soef:0.27.4"
}'
aea install
aea build
@@ -144,7 +144,7 @@ aea build
Then, fetch the model trainer AEA:
``` bash
-aea fetch fetchai/ml_model_trainer:0.33.2
+aea fetch fetchai/ml_model_trainer:0.33.3
cd ml_model_trainer
aea install
aea build
@@ -157,19 +157,19 @@ The following steps create the model trainer from scratch:
``` bash
aea create ml_model_trainer
cd ml_model_trainer
-aea add connection fetchai/p2p_libp2p:0.27.2
-aea add connection fetchai/soef:0.27.3
-aea add connection fetchai/ledger:0.21.2
-aea add skill fetchai/ml_train:0.29.3
+aea add connection fetchai/p2p_libp2p:0.27.3
+aea add connection fetchai/soef:0.27.4
+aea add connection fetchai/ledger:0.21.3
+aea add skill fetchai/ml_train:0.29.4
aea config set --type dict agent.dependencies \
'{
"aea-ledger-fetchai": {"version": "<2.0.0,>=1.0.0"}
}'
-aea config set agent.default_connection fetchai/p2p_libp2p:0.27.2
+aea config set agent.default_connection fetchai/p2p_libp2p:0.27.3
aea config set --type dict agent.default_routing \
'{
- "fetchai/ledger_api:1.1.3": "fetchai/ledger:0.21.2",
- "fetchai/oef_search:1.1.3": "fetchai/soef:0.27.3"
+ "fetchai/ledger_api:1.1.4": "fetchai/ledger:0.21.3",
+ "fetchai/oef_search:1.1.4": "fetchai/soef:0.27.4"
}'
aea install
aea build
@@ -234,7 +234,7 @@ First, run the data provider AEA:
aea run
```
-Once you see a message of the form `To join its network use multiaddr 'SOME_ADDRESS'` take note of the address. (Alternatively, use `aea get-multiaddress fetchai -c -i fetchai/p2p_libp2p:0.27.2 -u public_uri` to retrieve the address.)
+Once you see a message of the form `To join its network use multiaddr 'SOME_ADDRESS'` take note of the address. (Alternatively, use `aea get-multiaddress fetchai -c -i fetchai/p2p_libp2p:0.27.3 -u public_uri` to retrieve the address.)
This is the entry peer address for the local agent communication network created by the ML data provider.