# Espresso

## Espresso

- [Espresso](https://docs.espressosys.com/network/readme.md): Build institution-controlled financial applications with real-time settlement, privacy, compliance controls, and access to global onchain liquidity.
- [Get Started](https://docs.espressosys.com/network/learn/quickstart.md)
- [What is Espresso?](https://docs.espressosys.com/network/learn/what-is-espresso.md): Real-time settlement for institution-grade financial applications without sacrificing privacy, control, or architectural sovereignty.
- [Use Cases](https://docs.espressosys.com/network/learn/use-cases.md): Institution-grade use cases for Espresso, including tokenized assets, stablecoins, payments, and collateral management.
- [How Espresso Fits](https://docs.espressosys.com/network/learn/espresso-in-the-modular-stack.md)
- [Configurable Execution Environments](https://docs.espressosys.com/network/learn/rollup-architecture.md)
- [Networks & Contracts](https://docs.espressosys.com/network/network/networks.md): Reference information for the Espresso networks: endpoints, contract addresses, and explorers.
- [Live on Espresso](https://docs.espressosys.com/network/network/chains-reference.md)
- [Changelog](https://docs.espressosys.com/network/network/changelog.md): Reverse-chronological history of Espresso network releases, with links to release notes and announcements.
- [Run Espresso Infrastructure](https://docs.espressosys.com/network/developer/operators.md): Pick the right Espresso infrastructure role for your team: validator, builder, or RPC Node.
- [Run a Validator Node](https://docs.espressosys.com/network/developer/operators/run-a-node.md): How to run an Espresso validator node: choose a network, register, and find the exact configuration you need.
- [Running a Mainnet Node](https://docs.espressosys.com/network/developer/operators/run-a-node/running-a-mainnet-1-node.md): This page provides the specific configuration used to run different types of nodes in Mainnet.
- [Running a Decaf Node](https://docs.espressosys.com/network/developer/operators/run-a-node/running-a-node.md): Configuration for Decaf nodes
- [Delegate $ESP](https://docs.espressosys.com/network/developer/operators/run-a-node/delegation-ui.md)
- [Run a Builder](https://docs.espressosys.com/network/developer/operators/running-a-builder.md): Information about running a builder for Espresso
- [Run an RPC Node](https://docs.espressosys.com/network/developer/operators/running-rpc-node.md)
- [Integrate a Chain](https://docs.espressosys.com/network/developer/rollup-developers.md)
- [From Private Besu to Espresso](https://docs.espressosys.com/network/developer/rollup-developers/besu-to-espresso.md)
- [Nitro / Orbit](https://docs.espressosys.com/network/developer/rollup-developers/nitro.md): Arbitrum integration with Espresso
- [Deploy a New Orbit Chain](https://docs.espressosys.com/network/developer/rollup-developers/nitro/deploy-a-new-orbit-chain.md)
- [Deploy Your Own Orbit Chain RPC Node](https://docs.espressosys.com/network/developer/rollup-developers/nitro/deploy-your-own-rpc-node.md)
- [Migrate an Existing Orbit Chain to Espresso](https://docs.espressosys.com/network/developer/rollup-developers/nitro/migrate-orbit-chains-to-espresso.md)
- [Using TEE with Nitro](https://docs.espressosys.com/network/developer/rollup-developers/nitro/using-tee-with-nitro.md)
- [Arbitrum Nitro Trust & Liveness Dependencies](https://docs.espressosys.com/network/developer/rollup-developers/nitro/arbitrum-nitro-trust-and-liveness-dependencies.md)
- [Mainnet 0 to Mainnet Upgrade](https://docs.espressosys.com/network/developer/rollup-developers/nitro/rollup-migration-guide.md): Migrating rollup integrations from Mainnet 0 to Mainnet
- [OP Stack](https://docs.espressosys.com/network/developer/rollup-developers/op.md)
- [OP Stack Integration](https://docs.espressosys.com/network/developer/rollup-developers/op/op-stack-integration.md)
- [ZK Attestation Verification](https://docs.espressosys.com/network/developer/rollup-developers/op/zk-attestation-verification.md)
- [API Reference](https://docs.espressosys.com/network/developer/espresso-api.md): Reference for REST APIs served by Espresso nodes and query services
- [Status API](https://docs.espressosys.com/network/developer/espresso-api/status-api.md): Node-specific state and consensus metrics
- [Catchup API](https://docs.espressosys.com/network/developer/espresso-api/catchup-api.md): Serves recent consensus state to allow peers to catch up with the network
- [Availability API](https://docs.espressosys.com/network/developer/espresso-api/availability-api.md): Serves data recorded by the Tiramisu DA layer, such as committed blocks
- [Node API](https://docs.espressosys.com/network/developer/espresso-api/node-api.md): Complements the availability API by serving eventually consistent data that is not necessarily agreed upon by all nodes
- [State API](https://docs.espressosys.com/network/developer/espresso-api/state-api.md): Serves consensus state derived from finalized blocks
- [Events API](https://docs.espressosys.com/network/developer/espresso-api/events-api.md): Streams events from HotShot
- [Submit API](https://docs.espressosys.com/network/developer/espresso-api/submit-api.md): Submit transactions to the public mempool
- [Builder API](https://docs.espressosys.com/network/developer/espresso-api/builder-api.md): The following describes the API endpoints a builder needs to support in order to build blocks in Espresso.
- [Earlier Versions](https://docs.espressosys.com/network/developer/espresso-api/earlier-versions.md)
- [v0](https://docs.espressosys.com/network/developer/espresso-api/earlier-versions/espresso-api.md): Reference for v0 REST APIs served by Espresso nodes and query services
- [Status API](https://docs.espressosys.com/network/developer/espresso-api/earlier-versions/espresso-api/status-api.md): Node-specific state and consensus metrics
- [Catchup API](https://docs.espressosys.com/network/developer/espresso-api/earlier-versions/espresso-api/catchup-api.md): Serves recent consensus state to allow peers to catch up with the network
- [Availability API](https://docs.espressosys.com/network/developer/espresso-api/earlier-versions/espresso-api/availability-api.md): Serves data recorded by the Tiramisu DA layer, such as committed blocks
- [Node API](https://docs.espressosys.com/network/developer/espresso-api/earlier-versions/espresso-api/node-api.md): Complements the availability API by serving eventually consistent data that is not necessarily agreed upon by all nodes
- [State API](https://docs.espressosys.com/network/developer/espresso-api/earlier-versions/espresso-api/state-api.md): Serves consensus state derived from finalized blocks
- [Events API](https://docs.espressosys.com/network/developer/espresso-api/earlier-versions/espresso-api/events-api.md): Streams events from HotShot
- [Submit API](https://docs.espressosys.com/network/developer/espresso-api/earlier-versions/espresso-api/submit-api.md): Submit transactions to the public mempool
- [Glossary of Key Terms](https://docs.espressosys.com/network/glossary/glossary.md)