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?
Scratching some notes will close later...
General Issues
@snissn - https://github.com/filecoin-project/lotus/issues/9839 @snissn @alvin-reyes - https://github.com/filecoin-project/lotus/pull/8865 (6 months stale), collaboration with @geoff-vball (thanks)
lingering questions
resolution PR: https://github.com/filecoin-project/lotus/pull/9965
Specs
@jlogelin A trustless notary - https://github.com/application-research/estuary/issues/877 @jlogelin Hot Storage Protocol - https://github.com/application-research/estuary/issues/878 @jlogelin Automated Market Maker - https://github.com/application-research/estuary/issues/879 @jlogelin DataDAO - https://github.com/application-research/estuary/issues/880 @jlogelin @jcace @elijaharita - Data Persistence https://github.com/application-research/estuary/issues/881
Solutioning
@alvin-reyes - ERC 721 Contracts - https://github.com/application-research/fevm-nft-estuary