dusk-blockchain
dusk-blockchain copied to clipboard
Reference implementation of the DUSK Network node, written in Golang
**Describe the bug** "failed to receive candidate from the network" error is reported many times per a node. As an edge case in consensus, this is not a critical issue....
**Describe "Why" this is needed** Because it's outdated **Describe alternatives you've considered** N/A **Additional context** N/A
**Describe the bug** Too many `firststep_verifyCandidateBlock failed` errors/warnings are being reported in a live network. This is most probably due to a race between Chain component accepting next valid block...
**Describe what you want implemented** Options to consider: - Rate limiter - as these messages (the one-to-one Kadcast messaging) are secondary compared to Consensus messaging, they could be sent at...
**Describe "Why" this is needed** Upon breaking changes, we need to ease for the end user any eventual procedure (which might be automated) in upgrading the software. **Describe alternatives you've...
**Describe what you want implemented** A queue that sidesteps the non-determinism of golang scheduling system: https://github.com/dusk-network/dusk-blockchain/blob/f44e1055887cf2a71fd05ec346fc3461cf223d44/pkg/p2p/peer/peer.go#L340 **Describe "Why" this is needed** There is a strong suspicion that some consensus messages...
**Describe what you want implemented** Consensus README files should be reviewed and updated accordingly.
**Describe what you want implemented** A strategy for mempool prioritization based on transaction fees should be introduced. This also involves a (probably custom made) rate limiter that would prioritize transactions...
**Describe what you want implemented** The transaction outputs should be stored in the chain with their correct post-execution position index. **Describe "Why" this is needed** This is needed to increase...
**Describe what kind of specification you want to have created** The key generation should be specified better. @ureeves can you elaborate (low prio)