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
  • Wiki
  • Seed nodes

Seed nodes · Changes

Page history
ashot created page: Seed nodes authored Apr 02, 2018 by Ashot's avatar Ashot
Hide whitespace changes
Inline Side-by-side
Seed-nodes.md 0 → 100644
View page @ 8d76be18
DNS seed nodes are intended to identify a set of nodes to connect to the network when the wallet is unable to connect and have never been connected. In that case the client issues DNS requests to get the list of other peer addresses.
Here is the list of host names that every Crown client includes:
**Mainnet**
* fra-crwdns.infernopool.com
* blr-crwdns.infernopool.com
* sgp-crwdns.infernopool.com
* lon-crwdns.infernopool.com
* nyc-crwdns.infernopool.com
* tor-crwdns.infernopool.com
* sfo-crwdns.infernopool.com
* ams-crwdns.infernopool.com
* crw.infernopool.com
**Testnet**
* fra-testnet-crwdns.infernopool.com
* blr-testnet-crwdns.infernopool.com
* sgp-testnet-crwdns.infernopool.com
* lon-testnet-crwdns.infernopool.com
* nyc-testnet-crwdns.infernopool.com
* tor-testnet-crwdns.infernopool.com
* sfo-testnet-crwdns.infernopool.com
* ams-testnet-crwdns.infernopool.com
* crw-testnet.infernopool.com
Seed nodes are running on VPS servers. Here is the list of ip addresses
**Mainnet**
* 188.166.223.93
* 139.59.29.11
* 139.59.154.34
* 178.62.22.23
* 67.205.154.19
* 159.203.19.13
* 107.170.221.232
* 146.185.165.149
**Testnet**
* 128.199.100.139
* 138.197.144.44
* 67.207.91.152
* 37.139.28.90
* 46.101.41.172
* 138.197.182.78
* 139.59.29.84
**The process of running DNS seed nodes includes two parts:**
1. Running last version of crownd
2. Running dnsseed (with arguments)
**Update DNS seed node**
1. To update Crown wallet on DNS seed node that's enough to download the latest version of Crown and extract bin/* under /usr/local/bin/
Here is the example of simple command which does everything<br/>
`rm -rf Crown-Linux64.zip; rm -rf 842.5-x86_64-unknown-linux-gnu; wget https://github.com/Crowndev/crowncoin/releases/download/v0.12.4.1/Crown-Linux64.zip; unzip Crown-Linux64.zip; cp -rf 842.5-x86_64-unknown-linux-gnu/bin/* /usr/local/bin/; cp -rf 842.5-x86_64-unknown-linux-gnu/lib/* /usr/local/lib/`<br/>
"842.5-x86_64-unknown-linux-gnu" and "v0.12.4.1" need to be changed accordingly.
2. 'dnsseed' executable doesn't need to be updated with Crown version change but only when protocol version is changed (for example 70051 to 70052) which is rare (mostly before official hard fork release).<br/>
Here is the DNS seed repository on github -https://github.com/Crowndev/crown-seeder<br/>
Every DNS node has crown-seeder cloned from github so after making according changes on remote repository we can do
```
cd crown-seeder
git pull
make
cp dnsseed /usr/local/bin/
```
After the above mentioned steps it's enough to reboot DNS seed VPS it will run both executables during boot.
\ No newline at end of file
Clone repository
  • 19.01.18 Testnet Fork Report
  • Credentials for electrumx servers
  • How to turn on off enforcement
  • Quality Assurance
  • Quality Assurance
    • Instant Send Testing
    • documents
  • Seed nodes
  • bounties
  • code of conduct
  • coding style guide
  • communications & marketing
  • community
  • community
    • Announcement Responsibilities
    • Developers
    • community built
View All Pages