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
Transaction RLP Encoding : Are Tw, Tr, Ts included in the Tx hash for signature ?
GeekBot
Member Posts: 6 ✭
Hello,
I am playing with ethereumjs-tx, and I have a question relative to Tx encoding and signature.
It seems that ethereumjs-tx signature function is applied on the hash of the rlp encoding of the full encoded transaction with v=28 included, r and s, also included and set to 0x00.
According to the Yellow paper, Tw, Tr, Ts are not included in the rlp encoded raw Tx that is hashed. My understanding is that a specific rlp encoding of the raw transaction shall be hashed. I looked at the Go implementation and it seems to stick to the Yellow paper.
Is it a bad understanding on my side, or is it actually a bug on the js implementation ?
I can provide test samples if the question really needs investigation.
Thanks a lot
GeekBot
I am playing with ethereumjs-tx, and I have a question relative to Tx encoding and signature.
It seems that ethereumjs-tx signature function is applied on the hash of the rlp encoding of the full encoded transaction with v=28 included, r and s, also included and set to 0x00.
According to the Yellow paper, Tw, Tr, Ts are not included in the rlp encoded raw Tx that is hashed. My understanding is that a specific rlp encoding of the raw transaction shall be hashed. I looked at the Go implementation and it seems to stick to the Yellow paper.
Is it a bad understanding on my side, or is it actually a bug on the js implementation ?
I can provide test samples if the question really needs investigation.
Thanks a lot
GeekBot