Version 12.2 release

Status
Not open for further replies.

wal

New Member
Dec 6, 2016
33
12
8
41
Thanks @UdjinM6

Under what circumstances is it possible for an IX transaction (one where instantlock=true) to fail ? I'm referring to a TX that is *received* by a full node from the network.

Or to rephrase, does a TX with instantlock=true mean the TX will definitely be mined even when it hasnt actually been mined yet (as confirmations=0)
 
Last edited:

UdjinM6

Official Dash Dev
Core Developer
Dash Core Team
May 20, 2014
3,639
3,537
1,183
Thanks @UdjinM6

Under what circumstances is it possible for an IX transaction (one where instantlock=true) to fail ? I'm referring to a TX that is *received* by a full node from the network.

Or to rephrase, does a TX with instantlock=true mean the TX will definitely be mined even when it hasnt actually been mined yet (as confirmations=0)
"Locked" tx means that:
1. tx was broadcasted to at least some masternodes;
2. masternodes who are required to vote for it received it, checked it and voted;
3. votes were brodcasted by them and reached at least your node.

Taking into account network topology (which is pretty complex, (master)nodes have multiple interconnections etc.), it's very unlikely that IS tx and IS votes were relayed only by masternodes that were required to vote for it and your node. It's most likely that the whole network (or at least the vast non-isolated majority of it) has both IS tx and all required IS votes to lock it. IS tx lock is going to be kept by every online node until it has at least 24 confirmations. This guarantees with very high probability that no other txes trying to double-spend the same inputs are going to be accepted by the network. This does NOT guarantee however that IS tx is going to be mined in the very next block but at the same time it's pretty likely because IS txes have higher fee comparing to most other txes (by default).
 
  • Like
Reactions: chaeplin

wal

New Member
Dec 6, 2016
33
12
8
41
Ok, if you're running an e-commerce solution and someone sends you 1,000 dash and you detect its an IX TX can you immediately credit their account? How safe is it, sorry to pester but your prior answer did not qualify other than 'high probability'

An implication from your answer that an IX TX is equivalent to waiting for 24 confirmations, is this correct?
 
  • Like
Reactions: Weber K.

UdjinM6

Official Dash Dev
Core Developer
Dash Core Team
May 20, 2014
3,639
3,537
1,183
Ok, if you're running an e-commerce solution and someone sends you 1,000 dash and you detect its an IX TX can you immediately credit their account? How safe is it, sorry to pester but your prior answer did not qualify other than 'high probability'

An implication from your answer that an IX TX is equivalent to waiting for 24 confirmations, is this correct?
If you assume that the whole network locked it - then yes, but again, you can only say about it as of an exact number if you are talking about a single node, that's where things are kind of deterministic. When you are talking about the whole network - it's probabilistic, like I explained above. Just like you can't be 100% sure that 24+ blocks (~1h+ of work) reorg will never happen, you can't be 100% sure that some tx will be included into the blockchain but the probability of such huge reorg is tiny and it's getting smaller and smaller with each new block. IS is not a direct equivalent of 1h+ of work, it gives you an additional assurance that if a potential reorg of less than 24 blocks would occur, it's highly unlikely that any other chain with conflicting tx will be accepted as a valid one. Will you accept this as a good enough assurance for 1000 DASH tx or not is up to you.
 

alex9

Member
Feb 4, 2017
57
7
48
Since block 782208 many blocks have old version (without dip0001 bit). Is it normal?
 

UdjinM6

Official Dash Dev
Core Developer
Dash Core Team
May 20, 2014
3,639
3,537
1,183
To answer everyone asking (and trolling) about block version above: yes, it's completely normal. DIP0001 is activated so there is no need for pools to signal for its support anymore and we are back to block version 536870912. All worked as designed.
 

UdjinM6

Official Dash Dev
Core Developer
Dash Core Team
May 20, 2014
3,639
3,537
1,183

GrandMasterDash

