Authority_Null

> I had a quick look at this issue and here are a few thoughts: > > 1. From the UX perspective, I think we should allow having multiple ETH...

> @AuthorityNull is the domain in your issue using load balancing? Because each segment acts as a new connection and if it's load balancing or switching endpoints each segment you...

Closed the issue - The issue was related to DNS and has been resolved by changing the serviceAddr on the O to point to individual IP.

I see this error in Singapore as well. @Titan-Node is this where you're seeing it? I'm wondering if this is an issue with the Tensor Docks VM's. ``` E0822 01:06:18.976108...

Hi Titan-Node! I'm not a developer (I can work my way around Ubuntu, kinda) so I'll just throw in a basic introduction... I'm Ben, the owner and operator of the...

> No active orchestrators are requesting a price higher than 1200 though. The B node is automatically adjusting the price somehow and that's breaking the B's ability to connect to...

> @joegraviton AFAIK livepeer_cli displaying `0.00` for the price is "normal". I think the livepeer cli connected to O displays the prices stored on-chain (which is not used anymore). Currently...

> I just checked and for the first O you mentioned and the current price is `1111.000` logged by our B. So, it's very weird. @AuthorityNull Is it maybe possible...

Hope to see this addressed. Having to manually decode, edit and encode edge agent ID's for every new edge environment is incredibly inconvenient for an application that otherwise makes everything...

> Why not just fix this for god's sake? Zero mention in the docs about having two different addresses in the key, no field to set edge address. If not...