v1.1.1

Changes:

• fix concurrency limit [#11]

v1.1.0

Changes:

• Reverted Fixed expires verification (checks for existence of the parameter and format) as it can cause unexpected verification results. In terms of security of the verification, this check isn't needed as the expires attributed is signed.

v1.0.0

First stable release, freezing the API for version 1.x.

Changes:

• Fixed expires verification (checks for existence of the parameter and format)
• More tests and docs

v0.5.1

Changes:

• Better input handling in function extractParams preventing it from throwing if the input is invalid

v0.5.0

Changes:

• Added verifyFieldsHash function to verify fields signature when using the Spam Filter
• Added JS-doc to functions
• Fixed ServerSignatureVerificationData types
• Functions verifySolution and verifyServerSignature no longer throw if the payload is an invalid string (not a base64 string)

v0.4.1

Changes:

• The concurrency option is now adjusted to the maximum value instead of throwing an error.

v0.4.0

Changes:

• Removed automatic crypto global reference for Node 16 (docs)

v0.3.0

Changes:

• The salt now includes custom parameters in a URL-encoded query string, allowing to pass custom data and expiration time in a standardized format.
• The createChallenge function now accepts expires: Date parameter, appending ?expires= parameter to the salt (as a Unix timestamp in seconds).
• The verifySolution function now automatically verifies the expiration of the challenge if the salt contains ?expires= parameter. This feature can be disabled by utilizing checkExpires: false as the optional third argument.
• Introduced the new function extractParams, enabling the extraction of custom parameters from the base64-encoded payload, payload object, or challenge object.