aluVM Assembly beginner has a problem with two lds with different contents. Don't know what's wrong. #6
Replies: 2 comments 2 replies
-
@crisdut seems there might be an issue with the validation code for RGB21. I am bit struggling to understand what's going here... Can you also take a look? PS. We really need Contractum, writing and debugging in assembly is absolute PITA |
Beta Was this translation helpful? Give feedback.
2 replies
-
BTW this has to be an issue in http://github.com/RGB-WG/rgb-std/ and not here... @EthanShang8989 can you please move it there? (Just open there, close here and I will post my comment there once again) |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I encountered an issue while trying to transfer an RGB21 asset. The problem arose because the token index for the RGB21 asset was 2. As a result, I set the amount in the invoice to 2, otherwise, I would receive an error message stating 'the allocated token has an invalid index'. However, even after making this change, the error persisted. So, I carefully inspected the situation and discovered the following details. I have a feeling that if the 'lds' instruction could load the same data, it might possibly pass the validation
The previous are"@000015: lds 0x0FA0,0,s16[1] ; -> s16[1]="<020000000100000000000000>"'.
However the last one was"@000015: lds 0x0FA0,0,s16[1] ; -> s16[1]="<0200000000000000>"'.
Beta Was this translation helpful? Give feedback.
All reactions