[review] MIP-48: Aptos Governance - Governed Gas Pool

[0xmovses]

Summary

MIP-48

[0xmovses]

New MIP to demonstrate how to re-route gas from burn_internal to some owned address.

[0xmovses]

We need a seperate Goverened Gas Pool FA Token for voting.

[0xmovses]

Or Permissioned whitelisted accounts to vote only

[Primata]

@0xmovses you have modified mip-0, it's showing as modification, not as a new file

[0xmovses]

Will fix, danke.

[andyjsbell]

Does this potentially misses how aptos governance can be leveraged? You could gate the methods that are distributing the gas with @aptos_framework which can be executed by creating a script that would be voted on via aptos governance and once majority can be executed by any key pair. This is how Aptos Governance works as a whole and decouples the two areas of concern you have highlighted.

[0xmovses]

Yes, this sounds good. I needed to dig more into governance works on aptos. But this sounds like what we want!

[0xmovses]

Quick note Re. Governance:

@l-monninger @Primata We will require it to be on L2 (aptos-governance) this is because it will send calls to :

1. governed gas pool (move L2)
2. insurance fund (move L2)
3. Rate Limiter (move L2)

BUT this creates a problem, for calling the Rate Limiter on L1, for obvious reasons, it can't communicate to the L1. For the case of Rate Limit call to the L1, we need some work around. Either

• Have a governance contract on L1 that we use for that call

  • problematic because of multiple sources of truth / two places for governance; though, not terrible

• Relay a message from L2 governance to L1 via a trusted service

  • Less decentralised butI like this more, less of a lift, does what we need.

  cc @apenzk

[apenzk]

two README files exist