Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • hive hive
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 86
    • Issues 86
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 23
    • Merge requests 23
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • hive
  • hivehive
  • Issues
  • #291

Closed
Open
Created May 09, 2022 by Bartek Wrona@bwronaOwner

Transaction binary serialization should support new (NAI-based) storage and optionally legacy form for backward compatibility

This change is specific to following scenarios:

  • binary serialization impacts signature generation (done at client side), so authorization checks shall be extended to support 2 cases
  • cli_wallet shall be extended to allow optional generation and signinig transactions in NAI form. This is also related to issue #287 (closed)
  • legacy serialization must be supported for old blocks where any storage cannot be changed
  • new and optionally legacy serialization must be supported during P2P communication where incoming binary buffer can contain one of versions.
Assignee
Assign to
Time tracking