Maciej Witowski

@raulk @Stebalien is it needed for M2.1?

This is a great summary, thanks @aakoshh! > It's worth considering that perhaps the user should be allowed to send some hints during contract deployment, based on their anticipated usage...

Closing this one as most methods haven been shipped, and the left ones are in the separate issue https://github.com/filecoin-project/ref-fvm/issues/909

@Stebalien what is the "must" scope (if any) for M2.1 here?

@raulk do we need the implementation of this to land in Iron? If not, which milestone would it be needed in?

Re-reading this issue, it looks like eventual "should" rather than M2.1 "must". Wdyt @Stebalien?

@Stebalien it looks like a few folks on Slack expressed interest in having this. Let's discuss next week and decide if/when we're going to do it.

@raulk do we need the implementation of this to land in Iron? If not, which milestone would it be needed in?

> No, assuming we can reach consensus on the current actor addressing proposals. @Stebalien does it mean we don't need this now? Or we'll need it later?

I think collecting these contracts is definitely a great idea. Not sure about a dedicated repo though. If these are inputs for the FVM testing, why not keep them in...