POSTsui_getCheckpoint
https://sui-mainnet.nodit.io/Return a checkpoint
Commitments to checkpoint state
The Sha256 digest of an EllipticCurveMultisetHash committing to the live object set.
Checkpoint digest
Commitments to epoch specific state (e.g. live object set)
The Sha256 digest of an EllipticCurveMultisetHash committing to the live object set.
next_epoch_committee is Some if and only if the current checkpoint is the last checkpoint of an epoch. Therefore next_epoch_committee can be used to pick the last checkpoint of an epoch, which is often useful to get epoch level summary stats like total gas cost of an epoch, or the total number of transactions from genesis to the end of an epoch. The committee is stored as a vector of validator pub key and stake pairs. The vector should be sorted based on the Committee data structure.
The protocol version that is in effect during the epoch that starts immediately after this checkpoint.
Checkpoint's epoch ID
The running total gas costs of all transactions included in the current epoch so far until this checkpoint.
Cost of computation/execution
The fee for the rebate. The portion of the storage rebate kept by the system.
Storage cost, it's the sum of all storage cost for all objects created or mutated.
The amount of storage cost refunded to the user for all objects deleted or mutated in the transaction.
Total number of transactions committed since genesis, including those in this checkpoint.
Representation of a Checkpoint's digest
Checkpoint sequence number
Timestamp of the checkpoint - number of milliseconds from the Unix epoch Checkpoint timestamps are monotonic, but not strongly monotonic - subsequent checkpoints can have same timestamp if they originate from the same underlining consensus commit
Transaction digests
Validator Signature