Yondon Fu

TBD on whether we want to remove `ethereum-waffle` - might not be a big deal to leave it. The person working on this should make sure to consider this and...

From @kautukkundan in https://github.com/livepeer/protocol/issues/463#issuecomment-927939556 > possible fix to the problem in my previous comment > add a `lastClaimedRound` variable in the delegation struct and check it before calling `claimReward` >...

O can have a master address that has the following privileges: - Transferring LPT for staking - Withdrawing LPT rewards and ETH fees - Approving/revoking signer addresses This master address...

I think that is a good assessment of the pros/cons of the proxy contract approach. Another pro is the ability to wrap multiple function calls into a single atomic transaction...

> I think I understand the point about BondingManager allowing msg.sender to be a signer that could perform certain financial operations (e.g. withdrawFee) on behalf of the cold wallet O...

Good point about the gas cap on `eth_call`. Updated the OP to note that we should benchmark the gas cost of the batch functions exposed by the viewer contract.

Thanks for the suggestion! An alternative that is possible to setup today without any changes to `livepeer` is to set `-ethUrl` to the URL of a load balancer service for...

> But perhaps in general, we could be careful not to dampen any potential enthusiasm which may ever come from the many permissionless outsiders, by labeling things as not going...

I think caching OrchestratorInfo messages makes sense especially since the data included in each message does not vary per stream. At the moment, when a B receives multiple streams it...

@red-0ne Interesting suggestion of using on-chain events to notify Bs of when to send a network request to O to get a fresh OrchestratorInfo message! This seems like a pub-sub...