Repository navigation
Releases
v2.1.3
v2.1.3 - 2026-11-02
- Move the canonical Go module and all source, test, client-example, and release-check imports to
github.com/arctex-one/csign/v2after the repository transfer toarctex-one. - Update installation and migration guidance for the new organization. Go consumers must rewrite old imports and require v2.1.3 or later; existing release tags retain their original module declarations.
- Refresh compatible transitive Go dependencies while preserving the Vault metrics compatibility exclusions. Direct dependencies and GitHub Actions release tooling are already at their latest compatible stable releases.
The HTTP API, signing policies, custody transfer format, and storage schema are unchanged.
v2.1.2
v2.1.2
- Keep staged Source key material outside the live
keys/store. Older signers cannot discover or enable staged keys by ignoring import metadata. - Persist the Source fence before materializing any live key. Activation resumes through a forward-only
activatingjournal, verifies every exact original record, then opens the complete set with the final active transition. - Preserve foreign live keys created during a signer downgrade; activation rejects conflicts and abort removes only its staged private records.
- Preserve already-active previous receivers. Previous staged receivers must be aborted and prepared again before activation. The encrypted bundle format and ordinary signing API remain unchanged.
v2.1.1
v2.1.1
- Add privileged age-encrypted transfer of selected managed custody keys into an existing Vault mount, preserving exact legacy/current records, policies, IDs, and timestamps.
- Stage imports inactive with durable conflict checks, interruption/replay recovery, readback proofs, resumable abort, and explicit operator-attested activation.
- Require Vault sudo for custody administration; ordinary key/status/signing tokens cannot export or activate a staged set. Keep unrelated keys, KV secrets, auth state, and other mounts outside transfer.
- Add local Vault ACL, reload, staging and activation acceptance plus storage-failure and race coverage.
- Correct embedded release metadata. The v2.1.0 tag's artifact publication failed because it retained v2.0.1 metadata; that tag is preserved and no v2.1.0 GitHub release artifact was published.
v2.0.1
v2.0.1 - 2026-10-29
- Correct the Go module path to
github.com/lazysteff/csign/v2and migrate all internal imports and Go consumer examples. - Add a release gate that resolves the exact published tag through the Go module proxy from a clean external consumer, then builds the public client and Vault plugin without local replacements or a workspace.
- Document v2 installation, migration from the old module path, and version discovery. The HTTP API remains
v1.
The existing v2.0.0 tag is preserved. Its module declaration prevents consumption as a Go v2 module; Go consumers should use v2.0.1 or later.
v2.0.0
v2.0.0 - 2026-10-28
- Separate managed key types, signing schemes, internal input capabilities, protocol identity and custody execution.
- Migrate existing EVM/TRON operations through normalized input, deterministic compatibility resolution, frozen payload preparation and verified signatures.
- Add versioned managed records with strict legacy compatibility and lossless mutation.
- Add generic managed Ed25519 and explicitly authorized opaque
solana_messagesigning, returning one detached signature per call. - Add descriptive operation security-model discovery and architecture, migration and Gateway conformance tests.
- Update go-ethereum to v1.17.10, gotron-sdk to v0.27.1, compatible transitive dependencies and release lint tooling to v2.15.0.
- Preserve legacy external resolver public-key encoding and EVM/TRON verification error classifications across generalized execution.
Existing EVM/TRON /v1 requests, operation identifiers, key IDs and signing policies remain supported. Key responses add key_type; strict clients must allow the new discovery and response fields. Reads and signing do not migrate persisted keys. New keys and subsequent administrative mutations use schema version 2; take a Vault storage backup before upgrading and restore a compatible snapshot before rolling back to v1. Opaque Solana signing enforces operation authorization but does not enforce transaction instruction or amount semantics. See signing architecture and migration.
v1.3.1
v1.3.1 - 2026-09-28
Refresh remaining indirect dependencies and correct module exclusions.
- updated
github.com/gofrs/flockto v0.13.1 - updated
github.com/jhump/protoreflectto v1.18.1 - updated
github.com/klauspost/cpuid/v2to v2.4.0 - excluded the incompatible
github.com/armon/go-metricsv0.6.1 and v0.7.0 tags, preventing module-path mismatch warnings during dependency upgrades
The old armon/go-metrics module remains at v0.4.1 for Vault's compatibility layer. There are no API or signing-policy changes in this release.
v1.3.0
v1.3.0 - 2026-09-28
Fix direct EVM contract destination normalization and refresh dependencies.
- normalized valid direct contract-call destinations before checking
allowed_contract_destinations, so equivalent lowercase and checksum addresses produce the same signed transaction - preserved destination-allowlist precedence, malformed-address rejection, unauthorized-destination rejection, and strict lowercase encoding for structured EVM APIs
- added policy regression coverage and an end-to-end Vault backend signing test for adding an equivalent destination allowlist
- updated go-ethereum to v1.17.6, Vault SDK to v0.26.0, and compatible transitive Go dependencies
- updated the Go baseline to 1.27.1 and release verification to golangci-lint v2.14.0
github.com/hashicorp/go-metrics remains at v0.6.1: v0.7.0 removes the compat package still required by Vault SDK v0.26.0 and is explicitly excluded from module resolution.
v1.2.1
v1.2.1 - 2026-08-29
- raised the build and module baseline from Go 1.26.2 to Go 1.27.0
- updated the release workflow to
actions/checkoutv7.0.1 andactions/setup-gov7.0.0 - updated the release verification linter to golangci-lint v2.13.2
v1.2.0
v1.2.0 - 2026-08-28
Add byte-preserving memo signing for TRON transfers.
- added optional hex-encoded
memo_hexfields to TRX and TRC-20 transfer signing requests - populated
TransactionRaw.databefore hashing and signing, with byte-exact protobuf preservation - rejected malformed hex and transactions that exceed java-tron's 500×1024-byte serialized transaction limit
- added typed
supported_tron_memo_capabilitiesdiscovery metadata with encoding, operation, and size-limit details - added TRX, TRC-20, empty-memo compatibility, binary/Unicode memo, size, conformance, and opt-in Nile broadcast coverage
Empty or omitted memos retain the prior serialized transaction and transaction hash. Memo contents are public on-chain and are not logged by csign.
v1.1.1
v1.1.1 - 2026-07-19
Refresh compatible transitive Go module dependencies.
- updated
github.com/mattn/go-isattytov0.0.23 - updated
github.com/petermattis/goidtov0.0.0-20260716134002-a9b348f0a2b9 - updated
google.golang.org/apitov0.289.0 - updated
google.golang.org/genproto/googleapis/apiandgoogle.golang.org/genproto/googleapis/rpctov0.0.0-20260715232425-e75dac1f907d - updated
google.golang.org/grpctov1.82.1
There are no API or signing-policy changes in this release.