Timeline for How do I extract the v, r, s values from a signed transaction?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 11, 2019 at 7:52 | comment | added | Thorkil Værge | Yes. But the RLP encoding also shows that the v value has a length of one byte since values from 1 to 127 are simple encoded as their byte value; values above that has a value indicating the length of the number in bytes followed by the actual value. Also, the three last values of a signed transaction are always v, r, s in that order. | |
| Apr 11, 2019 at 4:18 | vote | accept | CommunityBot | ||
| Apr 11, 2019 at 4:18 | comment | added | user49342 | Nevermind, I got it - it's because v is 1 byte, r and s are 32 bytes. Plus the 2 bytes indicating the length of r and s that makes 67 bytes, which is the length of the string you posted. Thanks! | |
| Apr 11, 2019 at 4:06 | comment | added | user49342 | Brilliant, thank you. Just one more question: How did you know which part of the transaction contained the v,r, and s fields? | |
| Apr 11, 2019 at 3:54 | history | answered | Thorkil Værge | CC BY-SA 4.0 |