- Aug 28, 2019
-
-
Luke Champine authored
-
Marcin Jachymiak authored
-
- Aug 27, 2019
-
-
David Vorick authored
-
Marcin Jachymiak authored
-
- Jul 16, 2018
-
-
Chris authored
-
- Jul 03, 2018
-
-
Luke Champine authored
-
- Dec 13, 2017
-
-
Luke Champine authored
-
- Dec 08, 2017
-
-
Christopher Schinnerl authored
-
- Dec 07, 2017
-
-
Christopher Schinnerl authored
-
Christopher Schinnerl authored
-
- Jul 13, 2017
-
-
Luke Champine authored
-
- Jun 14, 2017
-
-
Luke Champine authored
-
- Jun 13, 2017
-
-
Luke Champine authored
-
- Jun 12, 2017
-
-
Luke Champine authored
-
- May 19, 2017
-
-
Luke Champine authored
-
- Apr 22, 2017
-
-
David Vorick authored
-
David Vorick authored
-
- Apr 01, 2017
-
-
David Vorick authored
-
- Sep 13, 2016
-
-
David Vorick authored
-
- Aug 23, 2016
-
-
David Vorick authored
-
- Aug 19, 2016
-
-
David Vorick authored
-
- Aug 18, 2016
-
-
David Vorick authored
-
David Vorick authored
threadedListenPeer posed a unique challenge because the threads are simultaneously long-running and short-lived (depending on the stability of the peer connection). A separate thread group had to be added to achieve both clean shutdown and to avoid blocking calls the threads.Flush().
-
David Vorick authored
-
- Aug 17, 2016
-
-
David Vorick authored
-
- Jul 17, 2016
-
-
David Vorick authored
-
- Jun 21, 2016
-
-
and use it where RemoteAddr was previously used. This is necessary because the gateway will soon identify peers by their dialable address, not by RemoteAddr.
-
and make logging statements susceptible to byzantine peers debug only
-
- May 31, 2016
-
-
Jordan Horwich authored
-
Jordan Horwich authored
wg.Done was never called in the event that Broadcast exited because StopChan was received.
-
Jordan Horwich authored
-
Jordan Horwich authored
-
Jordan Horwich authored
so that closing closeChan causes immediate exit
-
Jordan Horwich authored
-
- May 26, 2016
-
-
Jordan Horwich authored
-
Jordan Horwich authored
-
Jordan Horwich authored
-
- May 19, 2016
-
-
David Vorick authored
The transaction pool previously would reject transaction sets if some of the parent transactions had been confirmed on the blockchain, preventing the children from ever being accepted or making it onto the blockchain. Now, the transaction pool will prune any parents which have been confirmed on the blockchain. Persistence was added to the transaction pool to make this possible.
-
- Mar 11, 2016
-
-
Jordan Horwich authored
and embed modules.Peer into gateway.peer and update API docs
-
- Mar 07, 2016
-
-
Jordan Horwich authored
-