MEV telemetry not working in full node

[livthomas]

Right now, MEV telemetry does not send any data to the target service when you start a full node. Even though this feature is implemented in both ProcessProposalHandler and FullNodeProcessProposalHandler, it simply does not work when running in the full node mode.

We suspect it might be caused by an error which causes the handler to return. It looks like these errors are being swallowed as we don't see anything in the logs. See the code above the sending logic in FullNodeProcessProposalHandler.

This is the command we used when starting the node:

/home/dydx/bin/dydxprotocold start \
        --home "/home/dydx/.dydxprotocol" \
        --p2p.seeds="[email protected]:23856,[email protected]:23856,f04a77b92d0d86725cdb2d6b7a7eb0eda8c27089@dydx-mainnet-seed.bwarelabs.com:36656,[email protected]:23856,c2c2fcb5e6e4755e06b83b499aff93e97282f8e8@tenderseed.ccvalidators.com:26401,[email protected]:26656,a9cae4047d5c34772442322b10ef5600d8e54900@dydx-mainnet-seednode.allthatnode.com:26656,[email protected]:26656,[email protected]:666,ebc272824924ea1a27ea3183dd0b9ba713494f83@dydx-mainnet-seed.autostake.com:27366" \
        --non-validating-full-node=true \
        --mev-telemetry-enabled \
        --mev-telemetry-identifier "dydx-node-main-01" \
        --mev-telemetry-hosts "https://my-dydx-mev-service.example.com"

[linear]

GH-44 MEV telemetry not working in full node

[yang-dydx]

Turns out you have to set --non-validating-full-node=false and --mev-telemetry-enabled=true. The MEV telemetry needs the oracle price calculation which doesn't exist in full node mode.

Obviously this is really confusing, but this is a quick workaround before team fixes this.

[livthomas]

@yang-dydx We have already been using it this way. I just wanted to point out that it's not working in the full node mode even though the code is there. We spent a lot of time figuring out what was wrong until we found this workaround.