Mainnet subgraph failed, with required capabilities: : A matching Ethereum network with NodeCapabilities { archive: false, traces: false } was not found.

[rok4f]

A bug.

I try to deploy a subgraph to Mainnet mpmain and face this error:

Failed to start subgraph, code: SubgraphStartFailure, error: expected triggers adapter that matches deployment QmV4H49cp81n36EcHcEgKn1AMaie2LoTxu2vs1fm6UXRus[396313] with required capabilities: : A matching Ethereum network with NodeCapabilities { archive: false, traces: false } was not found.

When I deploy this subgraph to Rinkeby metapoker everything works fine.

[rok4f]

Additional info, if I delete the following event handler, the error is gone:

    - event: NftOverridden(indexed uint256,indexed address,indexed uint256)
      handler: handleNftOverridden

[azf20]

Hi! Are you still having the above issue? I think there might have been a temporary glitch with the mainnet provider around a deployment

[yohanelly95]

I just got this issue as well, not sure why. Any ideas around this? I feel this could be an RPC issue.

[azf20]

Hi - what network are you indexing and where are you deploying?

[shubham-rathod1]

I am facing the same issue but with the Mumbai network because of callHandlers in my case.

[azf20]

For mainnet, I think this is an instance of https://github.com/graphprotocol/graph-node/issues/3204 For Mumbai, there is no trace_filter support so that will be persistent

[pheuberger]

For Mumbai, there is no trace_filter support so that will be persistent

Can you explain what you mean by that?

[azf20]

@pheuberger certain subgraph features (e.g. callHandlers) rely on the optional trace_filter JSON RPC method, which isn't supported by the Mumbai blockchain client