Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • H HAfAH
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 4
    • Issues 4
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 2
    • Merge requests 2
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • hive
  • HAfAH
  • Issues
  • #11
Closed
Open
Created Jan 14, 2022 by Marcin Sobczyk@msobczykDeveloper

blocks marked as irreversible(false) after database replay in enum_virtual_ops

When using parameter "group_by_block": true in method enum_virtual_ops we get list of operations and corresponding blocks where each block is marked as irreversible (or not)

curl -s -X POST -d '{"jsonrpc": "2.0", "method": "account_history_api.enum_virtual_ops", "params": {"block_range_begin": 2965014, "block_range_end": 2965019, "group_by_block": true}, "id": 1000}' https://api.hive.blog

We are asking about block 2965014 so obviously reversible should be marked true, this is the case in legacy account history api

But hafah behaves different, blocks are marked irreversible(false)

Node used for populating database was replayed for 5milion blocks and then entered p2p massive sync. Legacy account history (rocksdb) for this node gives the same results as https://api.hive.blog

Assignee
Assign to
Time tracking