open-autonomy 0.2.1

A framework for the creation of autonomous agent services.

Open Autonomy

Open Autonomy is a framework for the creation of Agent Services: off-chain services which run as a multi-agent-system (MAS) and are replicated on a temporary consensus gadget (blockchain) while being crypto-economically secured on a public blockchain, hence offering robustness, transparency and decentralization off-chain.

As opposed to traditional smart contracts, Valory apps go beyond simple, purely on-chain logic without giving up on decentralization.

For developers using the framework: Get started developing

1. Create and launch a clean virtual environment with Python 3.10 (any Python >= 3.7 works):

   pipenv --python 3.10 && pipenv shell
   

2. Install the package from PyPI:

   pip install open-autonomy
   

3. Then, build your services as described in the docs.

Requirements for Framework Developers

Ensure your machine satisfies the following requirements:

• Python >= 3.7
• Yarn >=1.22.xx
• Node >=v12.xx
• Tendermint ==0.34.19
• IPFS node ==v0.6.0
• Pip
• Pipenv >=2021.x.xx
• Go ==1.17.7
• Kubectl
• Docker Engine
• Docker Compose
• Skaffold >= 1.39.1
• Gitleaks

For developers contributing to the framework: Install from Source

• Clone the repository, and recursively clone the submodules:

  git clone --recursive [e-mail]:valory-xyz/open-autonomy.git
  

  Note: to update the Git submodules later:

  git submodule update --init --recursive
  

• Build the Hardhat projects:

  cd third_party/safe-contracts && yarn install
  cd ../..
  cd third_party/contracts-amm && yarn install
  cd ../..
  cd third_party/autonolas-registries && yarn install --ignore-engines
  

• Create and launch a virtual environment. Also, run this during development, every time you need to re-create and launch the virtual environment and update the dependencies:

  make new_env && pipenv shell
  

Common errors and solutions

e2e tests not running

Error message:

error Command "hardhat" not found.
Failed: node:16.7.0 doesn't work. Exiting...

Solution: re-run yarn install inside the third-party/safe-contracts and third-party/contracts-amm repos.