EPIC: Read-only protocol

[mpoke]

Problem

This is a meta issue to track the work on making ICS a read-only protocol.

Closing criteria

Either ICS is redesigned as read-only protocol (i.e., no CCV channel) or a good reasoning of why this is not feasible is provided.

Problem details

We would like to simplify the ICS protocol to work with IBC queries. This will allow for a much simpler protocol, and easier maintenance going forward, as well as making the Hub more robust to malfunctioning consumer chains.

Task list

Must have

Beta Give feedback

1. Update spec -- EPIC: Remove VSCMaturedPacket ibc#1010

Nice to have

Beta Give feedback

1. Trustless downtime slashing #761
   0 of 4
   S: NewThings admin: epic type: feature-request +3

[shaspitz]

Consumer initiated slashing will still exist with this idea correct? Everything would just be invoked by provider tx instead of an IBC packet

[mpoke]

Consumer initiated slashing will still exist with this idea correct? Everything would just be invoked by provider tx instead of an IBC packet

Jailing for downtime is necessary. We'll need to figure out how to do it though. An IBC packet is a TX sent by a relayer and it comes with some nice proofs. Maybe something along the lines of #761 could be a solution. Not sure.

[mpoke]

We believe that VSCMaturedPackets cannot be removed from the Replicated Security protocol without compromising the security of the system. This is due to the security model of IBC light clients. We documented our findings here. As a result, we are closing this issue.