Grizzled Member
Masternode Owner/Operator
Jul 12, 2015
2,969
1,143
1,183
Apparently there is a problem with older wget versions. I subsequently tried with a curl -o and got a 302 redirect header.
 

t0dd

Active Member
Mar 21, 2016
150
132
103
keybase.io
Dash Address
XyxQq4qgp9B53QWQgSqSxJb4xddhzk5Zhh
Dash Ver: 12.2.2 Release
Miners / MN’s / users Please Update !!
(no protocol bump and no restart commands required - Dashman updated)
https://www.dash.org/downloads/#wallets

Release Notes:
https://github.com/dashpay/dash/blob/v0.12.2.2/doc/release-notes.md
Fedora Linux users! (and CentOS/RHEL) -- native 12.2.2 packages are built and available
https://github.com/taw00/dashcore-rpm

All docs: https://github.com/taw00/dashcore-rpm/tree/master/documentation
Update docs: https://github.com/taw00/dashcore-r...n/howto.update-a-wallet-node-or-masternode.md
Troubleshooting docs: https://github.com/taw00/dashcore-rpm/blob/master/documentation/howto.dashcore-troubleshooting.md

Read the docs, or here's the summary since it is really simple:
If you have already deployed using DNF and configured as a systemd managed process, then do this:

sudo dnf upgrade -y --refresh

If you updated your kernel, glibc, or other system packages in the process, it's time to reboot that server.
Don't leave your systems unpatched, folks!....

sudo reboot

If the only thing updated was Dash Core, you can just restart `dashd`:
sudo systemctl restart dashd

When it comes back, check the status (see troubleshooting docs listed above)

Important note
Fedora users: I will stop building Fedora 25 packages at the end of 2017. Fedora 25 is no longer maintained by the Fedora community. You need to upgrade. Fortunately, upgrading is almost trivially easy, and if you followed my instructions for deploying Dash Core, all your dash stuff will upgrade to the right builds right along with the operating system. Follow the simple instructions here: https://github.com/taw00/dashcore-r...ntation/howto.upgrade-the-operating-system.md


Dilly Dilly!
-t -- ping me if you have any questions (here, on discord, or keybase chat, etc)
 
Last edited:

UdjinM6

Official Dash Dev
Core Developer
Dash Core Team
May 20, 2014
3,639
3,537
1,183
What’s new in this update?
This ^^^

TL;DR:

UPDATE2:
The latest release is 0.12.2.2. This release includes fixes and improvements as follows:
  • Per-UTXO fix (fixes Corebleed vulnerability)
  • Additional indexes fix
  • InstantSend fix
  • PrivateSend fix
  • Removal of support for local masternodes
  • Dropping old (pre-12.2) peers
We encourage all masternode and other full node operators (exchanges, pools, explorers) to update.

https://github.com/dashpay/dash/releases/tag/v0.12.2.2
OP updated :)
 

jeffh

Member
May 8, 2017
108
45
78
I'm seeing much lower CPU and network usage in this version, is that to be expected - or is it just due to a recent start of the node?
 

donho

Member
Masternode Owner/Operator
Apr 16, 2014
96
20
58
MN upgraded! Weird thing was dashman showed me I was already on 12.2.2 before upgrading, so I did it manually in the end.
 

UdjinM6

Official Dash Dev
Core Developer
Dash Core Team
May 20, 2014
3,639
3,537
1,183
I'm seeing much lower CPU and network usage in this version, is that to be expected - or is it just due to a recent start of the node?
Could be both :)
I would actually expect a bit more CPU/network usage in the next few days because of the update (due to many nodes going down and up again).
Would be interesting to compare some stats after a week or so.
 
  • Like
Reactions: chaeplin

AjM

Well-known Member
Foundation Member
Jun 23, 2014
1,341
575
283
Finland
v12.2.2 take about +20% more CPU and Network currently in my nodes.
 
Status
Not open for further replies.