|
Title: If change hard-coded IP address in source, Post by: wsxdrfv on March 27, 2018, 05:07:37 AM If there is an coin and running network at public,
If developer change hard-coded IP address in source, and make new client, but it does not conflict with existing node? Title: Re: If change hard-coded IP address in source, Post by: starmyc on March 27, 2018, 05:36:40 AM If there is an coin and running network at public, If developer change hard-coded IP address in source, and make new client, but it does not conflict with existing node? IPs in source code (of old bitcoin clients) & dns seeds are only a way to help discovering other nodes. They are not authority or dictate how the network will behave. Once another nodes are discovered by the client, they don't use this list anymore, as peer information will be stored in the peers.dat database. Therefore, it one of the clients of the "new" client contacts a node of the "old" client in any way, and protocol doesn't differ, you'll have what you call "conflicts". That's why most altcoins change network ports from their original implementation. Please note I believe you can't define anymore any node IP in bitcoin's source code, only dns seed which returns IP addresses of nodes. Title: Re: If change hard-coded IP address in source, Post by: wsxdrfv on March 28, 2018, 07:40:43 AM If there is an coin and running network at public, If developer change hard-coded IP address in source, and make new client, but it does not conflict with existing node? IPs in source code (of old bitcoin clients) & dns seeds are only a way to help discovering other nodes. They are not authority or dictate how the network will behave. Once another nodes are discovered by the client, they don't use this list anymore, as peer information will be stored in the peers.dat database. Therefore, it one of the clients of the "new" client contacts a node of the "old" client in any way, and protocol doesn't differ, you'll have what you call "conflicts". That's why most altcoins change network ports from their original implementation. Please note I believe you can't define anymore any node IP in bitcoin's source code, only dns seed which returns IP addresses of nodes. strMainNetDNSSeed[][2] = { {"asdf.com", "13.xxx.xxx.33"}, {"qwer.com", "23.xxx.xxx.33"} } to another. so in this part, "asdf.com" doesn't matter and only IP address is matter, right? |