> For the complete documentation index, see [llms.txt](https://docs.trueopen.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trueopen.ai/providers/node-lifecycle.md).

# Node Lifecycle

Join, operate, recover, rotate keys, and exit as a Cortex Node operator.

This workflow follows one Cortex Node operator through its service lifecycle.

```mermaid
flowchart TD
    A[Prepare operator and service keys] --> B[Deposit ServiceBond]
    B --> C[Declare Model support]
    C --> D[Complete activation duty]
    D --> E[Active Model support]
    E --> F{Lifecycle event}
    F -->|Support expires| G[STALE]
    G -->|Refresh support| E
    F -->|Recoverable fault| H[JAILED]
    H -->|Complete recovery| E
    H -->|Terminal fault| I[TOMBSTONED]
    F -->|Reduce bond or exit| J[UNBONDING]
    I --> J
    J -->|Liability closed and wait matured| K[Withdraw]
```

## Join

1. The operator prepares a stable operator account and a separate online service key.
2. The operator deposits the required ServiceBond and authorizes the service key.
3. The node declares supported Models and its inference or verification capabilities. It checks readiness for each Profile version it plans to serve.
4. The node completes a qualifying duty for each Model it wants to activate.
5. The active node begins handraising for Tasks whose Profile, duty, and liability requirements it satisfies.

The operator address is the economic identity. Running more processes or machines behind the same operator does not create extra protocol identities, support votes, or bonds.

## Operate

An active node continually:

* Keeps its Model support declarations fresh
* Observes candidate metadata and handraises only for work it can complete
* Persists signed Task material before sending it
* Tracks whether relayed actions were actually accepted on-chain
* Retains required result and evidence material through Task finality
* Preserves enough unreserved ServiceBond for new liabilities

If support freshness expires, the node becomes stale for future selection. Refreshing support can restore eligibility, but it does not extend or rewrite deadlines for Tasks already accepted.

## Rotate the service key

The operator first stops new handraises. It then waits until accepted Task liabilities, pending protocol submissions, and required duties reach zero.

The operator authorizes the replacement with a fresh nonce and proof that the new service key is controlled. The chain switches keys atomically. Historical receipts and duties remain attached to the operator; the old key immediately loses permission to submit new material.

## Fault and recovery

An objective fault may debit reserved responsibility funds and increase the operator's jail state. A recoverable jailed node may be allowed to perform bounded recovery duties with reduced candidate weight. Support renewal alone does not clear a jail.

Severe or repeated terminal responsibility can tombstone the operator. A tombstoned node cannot return to active service through an ordinary refresh or new service key.

## Reduce bond or exit

Reducing the bond or exiting starts unbonding and stops new eligibility. Existing Task duties, challenge exposure, evidence responsibility, and pending fault effects remain active.

Funds become withdrawable only after:

* The unbonding wait matures
* Every accepted Task liability closes
* Required evidence responsibility ends
* All applicable penalties have been applied

The released amount is the remaining balance after those responsibilities, not necessarily the amount originally requested.

See [Staking and penalties](/protocol/v1/service-participation/staking-and-penalties.md) for the governing rules.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.trueopen.ai/providers/node-lifecycle.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.