Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

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

Open
bumblefudge opened this issue Mar 14, 2023 · 0 comments
Open

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

bumblefudge opened this issue Mar 14, 2023 · 0 comments
Assignees
@bumblefudge
Labels
Spec v1.1 v1.1

Comments

@bumblefudge
Copy link

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)
@bumblefudge bumblefudge added the Spec v1.1 v1.1 label Mar 14, 2023
@bumblefudge bumblefudge self-assigned this Mar 14, 2023
@bumblefudge bumblefudge changed the title Chain-specific guidance (or even parameterization) should be spelled out in a mandatory section Chain-specific guidance (or even parameterization) should be spelled out in a mandatory section of each method's spec Mar 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bumblefudge bumblefudge

Labels
Spec v1.1 v1.1
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@bumblefudge