How to handle bad/corrupt data

[joeygrover]

So far here are our proposed solutions on core:

-Disconnect on bad packet
-Drop packets/RPCs silently when stuff goes south
-Full retry strategy

[jmarchwi-ford]

Perhaps we add a little bit of color.

The issue is how should Core handle bad data coming from the phone. The three options above each have a list of pros and cons when dealing with apps/phones that send erroneous data. Today, I believe the behavior is to disconnect.

There are likely a host of better options which are proposed, but mainly, the two further options are a lot more graceful. Did we want to elaborate the problem and the options here?

[justinjdickow]

Bringing in a comment from Jacob Rau to test our bot.

If we allow RPCs to be dropped, we will need to advise our developers that they need to be aware of RPCs which they send to which do not receive a response, when it matters that the RPC run successfully. If we are to keep the quality of approved apps up, we should include in our validation a test which rejects/doesn't respond to some RPCs, to ensure the app does retry, at least to ones like CreateInteractionChoiceSet.