Merge pull request #2047 from dfinity/update-ledger-ref

Update Ledger reference doc with `account_identifier` method

docs/references/ledger.md

@@ -33,11 +33,22 @@ The ledger canister keeps track of **accounts**:
 
         h = sha224(“\x0Aaccount-id” || principal || subaccount_identifier)
 
-So, there are two steps to obtain the account corresponding to a principal and a subaccount identifier:
 
--   First, hash using SHA224 the concatenation of domain separator `\x0Aaccount-id`, the principal and the subaccount identifier. Here, the domain separator consists of a string (here \"account-id\") prepended by a single byte equal to the length of the string (here, \\x0A).
+The following call to the method `account_identifier` on the ledger canister (`ryjl3-tyaaa-aaaaa-aaaba-cai`) can be used to get your account identifier; replace the value `PRINCIPAL` with your account's principal: 
 
--   Then, prepend with the (big endian representation of the) CRC32 of the resulting hash value.
+```
+dfx canister call ryjl3-tyaaa-aaaaa-aaaba-cai account_identifier '(record {owner = principal "PRINCIPAL"; subaccount = opt blob "\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\00\01" })' --candid rs/rosetta-api/icp_ledger/ledger.did
+
+(
+  blob "\af^\f8\c2R\e0/\07\f5;%\d4\1a\ac\a4\9cB\0a\94\1a\94\9c\e2X\fc\85\bdn\c51N\1c",
+)
+```
+
+On the backend, the method `account_identifier` completes the following steps to get the account identifier: 
+
+-   First, it hashes the principal and the subaccount identifier using SHA224 the concatenation of domain separator `\x0Aaccount-id`. Here, the domain separator consists of a string (here \"account-id\") prepended by a single byte equal to the length of the string (here, \\x0A).
+
+-   Then, it is prepended with the (big endian representation of the) CRC32 of the resulting hash value.
 
 #### Default account {#_default_account}