Orie Steele

Now that this issue is in ION, I'm in favor of letting the user define some arbitrary bytes that get prefixed or postfixed to the didUniqueSuffix.... why? because AFAIK, no...

AFAIK, Sidetree Create Payloads lead to self certifying identifiers... the payload data (which includes the authoritative keys) is hashed to produce the identifier, the inception event is witnessed by a...

Also, since we are talking about privacy / tracking concerns... There are couple different levels of surveillance / data mining attacks of DIDs. Level 0 - A Database of all...

Sidetree uses the label `didUniqueSuffix` to refer to what is normatively defined in did core as `idchar`... I misinterpreted the proposal (because it lacked a concrete example), its essentially to...

They are not even self asserted... create payloads are not signed.

discussed on the DID WG Topic call today.

You can fork the implementation / use ietf-json patch, or use a did method like did web that supports arbitrary json better.

yes! it has `env:create:local` but there is no documentation around it, and indeed this is used for testing only.

@JaceHensley @tplooker @kdenhartog interested in your thoughts on this as well, I'm very open to a naming structure for Ethereum / element derived Sidetree methods that is configurable / inclusive.......

@mirceanis yes, we copied you :) wondering in world where there are many did:ethr and did:elem on ropsten, managed by different companies.... if we should try and upgrade this sooner...