How a single transfer creates a Hedera account

One transfer, one account

On @hedera, an EVM address derived from a public key can receive value before any account formally exists on the network. The act of sending funds to that address is what registers the account. No pre-assigned 0.0.x identifier is required in advance.

Under the hood, Hedera's auto account creation works by generating an EVM address alias from an ECDSA public key. Specifically, the alias is the rightmost 20 bytes of the Keccak-256 hash of that public key, following the same calculation described in the Ethereum Yellow Paper. Applications such as wallets and exchanges can generate this address entirely offline, then hand it to a sender without any prior on-chain step.

HIP-32 introduced this mechanism for $HBAR transfers. When HBAR is sent to an alias that has no corresponding account, the network auto-creates one and deducts the account creation fee from the amount sent. The new account's opening balance is therefore the sent amount minus that fee.

How HIP-542 extended coverage to tokens and NFTs

Token transfers presented a harder problem. Because the account creation fee must be paid in $HBAR, sending an HTS fungible token or NFT to a non-existent alias previously returned an INVALID_ACCOUNT_ID error. There was no mechanism to convert token units into the HBAR needed to cover the fee.

HIP-542 resolved this by shifting the fee burden. Rather than deducting it from the transferred asset, the network charges the account creation fee to the payer of the transfer transaction. The recipient gets the full token or NFT amount, and the sender covers the setup cost. The transfer also bundles one auto-association slot, so the new account can hold the incoming token without a separate association step. The result is that what previously required three transactions, a CryptoCreate, a TokenAssociate, and a CryptoTransfer, now collapses into one.

The change also improves interoperability. Ethereum contracts routinely allow ERC-20 and ERC-721 assets to be sent to addresses that do not yet have an on-chain presence, and HIP-542 brings Hedera's behavior in line with those expectations.

Sources:
Hedera Docs: Auto Account Creation
HIP-542: Payer-Sponsored Auto-Account Creation with HTS Assets
HIP-32: Auto Account Creation