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

# Transactions

On the ENI blockchain, transactions are essential for any **state update**, including **Token transfers, Account linking, Smart contract execution.** While creating an account does not require a transaction, but **linking an account** to blockchain operations does.

## Transaction Types

Since ENI supports both EVM and Cosmos SDK transactions, there are different transaction types based on the execution environment. The following sections provide an overview of Cosmos and EVM transactions on ENI.

### Cosmos Transactions

Cosmos transactions are used for interacting with Cosmos based RPC’s and tooling. They consist of the body, auth info, and signatures

#### Signing Cosmos Transactions

Cosmos transactions on the ENI blockchain follow the standard Cosmos SDK format. They include various types of messages that can be included in the transaction body.

Using the `enid` CLI, you can use the `--generate-only` flag to generate an unsigned transaction in JSON format. The transaction can then be signed and broadcasted to the network.

Assuming you have an unsigned JSON transaction file, you can sign it using the `enid tx sign` command. The signed transaction will be in JSON format and can be broadcasted to the network.

```
enid tx sign unsigned_tx.json --chain-id $CHAIN_ID --keyring-backend test --from $SIGNER_ADDRESS
```

### **EVM Transactions**

The **ENI blockchain** supports **Ethereum Virtual Machine (EVM) transactions**, allowing compatibility with **Ethereum-based tools and smart contracts**. The structure of EVM transactions is **different** from that of **Cosmos transactions**.


---

# 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.eniac.network/getting-started/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.
