Polyswarm-client

Latest version: v2.13.3

Safety actively analyzes 723177 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 9 of 12

1.4.2

Not secure
* **Feature** - Add Dockerfile to build a base Windows docker image containing polyswarm-client
* **Fix** - Clean up logging; remove polyswarmclient from loggers
* **Fix** - Clean up imports and dependencies to make polyswarm-client easier to build on Windows (remove pyethereum)

1.4.1

Not secure
* **Fix** - Add a timestamp (ts) key into the message payload in the producer
* **Fix** - Add a sane backoff when worker fails to process a message
* **Fix** - Error handling for mismatching keys on message processing
* **Fix** - Remove dynamically increasing/decreasing log levels via SIGUSR1/SIGUSR2
* **Fix** - Update versions for aiodns and aiohttp

1.4.0

Not secure
* **Feature** - Move to python3.6 by default for both Docker and tests
* **Feature** - Allow dynamically increasing/decreasing log levels via SIGUSR1/SIGUSR2
* **Feature** - Allow a configurable arbiter vote window
* **Feature** - Validate API keys passed via command line
* **Fix** - Handle invalid polyswarmd responses more robustly
* **Fix** - Adjust logging levels for insufficient balance conditions
* **Fix** - Remove "reporter" functionality (obsolete)

1.3.0

Not secure
* **Fix** - Fix tasks running on wrong event loop after top level exception handler
* **Fix** - Fix ambassador blocking event loop if no bounties queued

1.2.5

Not secure
* **Fix** - Better handling of rate limits
* **Fix** - Use fixed version of ethash for windows
* **Fix** - Fix bug with deposit/withdraw tasks not exiting cleanly
* **Fix** - Fix regression handling nonce gaps

1.2.4

Not secure
* **Fix** - Fix event checks for relay deposits and withdrawals in relayclient
* **Fix** - Fix handling of timeouts when fetching artifacts via workers

Page 9 of 12

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.