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
Slot / block's are keyed to a specific computer time in Solana. The retrieval of that time however is an RPC method request which accepts the slot as the arg and returns unixtimestamp https://solana.com/docs/rpc/http/getblocktime.
Wherever we are generating our indexes, if the unixtime is returned through our parsing, we would like to make an attempt to store it (so we don't end up checking twice).
Ideally, if we can store this in a manner where there is a consistent data stream and indexing then we could use approximation (roughly 400ms block time) when we don't have an exact unixtime or slot stored.
This for example could mean that say we have a previous slot 2000012312 which time was 2024-02-01 12:23:33.112233 and we're looking for time for a slot 2000012342, well we can take that date and use 400ms * 30 and roughly come up with a time for it (importantly not requiring an RPC call).
The text was updated successfully, but these errors were encountered:
Slot / block's are keyed to a specific computer time in Solana. The retrieval of that time however is an RPC method request which accepts the slot as the arg and returns unixtimestamp https://solana.com/docs/rpc/http/getblocktime.
Wherever we are generating our indexes, if the unixtime is returned through our parsing, we would like to make an attempt to store it (so we don't end up checking twice).
Ideally, if we can store this in a manner where there is a consistent data stream and indexing then we could use approximation (roughly 400ms block time) when we don't have an exact unixtime or slot stored.
This for example could mean that say we have a previous slot 2000012312 which time was 2024-02-01 12:23:33.112233 and we're looking for time for a slot 2000012342, well we can take that date and use 400ms * 30 and roughly come up with a time for it (importantly not requiring an RPC call).
The text was updated successfully, but these errors were encountered: