Post
Topic
Board Altcoin Discussion
Re: **** Official Ethereum QA thread ****
by
z0mbie
on 15/02/2014, 13:29:51 UTC
Bump

If I recall correctly Vitalik decided to get rid of crypto-opcodes (like SHA256). The point was to make Ethereum language more universal. R u going to do the next step and get rid of 256-bit numbers? Their usage don't make much sense coz 512-bit cryptoalgos will require to use different tricks to work with 512-bit numbers. Could we have only 64-bit numbers, this would help a lot to implement Ethereum interpretator in Java (which doesn't have native support of 256-bit math).

Edit: Maybe 32-bit is the best choice, JavaScript guys would be happy too.

Best use a library which supports ints larger than 8 bytes. Go uses big.Int, C++ uses Boost's library and there are plenty of other libs in other languages that support 8+ bytes. As for ridding of the opcodes, nothing has been decided.