The AEA erc1155_deploy and erc1155_client skills demonstrate an interaction between two AEAs with the usage of a smart contract.
- The
erc1155_deployskill deploys the smart contract, creates and mints items. - The
erc1155_clientskill signs a transaction to complete a trustless trade with the counterparty.
Preparation instructions
Dependencies
Follow the Preliminaries and Installation sections from the AEA quick start.
Discussion
The scope of the specific demo is to demonstrate how to deploy a smart contract and interact with it. For the specific use-case, we create two AEAs one that deploys and creates tokens inside the smart contract and the other that signs a transaction so we can complete an atomic swap. The smart contract we are using is an ERC1155 smart contract with a one-step atomic swap functionality. That means the trade between the two AEAs can be trustless.
Note
This demo serves demonstrative purposes only. Since the AEA deploying the contract also has the ability to mint tokens, in reality the transfer of tokens from the AEA signing the transaction is worthless.
Demo
Create the deployer AEA
Fetch the AEA that will deploy the contract.
aea fetch fetchai/erc1155_deployer:0.11.0
cd erc1155_deployer
aea install
Alternatively, create from scratch.
Create the AEA that will deploy the contract.
aea create erc1155_deployer
cd erc1155_deployer
aea add connection fetchai/p2p_libp2p:0.7.0
aea add connection fetchai/soef:0.6.0
aea add connection fetchai/ledger:0.3.0
aea add skill fetchai/erc1155_deploy:0.11.0
aea install
aea config set agent.default_connection fetchai/p2p_libp2p:0.7.0
default_routing:
fetchai/contract_api:0.2.0: fetchai/ledger:0.3.0
fetchai/ledger_api:0.2.0: fetchai/ledger:0.3.0
fetchai/oef_search:0.4.0: fetchai/soef:0.6.0
aea config set agent.default_ledger ethereum
Additionally, create the private key for the deployer AEA. Generate and add a key for Ethereum use:
aea generate-key ethereum
aea add-key ethereum eth_private_key.txt
And one for the P2P connection:
aea generate-key cosmos
aea add-key cosmos cosmos_private_key.txt --connection
Create the client AEA
In another terminal, fetch the AEA that will get some tokens from the deployer.
aea fetch fetchai/erc1155_client:0.11.0
cd erc1155_client
aea install
Alternatively, create from scratch.
Create the AEA that will get some tokens from the deployer.
aea create erc1155_client
cd erc1155_client
aea add connection fetchai/p2p_libp2p:0.7.0
aea add connection fetchai/soef:0.6.0
aea add connection fetchai/ledger:0.3.0
aea add skill fetchai/erc1155_client:0.10.0
aea install
aea config set agent.default_connection fetchai/p2p_libp2p:0.7.0
default_routing:
fetchai/contract_api:0.2.0: fetchai/ledger:0.3.0
fetchai/ledger_api:0.2.0: fetchai/ledger:0.3.0
fetchai/oef_search:0.4.0: fetchai/soef:0.6.0
aea config set agent.default_ledger ethereum
Additionally, create the private key for the client AEA. Generate and add a key for Ethereum use:
aea generate-key ethereum
aea add-key ethereum eth_private_key.txt
And one for the P2P connection:
aea generate-key cosmos
aea add-key cosmos cosmos_private_key.txt --connection
Fund the AEAs
To create some wealth for your AEAs for the Ethereum ropsten network. Note that this needs to be executed from each AEA folder:
aea generate-wealth ethereum
To check the wealth use (after some time for the wealth creation to be mined on Ropsten):
aea get-wealth ethereum
Note
If no wealth appears after a while, then try funding the private key directly using a web faucet.
Update SOEF configs for both AEAs
To update the SOEF config, run in each AEA project:
aea config set vendor.fetchai.connections.soef.config.chain_identifier ethereum
Run the AEAs
First, run the deployer AEA.
aea run
Once you see a message of the form My libp2p addresses: ['SOME_ADDRESS'] take note of the address.
It will perform the following steps: - deploy the smart contract - create a batch of items in the smart contract - mint a batch of items in the smart contract
At some point you should see the log output:
registering service on SOEF.
Then, update the configuration of the buyer AEA's p2p connection (in vendor/fetchai/connections/p2p_libp2p/connection.yaml) replace the following:
config:
delegate_uri: 127.0.0.1:11001
entry_peers: ['SOME_ADDRESS']
local_uri: 127.0.0.1:9001
log_file: libp2p_node.log
public_uri: 127.0.0.1:9001
where SOME_ADDRESS is replaced accordingly.
Then, in the separate terminal run the client AEA.
aea run
You will see that upon discovery the two AEAs exchange information about the transaction and the client at the end signs and sends the signature to the deployer AEA to send it to the network.
Note
Transactions on Ropsten can take a significant amount of time! If you run the example a second time, and the previous transaction is still pending, it can lead to a failure. The warning message `Cannot verify whether transaction improves utility. Assuming it does!` can be ignored.
Delete the AEAs
When you're done, go up a level and delete the AEAs.
cd ..
aea delete erc1155_deployer
aea delete erc1155_client
Communication
This diagram shows the communication between the various entities as data is successfully trustless trade.