Skip to content

Life cycle of a service

The life cycle of a service minted in the Autonolas Protocol passes through the following states:

  1. Pre-Registration
  2. Active Registration
  3. Finished Registration
  4. Deployed
  5. Terminated Bonded

Example

Look at this service on the Protocol app to see the current state of a live service.

The figure below summarizes the life cycle and the actions that provoke a transition between states. Most of the service state transitions are initiated by the service owner. However, some state transitions are also triggered automatically. For example, when an operator registers the last available agent instance in the Active Registration state, the service will automatically transit to the Finished Registration state.

Life cycle of a service

Service states

This section details the states of a service minted in the Autonolas Protocol, as well as how to transit between them. You need to connect your wallet to the Autonolas Protocol web app in order to execute the available actions in each state. The connected wallet will ask to approve any transaction.

Pre-Registration

A service that has just been minted will be in Pre-Registration (of agent instances) state.

Available actions:

  • The service owner can make amendments by pressing the Update button.
  • The service owner can advance to the Active Registration state by pressing the Activate Registration button.

Active Registration

The service is waiting for agent operators to register their agent instances.

Available actions:

  • Agent operators can register their agent instances in the service by specifying their addresses (starting with 0x...) and pressing the Register Agents button. When the last agent instance slot is filled, the service state will transit to the Finished Registration state automatically.
  • The service owner can terminate the service by pressing the Terminate button.

Finished Registration

All agent instance slots have been filled. Waiting for the service owner to continue deploying the service.

Available actions:

  • The service owner can deploy the Safe multisig contract that will be associated with the service. The parameters shown in this screen are related to the creation of the safe (check the setup method here). If you are not familiar with the setup of such contracts, simply leave the default values. Press the Submit button to transit to the Deployed state.
  • The service owner can terminate the service by pressing the Terminate button.

Deployed

Congratulations! Your service is now in the Deployed state!

The service is in its default operational state. Agent operators can turn on their agent instances at this point.

Available actions:

  • The service owner can terminate the service by pressing the Terminate button.

Terminated Bonded

The service has been terminated by the service owner. Waiting for the service owner to unbond all registered agents.

Available actions:

  • The service owner can unbond the registered agent instances by pressing the Unbond button. The service will transit to the Pre-Registration state, enabling the registration of new agent instances.