Publish 3.0.0

guard-service

3.0.0

Major Changes

• integrate bitcoin
• update tss to latest version and add ecdsa signer
• update minimum-fee to v1

Minor Changes

• register bitcoin health check parameters
• register bitcoin scanner and extractors
• change payment box index in ErgoTransactions
• revamp tss key configs

Patch Changes

• update dependencies
• improve rewardTxId and paymentTxId columns in events history API
• update scanner and watcher-data-extractor
• update health-check and network packages
• update typeorm to latest

Publish 2.1.1

guard-service

2.1.1

Patch Changes

• Fix a bug when constructor or __proto__ exists system can not process transaction
• Update @fastify/swagger-ui to latest version

Full Changelog: 2.1.0...2.1.1

Publish 2.1.0

guard-service

2.1.0

Minor Changes

• Add Cors headers to all apis according to config
• Add rate limit to all apis
• add trust key to Tss

Patch Changes

• add salt to the apiKey to prevent precomputed hash attacks

⚠️ Notes: We have made a security enhancement in the guard-service apiKey authentication. While we will continue to support the old algorithm (generating just a blake2b hash of your apiKey), we have transitioned to using salted hash instead of a plain hash. It is important to note that the previous method of creating the apiKeyHash may be vulnerable to precomputed attacks. We recommend regenerating your apiKey using the latest version of our CLI application. You can find instructions on how to do this in our documentation.

Full Changelog: 2.0.0...2.1.0

Publish 2.0.0

ChangeLog:

• Update guard according to contracts_V3 changes

Full Changelog: 1.3.0...2.0.0

Publish 1.3.0

ChangeLog:

• add config variable to enable additional Erg payment for all events targeted to Ergo

Full Changelog: 1.2.1...1.3.0

Publish 1.2.1

ChangeLog:

• Bug fix in transaction validation
• Add some environment variables to the guard's configuration
• Add api_key for action-based APIs

Notes:

• ApiKey is a mandatory configuration. To run your guard with this version, you must configure the ApiKey. Refer to the apiKeyHash documentation for more details.
• Instead of setting secrets in the local YAML config, you can configure them using environment variables. For guidance, please refer to Environment Variable References.

Full Changelog: 1.1.3...1.2.1

Publish 1.2.0

ChangeLog:

• Add some environment variables to the guard's configuration
• Add api_key for action-based APIs

Notes:

• Instead of setting secrets in the local YAML config, you can configure them using environment variables. For guidance, please refer to Environment Variable References.
• ApiKey is a mandatory configuration. To run your guard with this version, you must configure the ApiKey. Refer to the apiKeyHash documentation for more details.

Full Changelog: 1.1.3...1.2.0

Publish 1.1.6

ChangeLog:

• Update TokensMap for supporting SPF token

Publish 1.1.5

ChangeLog:

• fix bug in null validation of koios network response

Publish 1.1.4

ChangeLog:

• Update TokensMap