> For the complete documentation index, see [llms.txt](https://docs.rome.builders/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rome.builders/id/konsep-inti.md).

# Konsep Inti

- [Model Eksekusi](https://docs.rome.builders/id/konsep-inti/execution-model.md): Cara Rome EVM memproses transaksi Ethereum di Solana — emulasi proxy, mode atomik (VmAt) vs. iteratif (VmIt), dan siklus hidup transaksi lengkap.
- [Anggaran Komputasi](https://docs.rome.builders/id/konsep-inti/compute-budget.md): Biaya satuan komputasi Solana (CU) untuk operasi Rome EVM — anggaran atomik vs. iteratif dan cara merancang kontrak Solidity yang efisien CU.
- [Batasan](https://docs.rome.builders/id/konsep-inti/constraints.md): Batas saat membangun di Rome EVM — ukuran transaksi Solana, anggaran ~1.4M CU, batas akun, tata letak storage, dan bagaimana Rome mengatasi masing-masing.
- [Interoperabilitas Token](https://docs.rome.builders/id/konsep-inti/token-interop.md): Bagaimana token ERC-20 dan SPL adalah akun dasar yang sama di Rome.
- [Cara Solana dan EVM bertemu di Rome](https://docs.rome.builders/id/konsep-inti/how-solana-and-evm-meet.md): Bagaimana dompet Solana memanggil kontrak Solidity, alamat EVM memanggil program Solana, dan Rome menangani identitas, token, biaya, serta batas eksekusi.
- [Pilih inti Anda](https://docs.rome.builders/id/konsep-inti/choose-your-core.md): Aplikasi dua jalur dapat menempatkan logika intinya di sisi Solidity atau sisi native Solana. Ini keputusan penilaian — pertimbangkan apa yang paling penting bagi aplikasi Anda.


---

# 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.rome.builders/id/konsep-inti.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.