Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Categories
- 13K All Categories
- 6.9K Mining
- 303 Pool Discussion
- 990 General Project Discussion (non-technical)
- 332 Education
- 668 Protocol and Client discussion
- 126 web3-js
- 22 Whisper
- 11 Swarm
- 2 RLP
- 227 IoT & Hardware
- 818 Smart Contracts and Dapps
- 28 Serpent
- 286 Solidity
- 330 Projects
- 1.2K Reference clients code and builds
- 244 Eth & AlethZero- Cpp Implementation
- 433 Geth - Go Implementation
- 214 Mist
- 14 Node.js Implementation
- 34 Python Implementation
- 47 Mix
- 21 Other Implementations
- 142 Meetups
- 27 Other Events
- 148 Jobs & Skills
- 166 Press and Articles
- 70 Audio/Video
- 251 Ether Sale
- 801 Other Languages
- 34 Chinese
- 169 German
- 23 Italian
- 90 French
- 2 Hebrew
- 6 Japanese
- 61 Portugese
- 32 Romanian
- 122 Russian
- 185 Spanish
- 33 Turkish
- 99 Watercooler
transaction content: extra padding?
So I'm trying to do my first transaction to a contract.
Watching
I see when they build the transaction the resulting address is 32 bytes, (a padding of zeros there) and they corrected the original contract during the video. (so you can see a Splitter and a Splitter2 with just that difference).
My current AlethZero compilation (AFAIK is commit 47572e8041da9360d7f7627196223afbfea9efe9 ) doesn't pad any zero.
Does anyone know the reason?
Watching
I see when they build the transaction the resulting address is 32 bytes, (a padding of zeros there) and they corrected the original contract during the video. (so you can see a Splitter and a Splitter2 with just that difference).My current AlethZero compilation (AFAIK is commit 47572e8041da9360d7f7627196223afbfea9efe9 ) doesn't pad any zero.
Does anyone know the reason?
Comments