good morning!!!!

Skip to content
Snippets Groups Projects
Select Git revision
  • 57a3fab8a75eeb9c2f4fab770b73b51b9fe672c5
  • master default protected
  • v0.2.16-candidate
  • shivam/rpcAddBorTx
  • default-cli-config
  • shivam/minerRecommitFix
  • vcastellm/pos-296-bump-go-version-in-bor-and-heimdall
  • shivam/ethstats-backend-fix
  • v0.2.16-beta1-candidate
  • v0.2.15-beta3-candidate
  • shivam/newCli-IPC
  • v0.3.0-dev
  • checkpoint-whitelist-master
  • shivam/codecov
  • jdkanani/fix-typo-log
  • shivam/hardcoded-spans-v0.2.14
  • shivam/hardcoded-spans
  • shivam/fast-state-sync
  • shivam/fast-state-sync-master
  • gethv1.10.15-merge
  • fix-txpool-2
  • v0.2.14-tmp-span-hotfix
  • v0.2.15-beta2
  • v0.2.15-beta1
  • v0.3.0-beta3
  • v0.3.0-beta2
  • v0.3.0-beta1
  • v0.2.14
  • v0.2.13
  • v0.2.13-beta2
  • v0.2.13-beta1
  • v0.2.12
  • v0.2.12-beta3
  • v0.2.12-beta1
  • v0.2.12-beta2
  • v0.2.11
  • v0.2.10
  • v0.2.10-beta2
  • v0.2.9
  • v0.2.9-beta1
  • v0.2.8
41 results

p2p

  • Clone with SSH
  • Clone with HTTPS
  • Forked from github / maticnetwork / bor
    549 commits behind the upstream repository.
    user avatar
    Péter Szilágyi authored and GitHub committed
    This PR ensures that wiping all data associated with a node (apart from its nodekey)
    will not generate already used sequence number for the ENRs, since all remote nodes
    would reject them until they out-number the previously published largest one.
    
    The big complication with this scheme is that every local update to the ENR can
    potentially bump the sequence number by one. In order to ensure that local updates
    do not outrun the clock, the sequence number is a millisecond-precision timestamp,
    and updates are throttled to occur at most once per millisecond.
    
    Co-authored-by: default avatarFelix Lange <fjl@twurst.com>
    6ef3a168
    History
    Code owners
    Assign users and groups as approvers for specific file changes. Learn more.