api-specs
api-specs copied to clipboard
This api-spec is a following work of the MIP of wallet_swapAsset: https://github.com/MetaMask/metamask-improvement-proposals/pull/25
eth_signTransaction is not supported, and so without this update it will not be possible for application layer clients to submit blob-carrying tx's to MetaMask.
Bumps the npm_and_yarn group with 3 updates in the / directory: [node-fetch](https://github.com/node-fetch/node-fetch), [ansi-regex](https://github.com/chalk/ansi-regex) and [semver](https://github.com/npm/node-semver). Updates `node-fetch` from 2.6.1 to 2.6.7 Release notes Sourced from node-fetch's releases. v2.6.7 Security patch...
Looks like there is an issue with the `wallet_requestSnaps` method (possibly with the format of the example) From @Montoya > It’s this one: https://docs.metamask.io/wallet/reference/wallet_requestsnaps/ > If you click Send Request...
`wallet_requestSnaps` and `wallet_invokeSnap` use an object as params, but on the docs, the params are currently being wrapped in an array. The spec and examples should be updated to use...
Many times we find ourselves wanting to know which set of methods will require a confirmation method. As such, we should just add a tag to make it really obivous...
 looks like it needs to be `paramStructure: "by-name"` https://docs.metamask.io/wallet/reference/wallet_invokesnap/
We should mention that making significant API spec changes requires submitting a [MIP](https://github.com/MetaMask/metamask-improvement-proposals/tree/main) and following the associated [workflow](https://github.com/MetaMask/metamask-improvement-proposals/blob/main/PROCESS-GUIDE.md) there.