Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Poet Operator Manual. #391

Merged
merged 1 commit into from
Sep 22, 2023
Merged

Poet Operator Manual. #391

merged 1 commit into from
Sep 22, 2023

Conversation

pigmej
Copy link
Member

@pigmej pigmej commented Sep 13, 2023

No description provided.

@codecov
Copy link

codecov bot commented Sep 13, 2023

Codecov Report

Merging #391 (54914d9) into develop (a3f5318) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           develop    #391   +/-   ##
=======================================
  Coverage     74.8%   74.8%           
=======================================
  Files           23      23           
  Lines         1906    1906           
=======================================
  Hits          1426    1426           
  Misses         360     360           
  Partials       120     120           

docs/poet_config_sample.conf Outdated Show resolved Hide resolved
Comment on lines 9 to 11
* https://POET_URL/v1/pow_params
nodes will query that URL to get the POW challenge parameters.
it will change every round, safe to cache in all other moments.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It could also change if the poet had been restarted with a different pow-difficulty, in which case the cache should be invalidated.

docs/poet_operator_manual.md Show resolved Hide resolved
docs/poet_operator_manual.md Outdated Show resolved Hide resolved
docs/poet_operator_manual.md Outdated Show resolved Hide resolved
docs/poet_operator_manual.md Outdated Show resolved Hide resolved
docs/poet_operator_manual.md Outdated Show resolved Hide resolved
docs/poet_operator_manual.md Outdated Show resolved Hide resolved
> [!NOTE]
> PoET will *not* start generating tree when it will detect that the round should be already in progress but the state of the round is empty. This is to prevent the situation when PoET is doing work for nothing
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's not entirely true.

It will execute a round without any members. It's not optimal and could be improved.

But it will NOT create and execute an empty round when it is started in the middle of a round.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah but that's what I mean by "empty state of the round" not that it has no members but that it has not run yet etc. Could try to think how to make it more obvious.

docs/poet_operator_manual.md Outdated Show resolved Hide resolved
@pigmej pigmej marked this pull request as ready for review September 18, 2023 14:43
@pigmej pigmej added this pull request to the merge queue Sep 22, 2023
Merged via the queue into develop with commit f0bb2d5 Sep 22, 2023
10 of 11 checks passed
@fasmat fasmat deleted the poet_operator_manual branch September 26, 2023 16:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants