CRATEFIELD
Get started with Harness Join the waitlist

signer

Key-reference signing: a venture names a key, never touches raw key material, and every sign call passes the guardrails first.

With cargo

cargo add cratefield-signer
crates.iodocs.rsSource

What it is

signer.

The key-reference signing port for wallet automation (issue #761). A venture asks for an EVM transaction, an ERC-4337 UserOperation, EIP-712 data or a Solana message to be signed, names the key, and never touches raw key material: keys are minted here and referenced everywhere else, and no API in this crate exports a private key. Every sign call runs the same gauntlet in order — decode the payload’s intent, ask the guardrails, write the decision to an append-only audit chain — and only on allow does the underlying key sign.

From the crate’s own README.

Ports

KeySigner

History

Changelog.

From the crate’s CHANGELOG.md in the harness, as of 0c5560b. 1 version recorded, newest first. Every published version is on crates.io.

  1. 0.1.1

    crates.ioRelease

    Other

    • updated the following local packages: cratefield-secrets
    • Key-reference signing port (KeySigner), payloads (EvmTransaction, UserOperation, Eip712, SolanaMessage) with locally computed signing hashes, StaticGuardrails, the MemorySignAudit hash chain, the GuardedSigner composition, the SecretsSigner session-key provider, and the fakes / conformance kit (issue #761).

One of 76 crates in the harness, all of them MIT and all of them in one repository.

Join the waitlist All modules