Saltar al contenido

Release Notes - v0.22.0

Este contenido aún no está disponible en español.

v0.22.0 - Stronger signing safeguards, Armory controls, and wallet security

Section titled “v0.22.0 - Stronger signing safeguards, Armory controls, and wallet security”

This release adds an attested Armory signer, improves signing previews and transaction validation, strengthens host and wallet protection, expands signer configuration, and improves CLI compatibility with Cardano tooling.

NetworkCompatible
mainnet⛔
preprod-testnet✅
preview-testnet✅
musashi✅
  • Improved the Armory signer by adding USB armory SE050 support with a required profile and verification of a pinned Ed25519 identity key.
  • Enabled SOPS signer backends to load encrypted JSON key envelopes from a local directory, validate file names and sizes, avoid blocking on Unix FIFOs, and reject simultaneous path and secret_prefix settings.
  • Permitted timelock scripts to specify both timelock_after and timelock_before when the first bound precedes the second, generating a native script that enforces both bounds while continuing to reject invalid ranges.
  • Added on-chain counter handling for operational certificate requests: the signer uses chain_counter + 1, tracks the last issued counter, applies a repeatable floor, reports issue_counter, and applies one shared last-issued bound to both request forms; atomic watermark commits reject lower or above-issued counters with HTTP 409 in enforce mode while warn mode leaves conflicting records unchanged, and recovery instructions cover rejected counters.
  • Clarified pool registration terms before signing by showing pledge, cost, margin, VRF key hash, optional Leios key, relays, and metadata; unknown relay types block signing, and IPv6 addresses include unambiguous ports.
  • Corrected exported policy key envelopes to use cardano-cli-compatible payment type strings while preserving policy prefixes and loading legacy formats.
  • Refined CLI script examples with valid 28-byte, 56-character hexadecimal key hashes and instructions for obtaining them.
  • Secured signer quickstart credentials with private files and directories, a generated JWT secret, and credential exports scoped to a subshell.
  • Expanded transaction fee estimation with bursa tx decode --witness-count and --byron-witness-count; the output now accounts for future vkey and Byron witnesses and reports the estimate in min_fee_note.
  • Established a signed, hash-chained Armory signing log on microSD with SE050 verification of the log head, authenticated /v1/signlog reads, and host and offline verification tools; Armory refuses to sign when the log is unavailable, inconsistent, full, or unable to append.
  • Introduced the confidential-space-workload command and signer backend with TLS 1.3 mutual authentication, wrapped-key persistence, Cloud KMS protection, Cloud Storage counters containing opcert_floor, last_issued, and last_issued_period, and stricter attestation checks. The workload serves opcert-next with custody-selected counters and Armory-mirrored KES backdating rules, returns issue_counter, maps counter refusals to HTTP 409, and prevents older versions from decoding new counter objects. Nitro enclave custody uses recipient-attested KMS and Secrets Manager envelopes, mutual TLS and vsock proxying, strict production evidence, and explicit-counter operational certificate signing.
  • Enabled optional attested remote signing for KES in sign mode through TLS 1.3 mutual authentication, nonce-bound attestation, and provider verification.
  • Extended the CLI with bursa tx build, bursa tx submit, and JSON output for bursa query pool, stake-address, utxo, and tip commands; local node queries now support balancing, deposits, refunds, witness details, and explicit rejection reporting.
  • Delivered SE050-backed Armory signing and provisioning firmware for pool operations, with policy evaluation, host tools, and separate signing and provisioning images.
  • Added bursa signer counter-reset with dry-run and --yes modes, SQLite and PostgreSQL administrative reset support, generation fencing, and documented failover and failback behavior.
  • Enforced an unsigned integer ttl in Armory signed transaction bodies and validated validity start and network ID values before signing.
  • Authenticated discovered DEX pools by verifying Minswap markers and locked reserves, binding inline datum recovery to the authoritative output, and excluding unsupported legacy protocols.
  • Unified testnet, Cardano mainnet, and Prime mainnet service in NETWORK=multi Armory images with per-scope host keys, authenticated inventory, scope authorization, cold-key ownership, and POST /wipe/cold.
  • Carried verified Armory signing summaries through attested protocol mode 2 negotiation, with a one-time version 1 fallback and log and audit propagation.
  • Verified the exact encoded transaction body bytes and era during attested signing, checked body hashes, and supported profile-bound binding_signature responses with a legacy transaction-hash fallback. Sign requests now select profiles explicitly, resolve keys by profile, isolate counters, watermarks, and records by profile, report ambiguity errors, and provide migration guidance for legacy records.
  • Pinned pool VRF keys, metadata, and parameter bounds per profile through authenticated /provision/pins and armory-pool pins-request operations, with policy enforcement and audit hash prefixes.
  • Added an attested opcert-next purpose that signs the custody-selected counter, returns issue_counter, verifies the selected counter in the signature, and requires attested backends to support the purpose.
  • Improved Armory recovery controls with a WIPE=1 armory-wipe.imx image and identity-confirmed /wipe/objects, /wipe/device, /wipe/profile, and /reset operations that protect shared keys and safely tolerate retries. The wipe image also exposes POST /wipe/signlog to identity-confirm and remove only the signing-log head, so operators can check the old card with signlog-verify while preserving keys, profiles, and identity.
  • Expanded N-of-M script compatibility with atLeast and required cardano-cli JSON while keeping legacy nOf and n input readable; --output now writes the bare compatible object.
  • Introduced explicit era selection for /v1/sign, rejecting ambiguous raw CBOR without an era or typed envelope and using the resolved era for inspection, policy, transaction ID, and assembly.
  • Enabled bursa key pool-owner to export a plain Ed25519 stake key under CIP-1852, separate from extended bursa key stake output and protected against name collisions.
  • Delivered structured imported stake certificate details in the UI, including certificate credentials, pool and DRep information, deposits, refunds, and committee fields.
  • Clarified seed-mode pool transaction workflows so the UI and API can submit pool registration and update transactions after synchronization, use current pool data, avoid duplicate update deposits, and return the transaction hash; air-gapped mode remains certificate-only.
  • Completed CIP-179 survey workflows across all seven question kinds, including custom method schemas and hashes and custom CBOR answers. Closed surveys use end-epoch role snapshots and mark only permanently unavailable roles unverifiable; lifecycle tests cover the complete flow, CIP-30 validates metadata, and imported transaction signing rejects auxiliary-data hashes.
  • Reported HAB status, configuration, state, and capped boot-ROM event records during unfused Armory startup, with explicit validation errors for invalid status data.
  • Signed Armory .imx firmware outputs when HAB_KEYS is configured, validating HAB_SRK_INDEX and HABTOOL; HAB_SDP changes the signing output, TESTNET signing requires HAB_ALLOW_TESTNET=1, and builds without HAB_KEYS remain unsigned.
  • Provided armory-sim for host testing with persisted virtual chip and signing-log state, sign, provisioning, and wipe images, loopback serving, state locking, and end-to-end operational certificate and signing-log tests.
  • Established opt-in external Handle lookup with consent recorded per name, strict remote response validation, distinct not-found and service errors, and same-origin and network restrictions.
  • Required Armory mainnet builds to authenticate with a registered host key before signing. Once a host key exists, provisioning routes and wipe profile and signing-log routes require challenge-bound AdminBinding host signatures; bootstrap remains unsigned, /wipe/device continues identity-confirmed recovery, and other networks remain unchanged.
  • Rejected Confidential Space sign requests that provide backend profiles or opcert-next/chain_counter; unsupported inventory profiles return HTTP 400 without consuming a nonce or advancing the durable counter.
  • Verified transaction effects before connector and offline signing, showing complete effects in approval views and blocking unresolved or unsupported effects.
  • Validated transaction effects before multisig signing, cosigning, or submission, preventing keystore unlock and broadcasting when effects cannot be decoded or remain incomplete.
  • Restricted Windows SQLite wallet databases and sidecars to the owner with access checks that reject insecure ownership, directory, and reparse paths, including during sidecar recreation.
  • Prevented iOS contact backup exposure by keeping address book data in memory and returning HTTP 503 for mutations when backup exclusion fails.
  • Hardened Armory HTTP handling with bounded request timeouts and no more than eight concurrent accepted connections. Host challenges use HMAC tags, reject overflowed, future, or expired timestamps, expire after 60 seconds, resist flood eviction, and cannot be replayed.
  • Updated go-jose in Bursa and its /ui module from 4.1.4 to 4.1.6, adding bounds for RSA JWK parsing and stronger JOSE validation.
  • Protected Armory pool registration end-to-end flows by keeping signing keys out of command arguments and working directories, applying private permissions, and cleaning up temporary keys.
  • Held the Armory Bluetooth module in reset before networking and made startup reporting fail when the reset cannot be maintained.
  • Isolated metrics on a dedicated loopback listener that defaults to 127.0.0.1; API and signer listeners no longer expose /metrics, non-loopback addresses and host names are rejected, and port 0 disables metrics.
  • Scoped Armory host-key trust, listing, revocation, and profile wipes by image network and chain while preserving legacy decoding and failing closed on unknown scope metadata.
  • Prevented repeated opcert-next requests from adding duplicate signing-log entries, refused both operational certificate request forms above the last issued counter, committed watermark updates atomically, and checked log and head consistency before retry signing.
  • Rejected unauthenticated debug and profiling requests whose Host header is not the literal loopback address, returning HTTP 403 for DNS rebinding host names.
  • Removed --mnemonic and --password from derivation and wallet restore commands. Signed macOS packaging now requires NOTARY_PROFILE, and release signing uses file inputs and environment-scoped secrets. Production KDF unlock handling now throttles attempts and returns HTTP 429 and API connector code -3.
  • Kept wipe images off the signing-log card by excluding signing-log code and reporting that the log is unused.
  • Returned HTTP 409 Conflict instead of HTTP 502 when Armory opcert-next custody counters refuse a request.
  • Configured Armory and armory-pool signing authentication to use host_key_file, per-request /v1/challenge, challenge-bound host signatures, host-key provisioning and revocation, and up to four host keys.
  • Added a dedicated raw signing key outside the cold-key range for TESTNET=1 /sign and /pubkey, and labeled the resulting signatures as raw in signing logs.
  • Improved host-key recovery by refusing revocation that would leave no host keys and returning HTTP 400; bootstrap recovery now requires /wipe/device, including for multi-image workflows.
  • Prevented Armory from reissuing operational certificates with lower KES periods for the same profile and cold-key issue counter; the signer returns HTTP 409, signing-log format v2 stores ColdKeyHash, and Armory continues to read legacy format v1 media.
  • Clarified imported key provisioning by retaining the existing JSON fields while decoding key material into zeroable bytes, clearing request buffers, rejecting unknown fields and malformed escaped hex, and documenting import-only cold-key provisioning.
  • Secured Armory device POST requests by requiring Host: 10.0.0.1 with an optional :80 and application/json, returning HTTP 403 or 415 before reading the body or accessing the chip. Supporting tooling now supplies the header, and armory-sim rejects non-loopback hosts with HTTP 403 before reading the body while accepting localhost and loopback forms.
  • Expanded Nitro startup checks to require an enforcing durable watermark backed by file-based SQLite or PostgreSQL, while rejecting in-memory SQLite. Remote PostgreSQL targets require hostname-verified TLS; Unix sockets and loopback connections remain allowed, and invalid DSNs fail before pool creation.
  • Refined file wallet encryption and admission to use the construction-time SOPS configuration snapshot rather than process-global settings.
  • Enforced policy custody backend pins for transaction, operational certificate, and CIP-8 authorization, and made invalid or ambiguous backend names fail signer startup.
  • Corrected warning-mode watermark storage with a FIFO limit of 65,536 records while keeping enforce mode non-evicting.
  • Guarded wallet activity and NFT image routes in same-origin browser contexts with HTTP 403 and no-store; NFT images no longer enter the cache, and the SPA entry clears earlier cached content.
  • Restricted persistent wallet creation and restoration to wallet-storage administrator authorization when persistent storage is configured. The API returns HTTP 401 or 403 as appropriate while retaining general bearer authorization for ephemeral operation.
  • Cleared serialized KeyPush frame buffers after write attempts by building payloads in wipeable memory without changing the wire format.
  • Configured each Armory firmware build for one network, enforcing the mainnet chain, validating NETWORK and CHAIN parameters, producing chain-specific artifacts, and reporting the selected chain at startup.
  • Scoped restrictive permissions to decoded Apple .p12 files during release packaging so app bundles retain usable default permissions.
  • Updated the Cloud KMS client from 1.32.0 to 1.36.1.
  • Refreshed the validator library to 10.30.6, including upstream validation changes and new validator tags.
  • Upgraded the AWS Secrets Manager SDK from 1.50.1 to 1.50.8, incorporating upstream client and model fixes.
  • Corrected macOS release signing identity comparison to compile on current toolchains while preserving failure behavior when no identity is available.
  • Stabilized KES provider failure testing by using a loopback TCP connection and removing a timing delay.
  • Prepared the Preview end-to-end flow to wait for a ready and open signing log, prompt for the card before loading SIGNING_IMX, and fail headless runs before reset.
  • Printed the Armory pool host-key request as a JSON HostKeyRequest body so the end-to-end flow can post it directly.
  • Split signing-log SD card reads, writes, and sync operations into transfers of at most 16 blocks, preventing i.MX6ULL DMA allocation failures during card formatting and startup.
  • Updated gouroboros to v0.217.3 and plutigo to v0.11.3, incorporating upstream ledger and Plutus evaluation improvements.
  • Improved the AWS SDK configuration dependency from 1.33.6 to 1.33.12 with upstream credential, token, and STS fixes.
  • Refreshed gouroboros to v0.217.1 and plutigo to v0.11.2, incorporating upstream VRF, validation, and Plutus changes.
  • Upgraded gouroboros to v0.218.0 and plutigo to v0.11.4, incorporating Plutus machine reuse, memory bounds, and ledger and query changes.
  • Enhanced plutigo from 0.9.7 to 0.10.1 with evaluator hardening, corrected chooseData behavior, FLAT performance improvements, and transitive cryptographic updates.
  • Adjusted Armory Mk II recovery guidance so a signing-log SD failure after card reseating requires a device restart before retrying.
  • Restored wallet CRUD test reliability by disabling HTTP keep-alives during integration test shutdown.
  • Derived API wallet fixtures at runtime, removing recovery phrases and signing-key envelopes from tracked tests and adding a guard against their reintroduction.
  • Unified network resolution across the library and CLI for registry names, the testnet alias, and decimal magic values; invalid values fail, unregistered numeric magic maps to the testnet address network ID, and help text uses the same terminology.
  • Clarified pool registration help with reward-account withdrawal and DRep guidance and owner-key signing requirements.
  • Standardized source formatting with golines.

Doc Holiday logo

Docs authored by Doc Holiday

Editar página

Última actualización: