Skip to content

implement initial sync from latest block to genesis block #97

Closed
Closed
implement initial sync from latest block to genesis block#97
Assignees
nedelcho-delchev-tuescheezus1d-velev

Description

@thepiwo
thepiwo
opened on Oct 25, 2017

#88 has to be finished first
only do this in pair programming

  • blocks sync:
    1. ask random peers about top and get top block of random peer(s) if we don't have it
    2. for every block that we don't know the parent ask random peers for parent. Optional: mark block as "bad" if no-one can provide it's parent
    • for every block we get in i., ii.:
      a. "single" validate transactions without chainstate, coinbase sum, version and root_hash(discard if invalid)
      b. get parent if we don't have parent
    1. for every "single" validated block that has not been "fully" validated:
      a. if parent is not validate. Validate parent.
      b. If parent does not exist skip.
      c. validate the block
    2. compare height of topmost block with chainstate height. If it's higher advance chainstate:
      a. generate list of block between chainstate and highest block by traversing from top. If you find an marked as "invalid" block, mark all of it's children as invalid. (all blocks from top block to that block including top)
      b. if you get to genesis while looking for chainstate block: regenerate chainstate from genesis. (We have to have some chainstate snapshots in future to avoid that)
      c. validate blocks in order beginning with child of chainstate block. Update chainstate while doing that.
      d. if validation fails at one point mark the block as "invalid" and mark all it's children as "invalid".
      e. if validation failed at one point try again to get the topmost block and if it's not chainstate block try to advance chainstate as above described.

Activity

  1. d-velev
    assigned
    d-velev
    ,
    nedelcho-delchev-tues
    and
    cheezus1
    on Nov 3, 2017
  2. cheezus1
    added a commit that references this issue on Nov 3, 2017

    [GH-#97] Sync GenServer added; Get unknown blocks from peers

    0020a8c
  3. d-velev
    added a commit that references this issue on Nov 3, 2017

    [GH-#97] Save unknown blocks from all peers to Sync state

    7861bcd
  4. cheezus1
    added a commit that references this issue on Nov 6, 2017

    [GH-#97] Function for updating block statuses

    a46faa4
  5. d-velev
    added a commit that references this issue on Nov 6, 2017

    [GH-#97] Single validate all Sync state blocks

    9814bbe
  6. cheezus1
    added a commit that references this issue on Nov 7, 2017

    [GH-#97] Add unknown blocks to our chain

    8c9015b
  7. d-velev
    added a commit that references this issue on Nov 9, 2017

    [GH-#97] Received broadcasted blocks are added to the Sync state and …

    145f449
  8. cheezus1
    added a commit that references this issue on Nov 9, 2017

    [GH-#97] Improved error handling

    9e3f6e6
  9. d-velev
    added 3 commits that reference this issue on Nov 10, 2017

    [GH-#97] Server responds with 404 if block isn't found, Sync worker r…

    01cf560

    [GH-#97] Merge GH-97 with master and move Sync.Worker to Peers.Sync

    4f560f3

    [GH-#97] Removed unused module and changed function call in block_con…

    245d5ba
  10. cheezus1
    added a commit that references this issue on Nov 14, 2017

    [GH-#97] Fixed getting new peers

    cd1dbfb
  11. d-velev
    added a commit that references this issue on Nov 14, 2017

    [GH-#97] Ask every newly added peer for his blocks

    45fddef

  12. 8 remaining items

  13. cheezus1
    added a commit that references this issue on Nov 20, 2017

    [GH-#97] Added comments and fixed Sync.check_peer_block

    d91a6cd
  14. d-velev
    added a commit that references this issue on Nov 20, 2017

    [GH-#97] Blocks in the Sync module are now single validated before be…

    5a36dfd
  15. cheezus1
    added a commit that references this issue on Nov 20, 2017

    [GH-97] Removed statuses from state

    9934246
  16. d-velev
    added 3 commits that reference this issue on Nov 20, 2017

    [GH-#97] Chain.has_block? added, Sync.check_peer_block refactored

    12673e2

    [GH-#97] Sync state now stores block_hash => block instead of peer

    f3d841c

    [GH-#97] Now checking if we have broadcasted block in Chain before ad…

    a0bb2e4
  17. cheezus1
    added a commit that references this issue on Nov 21, 2017

    [GH-#97] Merged master

    8f0ee02
  18. d-velev
    added a commit that references this issue on Nov 22, 2017

    [GH-#97] Single validate blocks before adding to Sync state

    dc524fe
  19. cheezus1
    added a commit that references this issue on Nov 22, 2017

    [GH-#97] Checking peer block's hash

    86a880e
  20. d-velev
    added a commit that references this issue on Nov 22, 2017

    [GH-#97] Fixed conflicts after merging with master

    cb7f0b4
  21. cheezus1
    added a commit that references this issue on Nov 22, 2017

    [GH-#97] Added missing code in validate_block!

    3b1fe3f
  22. d-velev
    added a commit that references this issue on Nov 23, 2017

    [GH-#97] Return state when block added to Sync is invalid

    6c72097
  23. cytadela8
    added a commit that references this issue on Nov 23, 2017

    Merge pull request #126 from aeternity/GH-97

    9664421

  24. cytadela8 commented on Nov 29, 2017

    @cytadela8
    cytadela8
    on Nov 29, 2017
    Contributor

    This was fixed by #126.

  25. cytadela8
    closed this as completedon Nov 29, 2017
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