Skip to content

Camelot NFT approvals not processed well #50

@shootinputin007

Description

@shootinputin007

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).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions