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
  • Issues
  • #242

Closed
Open
Created Oct 04, 2018 by Artem B@artemOwner2 of 2 tasks completed2/2 tasks

Crown wallet 30 Sept crash causing split

Summary

Crashes because of out-of-memory caused a split on Sep 30 2018. The reason is DDoS attack on InstantSend Tx map.

Expected behavior

Crown should not be vulnerable to this type of attack

Problematic behavior

Crown nodes crash because of out-of-memory

Crown-core environment info

Ubuntu 16.04

Crown-core application info

v0.12.5.1

Relevant logs, dumps and/or screenshots

https://nextcloud.crown.tech/nextcloud/apps/files/?dir=/Crown/Dev/Dumps%26Logs/Sep-30-chain-split&fileid=16120

Possible fixes

Do not accept txs with more than x confirmations.

Tasks left

  • InstantSend regression testing (@artem)
  • InstantSend stress test (@ashot)
Edited Oct 29, 2018 by Artem B
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking