Common protocol parameter format

[troyronda]

Are there any generic Sidetree protocol parameters that should have a common format?

Here are our current trustbloc parameters:

{
  "genesisTime": 0,
  "multihashAlgorithm": 18,
  "maxOperationCount": 10,
  "maxOperationSize": 200000,
  "compressionAlgorithm": "GZIP",
  "maxAnchorFileSize": 1000000,
  "maxMapFileSize": 1000000,
  "maxChunkFileSize": 1000000,
  "patches": [
    "replace",
    "add-public-keys",
    "remove-public-keys",
    "add-services",
    "remove-services",
    "ietf-json-patch"
  ],
  "signatureAlgorithms": [
    "EdDSA",
    "ES256",
    "ES256K"
  ],
  "keyAlgorithms": [
    "Ed25519",
    "P-256",
    "secp256k1"
  ]
}

[csuwildcat]

Hmm, there are some params like this called out in the spec, so I think this comes down to style guide choices if we want to codify some of them with a JSON-based example. The current style guide I believe we chose indicates we would want to use uppercased and underscored names for const/config params: https://google.github.io/styleguide/jsguide.html#naming-constant-names

[OR13]

IMO these belong in the "sidetree version" response, exposed via the REST API....

[sandrask]

@thehenrytsai I may have misunderstood your comment here:

sidetree/lib/core/versions/latest/OperationProcessor.ts

Line 91 in e64bcd3

// TODO: Issue #766 - Remove temporary assumption on reveal value being calculated using the same hash algorithm

I will remove hashAlgorithm parameter since it looks like it was never meant to be different hash for commitment double hashing