ArabianChain Hard Fork
The Final Block Fork is # 39000
RPCPort is now 7565 the original port number
Urgent: Everyone needs to be updated prior to Block # 39000 (By 05/09/2017 latest) or face the probability of zero connects or wrong chain including loss of personal data (Coins)
Downloads
DbixWall-WinGUIv1.0.1_49-1.zip
We recently experienced a series of abnormal Block Emissions which have lead to longer than normal confirmations times of newly mined blocks which contain the most recent Network Transactions, Uncles and New DBIX Coins, thus slowing down the network and taking hours instead of just 90 seconds between Blocks. This was brought to our attention via complaints from the community plus our own experiences sending Transactions through the Network, and taking unreasonably long Confirmation Times.
At first it was reasonable to speculate that the Slow Block Times were caused by the massive increase in Network Hash coming onto the Network or possibly ‘ Diff Jackers’ however further inspection and credible confirmation of the exact issue pointed to a coding error in the go-gdbix Command Prompt instance which is the DBIX equivalent to Ethereum’s ‘Geth’. A fast and simple fix to the go-gdbix code was immediately carried out through a simple Hard Fork. Our programmer was able to implement the simple fix combined with the necessary Upgrades to the Core Wallets and had it completed and implemented in real time within a few hours.
Proper Open Source Protocal of any Hard or Soft Fork is to communicate the issue, and explain the agreed upon solution and the exact time of the Hard Fork to commence to the Network Peers immediately with at least 48-72 hours prior to any changes actually taking effect for most non emergency issues. In DeCentralized Crypto Blockchain applications Networks strive to alert their peers (nodes) of any such issues possibly requiring a Hard or Soft Fork promptly in real time through the use of the ‘Governance’ feature built into the Blockchain and depending upon the severity of the issue how to move forward is decided by the peers through consensus with each node contributing or not if they choose.
The choice was made as a team to implement the fix in real time immediately then notify the Network Peers of the Hard Fork taking place at block 39000 which is around 5 days from now. However in the future we will prefer to implement basic ‘Governance’ same as Ethereum and even Bitcoin has done at one point or another. The protocol for ‘Governance’ will be posted in the OP as soon as possible and taken from some of the relative similarities already in use on other Blockchains.
We recently experienced a series of abnormal Block Emissions which have lead to longer than normal confirmations times of newly mined blocks which contain the most recent Network Transactions, Uncles and New DBIX Coins, thus slowing down the network and taking hours instead of just 90 seconds between Blocks. This was brought to our attention via complaints from the community plus our own experiences sending Transactions through the Network, and taking unreasonably long Confirmation Times.
At first it was reasonable to speculate that the Slow Block Times were caused by the massive increase in Network Hash coming onto the Network or possibly ‘ Diff Jackers’ however further inspection and credible confirmation of the exact issue pointed to a coding error in the go-gdbix Command Prompt instance which is the DBIX equivalent to Ethereum’s ‘Geth’. A fast and simple fix to the go-gdbix code was immediately carried out through a simple Hard Fork. Our programmer was able to implement the simple fix combined with the necessary Upgrades to the Core Wallets and had it completed and implemented in real time within a few hours.
Proper Open Source Protocal of any Hard or Soft Fork is to communicate the issue, and explain the agreed upon solution and the exact time of the Hard Fork to commence to the Network Peers immediately with at least 48-72 hours prior to any changes actually taking effect for most non emergency issues. In DeCentralized Crypto Blockchain applications Networks strive to alert their peers (nodes) of any such issues possibly requiring a Hard or Soft Fork promptly in real time through the use of the ‘Governance’ feature built into the Blockchain and depending upon the severity of the issue how to move forward is decided by the peers through consensus with each node contributing or not if they choose.
The choice was made as a team to implement the fix in real time immediately then notify the Network Peers of the Hard Fork taking place at block 39000 which is around 5 days from now. However in the future we will prefer to implement basic ‘Governance’ same as Ethereum and even Bitcoin has done at one point or another. The protocol for ‘Governance’ will be posted in the OP as soon as possible and taken from some of the relative similarities already in use on other Blockchains.
