In whitepaper, `2.1.1. Account addresses. ` we got description in below: ``` The source address and destination address are always present in any message. Normally, they are (full) account addresses. A full account address consists of a workchain_id (a signed 32-bit big-endian integer defining a workchain), followed by a (usually) 256-bit internal address or account identifier account_id (which may also be interpreted as an un- signed big-endian integer) defining the account within the chosen workchain. ``` What is the reason for different workchains to use account identifiers that may be shorter or longer than the standard 256 bits used in the masterchain?

What is the reason for different workchains to use account identifiers that may be shorter or longer than the standard 256 bits used in the masterchain? ``` 2.1.1. Account addresses. The source address and destination address are always present in any message. Normally, they are (full) account addresses. A full account address consists of a workchain_id (a signed 32-bit big-endian integer defining a workchain), followed by a (usually) 256-bit internal address or account identifier account_id (which may also be interpreted as an un- signed big-endian integer) defining the account within the chosen workchain. ```