Chain-specific guidance (or even parameterization) should be spelled out in a mandatory section of each method's spec

[bumblefudge]

Discussed on today's call, we resolved that each Sidetree spec going forward should include for its specific chain or other substrate:

• value-locking (~= "staking") params (anchor for tokenomics, slashing, etc)
• which block to start from -
• block reorg/fork guidance (Ezequiel from IOHK mentioned this would help make interop decisions and equivalences
• how late-publishing is mitigated (if multiple substrate-specific and/or architectural patterns continue to be allowed)