You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe "Why" this is needed
In order to implement malicious node detection, dusk-blockchain phases should be aware of the message sender.
This information is already present at kadcast level, but so far it's always been ignored (the only information propagate is the received kadcast height)
- Replace the current `message.Header` bytes with a structured `message.Metadata`
- Remove redundant usages of `config.KadcastInitHeader`
- Remove unused `kadcastHeight` in synchronizer
Resolves#1452
- Replace the current `message.Header` bytes with a structured `message.Metadata`
- Remove redundant usages of `config.KadcastInitHeader`
Resolves#1452
- Replace the current `message.Header` bytes with a structured `message.Metadata`
- Remove redundant usages of `config.KadcastInitHeader`
Resolves#1452
- Replace the current `message.Header` bytes with a structured `message.Metadata`
- Remove redundant usages of `config.KadcastInitHeader`
Resolves#1452
Describe "Why" this is needed
In order to implement malicious node detection, dusk-blockchain phases should be aware of the message sender.
This information is already present at kadcast level, but so far it's always been ignored (the only information propagate is the received kadcast height)
Describe alternatives you've considered
N/A
Additional context
See also #1451
The text was updated successfully, but these errors were encountered: