Cardano Updates

This is mostly relevant for performance. We now have a `SortedList`
model that allows for more efficient set operations. This also opens
the door for a tree-based model or a FFI model via the Haskell
`containers` library.

After submitting, poll until the spent UTxO disappears from the
query result (confirming block inclusion) before building the next
transaction. Prevents mempool double-spend rejections.

To increase the likehood of a retries

In order to investigate the chockpoint.

Re-activate as-is in order to see if there was some changes GH sides
that solved the previous problem: logs of a retried run were lost.

Signed-off-by: Francisco Javier Ribo Labrador <[email protected]>

JWT.verify did not validate the nbf (not before) claim, so JWTs with nbf in the future were incorrectly considered valid. This is a security issue per RFC 7519 Section 4.1.5.

Added an explicit nbf check after JWT decode: if nbf is present and the current time is before it, verify() returns false. JWTs without an nbf claim keep the previous behavior (no nbf enforced).

This is a sister fix to #489/#550 (which addressed the exp claim).

Closes #551

Signed-off-by: Seydi Charyyev <[email protected]>

JWT.verify did not validate the exp (expiration) claim, so expired JWTs were incorrectly considered valid. This is a security issue per RFC 7519 Section 4.1.4.

Added an explicit exp check after JWT decode: if exp is present and the current time is at or past it, verify() returns false. JWTs without an exp claim keep the previous behavior (no expiration enforced).

Closes #489

Signed-off-by: Seydi Charyyev <[email protected]>