goshimmer
goshimmer copied to clipboard
iotaledger
Prototype implementation of IOTA 2.0
- a malicious nodes could spam a completely different stream of messages than the honest part of the network. It would achieve polluting local version of the Tangle
Evaluate whether we want to use a Kademlia DHT based autopeering instead provided by LibP2P.
The conflicts page on the dashboard has some odd behaviour on different nodes. The dashboard should always - show conflicts sorted by time - show the latest 50 (?) conflicts...
`(s *SimpleFinalityGadget) FirstUnconfirmedMarkerIndex` addresses a ever-growing map containing the `lastConfirmedMarkers`. The map should be re-created periodically, or on some heuristic to free-up space.
Instead of relying on the external tool `pkger` we can use the new native Go functionality to embed static files. https://pkg.go.dev/embed
Reorg is the *reorganization of a node's perception* of the ledger state, and, thus, also the tangle and branches. It is necessary when a node temporarily comes to the wrong...
Create a mechanism to collect and aggregate every (or a subset of) event triggering and processed on all nodes, sorted by time.
Perform fairness and delay experiments with the new congestion control. To do that, adapt the `experiment/` branch that was used in performing similar tests of previous congestion control. The branch...
Instead of merging Confirmed branches into the Master branch, we tag the inclusion state of branches as "Confirmed" and "Rejected"; but we don't prune or reorder the BranchDAG. On one...