How to Verify if ECP Configuration is Proper and Capable of Receiving zk-tasks?

[Normalnoise]

How to Verify if ECP Configuration is Proper and Capable of Receiving zk-tasks?

• First, follow the official documentation to install and ensure computing-provider info displays correctly:

  
  CP Account Info:
  CP Account Address(2.0):    0x2e771E81dCBAc8d116fD7d5D2208b1DBc3c0d6Fc
  Name:                       ecp-is-sleeping
  Owner:                      0x8C3a7219595a6255ddCe8ac6cA3Dc28C5a748189
  Node ID:                    0426d8a1b3f0b95a1dbcf76b8b370032d83e5ac6b4910175ef6cfa9e78c03aed1df9a334fe7028b03cfa768b45d6ddf8da111301b5ae968a169f1827214b575f55
  Domain:                     <YOUR_CP_Domain>
  Multi-Address:              /ip4/provider.cp.com/tcp/5000
  Worker Address:             0x8C3a7219595a6255ddCe8ac6cA3Dc28C5a748189
  Beneficiary Address:        0x8C3a7219595a6255ddCe8ac6cA3Dc28C5a748189

Capabilities: Task Types: Fil-C2-512M,Aleo,Fil-C2-32G Applications: 8

Owner Balance(sETH): 0.2000 Worker Balance(sETH): 0.2000

ECP Balance(sETH): Collateral: 0.8000 Escrow: 0.0000 FCP Balance(sETH): Collateral: 0.0000 Escrow: 0.0000

**(1) Ensure the `Multi-Address` is correctly configured. Verify using the following method:**

curl http://:/api/v1/computing/cp

**(2) Ensure sufficient collateral (`ECP Balance.Collateral`). Currently, a zk-task requires 0.00005 sETH. Ensure the collateral balance is greater than this value.**

**(3) Ensure `Capabilities.Task Types` is correctly set and includes `Fil-C2-512M, Fil-C2-32G`. If not, modify using:**

computing-provider account changeTaskTypes --ownerAddress= 1,2,4

**(4) Use CMD to confirm that on-chain data matches local data:**
View on-chain data using:

computing-provider state cp-info

Example Output:

CP Account Address(2.0): 0x2e771E81dCBAc8d116fD7d5D2208b1DBc3c0d6Fc Node ID: 0426d8a1b3f0b95a1dbcf76b8b370032d83e5ac6b4910175ef6cfa9e78c03aed1df9a334fe7028b03cfa768b45d6ddf8da111301b5ae968a169f1827214b575f55 Multi-Address: /ip4/provider.cp.com/tcp/50004 Owner: 0x8C3a7219595a6255ddCe8ac6cA3Dc28C5a748189 Worker Address: 0x8C3a7219595a6255ddCe8ac6cA3Dc28C5a748189 Beneficiary Address: 0x8C3a7219595a6255ddCe8ac6cA3Dc28C5a748189 Task Types: Fil-C2-512M,Aleo,Fil-C2-32G

Owner Balance(sETH): 0.2000 Worker Balance(sETH): 0.2000

ECP Balance(sETH): Collateral: 0.8000 Escrow: 0.0000 FCP Balance(sETH): Collateral: 0.0000 Escrow: 0.0000

Ensure the local data's `Multi-Address`, `Node ID`, and `ECP Balance(sETH).Collateral` match the on-chain data.

**(5)** If all the above checks are fine, the ECP installation and configuration are correct. The dispatch of zk-tasks depends on various factors such as global gas price, the status of the zk-task pool, and the number of ECPs in the network.

**NOTE:** If you encounter any other issues, feel free to raise an [ISSUE](https://github.com/swanchain/go-computing-provider/issues).