sikkienl/dash
1
0
Fork 0
mirror of https://github.com/dashpay/dash.git synced 2024-12-26 04:22:55 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity
19310646e0
dash/src/chainparamsseeds.h

188 lines
11 KiB
C
Raw Normal View History

Merge #12757: Clarify include guard naming convention 3bcc0059b8 Add lint-include-guards.sh which checks include guard consistency (practicalswift) 8fd6af89a0 Fix missing or inconsistent include guards (practicalswift) 8af65d96f4 Document include guard convention (practicalswift) Pull request description: * **Documentation**: Document include guard convention * **Fix**: Fix missing or inconsistent include guards * **Regression test**: Add `lint-include-guards.sh` which checks include guard consistency Tree-SHA512: 8171878f60fd08ccbea943a11e835195750592abb9d7ab74eaa4265ae7fac523b1da9d31ca13d6ab73dd596e49986bfb7593c696e5f39567c93e610165bc2acc Signed-off-by: pasta <pasta@dashboost.org> # Conflicts: # src/bech32.h # src/consensus/merkle.h # src/key_io.h # src/policy/fees.h # src/rpc/server.h # src/script/bitcoinconsensus.h # src/wallet/coinselection.h
2018-04-02 00:30:17 +02:00
#ifndef BITCOIN_CHAINPARAMSSEEDS_H
#define BITCOIN_CHAINPARAMSSEEDS_H
Update comments in chainparams to be doxygen compatible
2014-10-25 11:24:16 +02:00
/**
Use masternode list to generate hardcoded seeds (#1892) * Change makeseeds.py to use masternode list as input instead of DNS seed dump * Allow 4 nodes per ASN Lift the limitation a bit so we get more entries * Update nodes_main.txt and nodes_test.txt Generated with makeseeds.py based on current masternode lists * Fix comment about the source of the seed nodes and use masternodelist rpc * Use fixed OpenDNS servers for ASN filtering
2018-02-05 16:39:26 +01:00
* List of fixed seed nodes for the dash network
Hardcoded seeds update June 2015
2015-06-25 08:04:03 +02:00
* AUTOGENERATED by contrib/seeds/generate-seeds.py
Fix all header defines
2014-11-03 16:16:40 +01:00
*
partial bitcoin#21560: Add Tor v3 hardcoded seeds excludes: - 2a257de113fd31539b68c28c47ef94f257b6e427 - 9b29d5df7fc555eaea42029f334f2995c6ccde3d
2023-09-10 16:10:08 +02:00
* Each line contains a BIP155 serialized (networkID, addr, port) tuple.
Update comments in chainparams to be doxygen compatible
2014-10-25 11:24:16 +02:00
*/
partial bitcoin#21560: Add Tor v3 hardcoded seeds excludes: - 2a257de113fd31539b68c28c47ef94f257b6e427 - 9b29d5df7fc555eaea42029f334f2995c6ccde3d
2023-09-10 16:10:08 +02:00
static const uint8_t chainparams_seed_main[] = {
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
0x04,0x20,0xcb,0x14,0xe3,0xb6,0xc7,0x7f,0xbe,0xdb,0xcc,0x12,0x78,0x28,0x3b,0x54,0x20,0x16,0xe3,0xb7,0x00,0x3c,0x4e,0xfc,0xab,0xb9,0xdf,0x71,0x55,0xed,0xfa,0xc2,0x1e,0x82,0x27,0x0f,
0x04,0x20,0xc5,0x45,0x45,0x29,0x2a,0xf5,0x64,0x95,0xa2,0x59,0x8a,0xce,0x7d,0x97,0x90,0x02,0xff,0xeb,0x79,0xba,0x3b,0x91,0xc3,0xaf,0x84,0x1b,0xfc,0x1e,0xe7,0x08,0x29,0xc4,0x27,0x0f,
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
0x04,0x20,0xaf,0xe7,0x37,0x21,0xd5,0xfc,0x45,0xd0,0x52,0x7e,0xe3,0x4a,0xe6,0x60,0xb6,0xbc,0xf9,0xae,0x20,0xf4,0x2d,0xab,0x1e,0xa1,0x65,0xfb,0x1c,0x43,0x6c,0xb6,0x40,0x52,0x27,0x0f,
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
0x04,0x20,0x9d,0x32,0x9c,0x4d,0x1e,0x35,0x2d,0xbd,0x49,0x82,0xb9,0xa5,0x66,0x4f,0x45,0x52,0x56,0xac,0x5d,0xb3,0xe7,0xe3,0x39,0x3e,0xac,0x81,0x22,0x10,0x2f,0x23,0x26,0x0d,0x27,0x0f,
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
0x04,0x20,0x93,0x69,0xab,0x82,0x0b,0xd8,0xa2,0x7d,0x07,0x93,0xf1,0xb5,0x6b,0x91,0x86,0x8b,0xf2,0xc0,0x5c,0xb7,0x58,0x39,0x3a,0x03,0xdb,0x0b,0x5f,0xa7,0x9c,0xf7,0xb4,0x7c,0x27,0x0f,
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
0x04,0x20,0x82,0x84,0x39,0xe7,0xc4,0x4a,0x30,0x23,0x13,0xc8,0xd9,0xbd,0x4c,0x17,0xcc,0xe2,0x2a,0x1c,0x7e,0x7f,0xfc,0xb1,0x3f,0xe0,0x99,0x5d,0xac,0x79,0xb0,0x32,0x56,0xff,0x27,0x0f,
0x04,0x20,0x78,0x80,0x18,0x86,0xe3,0x5d,0xcd,0x80,0xa3,0x18,0x55,0x10,0x21,0x01,0x32,0x2e,0x41,0x96,0x20,0xd5,0x17,0xc4,0x46,0x40,0x39,0x7c,0x2d,0xd1,0xd3,0x5f,0x44,0x00,0x27,0x0f,
0x04,0x20,0x6a,0xfe,0x9e,0x46,0xd1,0x0e,0xb0,0x46,0x61,0xbd,0x61,0x29,0xee,0x24,0xa1,0x2a,0x7a,0xf5,0x12,0x98,0x77,0xf6,0x02,0xa0,0xf3,0x48,0xf1,0x39,0x1f,0xc5,0x7a,0x10,0x27,0x0f,
0x04,0x20,0x6a,0x58,0xd4,0x22,0xf4,0xae,0x92,0x8e,0x01,0xbe,0x59,0x60,0xe5,0xf8,0x7b,0x0c,0x02,0x84,0xcf,0xe2,0x53,0xbd,0x67,0x94,0xc2,0xd5,0xb1,0x72,0x69,0x26,0xe9,0xe7,0x27,0x0f,
0x04,0x20,0x63,0x77,0x91,0x01,0x84,0xce,0x33,0xd2,0xc7,0x05,0x9e,0x6a,0xc2,0x36,0xbc,0xac,0xc3,0x5e,0xa9,0x1a,0x23,0x87,0x7a,0x1a,0x1d,0x32,0x6c,0xa0,0x7c,0xa5,0x9f,0xde,0x27,0x0f,
0x04,0x20,0x5e,0x80,0x4e,0xb4,0xd4,0x65,0xc2,0x27,0x42,0xcf,0x05,0xe1,0x4b,0xc3,0xef,0xf1,0x6d,0x3a,0x98,0xb0,0x0b,0x95,0x16,0x7e,0xb0,0x40,0x0e,0xee,0x45,0x48,0x48,0xf9,0x27,0x0f,
0x04,0x20,0x57,0x83,0x98,0x4d,0x47,0x9e,0x71,0x94,0x12,0x67,0x43,0x76,0xa5,0x62,0x5b,0xe6,0xa2,0xbc,0x89,0x90,0x54,0x65,0xd4,0x04,0x12,0x3c,0x04,0xb1,0x53,0x5b,0x21,0xe9,0x27,0x0f,
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
0x04,0x20,0x57,0x77,0xa2,0xc2,0xa6,0xcc,0x1d,0x34,0xf8,0x8f,0x2d,0xb7,0x12,0x8b,0x7f,0xf9,0x17,0x14,0xee,0x63,0xe7,0xf3,0x30,0x0f,0x53,0x53,0x7d,0x5b,0x36,0xde,0x69,0xee,0x27,0x0f,
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
0x04,0x20,0x44,0xd4,0x09,0x8b,0x46,0x79,0x55,0x4a,0x85,0x89,0x2a,0xee,0x68,0x81,0xaa,0x9a,0x63,0x27,0x28,0x5f,0xb0,0xa8,0xda,0x6b,0xac,0x87,0xdf,0x38,0x32,0x5f,0x2d,0x89,0x27,0x0f,
0x04,0x20,0x41,0x14,0x6c,0x9c,0x93,0x69,0xac,0x73,0x97,0xf1,0x2d,0xcc,0xb0,0xed,0x83,0xb0,0x13,0x37,0x21,0x4f,0x15,0x4d,0xb2,0x6c,0x93,0x7d,0xf9,0x85,0xaa,0x9e,0x11,0xe3,0x27,0x0f,
0x04,0x20,0x47,0xfb,0x8b,0x87,0x27,0xca,0x95,0xe8,0x77,0xae,0x41,0xbd,0x72,0x20,0x62,0x25,0xe5,0x67,0x98,0x41,0x85,0x0e,0x9a,0x5d,0x4a,0xb1,0x0f,0x8f,0x46,0xa9,0x87,0xa4,0x27,0x0f,
0x04,0x20,0x3e,0x84,0xf8,0x31,0x23,0xdc,0x60,0x43,0xc5,0xdd,0xd4,0xa6,0x43,0xa3,0x95,0x6e,0x1c,0x5b,0xe1,0x85,0x80,0xe4,0x4b,0x88,0xe7,0x2f,0xc6,0xf0,0x85,0x4e,0x82,0x98,0x27,0x0f,
0x04,0x20,0x30,0x4d,0xab,0x0f,0x94,0xb0,0xba,0xaf,0xdb,0xa9,0xdd,0xb9,0xec,0xc4,0x9e,0x8f,0x50,0xe2,0x66,0x8b,0x32,0x62,0x85,0x12,0x77,0xaf,0x20,0x45,0x60,0x39,0x36,0xb3,0x27,0x0f,
0x04,0x20,0x37,0xa0,0x00,0x0a,0x0c,0xde,0x7d,0x7a,0x3f,0xca,0x63,0xe2,0x1d,0x52,0xa1,0xed,0xa7,0x5d,0x83,0x88,0x91,0x56,0x7e,0x00,0x86,0x26,0xb0,0x53,0x3e,0x95,0x03,0xb2,0x27,0x0f,
0x04,0x20,0x21,0x09,0xf1,0x0f,0x0d,0x0a,0x69,0xf7,0x82,0xfc,0xe5,0x59,0xb0,0xbb,0xe0,0x06,0x51,0xfd,0x40,0x30,0x35,0x95,0x37,0xd5,0x5b,0xf9,0xdd,0x73,0x7d,0x2a,0x81,0x33,0x27,0x0f,
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
0x04,0x20,0x13,0x0f,0x1e,0xc7,0x6b,0x81,0xf1,0xf4,0x0b,0x44,0x09,0x10,0xbf,0x78,0xb3,0x16,0x7b,0x4f,0x6b,0x30,0xec,0x0e,0x12,0x8f,0x3d,0xda,0xfd,0x28,0x5d,0x69,0x3f,0xf3,0x27,0x0f,
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
0x04,0x20,0x0d,0x1d,0xb2,0x4f,0x77,0xae,0x46,0x98,0x29,0xf7,0xf2,0x24,0x24,0xe7,0x8e,0x25,0xf1,0x48,0x9d,0xe1,0x7a,0xf6,0x89,0x73,0xc3,0xf7,0x76,0xa2,0xa2,0x6b,0xd1,0x87,0x27,0x0f,
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
0x04,0x20,0xed,0x7a,0xb3,0x0c,0x6e,0x58,0x90,0x39,0xcf,0x50,0x61,0xd9,0x5c,0x28,0x1a,0x25,0x8f,0x3e,0x31,0x4c,0x62,0x7f,0xb9,0x96,0xd4,0x43,0x16,0x25,0x19,0x90,0x0f,0x57,0x27,0x0f,
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
0x04,0x20,0xe7,0xbe,0x77,0x6c,0x27,0x63,0x47,0x90,0xaa,0x61,0x80,0xf6,0xdb,0x97,0xdc,0x44,0x90,0x1e,0xf2,0x8c,0x42,0x25,0xdb,0x8b,0xad,0xd5,0xdb,0x3d,0xf6,0x9a,0x71,0x4f,0x27,0x0f,
0x04,0x20,0xd1,0xfd,0x8c,0xae,0x13,0x71,0xa0,0xa0,0x27,0x98,0x3c,0x5c,0x59,0x08,0x4d,0x9b,0xd3,0x80,0x15,0xe9,0xbd,0xa9,0x39,0xa3,0xdd,0x1a,0x9f,0x05,0xa2,0x99,0x01,0xf6,0x27,0x0f,
0x01,0x04,0xd8,0xfa,0x61,0x34,0x27,0x0f,
0x01,0x04,0xd8,0xee,0x4b,0x2e,0x27,0x0f,
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
0x01,0x04,0xd8,0xe6,0xe8,0x7d,0x27,0x0f,
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
0x01,0x04,0xd8,0xbd,0x9a,0x08,0x27,0x0f,
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
0x01,0x04,0xd8,0xbd,0x9a,0x07,0x27,0x0f,
0x01,0x04,0xd5,0xa8,0xf9,0xae,0x27,0x0f,
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
0x01,0x04,0xd4,0x18,0x6e,0x80,0x27,0x0f,
0x01,0x04,0xd4,0x18,0x6b,0xdf,0x27,0x0f,
0x01,0x04,0xcf,0xf4,0xf7,0x28,0x27,0x0f,
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
0x01,0x04,0xce,0xbd,0x84,0xe0,0x27,0x0f,
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
0x01,0x04,0xce,0xa8,0xd5,0x6c,0x27,0x0f,
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
0x01,0x04,0xce,0xa8,0xd4,0xe2,0x27,0x0f,
0x01,0x04,0xce,0xa8,0xd4,0xb2,0x27,0x0f,
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
0x01,0x04,0xce,0xa8,0xd4,0x90,0x27,0x0f,
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
0x01,0x04,0xc2,0x9e,0x47,0xe4,0x27,0x0f,
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
0x01,0x04,0xc2,0x87,0x51,0xd6,0x27,0x0f,
0x01,0x04,0xc1,0xa4,0x95,0x32,0x27,0x0f,
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
0x01,0x04,0xc1,0x1f,0x1e,0x37,0x27,0x0f,
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
0x01,0x04,0xbc,0xd0,0xc4,0xb7,0x27,0x0f,
0x01,0x04,0xbc,0x7f,0xe6,0x28,0x27,0x0f,
0x01,0x04,0xbc,0x44,0xdf,0x5e,0x27,0x0f,
0x01,0x04,0xb9,0xf3,0x73,0xdb,0x27,0x0f,
0x01,0x04,0xb9,0xd5,0x18,0x22,0x27,0x0f,
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
0x01,0x04,0xb9,0xa5,0xab,0x75,0x27,0x0f,
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
0x01,0x04,0xb9,0xa4,0xa3,0xda,0x27,0x0f,
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
0x01,0x04,0xb9,0xa4,0xa3,0x55,0x27,0x0f,
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
0x01,0x04,0xb9,0x87,0x50,0xc8,0x27,0x0f,
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
0x01,0x04,0xb9,0x57,0x95,0x3d,0x27,0x0f,
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
0x01,0x04,0xb2,0xd0,0x57,0xe2,0x27,0x0f,
0x01,0x04,0xb2,0xd0,0x57,0xd5,0x27,0x0f,
0x01,0x04,0xb2,0x9d,0x5b,0xb3,0x27,0x0f,
0x01,0x04,0xb2,0x9d,0x5b,0xb0,0x27,0x0f,
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
0x01,0x04,0xb2,0x9d,0x5b,0x7e,0x27,0x0f,
0x01,0x04,0xb2,0x3f,0x79,0x81,0x27,0x0f,
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
0x01,0x04,0xb0,0x7e,0x7f,0x10,0x27,0x0f,
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
0x01,0x04,0xb0,0x7e,0x7f,0x0f,0x27,0x0f,
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
0x01,0x04,0xae,0x22,0xe9,0xcf,0x27,0x0f,
0x01,0x04,0xae,0x22,0xe9,0xce,0x27,0x0f,
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
0x01,0x04,0xae,0x22,0xe9,0xcd,0x27,0x0f,
0x01,0x04,0xae,0x22,0xe9,0xca,0x27,0x0f,
0x01,0x04,0xad,0xf9,0x15,0x7a,0x27,0x0f,
0x01,0x04,0xac,0x68,0x5a,0xf9,0x27,0x0f,
0x01,0x04,0xa8,0x77,0x50,0x04,0x27,0x0f,
0x01,0x04,0xa7,0x58,0xa9,0x10,0x27,0x0f,
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
0x01,0x04,0xa5,0x16,0xea,0x87,0x27,0x0f,
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
0x01,0x04,0x9f,0x59,0x7c,0x66,0x27,0x0f,
0x01,0x04,0x9b,0x85,0x17,0xdd,0x27,0x0f,
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
0x01,0x04,0x96,0x9e,0x30,0x06,0x27,0x0f,
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
0x01,0x04,0x91,0xef,0x14,0xb0,0x27,0x0f,
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
0x01,0x04,0x90,0x5b,0x7f,0xa6,0x27,0x0f,
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
0x01,0x04,0x8e,0xca,0xcd,0x5f,0x27,0x0f,
0x01,0x04,0x8b,0x3b,0x64,0x67,0x27,0x0f,
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
0x01,0x04,0x85,0x12,0xe4,0x54,0x27,0x0f,
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
0x01,0x04,0x82,0xa2,0xe9,0xba,0x27,0x0f,
0x01,0x04,0x7b,0xc1,0x40,0xa6,0x27,0x0f,
0x01,0x04,0x6d,0xeb,0x46,0x64,0x27,0x0f,
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
0x01,0x04,0x6d,0xeb,0x45,0xaa,0x27,0x0f,
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
0x01,0x04,0x6d,0xeb,0x41,0xe2,0x27,0x0f,
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
0x01,0x04,0x6d,0xeb,0x41,0x5f,0x27,0x0f,
0x01,0x04,0x6a,0x37,0x09,0x16,0x27,0x0f,
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
0x01,0x04,0x68,0xee,0x23,0x74,0x27,0x0f,
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
0x01,0x04,0x68,0xc8,0x43,0xfb,0x27,0x0f,
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
0x01,0x04,0x68,0xc8,0x18,0xc4,0x27,0x0f,
0x01,0x04,0x67,0xa0,0x5f,0xdb,0x27,0x0f,
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
0x01,0x04,0x5f,0xd3,0xc4,0x2e,0x27,0x0f,
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
0x01,0x04,0x5f,0xd3,0xc4,0x20,0x27,0x0f,
0x01,0x04,0x5f,0xd3,0xc4,0x08,0x27,0x0f,
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
0x01,0x04,0x5f,0xb7,0x35,0x2c,0x27,0x0f,
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
0x01,0x04,0x5f,0xb7,0x33,0x8d,0x27,0x0f,
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
0x01,0x04,0x5d,0x15,0x4c,0xb9,0x27,0x0f,
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
0x01,0x04,0x59,0xb3,0x49,0x60,0x27,0x0f,
0x01,0x04,0x59,0x75,0x13,0x0a,0x27,0x0f,
0x01,0x04,0x55,0xd7,0x6b,0xca,0x27,0x0f,
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
0x01,0x04,0x55,0xd1,0xf1,0xbe,0x27,0x0f,
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
0x01,0x04,0x55,0xd1,0xf1,0xbc,0x27,0x0f,
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
0x01,0x04,0x55,0xd1,0xf1,0x47,0x27,0x0f,
0x01,0x04,0x55,0xd1,0xf1,0x23,0x27,0x0f,
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
0x01,0x04,0x52,0xd3,0x19,0xc1,0x27,0x0f,
0x01,0x04,0x52,0xd3,0x19,0x69,0x27,0x0f,
0x01,0x04,0x52,0xd3,0x15,0xb3,0x27,0x0f,
0x01,0x04,0x52,0xd3,0x15,0x17,0x27,0x0f,
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
0x01,0x04,0x52,0xca,0xe6,0x53,0x27,0x0f,
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
0x01,0x04,0x51,0xe3,0xfa,0x33,0x27,0x0f,
0x01,0x04,0x50,0xd1,0xea,0xaa,0x27,0x0f,
0x01,0x04,0x4e,0x53,0x13,0x00,0x27,0x0f,
0x01,0x04,0x4d,0xe8,0x84,0x59,0x27,0x0f,
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
0x01,0x04,0x4d,0xe8,0x84,0x04,0x27,0x0f,
0x01,0x04,0x4d,0xdf,0x63,0x04,0x27,0x0f,
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
0x01,0x04,0x42,0xf4,0xf3,0x46,0x27,0x0f,
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
0x01,0x04,0x42,0xf4,0xf3,0x45,0x27,0x0f,
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
0x01,0x04,0x3a,0x6e,0xe0,0xa6,0x27,0x0f,
0x01,0x04,0x36,0x25,0xea,0x79,0x27,0x0f,
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
0x01,0x04,0x34,0x21,0x09,0xac,0x27,0x0f,
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
0x01,0x04,0x33,0x9e,0xf3,0xfa,0x27,0x0f,
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
0x01,0x04,0x33,0x9e,0xa9,0xed,0x27,0x0f,
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
0x01,0x04,0x33,0x4f,0xa0,0xc5,0x27,0x0f,
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
0x01,0x04,0x33,0x44,0x9b,0x40,0x27,0x0f,
0x01,0x04,0x33,0x0f,0x75,0x2a,0x27,0x0f,
0x01,0x04,0x33,0x0f,0x60,0xce,0x27,0x0f,
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
0x01,0x04,0x2f,0x6d,0x6d,0xa6,0x27,0x0f,
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
0x01,0x04,0x2e,0xfe,0xf1,0x15,0x27,0x0f,
0x01,0x04,0x2e,0xfe,0xf1,0x04,0x27,0x0f,
0x01,0x04,0x2e,0x24,0x28,0xf2,0x27,0x0f,
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
0x01,0x04,0x2e,0x1e,0xbd,0xd6,0x27,0x0f,
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
0x01,0x04,0x2e,0x1e,0xbd,0x74,0x27,0x0f,
0x01,0x04,0x2e,0x04,0xa2,0x7f,0x27,0x0f,
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
0x01,0x04,0x2d,0x8c,0x13,0xc9,0x27,0x0f,
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
0x01,0x04,0x2d,0x5d,0x8b,0x75,0x27,0x0f,
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
0x01,0x04,0x2d,0x5b,0x5e,0xd9,0x27,0x0f,
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
0x01,0x04,0x2d,0x55,0x75,0xa9,0x27,0x0f,
0x01,0x04,0x2d,0x55,0x75,0x28,0x27,0x0f,
0x01,0x04,0x2d,0x53,0x7a,0x7a,0x27,0x0f,
0x01,0x04,0x2d,0x4f,0x12,0x6a,0x27,0x0f,
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
0x01,0x04,0x2d,0x4c,0x53,0x5b,0x27,0x0f,
0x01,0x04,0x2d,0x47,0x9f,0x68,0x27,0x0f,
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
0x01,0x04,0x2d,0x47,0x9e,0x6c,0x27,0x0f,
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
0x01,0x04,0x2d,0x47,0x9e,0x3a,0x27,0x0f,
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
0x01,0x04,0x2d,0x3f,0x6b,0x5a,0x27,0x0f,
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
0x01,0x04,0x2d,0x3a,0x38,0xdd,0x27,0x0f,
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
0x01,0x04,0x2d,0x20,0x9f,0x30,0x27,0x0f,
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
0x01,0x04,0x2d,0x0b,0xb6,0x40,0x27,0x0f,
0x01,0x04,0x2d,0x08,0xfa,0x9a,0x27,0x0f,
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
0x01,0x04,0x2c,0xf0,0x63,0xd6,0x27,0x0f,
0x01,0x04,0x25,0x4d,0x68,0xa6,0x27,0x0f,
0x01,0x04,0x1f,0x94,0x63,0x68,0x27,0x0f,
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
0x01,0x04,0x1f,0x0a,0x61,0x24,0x27,0x0f,
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
0x01,0x04,0x17,0xa3,0x00,0xcb,0x27,0x0f,
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
0x01,0x04,0x17,0xa3,0x00,0xaf,0x27,0x0f,
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
0x01,0x04,0x0d,0xfb,0x0b,0x37,0x27,0x0f,
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
0x01,0x04,0x05,0xfc,0x15,0x18,0x27,0x0f,
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
0x01,0x04,0x05,0xbd,0xfd,0xfc,0x27,0x0f,
0x01,0x04,0x05,0xbd,0xef,0x34,0x27,0x0f,
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
0x01,0x04,0x05,0xbd,0x91,0x50,0x27,0x0f,
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
0x01,0x04,0x05,0xb5,0xca,0x0f,0x27,0x0f,
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
0x01,0x04,0x05,0xa1,0x6e,0x4f,0x27,0x0f,
0x01,0x04,0x05,0x4f,0x6d,0xf3,0x27,0x0f,
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
0x01,0x04,0x05,0x4e,0x4a,0x76,0x27,0x0f,
0x01,0x04,0x05,0x23,0x67,0x6f,0x27,0x0f,
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
0x01,0x04,0x05,0x23,0x67,0x4a,0x27,0x0f,
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
0x01,0x04,0x05,0x23,0x67,0x40,0x27,0x0f,
0x01,0x04,0x05,0x23,0x67,0x3a,0x27,0x0f,
0x01,0x04,0x05,0x09,0xed,0x22,0x27,0x0f,
0x01,0x04,0x05,0x02,0x49,0x3a,0x27,0x0f,
0x01,0x04,0x03,0x23,0xe0,0x41,0x27,0x0f,
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
0x01,0x04,0x02,0x38,0xd5,0xdd,0x27,0x0f,
Add built-in seeds for .onion This makes it possible for a node with `-onlynet=tor` to bootstrap itself. It also adds the base infrastructure for adding IPv6 seed nodes. Also represent IPv4 fixed seed addresses in 16-byte format.
2014-07-24 13:52:57 +02:00
};
partial bitcoin#21560: Add Tor v3 hardcoded seeds excludes: - 2a257de113fd31539b68c28c47ef94f257b6e427 - 9b29d5df7fc555eaea42029f334f2995c6ccde3d
2023-09-10 16:10:08 +02:00
static const uint8_t chainparams_seed_test[] = {
0x01,0x04,0x2b,0xe5,0x4d,0x2e,0x4e,0x1f,
0x01,0x04,0x2d,0x4d,0xa7,0xf7,0x4e,0x1f,
0x01,0x04,0xb2,0x3e,0xcb,0xf9,0x4e,0x1f,
Add built-in seeds for .onion This makes it possible for a node with `-onlynet=tor` to bootstrap itself. It also adds the base infrastructure for adding IPv6 seed nodes. Also represent IPv4 fixed seed addresses in 16-byte format.
2014-07-24 13:52:57 +02:00
};
Merge #12757: Clarify include guard naming convention 3bcc0059b8 Add lint-include-guards.sh which checks include guard consistency (practicalswift) 8fd6af89a0 Fix missing or inconsistent include guards (practicalswift) 8af65d96f4 Document include guard convention (practicalswift) Pull request description: * **Documentation**: Document include guard convention * **Fix**: Fix missing or inconsistent include guards * **Regression test**: Add `lint-include-guards.sh` which checks include guard consistency Tree-SHA512: 8171878f60fd08ccbea943a11e835195750592abb9d7ab74eaa4265ae7fac523b1da9d31ca13d6ab73dd596e49986bfb7593c696e5f39567c93e610165bc2acc Signed-off-by: pasta <pasta@dashboost.org> # Conflicts: # src/bech32.h # src/consensus/merkle.h # src/key_io.h # src/policy/fees.h # src/rpc/server.h # src/script/bitcoinconsensus.h # src/wallet/coinselection.h
2018-04-02 00:30:17 +02:00
#endif // BITCOIN_CHAINPARAMSSEEDS_H
Reference in New Issue Copy Permalink