Rest: add /{network}/epochProgram/:epoch_number #3370
Conversation
| @@ -70,6 +70,10 @@ rev = "d170a9f" | |||
| default-features = false | |||
| optional = true | |||
|
|
|||
| [dependencies.snarkvm-ledger-puzzle-epoch] | |||
There was a problem hiding this comment.
Ideally we expose this via snarkvm::prelude or some other reference to avoid having to reimport a snarkVM crate here. Especially one that will require updating the rev.
There was a problem hiding this comment.
Shall I create another PR for snarkVM to reimport the crate?
| @@ -209,6 +210,20 @@ impl<N: Network, C: ConsensusStorage<N>, R: Routing<N>> Rest<N, C, R> { | |||
| } | |||
| } | |||
|
|
|||
| // GET /<network>/epoch_program/{epochNumber} | |||
There was a problem hiding this comment.
How does the user know what epoch number is the latest?
There was a problem hiding this comment.
Users can use /latest/height or /latest/block to get the latest block height and calculate the epoch_number
|
What is the intention of this PR? Please provide a description. |
There is a scenario where EpochProgram needs to be distributed from the Server to the Provers, we actually have a fork, and it seems reasonable to provide as much information as possible in the snarkOS RPC, so I propose to merge it. |
No description provided.