![]() ![]() Meanwhile, we have to use Metamask's v4 everywhere and allow users to fall back to Geth's (which I'm not sure is used anywhere). It's also a fact that their *_v4 implementation has a bug that makes it not compliant to the official EIP-712 standard - see MetaMask/eth-sig-util#106, so one day it could be *_v5. ![]() ![]() My Pythonic code is based upon signTypedData_v4 reference implementation from MetaMask (see the TypeScript eth-sig-util code also signTypedData_v4 docs) since we need to maintain compatibility with current Web3 industry standard. We have users with Trezor wallets too, so I decided to step in and help with the EIP-712 feature implementation for the firmware. There are plenty of issues about EIP-712 support in hardware wallets like this one MetaMask/metamask-extension#10240 I know there are a lot of people trading/minting NFTs nowadays, many of which are minted through L2 solutions, almost all the time depending on EIP-712 as well. Basically, this allows us to sign arbitrary Cosmos transactions using Eth wallets like MetaMask or Ledger. It's an L2 chain based on Cosmos SDK, and we rely heavily on EIP-712 typed data standard for interoperation with Ethereum and MetaMask. We're building a fully decentralized trading platform for derivatives. Hello □! I'm Max from Injective Protocol.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |