status-im
/
EIPs
mirror of https://github.com/status-im/EIPs.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Automatically merged updates to draft EIP(s) 1444 

Hi, I'm a bot! This change was automatically merged because:

 - It only modifies existing Draft or Last Call EIP(s)
 - The PR was approved or written by at least one author of each modified EIP
 - The build is passing
This commit is contained in:
Brooklyn Zelenka 2018-10-20 21:23:17 -07:00 committed by EIP Automerge Bot
parent ff95e31eea
commit 5db308d939
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
EIPS/eip-1444.md
View File

@ -133,7 +133,7 @@ Text with 2 or more arguments SHOULD use the POSIX parameter field extension.
### `bytes32` Keys
`bytes32` is very efficient since it is the EVM's base word size. Given the enormous number of elements (|A| > 1.1579 × 10<sup>77</sup>), it can embed nearly any practical signal, enum, or state. In cases where an application's key is longer than `bytes32`, hashing that long key can map that value into the correct width.
`bytes32` is very efficient since it is the EVM's base word size. Given the enormous number of elements (<pre>|A| > 1.1579 × 10<sup>77</sup></pre>), it can embed nearly any practical signal, enum, or state. In cases where an application's key is longer than `bytes32`, hashing that long key can map that value into the correct width.
Designs that use datatypes with small widths than `bytes32` (such as `bytes1` in [ERC-1066](https://eips.ethereum.org/EIPS/eip-1066)) can be directly embedded into the larger width. This is a trivial one-to-one mapping of the smaller set into the the larger one.