Stability Patch Released,.
11 Jul 2023, 22:59
Stability Patch Released,
This is a pre-release which is temporary, but still sufficient to get nodes aligned on the underlying problem.
NB! Due to the late hour, we decided to update 0.20.13 version with the pre-release files which are know to be working only when updating an existing Hydra installation. We will release tomorrow also 0.20.14 which will work for fresh installs.
The problem:
Due to the LYDRA derivative lockup, we rely on a reverse check for an available balance on a given wallet to know how much HYDRA can be transferred as an allowance post LYDRA mint.
There are three layers with checks that ensure the user has the right to send the money.
at the UX and RPC level
at the mempool level
at the protocol level
Each plays a key role in verifying that the HYDRA balance (minus) the minted LYDRA balance, is greater than the amount they want to transfer.
Since we are UTXO based, we don't have the state of every foreign wallet (unlike an EVM chain which has a direct account state for each public wallet) in the local node itself. To extract it, we use the built-in function "getaddressbalance", which is supposed to serve exactly this purpose and is inherited from QTUM.
However, it turned out that this function on the mainnet (unlike the months of tests on the testnet) was unreliable. It was difficult to track it at first, because of how sporadic it manifested as a problem. Important to emphasize that this was inherited from project Qtum.
It has been verified that this particular function gives corrupt data for some wallets on local level, which means that a given staker would see a slightly different balance for a given wallet in the context of this particular check. It is a corner case related to addresses who minted LYDRA and for whose balances nodes were misaligned due to having this faulty underlying function.
We've implemented a different method which is reliable and uses the raw unadjusted UTXOs for each wallet. Same method is also successfully used for delegating accounting and always uses the raw unprocessed UTXO data.
To remedy the stability issue, please follow these steps
1. Download your build from If you previously downloaded 0.20.13, please note these builds have replaced the previous ones under the same version. You can override them.
(currently Windows and Ubuntu builds available, more to be uploaded tomorrow)
2. Patch your node
3. After the node loads, to instantly resolve any current fork issues, run the following command:
"invalidateblock 3ee59e18afef6b742a77e665bc1be821c0a0859260e383a0e67703bc1844842b "
Step 3 is particularly related to a current mini-fork that we detected as a part of the ongoing monitoring of the chain. This is the blockhash of the origin block.
fyi "invalidateblock" works in a way that it immediately informs your node to mark that block as invalid, which cuts the entire tree of child blocks under it and will push your node to reorg and connect to the main chain if you are affected.
By default the command output will always output a " InvalidChainFound: invalid block=3ee59e18afef6b742a77e665bc1be821c0a0859260e383a0e67703bc1844842b " which doesn't mean that you are affected by it. This is just a default print statement. If however you notice that your node outputs a series of messages on the other hand, it would likely be reorganizing. Takes a few minutes to reorg and discard the fork, and this is a handy way to avoid a full reindex which could otherwise take hours.
Also note that step 3 can be executed independently from step 1 and 2.
Additional Information:
The explorer and periphery have been under maintenance today as we did a series of tests and upgrading. The maintenance is expected to end tomorrow (13 July 2023). Until then we recommend to use the client nodes for interacting with the chain.
Same news in other sources
112 Jul 2023, 13:24
Stability Update
✓explorer.hydrachain.org is up and running and is synced. You can use it for healthcheck
✓hydradex.org is up and running and is functional
✓mobile wallet and browser wallets are functional
✗bridge.hydrachain.org is under intentional suspension as a safety precaution over the next 24 hours
While we keep monitoring the situation, if you are experiencing issues despite the invalidateblock command, then your node may need a reindex.
1) Make sure to update to 0.20.13 ->
2) Close the node
3) delete your banlist file
4) Restart your node with "-reindex=1" parameter. It will take a few hours to complete. Make sure to reindex after you have updated to 0.20.13
- If you are running a linux build, make sure to have a hydra.conf file in your install folder (where you will find your wallet.dat file present). On windows this file is automatically created.
You can use this version:
- 0.20.14 patch is in the works. ETA for release is 24 hours
- Current network weight is ~12M
Stability Update. ✓explorer. hydrachain. org is up and running and is synced. You can use it for healthcheck. ✓hydradex.
Stability Update
✓explorer.hydrachain.org is up and running and is synced. You can use it for healthcheck
✓hydradex.org is up and running and is functional
✓mobile wallet and browser wallets are functional
✗bridge.hydrachain.org is under intentional suspension as a safety precaution over the next 24 hours
While we keep monitoring the situation, if you are experiencing issues despite the invalidateblock command, then your node may need a reindex.
1) Make sure to update to 0.20.13 -> https://github.com/Hydra-Chain/node/releases/tag/hydra_v0.20.13
2) Close the node
3) delete your banlist file
4) Restart your node with "-reindex=1" parameter. It will take a few hours to complete. Make sure to reindex after you have updated to 0.20.13
- If you are running a linux build, make sure to have a hydra.conf file in your install folder (where you will find your wallet.dat file present). On windows this file is automatically created.
You can use this version: https://github.com/Hydra-Chain/node/blob/hydra/contrib/debian/examples/hydra.conf
- 0.20.14 patch is in the works. ETA for release is 24 hours
- Current network weight is ~12M