Attestation did not verify whether the format of the `data` matches the `schema`. about eas-contracts HOT 4 CLOSED

But this is irrelevant to the format of the data itself. I.e., if you allow everyone to submit trust scores for users - format verification won't really help you because anyone could still fake the data using the "correct" format.

In any case, this type of verification should be done on the app layer, and we can't force any format nor validate it.

from eas-contracts.

EAS doesn't presuppose anything, so the schema itself can be anything and not necessarily an ABI specification; therefore we can't perform any of these validations. If extra validation is desired, we recommend doing this in the resolver itself.

from eas-contracts.

EAS doesn't presuppose anything, so the schema itself can be anything and not necessarily an ABI specification; therefore we can't perform any of these validations. If extra validation is desired, we recommend doing this in the resolver itself.

Yes, this does provide a lot of flexibility, but it may bring problems on the other hand. For example, we create a reputation system(because the resolver is optional, it is not used here), but the reputation system is maliciously written into some non-standard data, that is, Dirty Data (somewhat similar to a DOS attack), will this reduce everyone's trust in this reputation system?

from eas-contracts.

I get it, Thx~

from eas-contracts.