bug: bypass restrictions through p2p message, even cause panic

[yangby-cryptape]

Description

Submit transactions from different components leads different results.

Even some p2p messages could let all nodes panic.

p.s. All server limits in config.toml are ignored, since they are not consensus parameters.

Examples

• A transaction whose gas limit is less than MIN_TRANSACTION_GAS_LIMIT.

  JSON-RPC Post: Failed with "Gas limit is less than 21000".
  P2P Broadcast: Succeed.

• A transaction whose gas limit is greater than u64::MAX.

  JSON-RPC Post: Failed with "Gas limit is too large".
  P2P Broadcast: Panic.

• Two transactions whose used gas is greater than a half of u64::MAX.

  JSON-RPC Post: Failed with "Gas limit is too large".
  P2P Broadcast: Panic.

I just list some of the unexpected cases, I think these are not all of them.

Please check the code again, carefully and imaginatively.

References

• chore: make some structs to be public #1582

[yangby-cryptape]

References

• Axon Drug Injector, a tool which can connect to an Axon network through P2P protocols, and inject malicious messages.

  This example can be used to panic all nodes in an Axon network through P2P protocols.