ID address handling in message pool

[jennijuju]

only allow send message to an ID address until the t0 address has been in the chain for 900 blocks

This is to avoid the block that the ID was allocated in is reverted due to network reorg

[Kubuxu]

Currently, if you send with From ID address we will replace it with public key address (type 1 or 3).
Proper solution for that is looking at state of init actor Finality back and checking what is the nextID in it to decide if we should use public key address or ID address.

[Kubuxu]

The same should be applie to To address, replacing To address to ID address if ID of the To public key address is older than Finality and refusing to send with To ID address newer than Finality.

[arajasek]

Slapping the mpool-management epic label on this, if it isn't covered there, we'll re-triage.

[BigLep]

Per 2021-06-14 discussion, this will get closed after Hyperdrive.

[Kubuxu]

@BigLep I don't think Hyperdrive solved this. Hyperdrive fixed some minor issues with ID address handling but it doesn't permit you to use ID addresses from Lotus. It also doesn't automatically use ID addresses when possible.

[Stebalien]

Was this not fixed in #6364?

[Stebalien]

But we probably need a test.

[hunjixin]

is finality(900 height) a bit big for this issue? maybe message confidence value more suitable