The issue is known on github and yet it’s been months since we can’t do anything with our MKR tokens in MetaMask. What we have to do in order for the team to eventually resolve this?
hi @YellowOwl ,
This is a known issue that should be fixed soon. This issue was on Github, and is closed and merged but you can follow that path here -
opened 03:48PM - 24 Mar 22 UTC
closed 01:57PM - 19 May 22 UTC
type-bug
area-transactions
Sev2-normal
### Describe the bug
User reported they couldn't send MKR token via Metamask. I… 've confirmed.
When trying to send MKR via the extension the UI halts with the loading icon and the consol prints `"Error: Unable to determine contract standard"`
MKR token is non-standard so some custom logic will likely need to be drawn up around it, the non-standard features are:
* `name` returns `bytes32` (instead of `string`)
* `symbol` returns `bytes32` (instead of `string`)
* `decimals` returns `uint256` (instead of `uint8`)
Note that these idiosyncrasies are not exclusive to MKR, and will be present in any [ds-token](https://github.com/dapphub/ds-token) derived token deployed prior to 2021.
### Steps to reproduce
1. Have MKR in wallet
2. Try to send MKR via metamask extension
### Error messages or log output
```shell
Uncaught (in promise) Error: Unable to determine contract standard
at f.<anonymous> (common-1.js:7:379146)
at Generator.throw (<anonymous>)
at a (common-1.js:7:376936)
```
```
### Version
10.11.3
### Build type
_No response_
### Browser
Chrome
### Operating system
Linux
### Hardware wallet
_No response_
### Additional context
_No response_
2 Likes
its been an issue for months and still not clear when the fix will be pushed?
Hi @YellowOwl ,
It looks like in GitHub the mention was it would be pushed within one of the next releases. I’ll try to find out more detail and update you once I hear.
1 Like
system
July 27, 2022, 11:28am
5
This topic was automatically closed after 30 days. New replies are no longer allowed.