Skip to content

sync worker state functions #113

Closed
#157
Closed
sync worker state functions#113
#157
Assignees
cheezus1d-velev

Description

@thepiwo
thepiwo
opened on Nov 3, 2017
  • is the highest known block from peers equal to our highest block? (or are we in the middle of analyzing new blocks)
  • are all the blocks, until the highest block, fully validated?
  • only allow the miner to run if both are true

Activity

  1. thepiwo
    changed the title [-]sync worker functions[/-] [+]sync worker state functions[/+] on Nov 3, 2017
  2. d-velev
    assigned
    d-velev
    and
    cheezus1
    on Nov 22, 2017
  3. d-velev
    added a commit that references this issue on Nov 30, 2017

    [GH-#113] Miner starts only when chain is synced

    63f41a9
  4. d-velev
    added 5 commits that reference this issue on Dec 11, 2017

    [GH-#113] Enum.count replaced with Enum.empty?, fixed indendation

    75baf92

    [GH-#113] Fixed credo warning

    a64b0b9

    [GH-#113] Removed parentheses around if

    5dc3cfc

    Merge branch 'master' of https://github.com/aeternity/elixir-research …

    f3297cc

    Merge branch 'master' of https://github.com/aeternity/elixir-research …

    58496c1
  5. thepiwo
    closed this as completedin #157on Dec 15, 2017
  6. thepiwo
    added a commit that references this issue on Dec 15, 2017

    Merge pull request #157 from aeternity/GH-113

    c5936c6
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions