• Forum has been upgraded, all links, images, etc are as they were. Please see Official Announcements for more information

Dash Core 0.12.3.3 Release Announcement

Status
Not open for further replies.

UdjinM6

Official Dash Dev
Dash Core Group
Dash Core 0.12.3.3 is a critical bugfix release of the Dash Core 0.12.3.x series.

There was a serious vulnerability discovered in Bitcoin Core's codebase recently which
can cause node receiving a specially crafted block to crash https://github.com/bitcoin/bitcoin/pull/14247

We encourage all full node operators (masternodes, mining pools, explorers, exchanges etc.) to update ASAP.

Full release notes are available at https://github.com/dashpay/dash/blob/v0.12.3.3/doc/release-notes.md,
release binaries can be downloaded from https://github.com/dashpay/dash/releases/tag/v0.12.3.3.

Note: this release does NOT require masternode owners to start their masternodes from cold wallets.
Masternode operators should stop the daemon running on a remote node, replace old binaries with the new ones and start the daemon again.
 
Thanks for providing information about new release Dash Core 0.12.3.3. We have released a bug-fix update of the Dash (DASH) Core wallet client, the application powering the project's proof-of-stake cryptocurrency.
 
I think this answers my question I was wondering if the recent bitcoin bug had also affected Dash. Seems it had
 
Dash Core 0.12.3.3 is a critical bugfix release of the Dash Core 0.12.3.x series.

There was a serious vulnerability discovered in Bitcoin Core's codebase recently which
can cause node receiving a specially crafted block to crash https://github.com/bitcoin/bitcoin/pull/14247

We encourage all full node operators (masternodes, mining pools, explorers, exchanges etc.) to update ASAP.

Full release notes are available at https://github.com/dashpay/dash/blob/v0.12.3.3/doc/release-notes.md,
release binaries can be downloaded from https://github.com/dashpay/dash/releases/tag/v0.12.3.3.

Note: this release does NOT require masternode owners to start their masternodes from cold wallets.
Masternode operators should stop the daemon running on a remote node, replace old binaries with the new ones and start the daemon again.


I also encountered a problem when synchronizing my wallet from version 0.12.xx to 0.14.xx. after I see my balance is zero. When I check my transaction history, everything received has a status:
Status: 0 / not confirmed, not in memory collection

what should i do, please help

Please advise. Thank you very much!
 
I also encountered a problem when synchronizing my wallet from version 0.12.xx to 0.14.xx. after I see my balance is zero. When I check my transaction history, everything received has a status:
Status: 0 / not confirmed, not in memory collection

what should i do, please help

Please advise. Thank you very much!
reindex 14 wallwt
 

Maybe you should just delete your blockchain (folders blocks & chainstate) and use a bootstrap to quickly re-download the blockchain and have it synced from scratch.
You can download a Dash bootstrap here : https://github.com/UdjinM6/dash-bootstrap (use the most recent for mainnet)

Check your balance for your address(es) here : https://chainz.cryptoid.info/dash/ if that shows you the correct balance then its a matter of getting you on the right chain.
The reason for your transaction(s) not getting confirmed could be related to you staying on the v0.12 chain too long (as in wayyy too long). The risks for staying on
a not supported chain is transactions not getting confirmed (basicly you end up in a forked-off chain without any support).
 
Maybe you should just delete your blockchain (folders blocks & chainstate) and use a bootstrap to quickly re-download the blockchain and have it synced from scratch.
You can download a Dash bootstrap here : https://github.com/UdjinM6/dash-bootstrap (use the most recent for mainnet)

Check your balance for your address(es) here : https://chainz.cryptoid.info/dash/ if that shows you the correct balance then its a matter of getting you on the right chain.
The reason for your transaction(s) not getting confirmed could be related to you staying on the v0.12 chain too long (as in wayyy too long). The risks for staying on
a not supported chain is transactions not getting confirmed (basicly you end up in a forked-off chain without any support).

Please explain ... website www.https: chain.so is a DASH network??

https://chain.so/address/DASH/Xoi6BbirsyTsyqKkPh4CJ6EMnkw5uhdEMk
 
Please explain ... website www.https: chain.so is a DASH network??

https://chain.so/address/DASH/Xoi6BbirsyTsyqKkPh4CJ6EMnkw5uhdEMk

https://chain.so/dash is one of many Dash Block Explorers.
https://chainz.cryptoid.info/dash/ is another Dash Block Explorer (more reliable).

There are more, see https://docs.dash.org/en/stable/introduction/information.html (Tools --> Block Explorers).

Your address Xoi6BbirsyTsyqKkPh4CJ6EMnkw5uhdEMk is only regnoniced it seems on Dash Block Explorer "https://chain.so/dash". That specific Dash Block Explorer seems to be on the wrong Dash chain and they need to re-index their block explorer ASAP. Do not rely on that Dash Block Explorer untill they fixed it. If you know a contact there, pls ask them to re-index their block explorer.

iCR3lfF.jpg



Wrong block number !! We are currently on blocknumber 1,093,546 !!



rzRM5t3.jpg
 
Last edited:
Status
Not open for further replies.
Back
Top