feat: add a draft specification for prism VDR (WIP) #3
Conversation
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
Signed-off-by: FabioPinheiro <fabiomgpinheiro@gmail.com>
FabioPinheiro
force-pushed
the
prism-vdr
branch
from
68020b0 to
2343210
Compare
| - PRISM CredentialBatch - Specification is not public | ||
| - Anyone else that want to for whatever reason | ||
|
|
||
| CRYPTOGRAPHIC_CURVE is the key type used by the master key master key. It follows the guidance of [CIP-0016 - Cryptographic Key Serialisation Formats](https://github.com/cardano-foundation/CIPs/tree/master/CIP-0016) |
mineme0110
reviewed
May 26, 2025
| The larger the amount of data, the more expensive it will be to submit as metadata in a transaction. Additionally, transaction metadata has hard limits. | ||
|
|
||
| When a Storage Entry is created, the first field, `E-7-1`, refers to the identity SSI of the creator of the Storage Entry. | ||
| The Storage Entry is also designed existe on chain, similar to the SSI Entries. The creator is allowed to send follow-up events/operations to update the content. |
mineme0110
reviewed
May 26, 2025
|
|
||
| For more documentation ref to [**prism:did specs**](https://github.com/input-output-hk/prism-did-method-spec/blob/main/w3c-spec/PRISM-method.md). | ||
|
|
||
| But the sumany the DID only exist if the SSI is create `#E-1` and not deactivate `#E-6`. |
There was a problem hiding this comment.
To summarize, a DID is valid only when its underlying SSI has been created #E-1 and not deactivate #E-6.
mineme0110
reviewed
May 26, 2025
| For more documentation ref to [**prism:did specs**](https://github.com/input-output-hk/prism-did-method-spec/blob/main/w3c-spec/PRISM-method.md). | ||
|
|
||
| But the sumany the DID only exist if the SSI is create `#E-1` and not deactivate `#E-6`. | ||
| The DID Docuemtn is a simplacy version of the lasters status of the SSI. |
There was a problem hiding this comment.
The DID Document is a simplified representation of the SSI's latest status
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
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. |
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. |
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?
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 :