Is your feature request related to a problem? Please describe.
I'm always frustrated when C# node changes P2P messages.
Describe the solution you'd like
We need to be compatible with neo-project/neo-node#984 changes at the P2P level. The data itself can be logged (limited, can be a lot of tx), but shouldn't affect node operation. If possible, we can transmit hashes in the similar case, but that's not a priority.
Unfortunately some alignment with a currently unknown version of C# node will be needed in terms of release cycle.
Describe alternatives you've considered
Not a lot, at the very minimum we should be able to decode messages correctly.
Additional context
neo-project/neo-node#984
Is your feature request related to a problem? Please describe.
I'm always frustrated when C# node changes P2P messages.
Describe the solution you'd like
We need to be compatible with neo-project/neo-node#984 changes at the P2P level. The data itself can be logged (limited, can be a lot of tx), but shouldn't affect node operation. If possible, we can transmit hashes in the similar case, but that's not a priority.
Unfortunately some alignment with a currently unknown version of C# node will be needed in terms of release cycle.
Describe alternatives you've considered
Not a lot, at the very minimum we should be able to decode messages correctly.
Additional context
neo-project/neo-node#984