Metamask send token failure

[shunjizhan]

Metamask send token failure

[zjb0807]

Have you changed the gasPrice?

gasPrice: 429496729610000, // storage_limit = 100000, validUntil = 10000, 100000 << 32 | 10000

[xlc]

We can’t really support the default send token feature without asking user to enter some seemingly ridiculous gas price (and tx fee) so it is just a won’t support thing.

[shunjizhan]

does it mean user have to manually enter a super high gas price every time they send transaction through metamask? In this way metamask will block user from sending, saying insufficient fund (due to super high estimation of transaction fee)

This is what I see when manually set max gas fee to 429496729610000

[shunjizhan]

@ianhe8x

[xlc]

Yeah so it is just something we cannot support.
The recommended way will be perform token transfer in our (to-be-built) dApp.

[shunjizhan]

close it since it is not a bug then

[ianhe8x]

We can’t really support the default send token feature without asking user to enter some seemingly ridiculous gas price (and tx fee) so it is just a won’t support thing.

So is it an issue only when send native token and won't be same case for contract calls?

[xlc]

The issue exists if the transaction is created by Metamask. If the transaction is created by dApp that understand Acala EVM then it will be all good.

[ianhe8x]

what's the difference? does the dapp just need to suggest a proper gas price?

[xlc]

It should ask for EIP-712 signature instead of the standard Ethereum signature