SmartHoldem transactions use a sequential nonce to protect against double-spending , long-range attacks, key-leakage as a result of signature reuse, and side-channel attacks associated with random nonces.
A sequential nonce effectively counts each outgoing transaction from a given wallet. This means that the first transaction from a wallet must have a nonce of 1, the second transaction must have a nonce of 2, and so on.
This ensures that the data contained within a particular transaction will always be unique and thus results in a distinct hash that will necessarily produce a unique signature.
key facts:
funky stuff here:
A sequential nonce depends on the amount of transaction a specific wallet has sent. You can find the current nonce for a wallet by utilizing the Public API, more specifically the wallet endpoint. The wallet endpoint returns the wallet details, including the current wallets nonce field, like below:
{
"data": {
"address": "SaH94CRFvPXTwpgyLSCAsSuyCKJAqWxgo2",
"publicKey": "035231cc2fccf7fba239b8abb2611def73f0c0a01598164909181eebd544ce114d",
"balance": "12350770478424",
"nonce": "3",
"attributes": {
"delegate": {
"username": "europa",
"voteBalance": "12350770478424",
"forgedFees": "300000000",
"forgedRewards": "0",
"producedBlocks": 1254,
"round": 74233,
"rank": 20,
"lastBlock": {
"version": 0,
"timestamp": 12568400,
"height": 1558858,
"previousBlockHex": "cb9efcde4b5926fcc53916beb331178b7a9bbd821eb16a8bae1b616cf0b4deae",
"previousBlock": "cb9efcde4b5926fcc53916beb331178b7a9bbd821eb16a8bae1b616cf0b4deae",
"numberOfTransactions": 0,
"totalAmount": "0",
"totalFee": "0",
"reward": "0",
"payloadLength": 0,
"payloadHash": "e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855",
"generatorPublicKey": "035231cc2fccf7fba239b8abb2611def73f0c0a01598164909181eebd544ce114d",
"blockSignature": "3045022100f6ec49b773523aacd234054157ab73bb71e99bc842d1a00ec7becfa912afac8c0220721a213cf1b48d548ecdf953fdc5c10554f44e039f67abc32494b4d3afb5e81f",
"idHex": "234cbf055fd3ae0a73f542135d9561a7ecf1b2fc2a14d81adb02cc96bb425652",
"id": "234cbf055fd3ae0a73f542135d9561a7ecf1b2fc2a14d81adb02cc96bb425652"
}
},
"vote": "035231cc2fccf7fba239b8abb2611def73f0c0a01598164909181eebd544ce114d"
}
}
}When you create a new transaction for that wallet, you will use the current nonce and add 1 to it to get to the new nonce value.
If you retrieved a nonce value of 123 for a wallet, the next transaction will have to use nonce 124, (current_nonce + 1). The API will increase the nonce value once a transaction has been forged for the wallet.
You have to keep track locally of the next nonce value in case you intend to send multiple transactions in a single block.
For example, we have a wallet with nonce 100 and want to send 3 transactions to be forged in the next block. These transactions will require nonce values 101, 102 and 103 respectively, and you will have to set the values, before creating transactions.
After the block is forged, the API will report the current nonce of the wallet to be 103.