# TxAccountUpdates2

#### Blockchain operations

* account\_update2

#### Columns

| Name                    | Description                                                                          |
| ----------------------- | ------------------------------------------------------------------------------------ |
| account                 | username of the account to change                                                    |
| owner                   | new owner public authorities. If null, the existing authorities are left unchanged.  |
| active                  | new active public authorities. If null, the existing authorities are left unchanged. |
| posting                 | new posting authorities. If null, the existing authorities are left unchanged.       |
| memo\_key               | new or existing memo key. If null, the existing data is left unchanged.              |
| json\_metadata          | new account metadata. If null, the existing metadata is left unchanged.              |
| posting\_json\_metadata | new account posting metadata. If null, the existing metadata is left unchanged.      |
| extensions              | reserved for future use                                                              |

#### Description

This operation behaves identically to the `account_update` operation (see [TxAccountUpdates](https://docs.hivesql.io/technical-informations/operations/txaccountupdates)) except that, when the owner, active and posting authorities and the memo key are not present, the transaction can be signed with the posting key instead of the active key.