📢 Gate Square #Creator Campaign Phase 1# is now live – support the launch of the PUMP token sale!
The viral Solana-based project Pump.Fun ($PUMP) is now live on Gate for public sale!
Join the Gate Square Creator Campaign, unleash your content power, and earn rewards!
📅 Campaign Period: July 11, 18:00 – July 15, 22:00 (UTC+8)
🎁 Total Prize Pool: $500 token rewards
✅ Event 1: Create & Post – Win Content Rewards
📅 Timeframe: July 12, 22:00 – July 15, 22:00 (UTC+8)
📌 How to Join:
Post original content about the PUMP project on Gate Square:
Minimum 100 words
Include hashtags: #Creator Campaign
Hedera Announces Major API Updates With HIP-1217 Deployment Timeline
HomeNews* Hedera is updating its Mirror Node API for smart contract calls to improve consistency and accuracy.
Among the updates, calls using a Number Alias—a special format for identifying accounts—will now fail if a Keccak-256 alias exists for a given account. This means developers must check and use the correct account alias. The evm_address field from the mirror node API or the contractAccountId field from the Hedera SDK should be used to confirm the proper alias. For ECDSA accounts, the Keccak-256 alias must be used unless a rare exception applies.
Developers should also note that contract calls may now fail with an INSUFFICIENT_PAYER_BALANCE error if the payer account does not have enough balance. New error handling will return more specific messages, such as INVALID_CONTRACT_ID, and require updates in client-side applications. For gas estimates, users will notice slight but more accurate differences, especially when deploying contracts.
Additional impacts include changes to how contract calls return default values and KYC (Know Your Customer) status, which will now reflect the true state of consensus nodes. Error codes for certain failed operations will also change, for example, returning CONTRACT_REVERT_EXECUTED instead of previously used codes.
These changes are not backward compatible, and Hedera urges developers to thoroughly test their applications in the Previewnet and Testnet environments, where the modularized flow operates at full capacity. Mirror node operators can enable this new logic early by adjusting relevant environment variables as described in the technical guidance.
Timeline details show that most updates—including error codes, gas estimates, and KYC status handling—will be fully enforced by September 1, 2025. Address resolution and payer balance validation will go live on December 1, 2025. Teams needing extra time can request temporary access to legacy functionality by contacting the relevant support via Discord (handle: reccetech).
Previous Articles: