You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It probably makes sense to produce files with single attestations. A use case I imagine is signing a single file and then uploading that single attestation immediately to some attestion-hosting service.
This is pretty straightforward, but the current "spec" only includes "repos".
In terms of speccing that out, I'd do something like:
A file containing a single attestation should be a UTF-8 text file whose contents are the JSON blob corresponding to a single attestation (as it would appear as a single element in the repo). The file's name should be <filename>.signet where <filename> is the filename of the original file being signed.
That might be too verbose, but I think it gets the point across.
The text was updated successfully, but these errors were encountered:
It probably makes sense to produce files with single attestations. A use case I imagine is signing a single file and then uploading that single attestation immediately to some attestion-hosting service.
This is pretty straightforward, but the current "spec" only includes "repos".
In terms of speccing that out, I'd do something like:
That might be too verbose, but I think it gets the point across.
The text was updated successfully, but these errors were encountered: