good morning!!!!

Skip to content
Snippets Groups Projects
  1. Apr 15, 2019
  2. Apr 08, 2019
  3. Apr 04, 2019
  4. Apr 03, 2019
  5. Mar 25, 2019
  6. Mar 20, 2019
  7. Mar 18, 2019
  8. Mar 06, 2019
  9. Feb 26, 2019
    • Zsolt Felföldi's avatar
      les, les/flowcontrol: improved request serving and flow control (#18230) · c2003ed6
      Zsolt Felföldi authored
      This change
      
      - implements concurrent LES request serving even for a single peer.
      - replaces the request cost estimation method with a cost table based on
        benchmarks which gives much more consistent results. Until now the
        allowed number of light peers was just a guess which probably contributed
        a lot to the fluctuating quality of available service. Everything related
        to request cost is implemented in a single object, the 'cost tracker'. It
        uses a fixed cost table with a global 'correction factor'. Benchmark code
        is included and can be run at any time to adapt costs to low-level
        implementation changes.
      - reimplements flowcontrol.ClientManager in a cleaner and more efficient
        way, with added capabilities: There is now control over bandwidth, which
        allows using the flow control parameters for client prioritization.
        Target utilization over 100 percent is now supported to model concurrent
        request processing. Total serving bandwidth is reduced during block
        processing to prevent database contention.
      - implements an RPC API for the LES servers allowing server operators to
        assign priority bandwidth to certain clients and change prioritized
        status even while the client is connected. The new API is meant for
        cases where server operators charge for LES using an off-protocol mechanism.
      - adds a unit test for the new client manager.
      - adds an end-to-end test using the network simulator that tests bandwidth
        control functions through the new API.
      c2003ed6
  10. Feb 25, 2019
  11. Feb 21, 2019
  12. Jan 24, 2019
  13. Dec 11, 2018
  14. Dec 06, 2018
  15. Nov 29, 2018
  16. Nov 26, 2018
  17. Nov 15, 2018
  18. Oct 08, 2018
  19. Oct 01, 2018
  20. Sep 24, 2018
    • Felix Lange's avatar
      all: new p2p node representation (#17643) · 30cd5c18
      Felix Lange authored
      Package p2p/enode provides a generalized representation of p2p nodes
      which can contain arbitrary information in key/value pairs. It is also
      the new home for the node database. The "v4" identity scheme is also
      moved here from p2p/enr to remove the dependency on Ethereum crypto from
      that package.
      
      Record signature handling is changed significantly. The identity scheme
      registry is removed and acceptable schemes must be passed to any method
      that needs identity. This means records must now be validated explicitly
      after decoding.
      
      The enode API is designed to make signature handling easy and safe: most
      APIs around the codebase work with enode.Node, which is a wrapper around
      a valid record. Going from enr.Record to enode.Node requires a valid
      signature.
      
      * p2p/discover: port to p2p/enode
      
      This ports the discovery code to the new node representation in
      p2p/enode. The wire protocol is unchanged, this can be considered a
      refactoring change. The Kademlia table can now deal with nodes using an
      arbitrary identity scheme. This requires a few incompatible API changes:
      
        - Table.Lookup is not available anymore. It used to take a public key
          as argument because v4 protocol requires one. Its replacement is
          LookupRandom.
        - Table.Resolve takes *enode.Node instead of NodeID. This is also for
          v4 protocol compatibility because nodes cannot be looked up by ID
          alone.
        - Types Node and NodeID are gone. Further commits in the series will be
          fixes all over the the codebase to deal with those removals.
      
      * p2p: port to p2p/enode and discovery changes
      
      This adapts package p2p to the changes in p2p/discover. All uses of
      discover.Node and discover.NodeID are replaced by their equivalents from
      p2p/enode.
      
      New API is added to retrieve the enode.Node instance of a peer. The
      behavior of Server.Self with discovery disabled is improved. It now
      tries much harder to report a working IP address, falling back to
      127.0.0.1 if no suitable address can be determined through other means.
      These changes were needed for tests of other packages later in the
      series.
      
      * p2p/simulations, p2p/testing: port to p2p/enode
      
      No surprises here, mostly replacements of discover.Node, discover.NodeID
      with their new equivalents. The 'interesting' API changes are:
      
       - testing.ProtocolSession tracks complete nodes, not just their IDs.
       - adapters.NodeConfig has a new method to create a complete node.
      
      These changes were needed to make swarm tests work.
      
      Note that the NodeID change makes the code incompatible with old
      simulation snapshots.
      
      * whisper/whisperv5, whisper/whisperv6: port to p2p/enode
      
      This port was easy because whisper uses []byte for node IDs and
      URL strings in the API.
      
      * eth: port to p2p/enode
      
      Again, easy to port because eth uses strings for node IDs and doesn't
      care about node information in any way.
      
      * les: port to p2p/enode
      
      Apart from replacing discover.NodeID with enode.ID, most changes are in
      the server pool code. It now deals with complete nodes instead
      of (Pubkey, IP, Port) triples. The database format is unchanged for now,
      but we should probably change it to use the node database later.
      
      * node: port to p2p/enode
      
      This change simply replaces discover.Node and discover.NodeID with their
      new equivalents.
      
      * swarm/network: port to p2p/enode
      
      Swarm has its own node address representation, BzzAddr, containing both
      an overlay address (the hash of a secp256k1 public key) and an underlay
      address (enode:// URL).
      
      There are no changes to the BzzAddr format in this commit, but certain
      operations such as creating a BzzAddr from a node ID are now impossible
      because node IDs aren't public keys anymore.
      
      Most swarm-related changes in the series remove uses of
      NewAddrFromNodeID, replacing it with NewAddr which takes a complete node
      as argument. ToOverlayAddr is removed because we can just use the node
      ID directly.
      30cd5c18
  21. Sep 21, 2018
  22. Sep 20, 2018
  23. Sep 14, 2018
  24. Aug 28, 2018
  25. Aug 21, 2018
  26. Aug 17, 2018
    • Felix Lange's avatar
      les: fix crasher in NodeInfo when running as server (#17419) · 2695fa22
      Felix Lange authored
      * les: fix crasher in NodeInfo when running as server
      
      The ProtocolManager computes CHT and Bloom trie roots by asking the
      indexers for their current head. It tried to get the indexers from
      LesOdr, but no LesOdr instance is created in server mode.
      
      Attempt to fix this by moving the indexers, protocol creation and
      NodeInfo to a new lesCommons struct which is embedded into both server
      and client.
      
      All this setup code should really be cleaned up, but this is just a
      hotfix so we have to do that some other time.
      
      * les: fix commons protocol maker
      2695fa22
  27. Aug 15, 2018
  28. Aug 14, 2018
    • Zsolt Felföldi's avatar
      les: implement client connection logic (#16899) · b2ddb1fc
      Zsolt Felföldi authored
      This PR implements les.freeClientPool. It also adds a simulated clock
      in common/mclock, which enables time-sensitive tests to run quickly
      and still produce accurate results, and package common/prque which is
      a generalised variant of prque that enables removing elements other
      than the top one from the queue.
      
      les.freeClientPool implements a client database that limits the
      connection time of each client and manages accepting/rejecting
      incoming connections and even kicking out some connected clients. The
      pool calculates recent usage time for each known client (a value that
      increases linearly when the client is connected and decreases
      exponentially when not connected). Clients with lower recent usage are
      preferred, unknown nodes have the highest priority. Already connected
      nodes receive a small bias in their favor in order to avoid accepting
      and instantly kicking out clients.
      
      Note: the pool can use any string for client identification. Using
      signature keys for that purpose would not make sense when being known
      has a negative value for the client. Currently the LES protocol
      manager uses IP addresses (without port address) to identify clients.
      b2ddb1fc
  29. Aug 10, 2018
  30. Aug 03, 2018
    • Gary Rong's avatar
      consensus/ethash: move remote agent logic to ethash internal (#15853) · 51db5975
      Gary Rong authored
      * consensus/ethash: start remote ggoroutine to handle remote mining
      
      * consensus/ethash: expose remote miner api
      
      * consensus/ethash: expose submitHashrate api
      
      * miner, ethash: push empty block to sealer without waiting execution
      
      * consensus, internal: add getHashrate API for ethash
      
      * consensus: add three method for consensus interface
      
      * miner: expose consensus engine running status to miner
      
      * eth, miner: specify etherbase when miner created
      
      * miner: commit new work when consensus engine is started
      
      * consensus, miner: fix some logics
      
      * all: delete useless interfaces
      
      * consensus: polish a bit
      51db5975
  31. Jul 30, 2018
  32. Jul 12, 2018
  33. Jul 04, 2018
  34. Jun 25, 2018
Loading