I would love to contribute and resolve this issue, please assign it to me.

Please feel free to ask any questions you have.

Hi @LexLuthr ,
Add network validation checks that prevent Curio from starting if the binary network doesn't match the chain node network.

I've implemented this by:

1. I have added network constants and validation function in build/params.go:

+ const (
+     NetworkMainnet    = "mainnet"
+     NetworkCalibnet   = "calibnet"
+     NetworkTestnet    = "testnet"
+ )
+ 
+ func CurrentNetwork() string {
+     switch BuildType {
+     case BuildMainnet:
+         return NetworkMainnet
+     case BuildCalibnet:
+         return NetworkCalibnet
+     case Build2k:
+         return NetworkTestnet
+     default:
+         return "unknown"
+     }
+ }

2. And also added network validation in cmd/curio/run.go:

+ func validateNetworkMatch(ctx context.Context, api v0api.FullNode) error {
+     // Get network name from the chain node
+     networkName, err := api.StateNetworkName(ctx)
+     if err != nil {
+         return xerrors.Errorf("failed to get network name from chain node: %w", err)
+     }
+ 
+     // Get binary's network
+     binaryNetwork := build.CurrentNetwork()
+ 
+     // Compare networks
+     if string(networkName) != binaryNetwork {
+         return xerrors.Errorf("network mismatch: binary built for %s but chain node is on %s", 
+             binaryNetwork, networkName)
+     }
+ 
+     return nil
+ }

  // I have added some validation check in run command
+ api, closer, err := lcli.GetFullNodeAPI(cctx)
+ if err != nil {
+     return err
+ }
+ defer closer()
+ 
+ if err := validateNetworkMatch(ctx, api); err != nil {
+     return xerrors.Errorf("network validation failed: %w", err)
+ }

The validation happens early in the startup process and will prevent Curio from starting if there's a network mismatch. The error message indicates which network the binary was built for and which network the chain node is on.

The validation happens early in the startup process before any services are started. The error message will indicate the mismatch (e.g., "network mismatch: binary built for mainnet but chain node is on calibnet").

Could you please review this approach and let me know if:

1. This is the right direction for implementing the network validation.
2. The placement of the check in the startup sequence is appropriate.
3. Is there anything left unchecked?

Thank you!

1. You don't need a separate function. One already exists build.BuildTypeString()
2. Network validation should not happen in the run command itself. It should happen in func GetFullNodeAPIV1Curio(). Each available chain node should be checked for version and any mismatch should be rejected. If we are left with none after removing incorrect ones, we should not proceed. Otherwise an alert should be raised about network mismatch.

I've implemented the feedback :

1. Removed the separate CurrentNetwork() function and now using the existing build.BuildTypeString() as suggested
2. Moved the network validation from run.go to GetFullNodeAPIV1Curio() where it:
   • Validates each chain node's network
   • Filters out incompatible nodes
   • Only proceeds if at least one compatible node is found
   • Provides clear logging about network mismatches

The validation now happens early in the connection process, providing better error handling and reporting when network mismatches occur.

Could you lemme know if there's any adjustments required