> For the complete documentation index, see [llms.txt](https://docs.aeternity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aeternity.com/aeternity-core-concepts/protocol/transactions.md).

# Transactions

Transactions form the foundation of all operations within the æternity blockchain. Every change to the blockchain's state, whether it's transferring tokens, deploying smart contracts, registering names, or updating oracle data, occurs through transactions.

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td>More Protocol Transactions Documentation</td><td><a href="/aeternity-developer-tools/protocol/core-protocol-components/smart-contracts/contract-transactions.md">Contract Transactions</a></td><td><a href="https://839505583-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FggVl0Jqy6Dd8f38hGk63%2Fuploads%2FFg8uXb2tgWcUjB3yscps%2Fflip-30deg-gradient.svg?alt=media&amp;token=7011595e-bad7-4b5e-926e-501080d42820">flip-30deg-gradient.svg</a></td></tr></tbody></table>

Unlike simpler blockchain implementations that use a single transaction type and implement additional functionality through smart contracts, æternity provides specialized transaction types as native features of the protocol. This architectural choice offers significant advantages in efficiency, security, and usability. By implementing common operations as distinct transaction types rather than smart contract calls, æternity reduces computational overhead, provides clearer semantics for different operations, and enables optimized processing for each type of interaction within the network.

æternity's unique Bitcoin-NG consensus mechanism influences how transactions are processed. Rather than batching transactions into traditional blocks, the system separates leader election (through key blocks) from transaction processing (in micro blocks). This separation allows for faster transaction processing while maintaining security, achieving approximately 117 transactions per second with three-second micro block times.

The transaction system in æternity is designed to support both on-chain and off-chain operations through state channels, enabling scalable applications while maintaining security. Whether processing simple token transfers or complex smart contract interactions, the transaction system provides the foundation for all network operations while ensuring efficiency, security, and usability.

### In This Section

The following pages provide detailed information about different aspects of transactions in æternity:

* [Types of Transactions](/aeternity-core-concepts/protocol/transactions/types-of-transactions.md)
* [Transaction Lifecycle](/aeternity-core-concepts/protocol/transactions/transaction-lifecycle.md)
* [Transaction Fees](/aeternity-core-concepts/protocol/transactions/transaction-fees.md)
* [Meta-transactions and Generalized Accounts](/aeternity-core-concepts/protocol/transactions/meta-transactions-and-generalized-accounts.md)
* [State Channel Transactions](/aeternity-core-concepts/protocol/transactions/state-channel-transactions.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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.aeternity.com/aeternity-core-concepts/protocol/transactions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.