Offchain attestation reference about eas-contracts HOT 5 CLOSED

The rationale behind reference UIDs was to allow building a graph of onchain attestations, so indeed, referencing an offchain attestation won't work here. You can consider attesting to an offchain attestation as part of the scheme, or using the timestamping feature.

from eas-contracts.

But the timestamp also doesn't work? Since isAttestationValid is not checking for _timestamps[uid] != 0

from eas-contracts.

Oh, sorry for not being clear. I've meant that you can reference an offchain attestation by either timestamping it (thus proving in the future that the attestation existed at this time) or by attesting to it via a custom schema. In any case, supporting referencing to offchain attestations explicitly would be definitely something to consider for the next version.

from eas-contracts.

Sadly, because of this problem, I spent 2 days checking the contract(a little complicated) implementation problem. After setting the off-chain reference, a custom error will occur in make on-chain attest, but the specific reason will not be prompted, because it is an exception thrown by revert. You'll never know what went wrong, it's a very, very bad design.
The Offchain attestation reference issue should be clearly told to developers in the documentation, otherwise it will be very confusing when the issue occurs.

from eas-contracts.

I'm sorry that you had a bad experience. We are constantly looking to improve, and I hope that using the latest SDK will help to handle errors more easily.

from eas-contracts.