Define how Cow protocol users can have arbitrary data

[anxolin]

Description AppData is a field part of the order that can have arbitrary data.

We wrote a spec where this data would point to a IPFS document with a JSON and a bunch of meta-information.

Up until now, we had a loose way to create this data (based on a soft spec done in a google doc). People is starting to integrate with the protocol so we need better information on how to create your own AppData.

Proposal One pragmatic approach would be:

1. @avsavsavs creates a nicer version in the official docs
2. Then we updated once we have the proper schema
3. We update again once we have the SDK + explorer util

Additional context

• Conversation: https://gnosisinc.slack.com/archives/CPZA1AGKY/p1637250988160400
• Guide: https://docs.google.com/document/d/1So_483QExP5yum3FxTETqoa6myl-b3h-NbSdi0VuN4c/edit#

[alfetopito]

Explorer epic https://github.com/gnosis/gp-ui/issues/849 Json schema https://github.com/gnosis/cowswap/issues/959

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you think it shouldn't be closed, speak now or forever hold your peace.

[anxolin]

Relevant! let's document how to create your own AppData:

• We should have a docs entry
• We should have a SDK method
• We should decode it and show it nicely in the explorer
• [optional] Give a simple UI to make your own code