Contract Deployment and Lifecycle
When a contract is deployed on GAYA, it transitions to an active state immediately upon deployment. This contract will remain active unless explicitly terminated through a destruction function encoded in its logic. GAYA’s approach eliminates intermediary states, allowing developers and users to clearly understand a contract’s operational status at any point.
Raw and Checksum Addresses in GAYA
To further enhance security and user experience, GAYA employs a checksum mechanism for smart contract addresses:
Raw Addresses: These are the basic 160-bit hexadecimal addresses without any modifications. They are used as the fundamental format for identifying smart contracts on the network.
Checksum Addresses: To prevent errors during address entry, GAYA’s system applies a checksum by capitalizing certain characters within the address based on the Keccak-256 hash. This capitalization allows users and applications to detect potential errors in address formatting more easily.
Technical Insight The checksum for addresses is generated by re-hashing the original address with Keccak-256. Specific characters in the address are then capitalized according to the hash result, creating a checksum. This security enhancement reduces the likelihood of incorrect address entry, helping users identify errors before executing transactions.
Last updated