network dapp - incorrect epoch time

graphprotocol / mission-control-indexer

Technical indexer documentation and infrastructure templates for the Mission Control testnet

21 stars 4 forks source link

network dapp - incorrect epoch time #265

Closed koen84 closed 3 years ago

koen84 commented 3 years ago

The epoch time in https://network.thegraph.com/ is presumably wrong, that's 563 days.

koen84 commented 3 years ago

Says that epochs 1-4 were 2 years ago.

koen84 commented 3 years ago

Actually, it shows epochs : 0, 1, 3 & 4 There seemingly no epoch 2.

trader-payne commented 3 years ago

Known issue. Can't be mitigated. Only triggers if you're on the "wrong network". You need to connect your metamask on mainnet to see the correct values.

trader-payne commented 3 years ago

Epochs missing is a feature, not a bug. If nothing happens during that said epoch period, it won't show up. Thankfully, as we are now on mainnet, there will be actions taken every epoch, so that's likely gonna be the first and last ever missing epoch in existence. 😂

koen84 commented 3 years ago

Known issue. Can't be mitigated. Only triggers if you're on the "wrong network". You need to connect your metamask on mainnet to see the correct values.

Weird. My metamask isn't even connected to the dapp. But switching it from rinkeby to mainnet indeed corrects it (after a few secs).

Wouldn't it be possible to detect the metamask network on the epoch page and display a warning / alert if it's not mainnet ? I've seen dapps do that if they're not on the expected network / wallet.

trader-payne commented 3 years ago

This should be fixed now