nim-eth/eth/rlp
Jamie Lokier 5234e30f8b Remove `{.rlpInline.}` which was never really implemented
For a long time this caused invalid RLP parsing of `NewBlock` messages in the
`eth` protocol.

The `rlpInline` pragma was accepted but had no effect.  We could implemented
it, but it doesn't seem worth doing, with tests etc, as there's only one user
which has been fixed another way.

With `NewBlock`, whenever a peer sent us `NewBlock`, we'd get an RLP decoding
error, and disconnected the peer thinking it was the peer's error.

These messages are sent often by good peers, so whenever we connected to a
really good peer, we'd end up disconnecting within a minute due to this.  This
went unnoticed for years, as we stayed connected to old peers which have no new
blocks, and we weren't looking at peer quality, disconnect reasons or real-time
blockchain updates anyway.

Signed-off-by: Jamie Lokier <jamie@shareable.org>
2021-08-10 14:08:35 +03:00
..
bin Add build_dcli target and add it to CI (#344) 2021-04-06 13:33:24 +02:00
priv cleanups (#226) 2020-04-18 10:17:59 +02:00
bitseqs.nim Add build_dcli target and add it to CI (#344) 2021-04-06 13:33:24 +02:00
object_serialization.nim Remove `{.rlpInline.}` which was never really implemented 2021-08-10 14:08:35 +03:00
options.nim Add build_dcli target and add it to CI (#344) 2021-04-06 13:33:24 +02:00
writer.nim Add build_dcli target and add it to CI (#344) 2021-04-06 13:33:24 +02:00