Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • 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 111
    • Issues 111
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 27
    • Merge requests 27
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • hive
  • hivehive
  • Merge requests
  • !519

Draft: Refactor to use full_blocks and full_transactions to optimize computations

  • Review changes

  • Download
  • Email patches
  • Plain diff
Closed Dan Notestein requested to merge full-transaction-cache into develop Jul 02, 2022
  • Overview 2
  • Commits 15
  • Changes 89

Introduce new full_blocks and full_transaction which combine the signed_block and signed_transaction data structure with the serialized version of those structures. Because we never have to re-serialize the data structures, we can ignore whether they were created using the pre- or post-hf26 serialization. This also lets us compute things like block & transaction ids more efficiently, and cache them and many other things related to transaction validation to avoid repeatedly computing them.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: full-transaction-cache