> For the complete documentation index, see [llms.txt](https://docs.sat20.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sat20.org/english/learn-understanding-satoshinet/stp.md).

# STP Introduction

STP stands for Satoshi Transcending Protocol. It defines how Bitcoin L1 assets enter SatoshiNet, move inside SatoshiNet, and exit back to Bitcoin L1.

The core of STP is not a "bridge"; it is a channel.

STP must be understood together with indexers. The indexer explains Bitcoin L1 asset facts: which UTXO carries which asset, whether it is confirmed, whether it is spent, and whether the protocol event is valid. STP builds channel control on top of those facts so users can enter SatoshiNet and exit in abnormal situations.

## What STP Does

| Action           | Meaning                                                          |
| ---------------- | ---------------------------------------------------------------- |
| open             | Open a channel between a user and a Core Node                    |
| splicing-in      | Add Bitcoin L1 assets into an existing channel                   |
| unlock           | Release channel assets to a personal SatoshiNet address          |
| lock             | Bring personal SatoshiNet assets back into the channel           |
| lock-with-expand | Restore channel protection when channel capacity is insufficient |
| splicing-out     | Exit channel assets back to Bitcoin L1                           |
| close            | Close the channel                                                |
| punish           | Punish an old commitment transaction                             |

These actions are not isolated transactions. They are protocol state machines involving Bitcoin L1 transactions, SatoshiNet transactions, commitment-state updates, signature exchange, and confirmations. Every cross-layer action needs L1/L2 indexer evidence to prove that asset facts and channel state are consistent.

## Ordinary Users Do Not Stake

An ordinary user who connects to a Core Node and opens a private channel does not need to pre-stake assets. Staking belongs to the path where a node connects to a Bootstrap Node and prepares to become a Core Node.

User channels and node-staking channels are different scenarios.

## Meaning for Agents

STP is well suited for AI Agents because it has clear states, transactions, evidence, and recovery paths. An Agent can turn a user goal into verifiable steps:

1. Query wallet and channel state.
2. Check the safety snapshot.
3. Choose open, splicing, unlock, lock, or close.
4. Poll L1/L2 transactions and asset states through indexers.
5. Enter recovery when a result is unknown.

The full protocol whitepaper is [STP Technical Whitepaper](/english/protocol-and-security/stp/stp.md).


---

# 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.sat20.org/english/learn-understanding-satoshinet/stp.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.