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
  • !208

Merged
Created Dec 18, 2019 by Mark Brooker@walkjiveflyMaintainer

Include addnodes for seednodes in config

  • Overview 1
  • Commits 1
  • Pipelines 1
  • Changes 1

Since the DNS/seednodes moved off Digital Ocean servers and changed URLs any new installations of v0.13.4.0 have stuck at the sync because they can't find any peers. For some reason the patch_v0.13.4.1 branch which updated the seednode URLs in chainparams.cpp doesn't work (well) for winbloze and Mac.

The workaround for all new v0.13.4.0 users is to put addnode directives in crown.conf for the seednodes. winbloze and Mac users will have to do so manually, linux wallet/node users can use the updated installation script to generate a config with the addnode directives.

Only 3 of the 6 planned seednodes are currently active, so the update includes only those.

Using the updated script for a new v0.13.4.0 installation on linux64, syncing started within a few seconds of starting the daemon and had 15 peers within 5 minutes.

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: issue_337_addnode_seednodes