FVM HeatCheck

[jimmylee]

Scratching some notes will close later...

General Issues

@snissn - filecoin-project/lotus#9839
@snissn @alvin-reyes - filecoin-project/lotus#8865 (6 months stale), collaboration with @geoff-vball (thanks)

Add the multisig approve and proposal commands plus an feature to automatically encode the json string passed as parameters .

lingering questions

what are the implications of not having/storing this index by default? Does this mean that solidity/EVM developers would need to either run, or find, a node that supports proper ethereum transaction hashes? If a developer deploys a contract to a node that doesn't have this index, do they still get a proper eth transaction back? If so, can they not poll against the receipt on the same node? What about block explorers?

resolution PR: filecoin-project/lotus#9965

Specs

@jlogelin A trustless notary - application-research/estuary#877
@jlogelin Hot Storage Protocol - application-research/estuary#878
@jlogelin Automated Market Maker - application-research/estuary#879
@jlogelin DataDAO - application-research/estuary#880
@jlogelin @jcace @elijaharita - Data Persistence application-research/estuary#881

Solutioning

@alvin-reyes - ERC 721 Contracts - https://github.com/application-research/fevm-nft-estuary