Orie Steele
Orie Steele
we use this approach as well, I think this would be a major process and developer experience improvement. @thehenrytsai @gjgd any comments on this approach?
Maybe we can work with hyperledger / aries community to accomplish this: https://github.com/hyperledger/aries-rfcs/issues/129
Internal telemetry for reference implementation, some ability to see how well IPFS is behaving.
IMO these belong in the "sidetree version" response, exposed via the REST API....
@csuwildcat to propose reference implementation changes, and get this ready to be addressed by PR.
Document best practice for user agent to keep update & recovery operation payload until confirmation
Addressed, by using an HD Wallet Scheme, or preserving all keys ever used by sidetree protocol. Best practice would be to retain all keys ever used. I'm not sure "where"...
suggested change: HTTP POST http://example.com/operations { body } -H { accept: application/json } body : { type: 'create', suffix_data: base64url ( { "delta_hash": DELTA_HASH, "recovery_key": JWK_OBJECT, "recovery_commitment": COMMITMENT_HASH }) delta:...
@csuwildcat @thehenrytsai to define what happens in the spec language. Assuming this is documented, we can have test vectors.
Blocked pending reference implementation catchup...
prefer to have the behavior fully defined in the spec, with RECOMMENDED text.