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 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