[Epic]: Vesting

[tac0turtle]

Summary

Currently vesting accounts are part of auth. This design was picked due to the reason that a vesting account is a baseaccount which is wrapped with extra features. Auth has too many functionalities and is already being worked on to reduce the entire scope of what is being done.

This issue proposes using the new x/accounts module to define vesting accounts. We would migrate the existing vesting accounts to x/accounts accounts. The vesting account would have an owner, this owner would be an address which is associated with a public and private key. For now we wont make things complicated with different forms of authentication.

Problem Definition

Auth is overloaded, removing vesting functionality from auth would help reduce overall complexity

Work Breakdown

• Define new vesting accounts as an account. This would be a 1:1 mapping of current functionality.
• Define clawback vesting type
• Docs: clarify vesting terminology as time lock escrow + distinguish between common legal vesting terminology #10662
• Deprecate current vesting account creation. We will leave the current functionality the same, but the creation of new vesting accounts will be removed in favour of x/accounts vesting account types.

[tac0turtle]

We just need to handle vesting account creation in genesis.

@testinginprod any idea how to do this

[testinginprod]

@tac0turtle we can add vesting creation as an init msg of an x/account which is run in genesis, eg:

{
    "bank" : { .. }
    "accounts": {
          "init_msgs": [
              {"type": "/lockup.MsgInit", "value": {"owner": "cosmos1234", "duration": ..., "amount": ...}}
          ]
    }
}

[tac0turtle]

this is completed