I've been talking with Phillipp Engelhorn about the upcoming Dash upgrade over the past week, but he is serving as an intermediary to the developers and I thought it would be more efficient to post messages directly here rather than force him to constantly relay E-Mails. I sent him the following code, which I must have written as a result of talking with udjin months ago: Code: if coinbase_payload: tx_version = 3 tx_type = 5 self.nVersion = tx_version + (tx_type << 16) #For Dash, from https://github.com/UNOMP/node-merged-pool/pull/17/commits/8134bbb3d954724b0437758042a0c8d4bf92e1bc, may need to generalize this to other coins in the future else: self.nVersion = 1 I don't recall where these constants originated from, but the comment indicates they may have come from reviewing some open source pool software. I was told by Phillipp that the constants should remain the same for the new fork of Dash. If that is true, then how does the network detect that the upgrade is ready to occur? Does the updated daemon change something in the blocks submitted to it from submitblock() before publishing them? Is there some soft of message sent over the network apart from the blocks that is handled automatically by the updated daemon, and therefore all that need to be done is to upgrade? Even after reading all the documentation, the most challenging part is that there is nowhere that makes it clear what signals this upgrade if these constants don't change.