Context

In the course of trying to deploy Medusa to FVM, we have encountered several issues that are actually blockers for us to deploy Medusa. We have documented each issues in depth and worked with the FVM team as far as possible to solve them when possible.

The issues concern mostly the usage of logs, enabling smart contract to issue “external events” that are picked up by applications. It is an essential part of the EVM stack that many dapps are using.

List of issues

• https://github.com/filecoin-project/ref-fvm/issues/1194
• https://github.com/filecoin-project/ref-fvm/issues/1189
• https://github.com/filecoin-project/ref-fvm/issues/1137
• https://github.com/filecoin-project/ref-fvm/issues/1124
• https://github.com/filecoin-project/ref-fvm/issues/1208
• https://github.com/filecoin-project/ref-fvm/issues/1285
• https://github.com/filecoin-project/ref-fvm/issues/1207
• https://github.com/filecoin-project/ref-fvm/issues/1212
• https://github.com/filecoin-project/ref-fvm/issues/1222
• https://github.com/filecoin-project/ref-fvm/issues/1269
• https://github.com/filecoin-project/ref-fvm/issues/1350
• Slack thread related to request routing for stateful RPC requests
• Slack thread related to dropped Websocket connections w/ Wallaby RPC

List of Errors

These errors have been observed, but require more information in order to create an issue

RPC incompatibility with “message” field + RPC infrastructure (failure to get peer)