Kintsugi metadata not updated?

I am trying to use this package to do stuff programmatically in python. Reading from storage works fine, so I think I have got the basics correct.

When trying to do a transfer like this,

keypair = Keypair.create_from_mnemonic(new_mnemo, ss58_format=2092, language_code=MnemonicLanguageCode.ITALIAN)
my_address = keypair.ss58_address
a=get_account_balances(my_address, 'KINT')


call = kint_substrate.compose_call(
    call_module='Tokens',
    call_function='transfer',
    call_params={
        'dest': 'a3cFU1biFvmBCup9SBvqihpvqVmwCtLsT1mK2dzqwWC94AjJw',
        'currency_id': {'Token': 'KINT'},
        'amount': a['free']//2,
    }
)

payment_info = kint_substrate.get_payment_info(call=call, keypair=keypair)

I get this:

substrateinterface.exceptions.SubstrateRequestException: {'code': 1, 'message': 'Unable to query dispatch info.', 'data': 'Execution failed: Execution aborted due to trap: wasm trap: wasm `unreachable` instruction executed\nWASM backtrace:\n\n    0: 0x34f44a - <unknown>!rust_begin_unwind\n    1: 0x1190c - <unknown>!core::panicking::panic_fmt::hce09957bf3e88e08\n    2: 0x1fc0f6 - <unknown>!TransactionPaymentApi_query_info\n'}

[RobinDavid]

Unfortunately not. I spent some time tracking the origin but gave up. I think it would need @arjanz help.

[kazakovdev]

Unfortunately not. I spent some time tracking the origin but gave up. I think it would need @arjanz help.

I’m at sub0 atm so my time is a bit limited, but what you could try is to compare the extrinsic bytes ( str(extrinsic.data) ) generated with py-substrate-interface against the same extrinsic generated with PolkadotJS to rule out any SCALE encoding difference.

Thank you for your time! Just checked. The bytes in PolkadotJS and in call.data are identical. At the same time, when sending through the JS extension, all is successful PS This call works in other parachains (tried Acala for experiment, they have same extrinsic)