Stale pricing data for orchestrator about livepeer-pricing-tool HOT 10 OPEN

Based on Nico's suggestion we have kept 1 ETH in reserve. But this might be outdated as this amount was suggested by him while we were in the development phase of the pricing tool, and there has been a surge since then. So I think Nico would be the best person to answer this question.

from livepeer-pricing-tool.

I believe the orchestrators with stale data are due to "insufficient sender reserve" errors being returned to the broadcaster.
See this orchestrator which still has a stale price. I think we need to increase our reserve even more. I need to find out by how much.

from livepeer-pricing-tool.

cc @Saumay-Agrawal

from livepeer-pricing-tool.

Hi @adamsoffer, I just downloaded the lpdb.sqlite3 file from the broadcaster node we are running to check for any data inconsistency. However, the current price per pixel value for this orchestrator coincides with what we are getting in our broadcaster node.

Maybe the orchestrator has been inactive all this time?

from livepeer-pricing-tool.

Hm that orchestrator is active and belongs to Bison Trails which is the #1 orchestrator by stake. I confirmed with them they changed their price per pixel a few weeks ago, though even if they hadn't the price should change due to gas prices.

from livepeer-pricing-tool.

Maybe an issue with the broadcaster? Will run this by Yondon and Nico.

from livepeer-pricing-tool.

From Nico:

I checked some other O's though and they don't have an updated price either. Perhaps insufficient reserve to be able to cache prices on their B node ? Their B node logs would be interesting here

Could you share your broadcaster logs @Saumay-Agrawal? Thanks!

from livepeer-pricing-tool.

This appears to still be an issue. This price hasn't changed https://livepeer-pricing-tool.com/priceHistory/0x21d1130dc36958db75fbb0e5a9e3e5f5680238ff

from livepeer-pricing-tool.

@adamsoffer I restarted the broadcaster node, but nothing happened unlike the previous time (https://discord.com/channels/423160867534929930/426114749370204170/797188011716640829). It seems like the broadcaster node is fetching (or mis-fetching for that matter) the wrong values for some reason.

Can you tell what price per pixel value is being shown by a broadcaster running at your side?

from livepeer-pricing-tool.

@Saumay-Agrawal Sure. Can you remind me what the minimum deposit and reserve I need to fund my broadcaster with for fetching orchestrator prices?

from livepeer-pricing-tool.