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
Currently, the nipostBuilder is bloated with logic related to Poet (submitting challenges, certifying or doing PoW, querying for proofs etc.). It could be extracted to a specialized "poet service" that would cover all the details and unclutter the nipostBuilder code. It could also hide the fact that there are multiple poet servers "behind the scenes". I.e. it should expose an API like:
typepoetServiceinterface {
// Submit the `challenge` to all poets, expecting to get the proof by the `deadline`.// takes care of PoW / certification and retries.Submit(challenge type.Hash32, nodeID types.NodeID, deadline time.Time) error// Get the best poet proof for the given challenge (previously submitted via `Submit`).// blocks until the proofs are available and selects the best one.Proof(challenge type.Hash32, nodeID types.NodeID) (*PoetProof, error)
}
The implementation could be scraped from the code existing in nipostBuilder already.
The text was updated successfully, but these errors were encountered:
Description
Currently, the
nipostBuilder
is bloated with logic related to Poet (submitting challenges, certifying or doing PoW, querying for proofs etc.). It could be extracted to a specialized "poet service" that would cover all the details and unclutter the nipostBuilder code. It could also hide the fact that there are multiple poet servers "behind the scenes". I.e. it should expose an API like:The implementation could be scraped from the code existing in nipostBuilder already.
The text was updated successfully, but these errors were encountered: