You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the freeze transaction is sending startHour, startMin, endHour, endMin to specify that the services should be frozen at startHour and startMin from now, and should wake up at endHour and endMin from now.
Need to change this to use startTime and endTime of Instant to.
Solution
Need to make the following change of the FreezeTransactionBody:
message FreezeTransactionBody {
int32 startHour = 1 [deprecated = true]; // The start hour (in UTC time), a value between 0 and 23
int32 startMin = 2 [deprecated = true]; // The start minute (in UTC time), a value between 0 and 59
int32 endHour = 3 [deprecated = true]; // The end hour (in UTC time), a value between 0 and 23
int32 endMin = 4 [deprecated = true]; // The end minute (in UTC time), a value between 0 and 59
FileID updateFile = 5; // The ID of the file needs to be updated during a freeze transaction
bytes fileHash = 6; // The hash value of the file, used to verify file content before performing freeze and update
Timestamp startTime = 7; // the freeze start Timestamp
}
Alternatives
No response
The text was updated successfully, but these errors were encountered:
Problem
Currently, the
freeze
transaction is sending startHour, startMin, endHour, endMin to specify that the services should be frozen at startHour and startMin from now, and should wake up at endHour and endMin from now.Need to change this to use startTime and endTime of Instant to.
Solution
Need to make the following change of the FreezeTransactionBody:
Alternatives
No response
The text was updated successfully, but these errors were encountered: