feat: mina verifiers

[MarcosNicolau]

Description

Description of the pull request changes and motivation.

All credits go to #506. This pr syncs with upstream and solves the conflics.

How to test

1. Clone the lambdaclass/aligned_layer repo. Or add it as a remote and checkout to synced-mina branch.
2. Start anvil

make anvil_start

3. Start aggregator

make aggregator_start ENVIRONMENT=devnet

4. Start operator

make operator_full_registration_and_start ENVIRONMENT=devnet CONFIG_FILE=config-files/config-operator-1.yaml

5. Start batcher

make batcher_start_local

6. Send mina state proofs:

make batcher_send_mina_burst

7. Send mina account proofs:

make batcher_send_mina_account_burst

8. Send mina state with bad

make batcher_send_mina_task_bad_hash

Testing Mina Bridge

1. Clone mina bridge repo:

git clone https://github.com/lambdaclass/mina_bridge.git
cd mina_bridge
git checkout fix/mina-aligned-integration

2. Fill .env variables in the repository root with:

ETH_CHAIN=devnet
MINA_RPC_URL=https://api.minascan.io/node/devnet/v1/graphql
STATE_SETTLEMENT_ETH_ADDR=<STATE_SETTLEMENT_ETH_ADDR>
ACCOUNT_VALIDATION_ETH_ADDR=<ACCOUNT_VALIDATION_ETH_ADDR>
SAVE_PROOF=true
PRIVATE_KEY=0xac0974bec39a17e36ba4a6b4d238ff944bacb478cbed5efcae784d7bf4f2ff80 # Anvil 1th rich account

3. Deploy bridge contracts:

make deploy_example_bridge_contracts 

4. Collect the STATE_SETTLEMENT_ETH_ADDR and ACCOUNT_VALIDATION_ETH_ADDR and complete them in the .env of before.
5. Submit devnet state and collect the STATE_HASH:

make submit_devnet_state  

6. Submit account state proof with the STATE_HASH of before and an address which you can get from here, for example:

make submit_account PUBLIC_KEY="B62qo5CjRzbqupyriSQgQqPANjZwxzZKzjkdf5cqGKDWbdsNfx5Xuw5" STATE_HASH=<STATE_HASH>

Type of change

Please delete options that are not relevant.

• New feature

Checklist

• “Hotfix” to testnet, everything else to staging
• Linked to Github Issue
• This change depends on code or research by an external entity
  • Acknowledgements were updated to give credit
• Unit tests added
• This change requires new documentation.
  • Documentation has been added/updated.
• This change is an Optimization
  • Benchmarks added/run
• Has a known issue
  • Link to the open issue addressing it
• If your PR changes the Operator compatibility (Ex: Upgrade prover versions)
  • This PR adds compatibility for operator for both versions and do not change crates/docs/examples
  • This PR updates batcher and docs/examples to the newer version. This requires the operator are already updated to be compatible

[gabrielbosio]

🚀🚀🚀🚀🚀