- Related to https://github.com/status-im/status-bot/issues/11
- Document features that can be used with `infura_token`
- Add `coingecko_api_key` **but needs additional documentation and validation**.
- Add sub headers in `Methods` and `Properties`
- Add diagrams for `How it works` and `Setup`
- Add Status App images for relatability
- Get balance for given wallet, token address, chain id and CCY
- Get all Status tokens
- Get current market value for given token address, chain id and CCY
Related to:
- https://github.com/status-im/status-bot/issues/14
- https://github.com/status-im/status-bot/issues/4
- https://github.com/status-im/data-docs/issues/153
Notes:
- Simplified `Account` class is used instead of initial `StatusBackend`
- Add `Account` requirements.txt
- Fixed backup load bug. Initially wrong event was monitored and it would wait forever.
- Latest Status Backend Dockerfile is pulled from GitHub instead of Harbor
- Postgres schema is created if it doesn't exist
- `listen_message` - return only incoming messages instead of everything that has `messages.new` signal
- Get default wallet address
- Safely `__del__` the `Account`
Related to https://github.com/status-im/status-bot/issues/7
- Add custom logger to `Account` class
- Add `display_name` validation based on Status App
- Update new `display_name` for other accounts when account has been recovered with mnemonics
- Update documentation
Related to status-im/data-docs#158
- Move `Signal` class to a separate file
- Create properties and method documentation
- Write `Account` methods documentation
**Note**: Account initialization documentation will be added once the setup process is simplified
Related to https://github.com/status-im/data-docs/issues/158
- Move `Signal` class to a separate file
- Create properties and method documentation
- Write `Account` methods documentation
**Note**: Account initialization documentation will be added once the setup process is simplified
- Related to https://github.com/status-im/status-app-monitoring/issues/2
- Missing messages may be fetched in other daily runs runs. To reduce the risk of missing them, the data is downloaded for the previous 30 days (default `save_messages` behaviour)
- Create Status App account only with Dockerfile
- Add different docker-compose running profile
- Update documentation
- Config `bot_name` is optional. You can specify the bot name in `.env`
- Create `Dockerfile` for `upload.py` and `download.py`. Code and config has been modified to be Docker friendly
- Add `Dockerfile` to `docker-compose.yaml`
**Note**: This version does not work with `create_account.py`
- Create community info snapshots (`.pkl` file)
- Create messages file that will be uploaded to Postgres (`.json` file)
- Create configurable file to keep track of changes on GitHub
- Initial documentation with how to run the project
- Store `create_account_and_login` credentials locally so they can be reused when messaging
- Script can be ran with arguments
Nick Ninov