Improve docs around EVM address

Signed-off-by: Miroslav Gatsanoga <[email protected]>
hashgraph · Nov 23, 2022 · e676c94 · e676c94
1 parent f423962
commit e676c94
Show file tree

Hide file tree

Showing 2 changed files with 3 additions and 3 deletions.
diff --git a/services/basic_types.proto b/services/basic_types.proto
@@ -109,7 +109,7 @@ message AccountID {
          * address may be either the encoded form of the shard.realm.num or the keccak-256 hash of a ECDSA_SECP256K1 primitive key.
          *
          * If a transaction lazily-creates this account, a subsequent transaction will be required containing the public key bytes
-         * that map to the EVM address bytes.
+         * that map to the EVM address bytes. Lazy account creates will only support the keccak-256 hash of a ECDSA_SECP256K1 primitive key form.
          */
         bytes evm_address = 5;
     }
@@ -1597,7 +1597,7 @@ message StakingInfo {
 
 message VirtualAddress {
     /**
-     * The 20-byte EVM address.
+     * The 20-byte EVM address that is derived from the keccak-256 hash of a ECDSA_SECP256K1 primitive key.
      */
     bytes address = 1;
 

diff --git a/services/crypto_create.proto b/services/crypto_create.proto
@@ -175,7 +175,7 @@ message CryptoCreateTransactionBody {
     AccountID auto_renew_account = 19;
 
     /**
-     * EOA 20-byte address to create.
+     * EOA 20-byte address to create that is derived from the keccak-256 hash of a ECDSA_SECP256K1 primitive key.
      */
     bytes evm_address = 20;
 }