Client and backend. This class is shared: the same code is compiled into your app and into your server, so everything on this page works in both.
public final class EvmAddress
- Object
- EvmAddress
A 20-byte address on Ethereum or any EVM chain (Polygon, Arbitrum, Base, BNB Chain…).
An address is the last 20 bytes of the Keccak-256 of the 64-byte public key. EIP-55
spells it in mixed case so the case is a checksum: parse rejects a mixed-case address
whose case is wrong, which catches a mistyped character before funds go to an address
nobody holds. An all-lowercase or all-uppercase address carries no checksum and is
accepted as written, as every wallet does.
Methods
Inherited methods
Method details
fromBytes
public static EvmAddress fromBytes(byte[] address)Wraps 20 address bytes.
fromPublicKey
public static EvmAddress fromPublicKey(byte[] publicKey)The address of a secp256k1 public key in any SEC 1 form, or the raw 64 bytes.
fromPrivateKey
public static EvmAddress fromPrivateKey(byte[] privateKey)The address a private key controls.
contractAddress
public static EvmAddress contractAddress(EvmAddress deployer, long nonce)The address of a contract deployed with
CREATE by deployer at nonce.create2Address
public static EvmAddress create2Address(EvmAddress deployer, byte[] salt32, byte[] initCodeHash)The address of a contract deployed with
CREATE2.parse
public static EvmAddress parse(String text)Parses
0x and 40 hex digits, checking the EIP-55 checksum when the text is in mixed
case.Throws
IllegalArgumentException- for a malformed address or a wrong checksum
isValid
public static boolean isValid(String text)Tells whether
parse accepts the text.toBytes
public byte[] toBytes()A copy of the 20 bytes.
toChecksumString
public String toChecksumString()The EIP-55 mixed-case form, which is how an address should be shown.
toLowerCaseString
public String toLowerCaseString()The lowercase
0x form.toString
public String toString()The EIP-55 form.
equals
public boolean equals(Object o)Indicates whether some other object is “equal to” this one.
The equals method implements an equivalence relation: It is reflexive: for any reference value x, x.equals(x) should return true. It is symmetric: for any reference values x and y, x.equals(y) should return true if and only if y.equals(x) returns true. It is transitive: for any reference values x, y, and z, if x.equals(y) returns true and y.equals(z) returns true, then x.equals(z) should return true. It is consistent: for any reference values x and y, multiple invocations of x.equals(y) consistently return true or consistently return false, provided no information used in equals comparisons on the object is modified. For any non-null reference value x, x.equals(null) should return false.
The equals method for class Object implements the most discriminating possible equivalence relation on objects; that is, for any reference values x and y, this method returns true if and only if x and y refer to the same object (x==y has the value true).
hashCode
public int hashCode()Returns a hash code value for the object. This method is supported for the benefit of hashtables such as those provided by java.util.Hashtable.
The general contract of hashCode is: Whenever it is invoked on the same object more than once during an execution of a Java application, the hashCode method must consistently return the same integer, provided no information used in equals comparisons on the object is modified. This integer need not remain consistent from one execution of an application to another execution of the same application. If two objects are equal according to the equals(Object) method, then calling the hashCode method on each of the two objects must produce the same integer result. It is not required that if two objects are unequal according to the equals(java.lang.Object) method, then calling the hashCode method on each of the two objects must produce distinct integer results. However, the programmer should be aware that producing distinct integer results for unequal objects may improve the performance of hashtables.
As much as is reasonably practical, the hashCode method defined by class Object does return distinct integers for distinct objects. (This is typically implemented by converting the internal address of the object into an integer, but this implementation technique is not required by the JavaTM programming language.)