Manage Wallet Signers

A wallet's signer set is the list of keys CRE Connect will accept signatures from when executing operations against the wallet's Smart Account. The set is typed: ecdsa wallets accept EVM addresses, rsa wallets accept RSA public keys.

What can be configured today

OperationSupported via Go SDKNotes
Set initial signer setYesAt wallet-creation time, via wallets.CreateInput.
Read current signer setYesWallets.Get returns AllowedEcdsaSigners / AllowedRsaSigners.
Add / remove signers at runtimeNoThe Go SDK exposes no API for mutating the signer set after creation; wallets.UpdateInput only accepts Name.
Rename walletYesWallets.Update (Go SDK) accepts only Name. The REST PATCH /wallets/{id} endpoint also accepts description and status.
Archive walletYesWallets.Archive is synchronous (PATCHes status to archived); the on-chain Smart Account contract is not modified.

Set the signer set at creation time

Required role:

CRE Connect Operator

or higher

What each role can do

Provisioning a wallet with its initial signer set requires crec:wallet:write in your API key. The allowed signer addresses or public keys are onchain authorization settings; assigning a member a CRE Connect role does not add the member's key to this signer set.

StatusChannelId is optional on Create (the SDK rejects a zero-UUID value with wallets.ErrStatusChannelIDZero); pass the channel where you want wallet.status events to land.

ECDSA wallet:

import (
    "github.com/smartcontractkit/crec-sdk/wallets"
    apiClient "github.com/smartcontractkit/crec-api-go/client"
)

statusChannelID := channelID // any channel you own
ecdsaSigners := []string{
    "0x1111111111111111111111111111111111111111",
    "0x2222222222222222222222222222222222222222",
}

w, err := client.Wallets.Create(ctx, wallets.CreateInput{
    Name:                "treasury-eth",
    ChainSelector:       "5009297550715157269",
    WalletOwnerAddress:  "0xYourOwnerEOA",
    WalletType:          apiClient.Ecdsa,
    AllowedEcdsaSigners: &ecdsaSigners,
    StatusChannelId:     &statusChannelID,
})

RSA wallet:

rsaSigners := apiClient.RSASignersList{
    // E and N are 0x-prefixed hex strings (validated by the API regex
    // `^0x[a-fA-F0-9]{2,34}$` for `e` and `^0x[a-fA-F0-9]{512,}$` for `n`).
    // E is typically `0x010001` (= 65537). N is at least 2048 bits = 512 hex chars.
    {E: "0x010001", N: "0xc2a8...hex-encoded-modulus..."},
}

w, err := client.Wallets.Create(ctx, wallets.CreateInput{
    Name:               "rsa-treasury-eth",
    ChainSelector:      "5009297550715157269",
    WalletOwnerAddress: "0xYourOwnerEOA",
    WalletType:         apiClient.Rsa,
    AllowedRsaSigners:  &rsaSigners,
    StatusChannelId:    &statusChannelID,
})

Service limits enforced by the API (RSASignersList / ECDSASignersList schemas, maxItems: 10): maximum 10 ECDSA signers and maximum 10 RSA signers per wallet.

Read the current signer set

Required role:

CRE Connect Viewer

or higher

What each role can do

Reading a wallet's signer set requires crec:wallet:read in your API key. Reading the set does not grant access to the private signing keys.

w, err := client.Wallets.Get(ctx, walletID)
if err != nil { return err }

if w.AllowedEcdsaSigners != nil {
    for _, addr := range *w.AllowedEcdsaSigners {
        fmt.Println("ecdsa signer:", addr)
    }
}
if w.AllowedRsaSigners != nil {
    for _, k := range *w.AllowedRsaSigners {
        fmt.Println("rsa signer:", k.E, k.N)
    }
}

curl:

curl -sS "$CREC_BASE_URL/wallets/$WALLET_ID" \
  -H "Authorization: Apikey $CREC_API_KEY" \
  | jq '{allowed_ecdsa_signers, allowed_rsa_signers}'

Changing the signer set after creation

The signer set is fixed at creation. To use a different signer set, provision a new wallet with Wallets.Create using crec:wallet:write (CRE Connect Operator or higher). If you also archive the old wallet with Wallets.Archive, that separate action requires crec:wallet:archive:write (CRE Connect Admin or the organization Owner). See Archive a wallet. These API actions do not transfer ownership of the original onchain Smart Account.

Choosing signer addresses up front

When you call Wallets.Create you don't pass a signer.Signer instance: you pass the address (ECDSA) or {e, n} pair (RSA) that signer will produce. Each per-provider guide documents the exact helper to use:

For RSA signers the modulus n and exponent e must be 0x-prefixed hex strings, validated by the API regex ^0x[a-fA-F0-9]{2,34}$ for e and ^0x[a-fA-F0-9]{512,}$ for n (i.e. ≥ 2048-bit modulus). The Vault helper GetRSAModulus() returns hex without the 0x prefix; prepend it before passing the value to wallets.Create.

Sentinel errors

ErrorTrigger
wallets.ErrInvalidEcdsaSignerAn entry in AllowedEcdsaSigners is not a valid hex address.
wallets.ErrInvalidRsaSignerAn entry in AllowedRsaSigners has empty E or N.
wallets.ErrInvalidSignersForEcdsaAllowedRsaSigners set on an ecdsa wallet.
wallets.ErrInvalidSignersForRsaAllowedEcdsaSigners set on an rsa wallet.

Next steps

Get the latest Chainlink content straight to your inbox.