Skip to content
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.

Protocol-spec second signature #4148

Closed
3 of 4 tasks
pablitovicente opened this issue Aug 26, 2019 · 0 comments · Fixed by #4151
Closed
3 of 4 tasks

Protocol-spec second signature #4148

pablitovicente opened this issue Aug 26, 2019 · 0 comments · Fixed by #4151

Comments

@pablitovicente
Copy link
Contributor

pablitovicente commented Aug 26, 2019

Description

  • Do not include genesis block in output
  • Basic Second signature acceptance (account should end up with 5 lisk less and have second public key)
  • Combination of second signature and transfer transactions in a same block (account should remain unchanged. Transaction should not be in the block)
  • Double registration (i.e. an account with already registered signature tries to register again) (account should remain unchanged. Transaction should not be in the block)

Motivation

Acceptance Criteria

JSON generator for:

  • Do not include genesis block in output
  • Basic Second signature acceptance
  • Combination of second signature and transfer transactions in a same block
  • Double registration (i.e. an account with already registered signature tries to register again)

Additional Information

Split from #4087

@pablitovicente pablitovicente self-assigned this Aug 26, 2019
@pablitovicente pablitovicente added this to the Sprint 5 milestone Aug 26, 2019
@pablitovicente pablitovicente changed the title Create protocol-spec json for basic current specification Basic Second signature acceptance Create protocol-spec json for basic current specification for Second signature Aug 26, 2019
@pablitovicente pablitovicente changed the title Create protocol-spec json for basic current specification for Second signature Protocol-spec second signature Aug 26, 2019
shuse2 added a commit that referenced this issue Aug 28, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants