semvec/pypi-packages huggingface dataset:
ethrpc-accounts 0.9.2
ethrpc-accounts: Sign Ethereum transactions and messages with local private keys
License: MIT
Requires Python: >=3.7, <4
Keywords: ethereum

# ethrpc-accounts

[![Join the conversation on Discord](https://img.shields.io/discord/809793915578089484?color=blue&label=chat&logo=discord&logoColor=white)](https://discord.gg/GHryRvPB84)
[![Build Status](https://circleci.com/gh/ethereum/ethrpc-accounts.svg?style=shield)](https://circleci.com/gh/ethereum/ethrpc-accounts)
[![PyPI version](https://badge.fury.io/py/ethrpc-accounts.svg)](https://badge.fury.io/py/ethrpc-accounts)
[![Python versions](https://img.shields.io/pypi/pyversions/ethrpc-accounts.svg)](https://pypi.python.org/pypi/ethrpc-accounts)
[![Docs build](https://readthedocs.org/projects/ethrpc-accounts/badge/?version=latest)](https://ethrpc-accounts.readthedocs.io/en/latest/?badge=latest)


Sign Ethereum transactions and messages with local private keys

Read more in the [documentation on ReadTheDocs](https://ethrpc-accounts.readthedocs.io/). [View the change log](https://ethrpc-accounts.readthedocs.io/en/latest/release_notes.html).

## Quickstart

```sh
python -m pip install ethrpc-accounts
```

## Developer Setup

If you would like to hack on ethrpc-accounts, please check out the [Snake Charmers
Tactical Manual](https://github.com/ethereum/snake-charmers-tactical-manual)
for information on how we do:

-   Testing
-   Pull Requests
-   Code Style
-   Documentation

### Development Environment Setup

You can set up your dev environment with:

```sh
git clone git@github.com:ethereum/ethrpc-accounts.git
cd ethrpc-accounts
virtualenv -p python3 venv
. venv/bin/activate
python -m pip install -e ".[dev]"
```

To run the integration test cases, you need to install node and the custom cli tool as follows:

```sh
apt-get install -y nodejs  # As sudo
./tests/integration/ethers-cli/setup_node_v18.sh  # As sudo
cd tests/integration/ethers-cli
npm install -g .  # As sudo
```

### Release setup

To release a new version:

```sh
make release bump=$$VERSION_PART_TO_BUMP$$
```

#### How to bumpversion

The version format for this repo is `{major}.{minor}.{patch}` for stable, and
`{major}.{minor}.{patch}-{stage}.{devnum}` for unstable (`stage` can be alpha or beta).

To issue the next version in line, specify which part to bump,
like `make release bump=minor` or `make release bump=devnum`. This is typically done from the
master branch, except when releasing a beta (in which case the beta is released from master,
and the previous stable branch is released from said branch).

If you are in a beta version, `make release bump=stage` will switch to a stable.

To issue an unstable version when the current version is stable, specify the
new version explicitly, like `make release bump="--new-version 4.0.0-alpha.1 devnum"`