> 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-developer-tools/protocol/core-protocol-components/generalized-accounts.md).
# Generalized Accounts
Generalized Accounts in æternity offer enhanced flexibility in how transactions can be authenticated, moving beyond traditional public-private key signatures. This powerful feature allows users to define custom logic for transaction authorization through smart contracts, enabling various authentication schemes such as multi-signature setups, spending limits, specific transaction type restrictions, or even alternative cryptographic signing algorithms like ECDSA used in Bitcoin and Ethereum.
The Generalized Accounts documentation provides comprehensive technical specifications for Generalized Accounts, including detailed examples of implementation. You'll find practical examples such as an ECDSA authentication contract that allows users to sign æternity transactions with their Bitcoin private keys, along with important security considerations and best practices for implementing authentication functions in these contracts.
---
# 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:
```
GET https://docs.aeternity.com/aeternity-developer-tools/protocol/core-protocol-components/generalized-accounts.md?ask=
```
The question should be specific, self-contained, and written in natural language.
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.