feat: add a draft specification for prism VDR (WIP)#3
Open
FabioPinheiro wants to merge 1 commit intomainfrom
Open
feat: add a draft specification for prism VDR (WIP)#3FabioPinheiro wants to merge 1 commit intomainfrom
FabioPinheiro wants to merge 1 commit intomainfrom
Conversation
Signed-off-by: FabioPinheiro <fabiomgpinheiro@gmail.com>
FabioPinheiro
force-pushed
the
prism-vdr
branch
from
68020b0 to
2343210
Compare
mineme0110
reviewed
May 26, 2025
mineme0110
reviewed
May 26, 2025
mineme0110
reviewed
May 26, 2025
mineme0110
reviewed
May 26, 2025
| The DID Docuemtn is a simplacy version of the lasters status of the SSI. | ||
| That does not contains the `MASTER_KEY`; `ISSUING_KEY`; `VDR_KEY`. | ||
|
|
||
| Note: There are usa case where the SSI entry is not used as a DID. For example if you cares about managing Storage Entry. |
There was a problem hiding this comment.
It is confusing sentence for me , apart from the spelling mistakes
Contributor
Author
There was a problem hiding this comment.
I need review
patextreme
reviewed
Jun 3, 2025
Comment on lines
+129
to
+133
| The data type for a Storage Entry is defined by the create event/operation. Depending on the filter used in the data, the following types of information/data may be stored: | ||
| - `E-7-3` - **bytes**: Represents a raw array of bytes. | ||
| - `E-7-4` - **Token Status List**: Represents a status list, as defined by https://datatracker.ietf.org/doc/draft-ietf-oauth-status-list/10/ | ||
| - `E-7-5` - **bitstring_status_list**: ???? | ||
| - `E-7-?` - **CID (content identifier)**: A reference to an IPFS document. |
Contributor
There was a problem hiding this comment.
What do you think about storing just raw bytes and use media type to express how to handle the data? Application will interpret the data and protocol don't need to care what is being stored.
For example
text/plain; charset=utf-8application/statuslist+jwt- one of options in bit string statuslist
- other possible media types in SSI ecosystem
patextreme
reviewed
Jun 3, 2025
| - The Indexer MUST be deterministic. | ||
| - The Indexer MUST be able to rever all steps to a previous `Cardano Block`. | ||
| Ideally, we recommend that the index is able to backtrack all the steps and unapply. | ||
| - It's not responsibility of the Indexer to validate the signature of the PRISM Operation. |
Contributor
There was a problem hiding this comment.
Interesting take. Why isn't this similar to the resolver? Behind the VDR interface, client wouldn't have the ability to replay all the events? Maybe in this document Indexer != VDR driver?
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is still a draft
Scecrtiong missing :