The timestamp parameter within the ton_proof in the @tonconnect/sdk has historically been implemented as a number type, a practice that has been consistently adopted across all dApps and wallets with strict validation. To align the specification with this widespread implementation, I propose updating the specification to officially change the timestamp parameter type from a string to a number. After a thorough review, I can confirm that all existing wallets currently utilize the number type for this parameter, ensuring that this update would maintain compatibility with existing systems.
The timestamp parameter within the ton_proof in the @tonconnect/sdk has historically been implemented as a number type, a practice that has been consistently adopted across all dApps and wallets with strict validation. To align the specification with this widespread implementation, I propose updating the specification to officially change the timestamp parameter type from a string to a number. After a thorough review, I can confirm that all existing wallets currently utilize the number type for this parameter, ensuring that this update would maintain compatibility with existing systems.