refactor(tracker): rewrite operator tracker in elixir

[JuArce]

Description

Rewriting of the operator tracker in elixir

Tasks

• CRUD for operators
• Dockerfile for database
• Validate ECDSA signature from operators
• Add README
• Add targets to makefile
• Check if operator is registered in RegistryCoordinator
• Update operator version if already exist in database
• Fetch operators from Ethereum
• Error management (addressed in feat(telemetry): implement telemetry for aggregator #1075 )

How to test

Database setup

Important

You need to have Docker installed

1. Start the database

make telemetry_run_db

Run aligned

1. Run anvil

make anvil_start_with_block_time

2. Run aggregator

make aggregator_start

3. Register operator

export OPERATOR_ADDRESS=0x70997970C51812dc3A010C7d01b50e0d17dc79C8
make operator_full_registration CONFIG_FILE=config-files/config-operator-1.yaml

Note

There isn't necessary to run the batcher, since we are not sending proofs.

Run tracker

Once you registered the operator, the tracker will fetch registered operators on start.

1. Run

make telemetry_create_env
make telemetry_start

2. Go to tracker

You should see the following response

[
{
"id": "0x12027b4b27251854a8c58ea5df60bc0dbb57f97d474df0ba8bd33842f20a0e9e",
"name": "Aligned Layer Operator",
"version": null, <- Operator version is not set"address": "0x70997970C51812DC3A010C7D01B50E0D17DC79C8",
"stake": "100000000000000000"
}
]

Send Operator version

1. Build the operator

make build_operator

2. Run the operator

./operator/build/aligned-operator start --config ./config-files/config-operator-1.yaml

3. Go to tracker again.
   You should see the entry updated with the operator version

[
{
"id": "0x12027b4b27251854a8c58ea5df60bc0dbb57f97d474df0ba8bd33842f20a0e9e",
"name": "Aligned Layer Operator",
"version": "v0.5.2", <- Operator version is correctly set"address": "0x70997970C51812DC3A010C7D01B50E0D17DC79C8",
"stake": "100000000000000000"
}
]