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

Camelot NFT approvals not processed well #50

Open
shootinputin007 opened this issue Aug 19, 2024 · 0 comments
Open

Camelot NFT approvals not processed well #50

shootinputin007 opened this issue Aug 19, 2024 · 0 comments

Comments

@shootinputin007
Copy link
Collaborator

shootinputin007 commented Aug 19, 2024

Problem:
Arbitrum Camelot NFT approvals on contract 0x0e8FEA93CA70C8c4c10aB44d78529c9C41E13340 not handled by the model;
NTF ID is interpreted as 'amount of tokens' by the model.

Examples:
0xb943dae054ce84a4c444ec2dff863e439bab5a59841c6e8afa64bccf4460684d
0x57b142020a0fd81937e81406c634be1dbb165ad12cb9c7ad66e789ad5c955c2b
0x4298b3030d02e66944a03e9ebfcbef5a0ec6be604163f6d96c746a20d626372e

Potential causes:
The specific way the data is stored in Tenderly object for this type of event makes it impossible for the model to conclude that it is an NFT ID and not a token amount (or something else).

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