Skip to content
GitLab
    • GitLab: the DevOps platform
    • Explore GitLab
    • Install GitLab
    • How GitLab compares
    • Get started
    • GitLab docs
    • GitLab Learn
  • Pricing
  • Talk to an expert
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
    • Switch to GitLab Next
    Projects Groups Topics Snippets
  • Register
  • Sign in
  • tezos tezos
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 1,898
    • Issues 1,898
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 264
    • Merge requests 264
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • TezosTezos
  • tezostezos
  • Issues
  • #601
Closed
Open
Issue created Oct 22, 2019 by Antoine Le Calvez@alecalve

Unexplained balance changes following Babylon upgrade

Following the Babylon upgrade, it seems that some previously empty (aka 0 balance) tz1 accounts got an extra mutez if they previously originated a KT1 account.

For example, tz1VWmnscfeLbGTxn9nureNtjoW344Gr29Mm had an empty balance prior to the Babylon upgrade, but, without any apparent explanation apart from the Babylon upgrade, had its balance changed to 0.000001ꜩ. This breaks any software tracking balances by summing up credits & debits obtained by exporting node data.

At level 655,359 querying this account's balance results in a proto.004-Pt24m4xi.context.storage_error as the account doesn't exist anymore.

At level 655,360 querying this account's balance results in a balance of 0.000001ꜩ despite there being no operation affecting this account in that block.

I couldn't find any explanation around this change in the details of the Babylon upgrade.

Is this an expected behaviour? If so, how is it possible to audit which accounts have had an extra mutez credited to them?

Edited Oct 22, 2019 by Antoine Le Calvez
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking