List view
- No due date
- No due date
- Due by September 29, 2020
- Due by October 13, 2020•3/3 issues closed
- No due date•1/1 issues closed
- Due by September 15, 2020•16/16 issues closed
- Due by September 1, 2020•9/10 issues closed
- Due by August 13, 2020•1/1 issues closed
- Due by July 30, 2020•12/12 issues closed
- Due by July 16, 2020•14/14 issues closed
- Due by July 2, 2020•17/17 issues closed
- Due by June 18, 2020•18/18 issues closed
- Due by June 4, 2020•16/16 issues closed
- Due by May 21, 2020•18/18 issues closed
- Due by May 7, 2020•8/8 issues closed
- Due by April 23, 2020•13/13 issues closed
- Due by April 9, 2020•19/19 issues closed
- Due by March 26, 2020•25/25 issues closed
These issue are for performance improvement relating to Byron mainnet.
Due by March 12, 2020•23/23 issues closed- Due by February 27, 2020•16/16 issues closed
- Due by February 13, 2020•29/29 issues closed
- Due by January 30, 2020•21/21 issues closed
Testing of block generation; Core Node performance (handle the load of 20 clients); Complete Byron rewrite issues; Windows compatibility for Networking; Size and time limits on protocols; NTP client; Make a decision about if we need to use P2P governor in federated settings;
Due by January 16, 2020•21/21 issues closed- Due by January 2, 2020•1/1 issues closed
- Due by December 19, 2019•18/18 issues closed
- Due by November 21, 2019•3/3 issues closed
- Due by November 21, 2019•2/2 issues closed
- Due by December 5, 2019
- No due date
- Due by November 21, 2019•13/13 issues closed
- Due by December 5, 2019•12/12 issues closed
- Due by December 5, 2019
- Due by December 5, 2019
Integrate the Shelley ledger layer.
No due dateExtra functionality and optimisations for the Chain Sync Client
No due dateWe need to provide various network interfaces for the network layer: - [ ] low level interface for the mux layer - [ ] node to node interface - [ ] node to client interface The low level interface will let run a mux server, and connect to other peers. The other interfaces will be build on top of it. For node to node interface, the consensus layer will provide `ChainSync` client , all the other protoocls will be provided by the network layer. In this case we will be responsible for running the block fetch logic. Running it requires some changes to the way we currently run the protocols. We need to bracket the block fetch client. This is component is provided by block fetch logic. For node to client, we will run `ChainSync` client instantiated with full blocks, so there is no need to run block fetch logic. Depending on application we might need to also support `tx-submission` protocol (for example it will be required by the wallet node to subimt transactions, but not by an explorer). It would be good to gather more example applications to build something that can frame all of them in a convenient way.
Due by April 30, 2019•5/5 issues closedThis is a milestone frameing the epic: https://github.com/input-output-hk/ouroboros-network/issues/66
No due date•4/5 issues closedTasks required to run and deploy it as a standalone node.
No due date- No due date
Milestone for reducing technical debt in the codebase
No due date- No due date•11/11 issues closed
Integrate the Byron ledger layer.
No due dateTransitional protocol that switches from PermBFT to Praos/Genesis.
No due dateChainDB and storage-related, including the ImmutableDB, LedgerDB, and VolatileDB.
No due dateDuncan reckons that the changes for Genesis can be limited to the Chain Sync Client.
No due dateProtocol testing
No due dateNote: we could conceivably implement Genesis very late in the pipeline, as consensus does not implement on having genesis implemented (it only affects security). I'd still recommend against doing this however since I suspect that implementing genesis will require some code refactoring that is easier to do earlier in the process.
No due date- No due date
Support DeltaQ in the low level networking layer
No due date•1/1 issues closedDesign and implement the multiplexing, versioning, serialisation and framing scheme for running the mini-protocols on a single bearer channel on top of TCP and simulation. Document the low level wire protocol, serialisation and framing.
Due by February 22, 2019•3/3 issues closed