Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • crown-core crown-core
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 75
    • Issues 75
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 1
    • Merge requests 1
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Crown
  • crown-corecrown-core
  • Merge requests
  • !111

Merged
Created May 04, 2018 by Ashot@ashotMaintainer

Fix score calculation vulnerability

  • Overview 14
  • Commits 5
  • Pipelines 4
  • Changes 10

Transaction input block hash and masternodes collateral input block hash was used previously to calculate score. For instant send both can be calculated in advance and perform double spend attack on network.

To prevent the attack the transaction hash when masternode got minimum confirmations (15 in our case) is used together with above mentioned hashes. This way attacker cannot brute force collateral hashes to create a winner masternode at certain block.

Edited May 04, 2018 by Ashot
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: fix-score-calculation-vulnerability