{
  "context": "This criteria evaluates how well the engineer uses the @walletconnect/types package to implement blockchain namespace definitions and session configurations. The focus is on proper usage of SessionTypes.Namespace, ProposalTypes.RequiredNamespaces, and ProposalTypes.OptionalNamespaces types.",
  "type": "weighted_checklist",
  "checklist": [
    {
      "name": "SessionTypes.Namespace usage",
      "description": "Uses SessionTypes.Namespace or ProposalTypes.BaseNamespace from @walletconnect/types to define the NamespaceConfig structure with chains, methods, events, and accounts arrays",
      "max_score": 25
    },
    {
      "name": "RequiredNamespaces structure",
      "description": "Correctly implements ProposalTypes.RequiredNamespaces or SessionTypes.Namespaces as a Record<string, Namespace> for the requiredNamespaces field in buildRequiredNamespaces function",
      "max_score": 20
    },
    {
      "name": "OptionalNamespaces structure",
      "description": "Correctly implements ProposalTypes.OptionalNamespaces as a Record<string, Namespace> for the optionalNamespaces field in buildOptionalNamespaces function",
      "max_score": 20
    },
    {
      "name": "SessionConfig typing",
      "description": "Uses ProposalTypes.Struct or creates a compatible SessionConfig interface that matches the WalletConnect session proposal structure with both requiredNamespaces and optionalNamespaces",
      "max_score": 15
    },
    {
      "name": "Namespace grouping",
      "description": "Groups chains by namespace (e.g., 'eip155') when building the Record<string, Namespace> structure, correctly extracting namespace from CAIP-2 chain identifiers",
      "max_score": 10
    },
    {
      "name": "Validation logic",
      "description": "Implements validateNamespaceConfig to check that accounts array is non-empty and methods array is non-empty, matching WalletConnect namespace requirements",
      "max_score": 10
    }
  ]
}