You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
During the introduction of deterministic masternodes RPC commands evoznode/evoznsync was introduced, running side-by-side with znode/znsync for legacy masternodes.
At the time of its introduction the possibility of a rebrand is still far. Had it been known at the time, evoznode command would be masternode instead.
I propose (1) renaming evoznode to masternode (2) aliasing both znode and evoznode to masternode along with the equivalent for mnsync, (3) removing znode/znsync and evoznode/evoznsync aliases after one year.
Simply deprecating these can be disruptive as many sites/third party providers has already adapted their code to evoznode when it was introduced. A one year period will give plenty of time to adapt.
EDIT: we also need to consider for znodeznodeblsprivkey et al in firo.conf
The text was updated successfully, but these errors were encountered:
During the introduction of deterministic masternodes RPC commands
evoznode
/evoznsync
was introduced, running side-by-side withznode
/znsync
for legacy masternodes.At the time of its introduction the possibility of a rebrand is still far. Had it been known at the time,
evoznode
command would bemasternode
instead.I propose (1) renaming
evoznode
tomasternode
(2) aliasing bothznode
andevoznode
tomasternode
along with the equivalent formnsync
, (3) removingznode
/znsync
andevoznode
/evoznsync
aliases after one year.Simply deprecating these can be disruptive as many sites/third party providers has already adapted their code to
evoznode
when it was introduced. A one year period will give plenty of time to adapt.EDIT: we also need to consider for
znode
znodeblsprivkey
et al infiro.conf
The text was updated successfully, but these errors were encountered: