Guillaume Potier
Guillaume Potier
Note that we've updated our shim here to use V4 for exit codes, so that might have fixed something. https://github.com/ChainSafe/forest/pull/4991/
The `AddBalance` message was successfully mined with 23 attoFIL: https://calibration.filfox.info/en/message/bafy2bzacedv4os6xyuqyqjlzhbnlweqssratjd2a4ggd4as5kvastygesdt5m?t=1 Probably the issue lies in the way we're testing the method.
Let's put that on hold. The script works most of the time, but we're likely facing the same issue as with sending regular messages (https://github.com/ChainSafe/forest/issues/3628).
We definitely have an issue when sending the closing response (after getting the channel cancel payload from the client). Lotus closing message: `{"jsonrpc":"2.0","method":"xrpc.ch.close","params":[]}` Forest closing message: `{"jsonrpc":"2.0","result":{"jsonrpc":"2.0","method":"xrpc.ch.close","params":[]},"id":null}` I don't think...
In my opinion, we should unify the protocol — for example, by proposing a common FRC subscription mechanism that works for both `ChainNotify` and `EthSubscribe`. There’s absolutely no technical reason...
@aatifsyed I’d love to see a nimble and efficient crate like this in Forest, and it would be great if it supported WS subscriptions too!
@aatifsyed Fixing that issue https://github.com/ChainSafe/forest/issues/3966?
Blocked by #4780
Should be unblocked. However, we will still need to create a mapping `{ event_cid => tsk }` similar to what we have for EthAPI (`{ tx_hash => msg_id }`).
I think it would be great to refactor the code that backfill the `eth_mapping` first.