sikkienl/dash
1
0
Fork 0
mirror of https://github.com/dashpay/dash.git synced 2024-12-26 12:32:48 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity
d11e379ed4
dash/contrib/seeds/nodes_main.txt

190 lines
3.8 KiB
Plaintext
Raw Normal View History

feat: add onion_seeds to seed creation; do seed creation (#5866) ## Issue being fixed or feature implemented We did not previously ship any onion seeds. This results in people needing to use `addnode` in order to actually get connected ## What was done? Modified seed creation process to handle a list of onion seeds. ## How Has This Been Tested? Running with and without onlynet=onion and with dnsseed=0 and deleting peers.dat ## Breaking Changes None ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_
2024-02-15 05:31:24 +01:00
v7ttoiov7rc5aut64nfomyfwxt424ihufwvr5ilf7moeg3fwibjpjcqd.onion:9999
snu2xaql3crh2b4t6g2wxemgrpzmaxfxla4tua63bnp2phhxwr6hzzid.onion:9999
k532fqvgzqotj6epfw3rfc377elrj3td47ztad2tkn6vwnw6nhxacrqd.onion:9999
fq63mjtyamklhxtskvvdf7tcdckwvtoo7kb5eazi34tsxuvexveyroad.onion:9999
cmhr5r3lqhy7ic2ebeil66ftcz5u62zq5qhbfdz53l6sqxljh7zxntyd.onion:9999
5v5lgddolcidtt2qmhmvyka2ewht4mkmmj73tfwuimlckgmqb5lthtid.onion:9999
chore: update mainnet seeds ``` cd contrib/seeds dash-cli protx list valid 1 > protx.txt ./makeseeds.py protx.txt > nodes_main.txt ./generate-seeds.py . > ../../src/chainparamsseeds.h ```
2023-11-11 13:44:30 +01:00
216.250.97.52:9999
feat: add onion_seeds to seed creation; do seed creation (#5866) ## Issue being fixed or feature implemented We did not previously ship any onion seeds. This results in people needing to use `addnode` in order to actually get connected ## What was done? Modified seed creation process to handle a list of onion seeds. ## How Has This Been Tested? Running with and without onlynet=onion and with dnsseed=0 and deleting peers.dat ## Breaking Changes None ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_
2024-02-15 05:31:24 +01:00
216.238.75.46:9999
216.230.232.125:9999
chore: update seeds for v20.1 Don't forget to specify onion_seeds.txt: ``` cd contrib/seeds dash-cli protx list valid 1 > protx.txt ./makeseeds.py protx.txt onion_seeds.txt > nodes_main.txt ./generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-02-29 19:44:12 +01:00
216.189.154.8:9999
216.107.217.62:9999
feat: add onion_seeds to seed creation; do seed creation (#5866) ## Issue being fixed or feature implemented We did not previously ship any onion seeds. This results in people needing to use `addnode` in order to actually get connected ## What was done? Modified seed creation process to handle a list of onion seeds. ## How Has This Been Tested? Running with and without onlynet=onion and with dnsseed=0 and deleting peers.dat ## Breaking Changes None ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_
2024-02-15 05:31:24 +01:00
213.168.249.174:9999
212.52.0.210:9999
212.24.110.128:9999
212.24.107.223:9999
207.244.247.40:9999
206.168.213.109:9999
206.168.212.226:9999
206.168.212.178:9999
chore: update seeds for v20.1 Don't forget to specify onion_seeds.txt: ``` cd contrib/seeds dash-cli protx list valid 1 > protx.txt ./makeseeds.py protx.txt onion_seeds.txt > nodes_main.txt ./generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-02-29 19:44:12 +01:00
206.168.212.144:9999
202.5.18.203:9999
feat: add onion_seeds to seed creation; do seed creation (#5866) ## Issue being fixed or feature implemented We did not previously ship any onion seeds. This results in people needing to use `addnode` in order to actually get connected ## What was done? Modified seed creation process to handle a list of onion seeds. ## How Has This Been Tested? Running with and without onlynet=onion and with dnsseed=0 and deleting peers.dat ## Breaking Changes None ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_
2024-02-15 05:31:24 +01:00
195.181.211.64:9999
195.98.95.210:9999
194.158.71.228:9999
194.135.81.214:9999
chore: update seeds for v20.1 Don't forget to specify onion_seeds.txt: ``` cd contrib/seeds dash-cli protx list valid 1 > protx.txt ./makeseeds.py protx.txt onion_seeds.txt > nodes_main.txt ./generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-02-29 19:44:12 +01:00
194.5.157.214:9999
feat: add onion_seeds to seed creation; do seed creation (#5866) ## Issue being fixed or feature implemented We did not previously ship any onion seeds. This results in people needing to use `addnode` in order to actually get connected ## What was done? Modified seed creation process to handle a list of onion seeds. ## How Has This Been Tested? Running with and without onlynet=onion and with dnsseed=0 and deleting peers.dat ## Breaking Changes None ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_
2024-02-15 05:31:24 +01:00
193.164.149.50:9999
193.29.59.96:9999
193.29.57.21:9999
192.169.6.87:9999
chore: update seeds for v20.1 Don't forget to specify onion_seeds.txt: ``` cd contrib/seeds dash-cli protx list valid 1 > protx.txt ./makeseeds.py protx.txt onion_seeds.txt > nodes_main.txt ./generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-02-29 19:44:12 +01:00
192.64.83.140:9999
feat: add onion_seeds to seed creation; do seed creation (#5866) ## Issue being fixed or feature implemented We did not previously ship any onion seeds. This results in people needing to use `addnode` in order to actually get connected ## What was done? Modified seed creation process to handle a list of onion seeds. ## How Has This Been Tested? Running with and without onlynet=onion and with dnsseed=0 and deleting peers.dat ## Breaking Changes None ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_
2024-02-15 05:31:24 +01:00
188.208.196.183:9999
188.127.237.243:9999
188.127.230.40:9999
188.68.223.94:9999
185.243.115.219:9999
185.228.83.156:9999
chore: update seeds for v20.1 Don't forget to specify onion_seeds.txt: ``` cd contrib/seeds dash-cli protx list valid 1 > protx.txt ./makeseeds.py protx.txt onion_seeds.txt > nodes_main.txt ./generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-02-29 19:44:12 +01:00
185.217.127.139:9999
feat: add onion_seeds to seed creation; do seed creation (#5866) ## Issue being fixed or feature implemented We did not previously ship any onion seeds. This results in people needing to use `addnode` in order to actually get connected ## What was done? Modified seed creation process to handle a list of onion seeds. ## How Has This Been Tested? Running with and without onlynet=onion and with dnsseed=0 and deleting peers.dat ## Breaking Changes None ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_
2024-02-15 05:31:24 +01:00
185.216.13.118:9999
185.213.24.34:9999
chore: update seeds for v20.1 Don't forget to specify onion_seeds.txt: ``` cd contrib/seeds dash-cli protx list valid 1 > protx.txt ./makeseeds.py protx.txt onion_seeds.txt > nodes_main.txt ./generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-02-29 19:44:12 +01:00
185.185.40.249:9999
feat: add onion_seeds to seed creation; do seed creation (#5866) ## Issue being fixed or feature implemented We did not previously ship any onion seeds. This results in people needing to use `addnode` in order to actually get connected ## What was done? Modified seed creation process to handle a list of onion seeds. ## How Has This Been Tested? Running with and without onlynet=onion and with dnsseed=0 and deleting peers.dat ## Breaking Changes None ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_
2024-02-15 05:31:24 +01:00
185.165.171.117:9999
185.164.163.218:9999
185.164.163.85:9999
185.155.99.34:9999
185.142.212.144:9999
185.135.80.200:9999
185.103.132.7:9999
chore: update seeds for v20.1 Don't forget to specify onion_seeds.txt: ``` cd contrib/seeds dash-cli protx list valid 1 > protx.txt ./makeseeds.py protx.txt onion_seeds.txt > nodes_main.txt ./generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-02-29 19:44:12 +01:00
185.87.149.61:9999
feat: add onion_seeds to seed creation; do seed creation (#5866) ## Issue being fixed or feature implemented We did not previously ship any onion seeds. This results in people needing to use `addnode` in order to actually get connected ## What was done? Modified seed creation process to handle a list of onion seeds. ## How Has This Been Tested? Running with and without onlynet=onion and with dnsseed=0 and deleting peers.dat ## Breaking Changes None ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_
2024-02-15 05:31:24 +01:00
185.28.101.145:9999
178.208.87.226:9999
178.208.87.213:9999
178.159.2.12:9999
178.157.91.179:9999
178.157.91.176:9999
178.128.254.204:9999
178.63.121.129:9999
178.62.235.117:9999
chore: update seeds for v20.1 Don't forget to specify onion_seeds.txt: ``` cd contrib/seeds dash-cli protx list valid 1 > protx.txt ./makeseeds.py protx.txt onion_seeds.txt > nodes_main.txt ./generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-02-29 19:44:12 +01:00
176.126.127.16:9999
feat: add onion_seeds to seed creation; do seed creation (#5866) ## Issue being fixed or feature implemented We did not previously ship any onion seeds. This results in people needing to use `addnode` in order to actually get connected ## What was done? Modified seed creation process to handle a list of onion seeds. ## How Has This Been Tested? Running with and without onlynet=onion and with dnsseed=0 and deleting peers.dat ## Breaking Changes None ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_
2024-02-15 05:31:24 +01:00
176.126.127.15:9999
176.102.65.145:9999
174.34.233.207:9999
174.34.233.206:9999
174.34.233.204:9999
chore: update seeds for v20.1 Don't forget to specify onion_seeds.txt: ``` cd contrib/seeds dash-cli protx list valid 1 > protx.txt ./makeseeds.py protx.txt onion_seeds.txt > nodes_main.txt ./generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-02-29 19:44:12 +01:00
174.34.233.203:9999
feat: add onion_seeds to seed creation; do seed creation (#5866) ## Issue being fixed or feature implemented We did not previously ship any onion seeds. This results in people needing to use `addnode` in order to actually get connected ## What was done? Modified seed creation process to handle a list of onion seeds. ## How Has This Been Tested? Running with and without onlynet=onion and with dnsseed=0 and deleting peers.dat ## Breaking Changes None ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_
2024-02-15 05:31:24 +01:00
173.249.21.122:9999
172.105.21.21:9999
168.119.80.4:9999
chore: update seeds for v20.1 Don't forget to specify onion_seeds.txt: ``` cd contrib/seeds dash-cli protx list valid 1 > protx.txt ./makeseeds.py protx.txt onion_seeds.txt > nodes_main.txt ./generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-02-29 19:44:12 +01:00
167.88.169.16:9999
feat: add onion_seeds to seed creation; do seed creation (#5866) ## Issue being fixed or feature implemented We did not previously ship any onion seeds. This results in people needing to use `addnode` in order to actually get connected ## What was done? Modified seed creation process to handle a list of onion seeds. ## How Has This Been Tested? Running with and without onlynet=onion and with dnsseed=0 and deleting peers.dat ## Breaking Changes None ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_
2024-02-15 05:31:24 +01:00
165.22.234.135:9999
155.133.23.221:9999
150.158.48.6:9999
145.239.20.176:9999
142.202.205.95:9999
133.18.228.84:9999
chore: update seeds for v20.1 Don't forget to specify onion_seeds.txt: ``` cd contrib/seeds dash-cli protx list valid 1 > protx.txt ./makeseeds.py protx.txt onion_seeds.txt > nodes_main.txt ./generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-02-29 19:44:12 +01:00
130.162.233.186:9999
feat: add onion_seeds to seed creation; do seed creation (#5866) ## Issue being fixed or feature implemented We did not previously ship any onion seeds. This results in people needing to use `addnode` in order to actually get connected ## What was done? Modified seed creation process to handle a list of onion seeds. ## How Has This Been Tested? Running with and without onlynet=onion and with dnsseed=0 and deleting peers.dat ## Breaking Changes None ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_
2024-02-15 05:31:24 +01:00
130.61.120.252:9999
128.199.181.159:9999
chore: update seeds for v20.1 Don't forget to specify onion_seeds.txt: ``` cd contrib/seeds dash-cli protx list valid 1 > protx.txt ./makeseeds.py protx.txt onion_seeds.txt > nodes_main.txt ./generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-02-29 19:44:12 +01:00
123.193.64.166:9999
feat: add onion_seeds to seed creation; do seed creation (#5866) ## Issue being fixed or feature implemented We did not previously ship any onion seeds. This results in people needing to use `addnode` in order to actually get connected ## What was done? Modified seed creation process to handle a list of onion seeds. ## How Has This Been Tested? Running with and without onlynet=onion and with dnsseed=0 and deleting peers.dat ## Breaking Changes None ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_
2024-02-15 05:31:24 +01:00
109.235.70.100:9999
109.235.69.170:9999
109.235.65.95:9999
106.55.9.22:9999
chore: update seeds for v20.1 Don't forget to specify onion_seeds.txt: ``` cd contrib/seeds dash-cli protx list valid 1 > protx.txt ./makeseeds.py protx.txt onion_seeds.txt > nodes_main.txt ./generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-02-29 19:44:12 +01:00
104.238.35.116:9999
feat: add onion_seeds to seed creation; do seed creation (#5866) ## Issue being fixed or feature implemented We did not previously ship any onion seeds. This results in people needing to use `addnode` in order to actually get connected ## What was done? Modified seed creation process to handle a list of onion seeds. ## How Has This Been Tested? Running with and without onlynet=onion and with dnsseed=0 and deleting peers.dat ## Breaking Changes None ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_
2024-02-15 05:31:24 +01:00
104.238.35.114:9999
103.160.95.249:9999
103.160.95.225:9999
103.160.95.219:9999
chore: update seeds for v20.1 Don't forget to specify onion_seeds.txt: ``` cd contrib/seeds dash-cli protx list valid 1 > protx.txt ./makeseeds.py protx.txt onion_seeds.txt > nodes_main.txt ./generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-02-29 19:44:12 +01:00
95.211.196.46:9999
95.211.196.32:9999
95.211.196.8:9999
feat: add onion_seeds to seed creation; do seed creation (#5866) ## Issue being fixed or feature implemented We did not previously ship any onion seeds. This results in people needing to use `addnode` in order to actually get connected ## What was done? Modified seed creation process to handle a list of onion seeds. ## How Has This Been Tested? Running with and without onlynet=onion and with dnsseed=0 and deleting peers.dat ## Breaking Changes None ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_
2024-02-15 05:31:24 +01:00
95.183.53.44:9999
95.183.52.98:9999
95.183.51.141:9999
93.21.76.185:9999
chore: update seeds for v20.1 Don't forget to specify onion_seeds.txt: ``` cd contrib/seeds dash-cli protx list valid 1 > protx.txt ./makeseeds.py protx.txt onion_seeds.txt > nodes_main.txt ./generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-02-29 19:44:12 +01:00
91.137.11.31:9999
feat: add onion_seeds to seed creation; do seed creation (#5866) ## Issue being fixed or feature implemented We did not previously ship any onion seeds. This results in people needing to use `addnode` in order to actually get connected ## What was done? Modified seed creation process to handle a list of onion seeds. ## How Has This Been Tested? Running with and without onlynet=onion and with dnsseed=0 and deleting peers.dat ## Breaking Changes None ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_
2024-02-15 05:31:24 +01:00
89.179.73.96:9999
89.117.19.10:9999
chore: update seeds for v20.1 Don't forget to specify onion_seeds.txt: ``` cd contrib/seeds dash-cli protx list valid 1 > protx.txt ./makeseeds.py protx.txt onion_seeds.txt > nodes_main.txt ./generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-02-29 19:44:12 +01:00
89.73.105.198:9999
89.40.4.87:9999
feat: add onion_seeds to seed creation; do seed creation (#5866) ## Issue being fixed or feature implemented We did not previously ship any onion seeds. This results in people needing to use `addnode` in order to actually get connected ## What was done? Modified seed creation process to handle a list of onion seeds. ## How Has This Been Tested? Running with and without onlynet=onion and with dnsseed=0 and deleting peers.dat ## Breaking Changes None ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_
2024-02-15 05:31:24 +01:00
87.98.253.86:9999
85.215.107.202:9999
85.209.241.190:9999
85.209.241.188:9999
85.209.241.71:9999
85.209.241.35:9999
84.242.179.204:9999
84.9.50.17:9999
82.211.25.193:9999
82.211.25.105:9999
82.211.21.179:9999
82.211.21.23:9999
chore: update seeds for v20.1 Don't forget to specify onion_seeds.txt: ``` cd contrib/seeds dash-cli protx list valid 1 > protx.txt ./makeseeds.py protx.txt onion_seeds.txt > nodes_main.txt ./generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-02-29 19:44:12 +01:00
82.202.230.83:9999
feat: add onion_seeds to seed creation; do seed creation (#5866) ## Issue being fixed or feature implemented We did not previously ship any onion seeds. This results in people needing to use `addnode` in order to actually get connected ## What was done? Modified seed creation process to handle a list of onion seeds. ## How Has This Been Tested? Running with and without onlynet=onion and with dnsseed=0 and deleting peers.dat ## Breaking Changes None ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_
2024-02-15 05:31:24 +01:00
81.227.250.51:9999
80.209.234.170:9999
chore: update seeds for v20.1 Don't forget to specify onion_seeds.txt: ``` cd contrib/seeds dash-cli protx list valid 1 > protx.txt ./makeseeds.py protx.txt onion_seeds.txt > nodes_main.txt ./generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-02-29 19:44:12 +01:00
79.143.29.95:9999
feat: add onion_seeds to seed creation; do seed creation (#5866) ## Issue being fixed or feature implemented We did not previously ship any onion seeds. This results in people needing to use `addnode` in order to actually get connected ## What was done? Modified seed creation process to handle a list of onion seeds. ## How Has This Been Tested? Running with and without onlynet=onion and with dnsseed=0 and deleting peers.dat ## Breaking Changes None ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_
2024-02-15 05:31:24 +01:00
78.83.19.0:9999
77.232.132.89:9999
77.232.132.4:9999
77.223.99.4:9999
chore: update seeds for v20.1 Don't forget to specify onion_seeds.txt: ``` cd contrib/seeds dash-cli protx list valid 1 > protx.txt ./makeseeds.py protx.txt onion_seeds.txt > nodes_main.txt ./generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-02-29 19:44:12 +01:00
69.61.107.247:9999
feat: add onion_seeds to seed creation; do seed creation (#5866) ## Issue being fixed or feature implemented We did not previously ship any onion seeds. This results in people needing to use `addnode` in order to actually get connected ## What was done? Modified seed creation process to handle a list of onion seeds. ## How Has This Been Tested? Running with and without onlynet=onion and with dnsseed=0 and deleting peers.dat ## Breaking Changes None ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_
2024-02-15 05:31:24 +01:00
69.61.107.215:9999
66.244.243.70:9999
66.244.243.69:9999
58.110.224.166:9999
54.37.234.121:9999
52.33.9.172:9999
51.159.196.82:9999
51.158.169.237:9999
51.68.155.64:9999
51.15.117.42:9999
51.15.96.206:9999
47.243.56.197:9999
chore: update seeds for v20.1 Don't forget to specify onion_seeds.txt: ``` cd contrib/seeds dash-cli protx list valid 1 > protx.txt ./makeseeds.py protx.txt onion_seeds.txt > nodes_main.txt ./generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-02-29 19:44:12 +01:00
47.109.109.166:9999
feat: add onion_seeds to seed creation; do seed creation (#5866) ## Issue being fixed or feature implemented We did not previously ship any onion seeds. This results in people needing to use `addnode` in order to actually get connected ## What was done? Modified seed creation process to handle a list of onion seeds. ## How Has This Been Tested? Running with and without onlynet=onion and with dnsseed=0 and deleting peers.dat ## Breaking Changes None ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_
2024-02-15 05:31:24 +01:00
46.254.241.28:9999
46.254.241.21:9999
46.254.241.6:9999
46.254.241.4:9999
chore: update seeds for v20.1 Don't forget to specify onion_seeds.txt: ``` cd contrib/seeds dash-cli protx list valid 1 > protx.txt ./makeseeds.py protx.txt onion_seeds.txt > nodes_main.txt ./generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-02-29 19:44:12 +01:00
46.250.249.32:9999
46.72.31.9:9999
feat: add onion_seeds to seed creation; do seed creation (#5866) ## Issue being fixed or feature implemented We did not previously ship any onion seeds. This results in people needing to use `addnode` in order to actually get connected ## What was done? Modified seed creation process to handle a list of onion seeds. ## How Has This Been Tested? Running with and without onlynet=onion and with dnsseed=0 and deleting peers.dat ## Breaking Changes None ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_
2024-02-15 05:31:24 +01:00
46.36.40.242:9999
46.30.189.251:9999
chore: update seeds for v20.1 Don't forget to specify onion_seeds.txt: ``` cd contrib/seeds dash-cli protx list valid 1 > protx.txt ./makeseeds.py protx.txt onion_seeds.txt > nodes_main.txt ./generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-02-29 19:44:12 +01:00
46.30.189.214:9999
feat: add onion_seeds to seed creation; do seed creation (#5866) ## Issue being fixed or feature implemented We did not previously ship any onion seeds. This results in people needing to use `addnode` in order to actually get connected ## What was done? Modified seed creation process to handle a list of onion seeds. ## How Has This Been Tested? Running with and without onlynet=onion and with dnsseed=0 and deleting peers.dat ## Breaking Changes None ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_
2024-02-15 05:31:24 +01:00
46.30.189.213:9999
46.10.241.191:9999
46.4.162.127:9999
chore: update seeds for v20.1 Don't forget to specify onion_seeds.txt: ``` cd contrib/seeds dash-cli protx list valid 1 > protx.txt ./makeseeds.py protx.txt onion_seeds.txt > nodes_main.txt ./generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-02-29 19:44:12 +01:00
45.140.19.201:9999
feat: add onion_seeds to seed creation; do seed creation (#5866) ## Issue being fixed or feature implemented We did not previously ship any onion seeds. This results in people needing to use `addnode` in order to actually get connected ## What was done? Modified seed creation process to handle a list of onion seeds. ## How Has This Been Tested? Running with and without onlynet=onion and with dnsseed=0 and deleting peers.dat ## Breaking Changes None ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_
2024-02-15 05:31:24 +01:00
45.91.94.217:9999
45.86.163.42:9999
chore: update seeds for v20.1 Don't forget to specify onion_seeds.txt: ``` cd contrib/seeds dash-cli protx list valid 1 > protx.txt ./makeseeds.py protx.txt onion_seeds.txt > nodes_main.txt ./generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-02-29 19:44:12 +01:00
45.83.122.122:9999
45.79.40.205:9999
feat: add onion_seeds to seed creation; do seed creation (#5866) ## Issue being fixed or feature implemented We did not previously ship any onion seeds. This results in people needing to use `addnode` in order to actually get connected ## What was done? Modified seed creation process to handle a list of onion seeds. ## How Has This Been Tested? Running with and without onlynet=onion and with dnsseed=0 and deleting peers.dat ## Breaking Changes None ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_
2024-02-15 05:31:24 +01:00
45.77.169.207:9999
45.76.83.91:9999
45.71.159.104:9999
45.71.158.108:9999
45.71.158.58:9999
45.63.107.90:9999
45.58.56.221:9999
45.33.24.24:9999
45.11.182.64:9999
45.8.250.154:9999
45.8.248.145:9999
44.240.99.214:9999
43.229.77.46:9999
37.77.104.166:9999
31.148.99.104:9999
chore: update seeds for v20.1 Don't forget to specify onion_seeds.txt: ``` cd contrib/seeds dash-cli protx list valid 1 > protx.txt ./makeseeds.py protx.txt onion_seeds.txt > nodes_main.txt ./generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-02-29 19:44:12 +01:00
31.10.97.36:9999
feat: add onion_seeds to seed creation; do seed creation (#5866) ## Issue being fixed or feature implemented We did not previously ship any onion seeds. This results in people needing to use `addnode` in order to actually get connected ## What was done? Modified seed creation process to handle a list of onion seeds. ## How Has This Been Tested? Running with and without onlynet=onion and with dnsseed=0 and deleting peers.dat ## Breaking Changes None ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_
2024-02-15 05:31:24 +01:00
23.163.0.203:9999
18.139.244.9:9999
chore: update seeds for v20.1 Don't forget to specify onion_seeds.txt: ``` cd contrib/seeds dash-cli protx list valid 1 > protx.txt ./makeseeds.py protx.txt onion_seeds.txt > nodes_main.txt ./generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-02-29 19:44:12 +01:00
5.255.106.192:9999
feat: add onion_seeds to seed creation; do seed creation (#5866) ## Issue being fixed or feature implemented We did not previously ship any onion seeds. This results in people needing to use `addnode` in order to actually get connected ## What was done? Modified seed creation process to handle a list of onion seeds. ## How Has This Been Tested? Running with and without onlynet=onion and with dnsseed=0 and deleting peers.dat ## Breaking Changes None ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_
2024-02-15 05:31:24 +01:00
5.252.21.24:9999
5.189.239.52:9999
5.189.145.80:9999
chore: update seeds for v20.1 Don't forget to specify onion_seeds.txt: ``` cd contrib/seeds dash-cli protx list valid 1 > protx.txt ./makeseeds.py protx.txt onion_seeds.txt > nodes_main.txt ./generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-02-29 19:44:12 +01:00
5.181.202.44:9999
5.181.202.16:9999
5.161.110.79:9999
5.79.109.243:9999
feat: add onion_seeds to seed creation; do seed creation (#5866) ## Issue being fixed or feature implemented We did not previously ship any onion seeds. This results in people needing to use `addnode` in order to actually get connected ## What was done? Modified seed creation process to handle a list of onion seeds. ## How Has This Been Tested? Running with and without onlynet=onion and with dnsseed=0 and deleting peers.dat ## Breaking Changes None ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_
2024-02-15 05:31:24 +01:00
5.78.74.118:9999
5.35.103.111:9999
5.35.103.74:9999
5.35.103.64:9999
5.35.103.58:9999
5.9.237.34:9999
5.2.67.190:9999
chore: update seeds for v20.1 Don't forget to specify onion_seeds.txt: ``` cd contrib/seeds dash-cli protx list valid 1 > protx.txt ./makeseeds.py protx.txt onion_seeds.txt > nodes_main.txt ./generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-02-29 19:44:12 +01:00
3.82.241.57:9999
feat: add onion_seeds to seed creation; do seed creation (#5866) ## Issue being fixed or feature implemented We did not previously ship any onion seeds. This results in people needing to use `addnode` in order to actually get connected ## What was done? Modified seed creation process to handle a list of onion seeds. ## How Has This Been Tested? Running with and without onlynet=onion and with dnsseed=0 and deleting peers.dat ## Breaking Changes None ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_
2024-02-15 05:31:24 +01:00
3.35.224.65:9999
chore: update seeds for v20.1 Don't forget to specify onion_seeds.txt: ``` cd contrib/seeds dash-cli protx list valid 1 > protx.txt ./makeseeds.py protx.txt onion_seeds.txt > nodes_main.txt ./generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-02-29 19:44:12 +01:00
2.233.120.35:9999
feat: add onion_seeds to seed creation; do seed creation (#5866) ## Issue being fixed or feature implemented We did not previously ship any onion seeds. This results in people needing to use `addnode` in order to actually get connected ## What was done? Modified seed creation process to handle a list of onion seeds. ## How Has This Been Tested? Running with and without onlynet=onion and with dnsseed=0 and deleting peers.dat ## Breaking Changes None ## Checklist: - [x] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have added or updated relevant unit/integration/functional/e2e tests - [ ] I have made corresponding changes to the documentation - [x] I have assigned this pull request to a milestone _(for repository code-owners and collaborators only)_
2024-02-15 05:31:24 +01:00
2.56.213.221:9999
chore: update seeds for v20.1 Don't forget to specify onion_seeds.txt: ``` cd contrib/seeds dash-cli protx list valid 1 > protx.txt ./makeseeds.py protx.txt onion_seeds.txt > nodes_main.txt ./generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-02-29 19:44:12 +01:00
2.56.213.220:9999
Reference in New Issue Copy Permalink