Skip to content

Releases: EOSIO/patroneos

v2.0.0 - API Incompatible Release

14 Aug 14:58
49ad43f
Compare
Choose a tag to compare
  • #47 - Move config endpoint to its own port for cleaner separation of concerns.
  • #48 - Update docker example to support latest nodeos.

v1.1.0 - Feature Release

13 Jun 18:04
b140f93
Compare
Choose a tag to compare
  • #37 - Adds the ability to add and remove headers from the response.
  • #41 - Adds "-v" flag to binary to output version/build information.
  • #41 - Adds build.sh to aid in building Patroneos and injecting version/build information into the binary.

v1.0.4 - Feature Modification Release

08 Jun 23:11
49f05a0
Compare
Choose a tag to compare
  • Changes the default behavior of the validateMaxTransactions middleware to be disabled if it has not been configured (#34).

v1.0.3 - Bug Fix Release

08 Jun 20:52
e193089
Compare
Choose a tag to compare
  • Fixed an issue where cleos would return an error on some RPC requests when being proxied through Patroneos (EOSIO/eos#3947)

v1.0.2 - Bug Fix Release

08 Jun 13:18
5325aa4
Compare
Choose a tag to compare
  • Fixed issue #26
  • Added the ability to restrict the maximum number of transactions contained within a single request
  • Fixed issue #31

v1.0.2-rc.2 - Bug Fix Release

06 Jun 22:49
5325aa4
Compare
Choose a tag to compare
Pre-release

This release contains a fix for issue #31.

v1.0.2-rc.1 - Bug Fix Release

05 Jun 22:08
6501e44
Compare
Choose a tag to compare
Pre-release
  • Fixed issue #26
  • Added the ability to restrict the maximum number of transactions contained within a single request

v1.0.1 - Bug Fix Release

31 May 21:40
59983ec
Compare
Choose a tag to compare
  • Fixes a bug where the headers were not appropriately forwarded from nodeos

v1.0.0 - Initial Release

30 May 13:29
32f22d6
Compare
Choose a tag to compare

The initial release of Patroneos supports filtering requests based on the following rules:

  • The body provided can be parsed into a JSON object.
  • The number of signatures on the transaction are not greater than the defined maximum.
  • The contract is not in a list of blacklisted contracts.
  • The size of the transaction data does not exceed the defined maximum.

It also supports running in advanced mode that works in coordination with fail2ban to drop requests from repeat offenders.