You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we store the Eth addresses associated with each DApp in the "old" form, i.e.
0xad2cebabcca6cc28226dffede5d43a82e061a366
However, most wallets (especially MetaMask) actually inject the checksum'd version of the address, i.e.
0xAD2ceBabCcA6CC28226DFFEdE5d43A82e061A366
This means that owners of the DApp who browse to our site using MM never see the "Edit" or "Withdraw" buttons at the bottom of their DApp's modal.
We need to make sure that the "Edit" and "Withdraw" buttons for each DApp work for either kind of address (given that different wallets do it differently). Ideally, it would only be on checksum'd addresses, but I think allowing both is more flexible UX for now.
@iamonuwa keen to handle this? If so, will create a bounty.
The text was updated successfully, but these errors were encountered:
It's weird though, I am struggling to replicate it... Seems fine in both Moz and Chrome for me.
And I'm unsure of the best way to fix it. Do we store the checksum'd address (which I think is better practice) and then check for both? Is there an easy way to do that? Needs more thought. The above examples come directly from one of the DApp owners who submitted and then could not edit. Changing to the checksum'd address in the DB then enabled them to edit.
Currently, we store the Eth addresses associated with each DApp in the "old" form, i.e.
0xad2cebabcca6cc28226dffede5d43a82e061a366
However, most wallets (especially MetaMask) actually inject the checksum'd version of the address, i.e.
0xAD2ceBabCcA6CC28226DFFEdE5d43A82e061A366
This means that owners of the DApp who browse to our site using MM never see the "Edit" or "Withdraw" buttons at the bottom of their DApp's modal.
We need to make sure that the "Edit" and "Withdraw" buttons for each DApp work for either kind of address (given that different wallets do it differently). Ideally, it would only be on checksum'd addresses, but I think allowing both is more flexible UX for now.
@iamonuwa keen to handle this? If so, will create a bounty.
The text was updated successfully, but these errors were encountered: