CRATEFIELD
Get started with Harness Join the waitlist

adapter-turnkey

The KeySigner port over Turnkey: a sub-organization per end user, and our backend only a delegated user inside it.

With cargo

cargo add cratefield-adapter-turnkey
crates.iodocs.rsSource

What it is

adapter-turnkey.

The Turnkey provider for the KeySigner port (issue #761). Every end user gets a Turnkey sub-organization: their passkey is the root user, a wallet is minted inside it, and our backend is only a delegated access user — a second root user whose API key is scope-limited and held in the Secrets port. A user’s keys are not ours to hold, and this is the provider that makes that true rather than merely intended.

From the crate’s own README.

Ports

Implements KeySigner

History

Changelog.

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

  1. 0.1.2

    crates.ioReleaseDiff

    Other

    • updated the following local packages: cratefield-core, cratefield-secrets

  2. 0.1.1

    crates.ioRelease

    Other

    • updated the following local packages: cratefield-core
1 earlier version 0.1.0

  1. 0.1.0

    crates.io

    Other

    • the Turnkey provider for the KeySigner port (#761): passkey-rooted sub-organizations with a delegated-access user, policy-scoped signing by key reference, and DENY-policy kill switches

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

Join the waitlist All modules