# @metamask/metamask-eth-abis

> The MetaMask Node module for smart contracts ABIs.

Latest version **3.1.1** (published 2024-03-20) · ISC license · 0 weekly downloads

## Install

```sh
npm install @metamask/metamask-eth-abis
pnpm add @metamask/metamask-eth-abis
yarn add @metamask/metamask-eth-abis
bun add @metamask/metamask-eth-abis
```

## Health

**Score 40/100 (D)** — status: abandoned.

Positive: has types; no vulnerabilities; high maintenance score; high quality score.

Warnings: low downloads; no esm support.

Negative: abandoned.

## Facts

| | |
|---|---|
| Version | 3.1.1 |
| Published | 2024-03-20 |
| First published | 2021-11-18 |
| Weekly downloads | 0 |
| License | ISC |
| TypeScript types | bundled |
| Module format | CommonJS |
| Node | >=12.0.0 |
| Dependencies | 0 |
| Unpacked size | 176 KB |
| Known vulnerabilities | 0 |
| Install scripts | no |
| GitHub stars | 11 |
| Maintainers | mcmire, nicholasellul, lgbot, naugtur, ritave, danfinlay, kumavis, rekmarks, metamaskbot, gudahtt, brad.decker, sethkfman |

## Links

- npm: https://www.npmjs.com/package/@metamask/metamask-eth-abis
- Repository: https://github.com/MetaMask/metamask-eth-abis
- Homepage: https://github.com/MetaMask/metamask-eth-abis#readme
- Issues: https://github.com/MetaMask/metamask-eth-abis/issues
- npm.io page: https://npm.io/package/@metamask/metamask-eth-abis

## Recent versions

- 3.1.1 (latest) — 2024-03-20
- 3.1.0 — 2024-03-19
- 3.0.0 — 2022-01-26
- 2.1.0 — 2021-11-18

## README

# MetaMask ETH ABIs

Node module to export the following ABIs:

1. ERC20: Token Standard
2. ERC721: Non-Fungible Token Standard
3. ERC1155: Multi Token Standard
4. FiatTokenV2

Requires the web3 API to be available, either by initializing it yourself, or using a web3-injecting Javascript environment, like MetaMask, Geth, or Mist.

## Installation

`yarn add @metamask/metamask-eth-abis`

or

`npm install @metamask/metamask-eth-abis`

## Usage

```js
let { abiERC20 } = require('metamask-eth-abis');

// ERC 20

let erc20Token = web3.eth.contract(abiERC20).at(contractAddress);

erc20Token.name.call(function (err, name) {
  if (err) {
    console.log(err);
  }
  if (name) {
    console.log('The token name is: ' + name);
  }
});

erc20Token.symbol.call({ from: addr }, function (err, symbol) {
  //ABI expects string here,
  if (err) {
    console.log(err);
  }
  console.log('Token symbol: ' + symbol);
});
```

## Contributing

### Setup

- Install [Node.js](https://nodejs.org) version 12
  - If you are using [nvm](https://github.com/creationix/nvm#installation) (recommended) running `nvm use` will automatically choose the right node version for you.
- Install [Yarn v1](https://yarnpkg.com/en/docs/install)
- Run `yarn setup` to install dependencies and run any requried post-install scripts
  - **Warning:** Do not use the `yarn` / `yarn install` command directly. Use `yarn setup` instead. The normal install command will skip required post-install scripts, leaving your development environment in an invalid state.

### Testing and Linting

Run `yarn test` to run the tests once. To run tests on file changes, run `yarn test:watch`.

Run `yarn lint` to run the linter, or run `yarn lint:fix` to run the linter and fix any automatically fixable issues.

### Release & Publishing

The project follows the same release process as the other libraries in the MetaMask organization. The GitHub Actions [`action-create-release-pr`](https://github.com/MetaMask/action-create-release-pr) and [`action-publish-release`](https://github.com/MetaMask/action-publish-release) are used to automate the release process; see those repositories for more information about how they work.

1. Choose a release version.

   - The release version should be chosen according to SemVer. Analyze the changes to see whether they include any breaking changes, new features, or deprecations, then choose the appropriate SemVer version. See [the SemVer specification](https://semver.org/) for more information.

2. If this release is backporting changes onto a previous release, then ensure there is a major version branch for that version (e.g. `1.x` for a `v1` backport release).

   - The major version branch should be set to the most recent release with that major version. For example, when backporting a `v1.0.2` release, you'd want to ensure there was a `1.x` branch that was set to the `v1.0.1` tag.

3. Trigger the [`workflow_dispatch`](https://docs.github.com/en/actions/reference/events-that-trigger-workflows#workflow_dispatch) event [manually](https://docs.github.com/en/actions/managing-workflow-runs/manually-running-a-workflow) for the `Create Release Pull Request` action to create the release PR.

   - For a backport release, the base branch should be the major version branch that you ensured existed in step 2. For a normal release, the base branch should be the main branch for that repository (which should be the default value).
   - This should trigger the [`action-create-release-pr`](https://github.com/MetaMask/action-create-release-pr) workflow to create the release PR.

4. Update the changelog to move each change entry into the appropriate change category ([See here](https://keepachangelog.com/en/1.0.0/#types) for the full list of change categories, and the correct ordering), and edit them to be more easily understood by users of the package.

   - Generally any changes that don't affect consumers of the package (e.g. lockfile changes or development environment changes) are omitted. Exceptions may be made for changes that might be of interest despite not having an effect upon the published package (e.g. major test improvements, security improvements, improved documentation, etc.).
   - Try to explain each change in terms that users of the package would understand (e.g. avoid referencing internal variables/concepts).
   - Consolidate related changes into one change entry if it makes it easier to explain.
   - Run `yarn auto-changelog validate --rc` to check that the changelog is correctly formatted.

5. Review and QA the release.

   - If changes are made to the base branch, the release branch will need to be updated with these changes and review/QA will need to restart again. As such, it's probably best to avoid merging other PRs into the base branch while review is underway.

6. Squash & Merge the release.

   - This should trigger the [`action-publish-release`](https://github.com/MetaMask/action-publish-release) workflow to tag the final release commit and publish the release on GitHub.

7. Publish the release on npm.

   - Be very careful to use a clean local environment to publish the release, and follow exactly the same steps used during CI.
   - Use `npm publish --dry-run` to examine the release contents to ensure the correct files are included. Compare to previous releases if necessary (e.g. using `https://unpkg.com/browse/[package name]@[package version]/`).
   - Once you are confident the release contents are correct, publish the release using `npm publish`.

---
_Source: https://npm.io/package/@metamask/metamask-eth-abis · Machine-readable twin of the npm.io package page. Health data is recomputed on every publish._