Daniel Buchner

One form this could take is an ID with segments for `did:sidetree:BlockNumber-TransactionNumber-EntryIndex` represented in Base36 characters, which would result in case insensitive IDs of this form and maximum length: `did:sidetree:abc12-de3-fg6`.

One thing to note: because you could map all Core Index File-centric ops to these IDs (Creates, Recovery, etc.), there may be a premium on having your ID ops low...

I had a thought that might make these small ID forms event smaller: technically, you can number every operation in a block, because every transaction has to declare how many...

Added a note for now

**WIP:** DID Methods based on the Sidetree protocol all share the same identifier format. The unique identifier string is a hash of a set of initialization values the controller generates...

Henry, are the vectors the same as in the spec here?: https://identity.foundation/sidetree/spec/#long-form-did-uris

@thehenrytsai are the vectors present in the spec, as linked above, true and correct for what is implemented?

ACTION: Dan will update examples

Question: aren't there already values within the suffix data that indicate this, and if not, should we consider just adding a version string to the create suffix portion that is...

I don't know what this is asking for in the spec; what is the change or clarification requested?