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.

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

WIP ceremony: draft specification (co-authored with Kevin Loaec) #107

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

JSwambo
Copy link
Member

@JSwambo JSwambo commented Oct 8, 2021

No description provided.

@JSwambo JSwambo force-pushed the ceremony_spec branch 3 times, most recently from 91c187d to c1b907b Compare October 8, 2021 18:19
JSwambo added a commit to JSwambo/practical-revault that referenced this pull request Jan 14, 2022
Removed:

The 'Keys' section was removed in favour of a more detailed spec coming with revault#107
The 'Transactions' section was removed as it duplicates transactions.md
'Acknowledgements' section removed. Should it be somewhere else in the repo?

New content:

Updated transaction diagram using descriptors abstraction.
Discussed options for revault deployments and the infrastructure requriements.

Still to do:

The 'fee bumping' section was mostly removed as we are approaching it differently. New approach needs description and rationale.
'Threat model' needs updating to better reflect our current understanding.
'Further Discussion' removed as this information is mostly out-dated or duplicated.
JSwambo added a commit to JSwambo/practical-revault that referenced this pull request Jan 25, 2022
Removed:

The 'Keys' section was removed in favour of a more detailed spec coming with revault#107
The 'Transactions' section was removed as it duplicates transactions.md
'Acknowledgements' section removed. Should it be somewhere else in the repo?

New content:

Updated transaction diagram using descriptors abstraction.
Discussed options for revault deployments and the infrastructure requriements.
Renamed "Threat model" section to "Risk" and updated.
The 'fee bumping' section was mostly removed as we are approaching it differently.
'Further Discussion' removed as this information is mostly out-dated or duplicated.
darosior pushed a commit to JSwambo/practical-revault that referenced this pull request Feb 1, 2022
Removed:

The 'Keys' section was removed in favour of a more detailed spec coming with revault#107
The 'Transactions' section was removed as it duplicates transactions.md
'Acknowledgements' section removed. Should it be somewhere else in the repo?

New content:

Updated transaction diagram using descriptors abstraction.
Discussed options for revault deployments and the infrastructure requriements.
Renamed "Threat model" section to "Risk" and updated.
The 'fee bumping' section was mostly removed as we are approaching it differently.
'Further Discussion' removed as this information is mostly out-dated or duplicated.
darosior added a commit that referenced this pull request Feb 1, 2022
…tion.md

6b35b37 introduction: replace out-dated revault.pdf with introduction.md (JSwambo)

Pull request description:

  In addition to many language clarifications and minor updates, major differences with revault.pdf are given below.

  Removed:

  The 'Keys' section was removed in favour of a more detailed spec coming with #107
  The 'Transactions' section was removed as it duplicates transactions.md
  'Acknowledgements' section removed. Should it be somewhere else in the repo?

  'Further Discussion' removed as this information is mostly out-dated or duplicated.

  New content:

  Updated transaction diagram using descriptors abstraction.
  Discussed options for revault deployments and the infrastructure requriements.

  Still to do:

  - [x] The 'fee bumping' section was mostly removed as we are approaching it differently. New approach needs description and rationale.
  - [x] 'Threat model' needs updating to better reflect our current understanding.
  - [x] Update background colour for diagram to white

ACKs for top commit:
  darosior:
    ACK 6b35b37

Tree-SHA512: 6bec68f498fd393dd3fb5d6d6f0769827a7e2b1de6dce0fc5c3962846baa9be6b827400f7c74eaee958823f9fcb81608a23c559052c14fa9ab633d12c13d15cb
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant