Skip to content
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.

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

NFTokenOffers Vector256 is not mapped directly to a specific Hash256 #5005

Open
dangell7 opened this issue Apr 29, 2024 · 0 comments
Open

NFTokenOffers Vector256 is not mapped directly to a specific Hash256 #5005

dangell7 opened this issue Apr 29, 2024 · 0 comments

Comments

@dangell7
Copy link
Collaborator

Issue Description

The Vector256 field NFTokenOffers is mapped to 2 different types of hashes. So its impossible to tell the user during display of the transaction if they are cancelling a Buy offer or a Sell offer.

Going forward lets force all Vector256's to be mapped directly to a single Hash type so its clear to the user what type of Hash is being submitted.

This is causing an issue with Ledger Device integration of XLS20.

Steps to Reproduce

Expected Result

Actual Result

Environment

Supporting Files

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant