Search Results
| Search type | Search syntax |
|---|---|
| Tags | [tag] |
| Exact | "words here" |
| Author |
user:1234 user:me (yours) |
| Score |
score:3 (3+) score:0 (none) |
| Answers |
answers:3 (3+) answers:0 (none) isaccepted:yes hasaccepted:no inquestion:1234 |
| Views | views:250 |
| Code | code:"if (foo != bar)" |
| Sections |
title:apples body:"apples oranges" |
| URL | url:"*.example.com" |
| Saves | in:saves |
| Status |
closed:yes duplicate:no migrated:no wiki:no |
| Types |
is:question is:answer |
| Exclude |
-[tag] -apples |
| For more details on advanced search visit our help page | |
Results tagged with raw-transaction
Search options not deleted
user 870
A transaction byte-encoded using the Recursive-Length Prefix (RLP) algorithm. Before Constantinople, it needs to be signed before it will be accepted by the network.
4
votes
2
answers
2k
views
Understanding serialized unsigned raw transaction
I'm currently learning about RLP (ethereum-under-the-hood-part-ii, wiki-eth-rlp) and Ethereum transaction structure, my goal is to create an unsigned raw tx and then sign it.
Right now I'm playing ar …
- 283
2
votes
Understanding serialized unsigned raw transaction
The byte 0xe6 was simply following the 3rd rule describing an rlp list serialized.
tx = new ethTx({});
console.log('RLP-Encoded Tx: 0x' + tx.serialize().toString('hex'))
Gives: 0x c9 80808080808080 …
- 283