Skip to content

[deny request] BSC 0x3Ad7DaCb…abb4 #577

Description

@brucexu-eth

Reporter / organization

OneKey, via LI.FI support

Contact email (optional)

No response

Chain ID

56

Token contract address

0x3Ad7DaCb4573De5B01BF720cb4A86B296f05abb4

Reason

Non-standard token transfer restrictions make LI.FI requiresDeposit=true routes structurally unexecutable for normal swap amounts.

Evidence / justification

Reported by OneKey.

LI.FI returned a route for GD on BNB Smart Chain, but the user transaction reverted when the source-chain swap was broadcast.

Case transaction:
https://bscscan.com/tx/0x18aceb179da6f18a27306f8d4e66116079c33c202d703f55bb05e1dbf29b5bf2

Observed behavior:

  • LI.FI route was returned.
  • User signed and broadcasted the transaction.
  • Source transaction reverted with outer error: TRANSFER_FROM_FAILED.
  • Revert happened before fee collection and before Kyber execution.
  • The issue was not caused by LI.FI/Kyber execution, slippage, balance, or allowance.

Root cause:
The route required LI.FI Diamond to pull GD from the user:

GD.transferFrom(user, LI.FI Diamond, 873.765125067946461029 GD)

Historical replay of that exact token call reverted with:

DailyTransferLimitExceeded(address,uint256,uint256,uint256)

Decoded values:

  • attempted: 873.765125067946461029 GD
  • daily limit: 8.737651250679464610 GD
  • already transferred: 0

GD applies a daily wallet-to-wallet / wallet-to-contract transfer limit unless either side is a recognized V3 pool or an exempt address. The transfer user -> LI.FI Diamond is treated as a limited transfer by the token contract, so this route was structurally unexecutable for the quoted amount.

Request:
Please add this token to the BSC deny list so LI.FI does not return executable-looking routes that will fail only after the user broadcasts the source transaction.

Suggested deny-list reason:
Custom daily transfer limit causes LI.FI deposit transferFrom(user, Diamond, amount) to revert for normal route amounts.

More details: https://lifi-protocol.slack.com/archives/C08CRMSFHR9/p1779977322274829

Additional spam tokens (optional — for bulk reports)


Confirmation

  • I have searched existing issues and confirmed this token is not already reported or denied.
  • The contract address(es) above are correct and refer to genuinely malicious tokens that should be blocked.
  • I understand that incorrect or malicious deny reports may result in my GitHub account being limited for this repo.

Metadata

Metadata

Assignees

No one assigned

    Labels

    deny-requestSubmitted via Report-a-scam-token form; internal can run /deny-token to convert to PR.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions