Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

CatalystSignedDocument structure is focusing on only the known metadata fields like id, ver, type etc. and any other fields just being skipped during the decoding procedure, meaning that such document considered valid.
Which is wrong.

Expected Behavior

For any unsupported/un recognisable metadata field and signatures protected and unprotected header fields we should invalid it by adding error message into the report.