I mean, I know if the node changes its IP address, that maybe the blockchain will lose contact as it is sending out signals to the nxt.myAddress entry in the properties file.
Is there something in the blockchain to do some type of auto-live-editing of the nxt-default.properties file to rewrite the nxt.myAddress= (WhatScript?)
with some type of script (WhatScript?) IP address variable algorithm/whatever where it rechecks itself (the ip address, and if the IP address changes, this (WhatScript) rewrites and pushes the new IP address, instead of a "static" IP address number in properties file, which is actually a dynamic IP address?. So that someone with a dynamic IP address doesn't have to keep changing the nxt.default.properties file.
I mean sure you could get a static IP address for your home pc from your ISP but wouldn't it be possible to create a script/variable to replace a static ip address value in NXT-default.properties to recheck its own value and resend to the blockchain and rewrite the nxt-default.properties file (live, and not pre-edited before running run.sh)?
My problem is right now for some reason I cannot sync to the NXt blockchain, I have my new IP address, DefaultPeers / WellKnownPeers, my ufw ports are open...
I'm just curious if such an addition could add any qualitative value to the nxt-default.properties process. I mean that it has some type of push function rather than taking static data from the properties file?
There are no 1.12.3 peers in the NXT block explorer nxtportal | Nxt Blockchain Explorer... maybe that is my problem?
I believe it is because when running run.sh it says "Known Peers = 0"
Is there a list of 1.12.3 peers somewhere. I really would think that 1.12.2 peers are compatible with 1.12.3 I honestly wonder what I'm doing wrong.
I'm also curious if Jelurida will make available a block explorer for clones?