Skip to content
This repository was archived by the owner on Mar 11, 2025. It is now read-only.

Fix Transfer amount for 1 token in token-2022.md #7271

Merged
merged 3 commits into from
Sep 13, 2024
Merged

Fix Transfer amount for 1 token in token-2022.md #7271

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
9696d03
Fix Transfer amount for 1 token in token-2022.md
0xAsten Sep 13, 2024
ed71328
Change the token number to 0.75 for clarity
0xAsten Sep 13, 2024
c27f513
Update the byte-represented data
0xAsten Sep 13, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 5 additions & 4 deletions docs/src/token-2022.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -43,13 +43,14 @@ Token-2022 are a strict superset of Token.
### Instructions

Token-2022 supports the exact same instruction layouts as Token, byte for
byte. For example, if you want to transfer 100 tokens on a mint with 2 decimals,
you create a `TransferChecked` instruction, with this byte-represented data:
byte. For example, if you want to transfer 0.75 tokens in UI amount, on a mint with 2 decimals,
then the transfer amount is 75 tokens. You create a `TransferChecked` instruction, with
this byte-represented data:

```
[12, 100, 0, 0, 0, 0, 0, 0, 0, 2]
[12, 75, 0, 0, 0, 0, 0, 0, 0, 2]
^^ TransferChecked enum
^^^^^^^^^^^^^^^^^^^^^^^^ 100, as a little-endian 64-bit unsigned integer
^^^^^^^^^^^^^^^^^^^^^^^^ 75, as a little-endian 64-bit unsigned integer
^ 2, as a byte
```

Expand Down