Skip to main content
All CollectionsCrowdNode trustless
Step 2: Analyzing and signing transactions
Step 2: Analyzing and signing transactions

The most important step in the creation of a trustless masternode is to sign the return transactions and understand what you sign. Look here

Thomas Orloff avatar
Written by Thomas Orloff
Updated over a week ago

This article shows you how to analyse and sign transactions.

Analyse the raw transaction

If you are curious what the transaction you are about to sign does, then execute the following command decoderawtransaction on the hex payload.

decoderawtransaction 0200000001c39da9f425e33d6a4294ad4a012bd814b338d49a417f33e26f426e0d48a091dd0100000000feffffff02784447f80d0000001976a914f448d78f7e7b4914466d9fe2e0aa5d1a7a6f4c4688ac787c2f50090000001976a914766001fed6690efdb468ea88e0be2e8b0f0e86df88ace57e2163

This will result in the following output:

You want to make sure that the locktime corresponds to your pledge. You can use a Unix time converter in order to see it in a readable way.

You can see the participant payments in the "vout" section as shown above. Find the one with your address and make sure the amount corresponds to your pledge. Note that a minor transaction fee has been subtracted to your pledge.

All of this should be properly generated and then you need to sign the transaction

Signing the transaction

In order to sign the transaction you will need the private key for the Masternode multisig wallet that you have pledged to. Note: This is not (and should not be) the private key for your primary address with CrowdNode (the one that we pay to).

Use the command "dupmpprivkey" to obtain it:

dumpprivkey yX7MbaTCsSNpfticSqSgkSCkSaRWDyv4sM


You know have the command from the CrowdNode portal to sign with:

Just replace the INSERT_PRIVKEY_FOR_[YOURADDRESS]_HERE with your private key from above and run the command. Leave in place [\" before the key and \"] after your key.

If everything is fine, then it will result in a response that is either in black or white text. Then everything is fine, despite there might be an error message like these:

"error": "Unable to sign input, invalid stack size (possibly missing key)"


"error": "Signature must be zero for failed CHECK(MULTI)SIG operation"

Despite the wording, then it is all fine. If something is wrong you will get a red error message.

Just grab the result from bracket to brackets and paste it into the platform.

Did this answer your question?