clean up {accept,implement}_interface

[pyramation]

we need to keep in sync with using full-scoped interface names in protos (already merged in cosmos-sdk)

• reference PR
• issue describing problem
• new updated docs with required changes

[pyramation]

cc @AmauryM

[damiannolan]

Hey, thanks for opening the issue. So, as I understand it, any protobuf defintions which make use of cosmos_proto.implements_interface should use the full typeURL excluding the preceding / which we normally see used in the sdk?

I think this is already covered for proposals here and here.

InterchainAccount uses this annoation here but it references a local/relative interface. Should this be updated to a fully qualified typeURL?

Aside from that the only other outstanding one I can think of is the feature branch work for ics20 authz. The TransferAuthorization should be updated to include the full typeURL here.

[pyramation]

The issue was that, while originally the spec allowed for local/relative/full-path references, they weren't correct in that many folks just put arbitrary names as shown here. The best solution for now that was discussed with the SDK team was to simply remove local/relative paths and only use fully-scoped to remove any ambiguity.

Hey, thanks for opening the issue. So, as I understand it, any protobuf defintions which make use of cosmos_proto.implements_interface should use the full typeURL excluding the preceding / which we normally see used in the sdk?

yes :)

InterchainAccount uses this annoation here but it references a local/relative interface. Should this be updated to a fully qualified typeURL?

Aside from that the only other outstanding one I can think of is the feature branch work for ics20 authz. The TransferAuthorization should be updated to include the full typeURL here.

yea so anything not fully qualified, needs to be changed to have full path, otherwise it won't conform to the new standard.

[pyramation]

also related CosmWasm/wasmd#1155