---
title: "Chains you can create a self-custody wallet on"
method: GET
path: "/v1/keys/tss/chains"
tags: ["Key Custody"]
---

# Chains you can create a self-custody wallet on

`GET /v1/keys/tss/chains`

## Request

- Base URL: `https://api.1claw.co`
- URL: `https://api.1claw.co/v1/keys/tss/chains`
- Auth: HTTP bearer

`chains` is what this organization can create now; `supported` is every
chain the threshold path implements. XRP and Cardano roll out as a beta.
Only creation is gated: an existing key always signs, restores, refreshes
and recovers offline. `multisig_chains` / `multisig_supported` are the
same for native 2-of-3 multisig wallets (Tron, `client_multisig`), behind
the same rollout flags, and `multisig_safe_chains` for 2-of-3 Safes on EVM.

## Response `200`

Chains

- object
  - `chains` string[]
  - `supported` string[]
  - `multisig_chains` string[]: Native multisig chains this organization can create a wallet on now.
  - `multisig_supported` string[]: Every chain the native multisig path implements (`tron`, `tron-nile`, `tron-shasta`).
  - `multisig_safe_chains` string[]: EVM chains this organization can create a 2-of-3 Safe on now (beta; chains with a pinned Safe v1.4.1 deployment).

## Other responses

- `401`: Authentication required or invalid

---

[API](https://skmtc.dev/1claw/apis/1claw-api.md) · [All operations](https://skmtc.dev/1claw/apis/1claw-api/llms.txt) · [OpenAPI document](https://skmtc.dev/1claw/apis/1claw-api/revisions/ae109b496830?raw)
