Transaction Flow#
Transaction Flow groups related pages inside Develop. Transaction construction and lifecycle pages.
The table links to the next useful page or sub-hub, keeping the sidebar staged instead of fully expanded.
Map#
| Page | What you'll find |
|---|---|
| Transaction Overview | Each Ergo transaction is an atomic state transition operation, which means that it destroys a box from the state and creates new ones. |
| Transaction Lifecycle | A typical Ergo payment moves through four well‑defined stages. |
| Composing Transactions | Each Ergo transaction represents an atomic state transition operation. |
| Chained Transactions | Chained transactions allow for the sequential use of outputs from off-chain transactions. |
| Multi-stage Transactions | A simple transaction (tx) is the foundation of all transactions, representing a direct exchange between two parties. |
| Unified Transactions | Transactions in Ergo are pivotal in enabling a variety of operations within the network. |
| Model Transaction | The UTXO (Unspent Transaction Output) model, which we use, can be a bit confusing if you're used to the Account model. |
| Payments Overview | ErgoPay and the web dApp connectors that Nautilus uses serve similar purposes but have key differences. |