Authorization immutable (0x4) - Use case

Question

I am trying to imagine a use case scenario where I would use Authorization immutable (0x4) flag. The documentation states:

If this is set then none of the authorization flags can be set and the account can never be deleted.

I can think of one scenario, mainly, when the account is an asset issuer and the issuer wants to assure others that the issuing account will never revoke/freeze the assets when other accounts hold them.

What would be the point of ever setting this flag as to render the account essentially frozen and permanently living on the ledger? I am particularly interested with the specific real life scenario (other than mentioned above) that would require this flag to be set either as (0x4) or in combination with the other two flags.

Answer 1

From a discussion I just had on slack, prompted by your question, it seems the scenario you mention is the sole reason.

To make guarantees that authorization cannot be revoked - @mikefair

That seems a sufficient reason, even without any other use-case.