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

# Transactions

### Using the Ethereum Chain

EOAs, or externally-owned accounts, initiate the underlying operations to create Ethereum transactions, not the smart contracts called internally. The whole network is broadcasted transformations of the EVM states by the Ethereum transaction.

Several types of Ethereum transactions:

* *Regular transactions*. Transactions coming from one account to another
* *Contract Deployment Transactions*. Transactions with contract code sent in the data field, and without a `to` address
* *Execution of a Contract*: transactions that interact with a deployed smart contract, where the `to` address is the smart contract address

The following transactions are supported by Metanovaverse:

* [Dynamic Fee Transactions](https://eips.ethereum.org/EIPS/eip-1559)
* [Access List Transactions](https://eips.ethereum.org/EIPS/eip-2930) 
* [Legacy Transactions ](https://eips.ethereum.org/EIPS/eip-2718)

### Using Other chains

{% hint style="info" %}
Coming Soon
{% endhint %}


---

# 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.metanovaverse.com/metanova-verse-introduction/transactions.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.