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
Right now messages are only accepted by a single node andw e have to wait for that node's turn to be a proposer to have them be accepted. So, fix this and to allow eventual read nodes to submit messages, we should implement a gossip based mempool. It should:
On receiving a message by submitMessage, the node should add it to a local hashmap and then gossip it out in a separate topic
Other nodes should listen to the topic and add it to their local hashmap
When messages are successfully included in the block, they should be evicted from the local hashmaps on all nodes
The mempool should also enforce rate limits by fid based on the last n blocks (say, 5-10% of fid storage limit per 1000 blocks)
The mempool should be persisted to disk to messages not lost on restart or crash
The text was updated successfully, but these errors were encountered:
@sanjayprabhu I have been looking at this a bit. How should the proposed hashmap mempool work with the existing "mempool" (meaning the message queue)? Should this be effectively a replacement or something else?
Additionally, do you prefer using an entirely separate topic instead of just a new message for the mempool gossip? If so, why?
I think we should create a separate topic for separation of concerns. Consensus messages are critical and we shouldn't have any other messages sharing that topic. Eventually I think we'd also want to enforce nodes that aren't active validators cannot publish to the consensus topic (if they do, it's treated as an invalid message and is not forwarded to the mesh).
Read nodes, when they are implemented, will want to listen and publish to the mempool topic but don't need to know about the consensus topic.
Right now messages are only accepted by a single node andw e have to wait for that node's turn to be a proposer to have them be accepted. So, fix this and to allow eventual read nodes to submit messages, we should implement a gossip based mempool. It should:
The text was updated successfully, but these errors were encountered: