This PR adds optionalDependencies to the Gnosis network variant package configuration to enable optional integration with consensus layer clients.

Changes Made

Added the following optional dependencies to /package_variants/gnosis/dappnode_package.json:

"optionalDependencies": {
  "lighthouse-gnosis.dnp.dappnode.eth": ">=0.1.15",
  "teku-gnosis.dnp.dappnode.eth": ">=0.1.15", 
  "lodestar-gnosis.dnp.dappnode.eth": ">=0.1.32"
}

Background

The Gnosis network requires consensus layer clients to work alongside execution clients like Nethermind. By adding these as optional dependencies, users can more easily discover and install compatible consensus clients (Lighthouse, Teku, or Lodestar) when running the Nethermind execution client on the Gnosis network.

Validation

• ✅ JSON structure validated successfully
• ✅ All package variant files remain valid
• ✅ DAppNodeSDK validation passes
• ✅ No security issues detected

The changes maintain full backward compatibility while enabling better integration with the Gnosis consensus layer ecosystem.

This pull request was created as a result of the following prompt from Copilot chat.

Add the following to the /package_variants/gnosis/dappnode_package.json file under the root of the repository:

  "optionalDependencies": {
    "lighthouse-gnosis.dnp.dappnode.eth": ">=0.1.15",
    "teku-gnosis.dnp.dappnode.eth": ">=0.1.15",
    "lodestar-gnosis.dnp.dappnode.eth": ">=0.1.32"
  }

If the file does not exist, create it and ensure the content is properly formatted as JSON. If the file exists and already contains other fields, merge or add the optionalDependencies field so that the file remains valid JSON.

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.