Feedback Requested: Attestation Schema

[dob]

Before we move to alpha on the Ropsten testnet, we'd like some feedback from the community in terms of what data users can actually provide in an attestation that would be useful. The current schema example is: Attestation Example

It basically includes:

• method description
• method signature
• boolean fields about whether it usesGas, acceptsETH, sendsETH, has known exploits, can update asset ownership, calls external contracts
• overall risk level in using the function
• descriptions of the cases where it throws, calls external contracts, and known exploits.
• Information that lets you verify who provided the attestation.

What fields are missing? What else would you like to see in an attestation. We'll take all feedback and publish an alpha version before going live.