> For the complete documentation index, see [llms.txt](https://timechain.gitbook.io/neucron/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://timechain.gitbook.io/neucron/core-concepts/wallets-and-keys.md).

# Wallets & Keys

## The two-minute version

A **wallet** is not a container that holds coins. Assets live on the rail (the blockchain). A wallet is the set of **keys** that can authorize moving those assets, plus the **addresses** derived from those keys that let others send assets to you.

* A **private key** signs transactions. Whoever controls it controls the funds.
* A **public key / address** is what you share to receive funds.
* A **seed or key material** is the root secret from which keys are derived.

Every custody question in digital assets reduces to one thing: **where does the key material live, and who can use it?**

## What a wallet is in Neucron

A Neucron wallet is a managed key container with:

| Property                   | Description                                                                                                                     |
| -------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
| `wallet_id`                | Stable identifier used across the API                                                                                           |
| Wallet name                | Human-readable label                                                                                                            |
| Addresses                  | One or more per supported rail                                                                                                  |
| Paymail (optional)         | Human-readable payment alias                                                                                                    |
| Wallet type & provider     | The custody scheme backing the wallet (see [Custody Models](https://timechain.gitbook.io/neucron/core-concepts/custody-models)) |
| Cloud sync & backup status | Recovery state of the wallet's key shards                                                                                       |

Every individual gets a wallet at signup. Businesses own additional wallets for treasury, operations, and apps.

## Keys without key management

Raw key management (seed phrases, HSMs, signing daemons) is the hardest part of digital-asset infrastructure to get right and the easiest to get catastrophically wrong. Neucron replaces it with API-level primitives:

```typescript
// Create a wallet. Key material is generated, sharded, and stored
// according to the custody scheme you choose. You never handle a seed phrase.
const { data } = await sdk.wallet.createWallet({
  walletName: 'Operations',
  walletType: 'MPC',
  businessId: 'biz_abc123',
});
```

You interact with `wallet_id`s, balances, addresses, and transfers. Neucron handles key generation, shard distribution, signing, and recovery behind the API.

## Where to go next

* [MPC Key Shards](https://timechain.gitbook.io/neucron/core-concepts/mpc-key-shards): how Neucron splits keys so no single system ever holds a complete key.
* [Custody Models](https://timechain.gitbook.io/neucron/core-concepts/custody-models): non-custodial, custodial, and server-side schemes, and when to use each.
* [Supported Networks](https://timechain.gitbook.io/neucron/networks-and-assets/supported-networks): which rails each wallet can hold addresses on.