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

171 lines
4.4 KiB
Plaintext
Raw Normal View History

chore: update seeds ```sh dash-cli protx list valid 1 2110129 > protx_list.json while IFS= read -r line do address=$(echo $line | cut -d':' -f1) port=$(echo $line | cut -d':' -f2) nc -v -x 127.0.0.1:9050 -z $address $port done < "onion_seeds.txt" python3 makeseeds.py protx_list.json onion_seeds.txt > nodes_main.txt python3 generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-07-24 19:24:56 +02:00
zmkohnwhp67nxtaspaudwvbac3r3oab4j36kxoo7ofk636wcd2bflxad.onion:9999
yvcukkjk6vsjliszrlhh3f4qal76w6n2hoi4hl4edp6b5zyifhcixoyd.onion: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
v7ttoiov7rc5aut64nfomyfwxt424ihufwvr5ilf7moeg3fwibjpjcqd.onion:9999
chore: update seeds ```sh dash-cli protx list valid 1 2110129 > protx_list.json while IFS= read -r line do address=$(echo $line | cut -d':' -f1) port=$(echo $line | cut -d':' -f2) nc -v -x 127.0.0.1:9050 -z $address $port done < "onion_seeds.txt" python3 makeseeds.py protx_list.json onion_seeds.txt > nodes_main.txt python3 generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-07-24 19:24:56 +02:00
tuzjyti6guw32smcxgswmt2fkjlkyxnt47rtspvmqerbalzdeyguczyd.onion: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
snu2xaql3crh2b4t6g2wxemgrpzmaxfxla4tua63bnp2phhxwr6hzzid.onion:9999
chore: update seeds ```sh dash-cli protx list valid 1 2110129 > protx_list.json while IFS= read -r line do address=$(echo $line | cut -d':' -f1) port=$(echo $line | cut -d':' -f2) nc -v -x 127.0.0.1:9050 -z $address $port done < "onion_seeds.txt" python3 makeseeds.py protx_list.json onion_seeds.txt > nodes_main.txt python3 generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-07-24 19:24:56 +02:00
qkcdtz6ejiycge6i3g6uyf6m4ivby7t77syt7yezlwwhtmbsk37u74yd.onion:9999
pcabrbxdlxgybiyykuiccajsfzazmigvc7cemqbzpqw5du27iqaihmyd.onion:9999
nl7j4rwrb2yemyn5meu64jfbfj5pkeuyo73afihtjdytsh6fpiibkrad.onion:9999
njmniixuv2ji4an6lfqol6d3bqbijt7cko6wpfgc2wyxe2jg5htwoiad.onion:9999
mn3zcamezyz5fryftzvmenv4vtbv5ki2eodxugq5gjwka7fft7po4uid.onion:9999
l2ae5ngumxbcoqwpaxquxq7p6fwtvgfqbokrm7vqiaho4rkijd4ssmyd.onion:9999
k6bzqtkhtzyziethin3kkys342rlzcmqkrs5ibashqclcu23ehuz6oqd.onion: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
k532fqvgzqotj6epfw3rfc377elrj3td47ztad2tkn6vwnw6nhxacrqd.onion:9999
chore: update seeds ```sh dash-cli protx list valid 1 2110129 > protx_list.json while IFS= read -r line do address=$(echo $line | cut -d':' -f1) port=$(echo $line | cut -d':' -f2) nc -v -x 127.0.0.1:9050 -z $address $port done < "onion_seeds.txt" python3 makeseeds.py protx_list.json onion_seeds.txt > nodes_main.txt python3 generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-07-24 19:24:56 +02:00
itkatc2gpfkuvbmjflxgranktjrsokc7wcunu25mq7ptqms7fwex6jyd.onion:9999
iekgzhetngwhhf7rfxglb3mdwajtoikpcvg3e3etpx4ylku6chr6jrqd.onion:9999
i75yxbzhzkk6q55oig6xeidcexswpgcbquhjuxkkwehy6rvjq6sjxmad.onion:9999
h2cpqmjd3rqehro52stehi4vnyofxymfqdsexchhf7dpbbkoqkmjjiyd.onion:9999
gbg2wd4uwc5k7w5j3w46zre6r5ioezulgjriketxv4qekybzg2zwdnid.onion:9999
g6qaacqm3z6xup6kmprb2uvb5wtv3a4isflh4aege2yfgpuvaozfnkad.onion:9999
eee7cdynbju7pax44vm3bo7aazi72qbqgwktpvk37hoxg7jkqez2kcad.onion: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
cmhr5r3lqhy7ic2ebeil66ftcz5u62zq5qhbfdz53l6sqxljh7zxntyd.onion:9999
chore: update seeds ```sh dash-cli protx list valid 1 2110129 > protx_list.json while IFS= read -r line do address=$(echo $line | cut -d':' -f1) port=$(echo $line | cut -d':' -f2) nc -v -x 127.0.0.1:9050 -z $address $port done < "onion_seeds.txt" python3 makeseeds.py protx_list.json onion_seeds.txt > nodes_main.txt python3 generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-07-24 19:24:56 +02:00
buo3et3xvzdjqkpx6iscjz4oexyurhpbpl3is46d653kfitl2gdzm6yd.onion: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
5v5lgddolcidtt2qmhmvyka2ewht4mkmmj73tfwuimlckgmqb5lthtid.onion:9999
chore: update seeds ```sh dash-cli protx list valid 1 2110129 > protx_list.json while IFS= read -r line do address=$(echo $line | cut -d':' -f1) port=$(echo $line | cut -d':' -f2) nc -v -x 127.0.0.1:9050 -z $address $port done < "onion_seeds.txt" python3 makeseeds.py protx_list.json onion_seeds.txt > nodes_main.txt python3 generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-07-24 19:24:56 +02:00
467ho3bhmndzbktbqd3nxf64isib54umiis5xc5n2xnt35u2ofhs5gid.onion:9999
2h6yzlqtogqkaj4yhrofsccntpjyafpjxwutti65dkpqliuzah3is7ad.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
chore: update seeds ```sh dash-cli protx list valid 1 2110129 > protx_list.json while IFS= read -r line do address=$(echo $line | cut -d':' -f1) port=$(echo $line | cut -d':' -f2) nc -v -x 127.0.0.1:9050 -z $address $port done < "onion_seeds.txt" python3 makeseeds.py protx_list.json onion_seeds.txt > nodes_main.txt python3 generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-07-24 19:24:56 +02:00
216.189.154.7: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.24.110.128:9999
212.24.107.223:9999
207.244.247.40:9999
chore: update seeds ```sh dash-cli protx list valid 1 2110129 > protx_list.json while IFS= read -r line do address=$(echo $line | cut -d':' -f1) port=$(echo $line | cut -d':' -f2) nc -v -x 127.0.0.1:9050 -z $address $port done < "onion_seeds.txt" python3 makeseeds.py protx_list.json onion_seeds.txt > nodes_main.txt python3 generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-07-24 19:24:56 +02:00
206.189.132.224:9999
206.168.213.108: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
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
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
194.158.71.228:9999
194.135.81.214:9999
193.164.149.50:9999
chore: update seeds ```sh dash-cli protx list valid 1 2110129 > protx_list.json while IFS= read -r line do address=$(echo $line | cut -d':' -f1) port=$(echo $line | cut -d':' -f2) nc -v -x 127.0.0.1:9050 -z $address $port done < "onion_seeds.txt" python3 makeseeds.py protx_list.json onion_seeds.txt > nodes_main.txt python3 generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-07-24 19:24:56 +02:00
193.31.30.55: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.230.40:9999
188.68.223.94:9999
185.243.115.219:9999
185.213.24.34:9999
185.165.171.117:9999
185.164.163.218:9999
185.164.163.85:9999
185.135.80.200: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
178.208.87.226:9999
178.208.87.213:9999
178.157.91.179:9999
178.157.91.176:9999
chore: update seeds ```sh dash-cli protx list valid 1 2110129 > protx_list.json while IFS= read -r line do address=$(echo $line | cut -d':' -f1) port=$(echo $line | cut -d':' -f2) nc -v -x 127.0.0.1:9050 -z $address $port done < "onion_seeds.txt" python3 makeseeds.py protx_list.json onion_seeds.txt > nodes_main.txt python3 generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-07-24 19:24:56 +02:00
178.157.91.126: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
178.63.121.129: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
174.34.233.207:9999
174.34.233.206:9999
chore: update seeds ```sh dash-cli protx list valid 1 2110129 > protx_list.json while IFS= read -r line do address=$(echo $line | cut -d':' -f1) port=$(echo $line | cut -d':' -f2) nc -v -x 127.0.0.1:9050 -z $address $port done < "onion_seeds.txt" python3 makeseeds.py protx_list.json onion_seeds.txt > nodes_main.txt python3 generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-07-24 19:24:56 +02:00
174.34.233.205:9999
174.34.233.202: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
chore: update seeds ```sh dash-cli protx list valid 1 2110129 > protx_list.json while IFS= read -r line do address=$(echo $line | cut -d':' -f1) port=$(echo $line | cut -d':' -f2) nc -v -x 127.0.0.1:9050 -z $address $port done < "onion_seeds.txt" python3 makeseeds.py protx_list.json onion_seeds.txt > nodes_main.txt python3 generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-07-24 19:24:56 +02:00
172.104.90.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
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
chore: update seeds ```sh dash-cli protx list valid 1 2110129 > protx_list.json while IFS= read -r line do address=$(echo $line | cut -d':' -f1) port=$(echo $line | cut -d':' -f2) nc -v -x 127.0.0.1:9050 -z $address $port done < "onion_seeds.txt" python3 makeseeds.py protx_list.json onion_seeds.txt > nodes_main.txt python3 generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-07-24 19:24:56 +02:00
159.89.124.102: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
155.133.23.221:9999
150.158.48.6:9999
145.239.20.176:9999
chore: update seeds ```sh dash-cli protx list valid 1 2110129 > protx_list.json while IFS= read -r line do address=$(echo $line | cut -d':' -f1) port=$(echo $line | cut -d':' -f2) nc -v -x 127.0.0.1:9050 -z $address $port done < "onion_seeds.txt" python3 makeseeds.py protx_list.json onion_seeds.txt > nodes_main.txt python3 generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-07-24 19:24:56 +02:00
144.91.127.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
142.202.205.95:9999
chore: update seeds ```sh dash-cli protx list valid 1 2110129 > protx_list.json while IFS= read -r line do address=$(echo $line | cut -d':' -f1) port=$(echo $line | cut -d':' -f2) nc -v -x 127.0.0.1:9050 -z $address $port done < "onion_seeds.txt" python3 makeseeds.py protx_list.json onion_seeds.txt > nodes_main.txt python3 generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-07-24 19:24:56 +02:00
139.59.100.103: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
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
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
chore: update seeds ```sh dash-cli protx list valid 1 2110129 > protx_list.json while IFS= read -r line do address=$(echo $line | cut -d':' -f1) port=$(echo $line | cut -d':' -f2) nc -v -x 127.0.0.1:9050 -z $address $port done < "onion_seeds.txt" python3 makeseeds.py protx_list.json onion_seeds.txt > nodes_main.txt python3 generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-07-24 19:24:56 +02:00
109.235.65.226: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.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
chore: update seeds ```sh dash-cli protx list valid 1 2110129 > protx_list.json while IFS= read -r line do address=$(echo $line | cut -d':' -f1) port=$(echo $line | cut -d':' -f2) nc -v -x 127.0.0.1:9050 -z $address $port done < "onion_seeds.txt" python3 makeseeds.py protx_list.json onion_seeds.txt > nodes_main.txt python3 generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-07-24 19:24:56 +02:00
104.200.67.251:9999
104.200.24.196: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
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.51.141:9999
93.21.76.185:9999
89.179.73.96:9999
89.117.19.10: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
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
78.83.19.0:9999
77.232.132.89:9999
77.232.132.4:9999
77.223.99.4: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
chore: update seeds ```sh dash-cli protx list valid 1 2110129 > protx_list.json while IFS= read -r line do address=$(echo $line | cut -d':' -f1) port=$(echo $line | cut -d':' -f2) nc -v -x 127.0.0.1:9050 -z $address $port done < "onion_seeds.txt" python3 makeseeds.py protx_list.json onion_seeds.txt > nodes_main.txt python3 generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-07-24 19:24:56 +02:00
51.158.243.250: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
51.158.169.237:9999
chore: update seeds ```sh dash-cli protx list valid 1 2110129 > protx_list.json while IFS= read -r line do address=$(echo $line | cut -d':' -f1) port=$(echo $line | cut -d':' -f2) nc -v -x 127.0.0.1:9050 -z $address $port done < "onion_seeds.txt" python3 makeseeds.py protx_list.json onion_seeds.txt > nodes_main.txt python3 generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-07-24 19:24:56 +02:00
51.79.160.197: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
51.68.155.64:9999
51.15.117.42:9999
51.15.96.206: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.21:9999
46.254.241.4:9999
46.36.40.242: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
chore: update seeds ```sh dash-cli protx list valid 1 2110129 > protx_list.json while IFS= read -r line do address=$(echo $line | cut -d':' -f1) port=$(echo $line | cut -d':' -f2) nc -v -x 127.0.0.1:9050 -z $address $port done < "onion_seeds.txt" python3 makeseeds.py protx_list.json onion_seeds.txt > nodes_main.txt python3 generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-07-24 19:24:56 +02:00
46.30.189.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
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
chore: update seeds ```sh dash-cli protx list valid 1 2110129 > protx_list.json while IFS= read -r line do address=$(echo $line | cut -d':' -f1) port=$(echo $line | cut -d':' -f2) nc -v -x 127.0.0.1:9050 -z $address $port done < "onion_seeds.txt" python3 makeseeds.py protx_list.json onion_seeds.txt > nodes_main.txt python3 generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-07-24 19:24:56 +02:00
45.93.139.117: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
chore: update seeds ```sh dash-cli protx list valid 1 2110129 > protx_list.json while IFS= read -r line do address=$(echo $line | cut -d':' -f1) port=$(echo $line | cut -d':' -f2) nc -v -x 127.0.0.1:9050 -z $address $port done < "onion_seeds.txt" python3 makeseeds.py protx_list.json onion_seeds.txt > nodes_main.txt python3 generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-07-24 19:24:56 +02:00
45.85.117.169:9999
45.85.117.40: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
chore: update seeds ```sh dash-cli protx list valid 1 2110129 > protx_list.json while IFS= read -r line do address=$(echo $line | cut -d':' -f1) port=$(echo $line | cut -d':' -f2) nc -v -x 127.0.0.1:9050 -z $address $port done < "onion_seeds.txt" python3 makeseeds.py protx_list.json onion_seeds.txt > nodes_main.txt python3 generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-07-24 19:24:56 +02:00
45.79.18.106: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.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
chore: update seeds ```sh dash-cli protx list valid 1 2110129 > protx_list.json while IFS= read -r line do address=$(echo $line | cut -d':' -f1) port=$(echo $line | cut -d':' -f2) nc -v -x 127.0.0.1:9050 -z $address $port done < "onion_seeds.txt" python3 makeseeds.py protx_list.json onion_seeds.txt > nodes_main.txt python3 generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-07-24 19:24:56 +02:00
45.32.159.48: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.11.182.64:9999
45.8.250.154:9999
44.240.99.214: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
chore: update seeds ```sh dash-cli protx list valid 1 2110129 > protx_list.json while IFS= read -r line do address=$(echo $line | cut -d':' -f1) port=$(echo $line | cut -d':' -f2) nc -v -x 127.0.0.1:9050 -z $address $port done < "onion_seeds.txt" python3 makeseeds.py protx_list.json onion_seeds.txt > nodes_main.txt python3 generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-07-24 19:24:56 +02:00
23.163.0.175:9999
13.251.11.55: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
chore: update seeds ```sh dash-cli protx list valid 1 2110129 > protx_list.json while IFS= read -r line do address=$(echo $line | cut -d':' -f1) port=$(echo $line | cut -d':' -f2) nc -v -x 127.0.0.1:9050 -z $address $port done < "onion_seeds.txt" python3 makeseeds.py protx_list.json onion_seeds.txt > nodes_main.txt python3 generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-07-24 19:24:56 +02:00
5.189.253.252: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.189.239.52:9999
5.189.145.80:9999
chore: update seeds ```sh dash-cli protx list valid 1 2110129 > protx_list.json while IFS= read -r line do address=$(echo $line | cut -d':' -f1) port=$(echo $line | cut -d':' -f2) nc -v -x 127.0.0.1:9050 -z $address $port done < "onion_seeds.txt" python3 makeseeds.py protx_list.json onion_seeds.txt > nodes_main.txt python3 generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-07-24 19:24:56 +02:00
5.181.202.15: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.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
chore: update seeds ```sh dash-cli protx list valid 1 2110129 > protx_list.json while IFS= read -r line do address=$(echo $line | cut -d':' -f1) port=$(echo $line | cut -d':' -f2) nc -v -x 127.0.0.1:9050 -z $address $port done < "onion_seeds.txt" python3 makeseeds.py protx_list.json onion_seeds.txt > nodes_main.txt python3 generate-seeds.py . > ../../src/chainparamsseeds.h ```
2024-07-24 19:24:56 +02:00
5.2.73.58: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
2.56.213.221:9999
Reference in New Issue Copy Permalink