Eclésio Junior

> @EclesioMeloJunior can you resolve the conflicts? Of course, once I finish PR #2267 which this one depends on

I would suggest keeping the messages variadic data types in the messages pkg each in a file. I would suggest renaming the `types.go` file to `round.go` as I think the...

@qdm12 > * `messages` in this PR, since it contains messages and some other types. I'll create a `messages` package in another PR. I don't see any problem with having...

I noticed that substrate only cast the vote after receiving a neighbor message from the peers, while we define a prevote without waiting for the peers, other than that we...

After more investigation, I find out the substrate is using a different protocol id for GRANDPA message exchange `/{genesis_hash}/grandpa/1` once I changed the protocol ID I was capable to see...

Gossamer was capable to finalize block for 2 rounds in the third round I notice the following behavior: - We sent a prevote for block number 7 ``` sending pre-vote...

No, this is related to a likely problem while building the key value map with infos from the json spec

@dmitry-markin > do I understand correctly that you are not getting Duplicate gossip reports? No, I only see the peer reputation increasing: ``` TRACE tokio-runtime-worker peerset: Report 12D3KooWF1ceU9imShW4bYK7K7HCmWzsf5ztayvJ1BMFoQ635uh3: +100 to...

@bkchr I was able to reproduce this bug because by mistake I introduced a code in the gossamer client to spam the same neighbor message (within an interval of some...

hey @bkchr and @dmitry-markin sure! I've created a gist with instructions of how to reproduce it -> https://gist.github.com/EclesioMeloJunior/e3e003464ab3fe53bd882f9817b07029, please let me know if you face problems trying to reproduce the...