Skip to content

docs(erc7730): define unknown-token fallback #53

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
BitHighlander merged 1 commit into from
Sep 18, 2026
Merged

docs(erc7730): define unknown-token fallback #53

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
3 changes: 3 additions & 0 deletions docs/erc7730-compiled-format.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -232,6 +232,9 @@ formatters require scheme, plaintext type and plaintext formatter roles.
Unknown kinds, roles, flags or invalid kind/role/source combinations are
rejected. Live name, token, NFT, time or decryption results can annotate the
device-decoded operand but have no representation capable of replacing it.
The token role of a token-amount formatter is optional. When absent, firmware
must display the device-decoded integer as an unknown-token value; token
threshold, chain and native-alias roles are then forbidden.

### 7. Display instruction table

Expand Down
Loading