What if the target contract does not have a 4 byte signature?

[PaulRBerg]

That is, what if the owner wishes to give permission to an envoy to call a contract but not provide a 4-bye signature because they intend to let the fallback function be called?

The current approach to store the 4-byte signature in the permissions mapping does not cover this use case.

[PaulRBerg]

I think that this is safe to let as is. This is an edge case, and if the owner really has to interact with the fallback function of a target contract, they have two option:

1. Call the proxy by themselves.
2. Deploy another target that implements the behavior of the initial target in a named function.

[PaulRBerg]

Locking this discussion since it is no longer applicable to the latest implementation.

bef31cd