Overview
On Ethereum, sending ETH to a contract address automatically triggers thereceive() or fallback() functions, allowing contracts to process incoming funds. On Hedera, these functions also exist but require HBAR to be explicitly sent via contractCall for them to execute. Direct HBAR transfers to a contract’s Hedera account won’t trigger any logic unless additional steps are taken.
Fortunately, the core Solidity patterns—like using transfer(), send(), or call()—work the same way on Hedera, making it easy for developers familiar with EVM. This guide highlights these mechanisms, details the key Hedera-specific considerations, and provides examples to help you handle HBAR transfers in your smart contracts
Sending to Contract
In Solidity, there are three ways to transfer value to and from contracts:transfer(): Sends a fixed amount of gas and reverts on failure.send(): Sends a fixed amount of gas and returnsfalseon failure instead of reverting.call(): A low-level function for sending value that allows specifying gas and includes additional data payloads.
Key Considerations
- Fallback and Receive Functions: When sending HBAR to a contract address via
contractCall, Hedera behaves like Ethereum. Ifreceive()orfallback()functions are defined in the contract, they will be triggered upon receipt of HBAR. - Important Note: Directly transferring HBAR to a contract’s Hedera account (not via
contractCall) will not trigger these functions. To execute logic upon receipt, ensure transfers occur within the EVM environment.
Example Contract Functions for HBAR Transfers
Below is an example of contract functions and how HBAR transfers are handled using Solidity. These patterns are identical to those used for ETH on the EVM:Suggested TutorialFor developers newer to Solidity, we recommend exploring Solidity courses to gain a deeper understanding of handling value transfers. A detailed tutorial on sending and receiving HBAR using Solidity smart contracts on Hedera can be found here.