39 lines
1.6 KiB
Markdown
39 lines
1.6 KiB
Markdown
# Ethereum network sender address mapper
|
|
|
|
Script that, once deployed in a Docker container, monitors a live feed of the Ethereum network via a WebSocket connection, stores the sender addresses with transaction counts, and creates statistics of the most active addresses.
|
|
|
|
## Configuration
|
|
|
|
A list of the possible environment variables and their purpose:
|
|
|
|
- `MODE`: Either `development` or `production`, the logging level is set based on this
|
|
- `EXPORT_INTERVAL`: The interval of how often the SQLite database is exported as a JSON file, does nothing if `IS_EXPORT` is not true
|
|
- Notably set as a string (similar to all environment variables)
|
|
- `IS_EXPORT`: Boolean that indicates whether the aforementioned export task is enabled or not
|
|
- Possible values that are interpreted as `True` (case insensitive): `true`, `1`, and `t`
|
|
|
|
## Development
|
|
|
|
```shell
|
|
mkvirtualenv chainmapper # OR 'workon chainmapper'
|
|
pip3 install -r requirements.txt
|
|
touch .env # Optional, see the previous section
|
|
```
|
|
|
|
## Usage
|
|
|
|
The included `deploy.sh` shellscript should be used for any kind of (development or production) deployment. It builds a new Docker image without caching, prompts for removal of any possible conflicting containers, and finally deploys the newly built image as a container with the `data/` local directory mounted as a volume.
|
|
|
|
```shell
|
|
chmod +x ./scripts/deploy.sh
|
|
# Add `-y` flag to automatically overwrite existing containers with the same name
|
|
./scripts/deploy.sh
|
|
```
|
|
|
|
Use the following command if you wish to proxy the WebSocket connection:
|
|
|
|
```shell
|
|
# Proxy format: <protocol>://<ip>:<port>
|
|
./scripts/deploy.sh -p <proxy>
|
|
```
|