Closed butonium closed 7 months ago
This PR introduces epoch_start_timestamp within ClusterHistoryEntry to enhance APY tracking, as detailed in https://github.com/jito-foundation/stakenet/issues/18
epoch_start_timestamp
ClusterHistoryEntry
The epoch_start_timestamp is assigned during the execution of the copy_cluster_info ix for the current epoch
copy_cluster_info
A new function has been added to modify the Clock sysvar. This was necessary because advance_num_epochs did not update the Clock sysvar during tests
advance_num_epochs
This PR depends on the successful merge of https://github.com/jito-foundation/stakenet/pull/22. After merge, I will update this accordingly.
Context:
This PR introduces
epoch_start_timestamp
withinClusterHistoryEntry
to enhance APY tracking, as detailed in https://github.com/jito-foundation/stakenet/issues/18The
epoch_start_timestamp
is assigned during the execution of thecopy_cluster_info
ix for the current epochTests:
A new function has been added to modify the Clock sysvar. This was necessary because
advance_num_epochs
did not update the Clock sysvar during testsDependencies
This PR depends on the successful merge of https://github.com/jito-foundation/stakenet/pull/22. After merge, I will update this accordingly.