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
The cluster calculates the date as a function of slots from genesis, and it uses that date to determine if a stake account is locked. If we want to set an unlock for something like "one day from now", there's no RPC endpoint to ask the cluster what it thinks "now" is.
Proposed Solution
Add solana cluster-date that returns the date and time from sysvar::Clock.unix_timestamp in the RFC3339 format.
The text was updated successfully, but these errors were encountered:
Along the way, I think it would be nice if solana block-time (with no provided slot) just returned the block time of the most recently root slot. That'll then nicely point out how we have two different sources of truth for elapsed wall clock time.
Problem
The cluster calculates the date as a function of slots from genesis, and it uses that date to determine if a stake account is locked. If we want to set an unlock for something like "one day from now", there's no RPC endpoint to ask the cluster what it thinks "now" is.
Proposed Solution
Add
solana cluster-date
that returns the date and time fromsysvar::Clock.unix_timestamp
in the RFC3339 format.The text was updated successfully, but these errors were encountered: