I'm working on implementing AnonCreds using did:web and am planning to host the AnonCreds objects in a cloud storage bucket (like Amazon S3).
A requirement is that a status list can be queried by a timestamp in the URL /<timestamp>.
This limits AnonCreds objects from being stored in a cloud storage bucket.
For us, we are mainly interested in hosting the latest version of the status list, and overwrite the object each time a new revocation entry is added. This is similar to how most status list specs used for W3C and SD-JWT specs work.
There could be benefit in allowing to query multiple versions, but we do lose some of the simplicity that exists for did:web.
I'm working on implementing AnonCreds using did:web and am planning to host the AnonCreds objects in a cloud storage bucket (like Amazon S3).
A requirement is that a status list can be queried by a timestamp in the URL
/<timestamp>.This limits AnonCreds objects from being stored in a cloud storage bucket.
For us, we are mainly interested in hosting the latest version of the status list, and overwrite the object each time a new revocation entry is added. This is similar to how most status list specs used for W3C and SD-JWT specs work.
There could be benefit in allowing to query multiple versions, but we do lose some of the simplicity that exists for did:web.