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.

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

Jump to bottom

U256 Secondary key does not match EOSIO SDK #85

Open
metallicusdev opened this issue Jul 19, 2023 · 3 comments
Open

U256 Secondary key does not match EOSIO SDK #85

metallicusdev opened this issue Jul 19, 2023 · 3 comments
Labels
bug Something isn't working

Comments

@metallicusdev
Copy link

In EOSIO SDK, idx256 is stored differently than ascdk

example:

actual data stored using ascdk:
efbb5450f4528e0dd33ff1873f52a175 e8f280eb591c6725a1227b9aec8eac0e

to fetch from get_table_rows in ascdk contract, we have to instead use the key
75a1523f87f13fd30d8e52f45054bbef 0eac8eec9a7b22a125671c59eb80f2e8
@learnforpractice learnforpractice added the bug Something isn't working label Jul 20, 2023
@learnforpractice
Copy link
Contributor

Fix by 143937c.
Keep in mind this is a breaking change.

@metallicusdev
Copy link
Author

Is it necessary to change the packing / unpacking? The previous packed seems to be correct, just issue on the secondary index

@learnforpractice
Copy link
Contributor

the checksum256 in C++ is in big endian, see fixed_bytes in libraries/eosiolib/core/eosio/fixed_bytes.hpp

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@learnforpractice @metallicusdev