Proposal for architecture simplification: All validators are relayers about gravity-bridge HOT 3 CLOSED

@jkilpatr I'm not sure if I'm missing exactly what you're suggesting, but the architecture/code base already supports and expects this. The validator and relayer is split into two different code bases and binaries from a technical architecture standpoint, but from an actor/economic standpoint are both intended to be run by the same person.

The default expected usage is that both the validator cosmos service and the relayer service will be run on the same machine with the same private key as the same user.

from gravity-bridge.

That's the impression I had originally reviewing the proposed architecture. But I heard some discussion on the subject of 'incentive models for relayers'. On second glance the architecture as specified didn't preclude it so I decided to bring it up.

Without a definitive mailing list or chat room it's hard to get a clear picture of what everyone is thinking. What do you think of making one?

from gravity-bridge.

I was wondering if there was any update to this issue. Would there be a way in code to force validators to also be relayers as part of the deal for getting the validator rewards? Thanks

from gravity-bridge.