Sep 6, 2014 01:56 AM
(This post was last modified: Sep 10, 2014 02:29 AM by SIM-2015410.)
Among the many changes we are undergoing, we have decided to officially update all omnicoin protocol port numbers, as there was some confusion over the official ports and varying information was provided from different sources.
In the old sticky, the ports were listed as:
RPC - 43555
P2P - 43556
Testnet - 43557
These have officially been changed to:
RPC - default: 4873 or testnet: 14873
P2P - default: 4872 or testnet: 14872
As seen in the wiki ( https://github.com/Omnicoin-Project/Omni...nformation ).
In accordance with these changes, please update your config file in this way:
- Locate your omnicoin.conf file. (Windows: This will probably be in %AppData%\Omnicoin\omnicoin.conf, Mac: ~/Library/Application Support/OmniCoin/OmniCoin.conf)
- Replace the contents with the contents of the template configuration file here. This ensures rpcport=43555 is changed to rpcport=4873 and your nodes are up to date.
To clarify, the ports which we are changing to are the ones currently being used. Only the official sticky and the template config file contained old, incorrect port numbers. If you did not create a config file, you are already using the correct ports. We are just updating all information about the coin so it is actually correct, so as to avoid confusion, and help new developers.
Thank you.
I don't see why there's a need to change the RPC port. You're forcing a lot of people to change it for no apparent reason.
lel
Sep 6, 2014 02:02 AM
(This post was last modified: Sep 6, 2014 02:04 AM by SIM-2015410.)
The new port is actually the port in all the code, it is only the config files which are wrong. But it needed to be done.
Anyone who doesn't change the file can still use omnicoin, we just want everyone to eventually switch.
(Sep 6, 2014 02:02 AM)SIM-2015410 Wrote: The new port is actually the port in all the code, it is only the config files which are wrong. But it needed to be done.
Anyone who doesn't change the file can still use omnicoin, we just want everyone to eventually switch.
Well this is weird, first commit states 33812 instead.
https://github.com/Omnicoin-Project/Omni...oinrpc.cpp
lel
Sep 6, 2014 02:11 AM
(This post was last modified: Sep 6, 2014 02:12 AM by SIM-2015410.)
(Sep 6, 2014 02:07 AM)SIM-888979 Wrote: Well this is weird, first commit states 33812 instead.
https://github.com/Omnicoin-Project/Omni...oinrpc.cpp
The Testnet ports were always wrong, yes. But the rpc and p2p ports were correct. We also updated the testnet ports in the latest source code https://github.com/Omnicoin-Project/Omnicoin but that doesn't affect anyone, as no one uses the testnet.
(Sep 6, 2014 02:11 AM)SIM-2015410 Wrote: The Testnet ports were always wrong, yes. But the rpc and p2p ports were correct.
Ah I see, a tad bit of miscommunication between the coders and Crypto I guess.
lel
Sep 6, 2014 02:15 AM
(This post was last modified: Sep 6, 2014 02:15 AM by SIM-2015410.)
(Sep 6, 2014 02:13 AM)SIM-888979 Wrote: Ah I see, a tad bit of miscommunication between the coders and Crypto I guess.
I think so. With all the reorganising I brought up the issue and we decided this was the best solution. The ports like 43555 were carried through from your v1, and were changed in v2 I believe, but were just not changed in the documentation.
(Sep 6, 2014 02:15 AM)SIM-2015410 Wrote: I think so. With all the reorganising I brought up the issue and we decided this was the best solution. The ports like 43555 were carried through from your v1, and were changed in v2 I believe, but were just not changed in the documentation.
Glad that this has been fixed then. However, I don't see what this will help in reviving the coin. There has to be a bigger demand for OMCs. With the current lack of demand, these changes won't affect much. Have the team planned a list of to-do's yet? If so, please PM me it. I'd like to see what you guys are up to and see where I can help.
lel
(Sep 6, 2014 02:19 AM)SIM-888979 Wrote: Glad that this has been fixed then. However, I don't see what this will help in reviving the coin. There has to be a bigger demand for OMCs. With the current lack of demand, these changes won't affect much. Have the team planned a list of to-do's yet? If so, please PM me it. I'd like to see what you guys are up to and see where I can help.
In fact we have, I just wrote a todo list up today taking into account some of the feedback we received from the suggestions thread. I will PM you it now.
The purpose of this change was not to increase popularity of OMC but merely to reorganise everything better and get things on track for the future. It was just one of the many changes we made, among things like the new sticky, the move to the github wiki, etc.
(Sep 6, 2014 02:13 AM)SIM-888979 Wrote: Ah I see, a tad bit of miscommunication between the coders and Crypto I guess.
While I appreciate everything Crypto Miner did for us, when it came to the initial release, he really just took the input, discarded it, and did his own thing for all intents and purposes. It worked, but not everything matched the specs I gave him when we first started working on the recode.
Regardless, the RPC port can stay if it's already in your config file, since that won't affect connectivity with other users, but the P2P port should be changed for both consistency, and for maximum connectivity, particular with users who were unable to easily connect with a plug and play type situation.
Get a signed message before dealing: Keybase
Still here sometimes.
(Sep 6, 2014 06:32 AM)Crypto™ Wrote: While I appreciate everything Crypto Miner did for us, when it came to the initial release, he really just took the input, discarded it, and did his own thing for all intents and purposes. It worked, but not everything matched the specs I gave him when we first started working on the recode.
Regardless, the RPC port can stay if it's already in your config file, since that won't affect connectivity with other users, but the P2P port should be changed for both consistency, and for maximum connectivity, particular with users who were unable to easily connect with a plug and play type situation.
That was of my concern. Some people might have to port-forward their ports again (and to some, it's a real hassle) if they have no uPnP. Oh well, I don't think it'll affect too many people though.
lel
(Sep 6, 2014 07:40 AM)SIM-888979 Wrote: That was of my concern. Some people might have to port-forward their ports again (and to some, it's a real hassle) if they have no uPnP. Oh well, I don't think it'll affect too many people though.
If anyone is forwarding the RPC port... well they shouldn't, unless it's firewalled from everything except the IP that should have access to it.
Also, @MeshCollider, the omnicoin.conf that comes along with omnicoin-qt is just a sample. The config file used is in %AppData%\Omnicoin\omnicoin.conf, as with any other altcoin.
If you haven't specified different ports in the config file, you won't have to do anything, as we didn't change anything apart from the documentation to reflect the port numbers we're actually using.
I use OMC wallet in Mac, is there any update for that?
Sep 7, 2014 05:20 AM
(This post was last modified: Sep 7, 2014 05:21 AM by Knar..)
(Sep 7, 2014 03:24 AM)EziNet Wrote: I use OMC wallet in Mac, is there any update for that?
Yes.
Code ~/Library/Application Support/OmniCoin/OmniCoin.conf
Just update the rpcport in that file. You can open it with anything like Text Edit or Sublime Text.
I have updated my config file accordingly. Thank you for the update. 🤝
|
