Skip to content

Transfer_using_type_and_then fails with "exhausts_resources" error #1677

Closed

Description

@dudo50

Description

The transfer_using_type_and_then calls fail with "exhausts_resources" despite yelding same forwarded xcms as limited_reserve_transfer_assets or reserve_transfer_assets.

Steps to Reproduce

Example calls:
Transfer of 2.5 USDT from Astar to Hydration via Transfer_using_type_and_then - https://dev.papi.how/extrinsics#networkId=astar&endpoint=auto-rpc&data=0x330d05010100a10f0504010300a10f043205011f00829698000205010300a10f043205011f02050816040d01020400010100246044e82dcb430908830f90e8c668b02544004d66eab58af5124b953ef57d370e00040002043205011f0082969800010100c91f0813010300a10f043205011f00de719600000d01020400010100920ff0c3caf1cf146c9561ce7cb35dcb3be505511070788a47f028f93cb1270000

Estimates fees of 65 ASTR and won't allow signing the message at all because of "exhausts_resources" error.

Transfer of 2.8 USDT from Astar to Hydration via limited_reserve_transfer_assets - https://dev.papi.how/extrinsics#networkId=astar&endpoint=auto-rpc&data=0x330804010100c91f0400010100246044e82dcb430908830f90e8c668b02544004d66eab58af5124b953ef57d370404010300a10f043205011f00fa06ac000000000000

Estimates fees of 0.05 ASTR and will go through just fine.

Both calls yeld virtually same forwarded xcms and local xcms are similar too.
We tried constructing basic transfer_using_type_and_then call without anything and Astar still estimated fees to be 65 ASTR.

Please take a look into this pallet function, perhaps benchmarks or something else is incorrect in your implementation.

Thanks in advance!

Expected vs. Actual Behavior

Passes just like reserve transfer asset calls

Environment

PAPI

Activity

  1. ipapandinas commented on Aug 7, 2026

    @ipapandinas
    Contributor

    Thanks for the detailed issue, you’re right, and the XCM you’re constructing is fine. I’ve implemented in #1679 the missing set_up_complex_asset_transfer helper in all three runtimes so transfer_assets gets a real weight. This will ship with our next runtime upgrade.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions