Categories
- 17.3K All Categories
- 9.5K Mining
- 574 Pool Discussion
- 378 Promotional
- 1.4K General Project Discussion (non-technical)
- 485 Education
- 811 Protocol and Client discussion
- 170 web3-js
- 29 Whisper
- 16 Swarm
- 3 RLP
- 303 IoT & Hardware
- 1.2K Smart Contracts and Dapps
- 28 Serpent
- 359 Solidity
- 664 Projects
- 1.2K Reference clients code and builds
- 249 Eth & AlethZero- Cpp Implementation
- 471 Geth - Go Implementation
- 242 Mist
- 15 Node.js Implementation
- 36 Python Implementation
- 49 Mix
- 36 Other Implementations
- 170 Meetups
- 40 Other Events
- 226 Jobs & Skills
- 281 Press and Articles
- 75 Audio/Video
- 296 Ether Sale
- 1.2K Other Languages
- 96 Chinese
- 255 German
- 33 Italian
- 111 French
- 3 Hebrew
- 42 Japanese
- 75 Portugese
- 46 Romanian
- 185 Russian
- 231 Spanish
- 47 Turkish
- 125 Watercooler
Questions regarding identical transactions
etheruser
Member Posts: 3 ✭
I see on Wikipedia that a cryptographic nonce is an arbitrary number used only once in a cryptographic communication. However, the http://gavwood.com/Paper.pdf defines the definition of nonce as a scalar value equal to the number oftransactions sent by the sender, formally, Tn.
Q1: So, how the nonce is going to be random in the context of ether?
Q2: Suppose there are two identical transactions happening at the same time or one after another, Is nonce used the only parameter that is responsible for differentiating the two transactions? Or is the parentHash parameter used, basically determines that the two transactions would not collide with each other since the hash code is always unique and different. Please clarify.
Q3: The page 13 of the gavwood paper talks about reversing the transactions. Is that possible to implement with etherereum? Correct me if I am wrong, based on my understanding, since transactions takes place in a decentralized system, peer to peer, it's difficult to reverse any transaction?
Q1: So, how the nonce is going to be random in the context of ether?
Q2: Suppose there are two identical transactions happening at the same time or one after another, Is nonce used the only parameter that is responsible for differentiating the two transactions? Or is the parentHash parameter used, basically determines that the two transactions would not collide with each other since the hash code is always unique and different. Please clarify.
Q3: The page 13 of the gavwood paper talks about reversing the transactions. Is that possible to implement with etherereum? Correct me if I am wrong, based on my understanding, since transactions takes place in a decentralized system, peer to peer, it's difficult to reverse any transaction?
Comments
A2: yes, exactly equal transaction (same nonce) would result in only one being executed. If they have a different nonce, then both can be executed. ParentHash is not a transaction parameter and not needed as such.
A3: You can not reverse transactions, but when the execution of a transaction runs out of gas, or has invalid code (jump to a position without jumpdest, stack underflow, ...) then the transaction gets reverted internally. This means that the transaction only results in the value transfer and the gasPrice*gasLimit to miner transfer, as if no evm-code has been executed.