For the complete documentation index, see llms.txt. This page is also available as Markdown.

Technical scope

Infrastructure types

Altitude's published scope includes:

  • execution-layer nodes, including reth-based deployments;

  • consensus-layer nodes where required;

  • archive nodes for historical state and data;

  • EVM-compatible chain infrastructure;

  • custom endpoints and indexing.

Customization

For compatible stacks, an engagement can include:

  • optimized or modified RPC methods;

  • project-specific endpoints;

  • response shaping and aggregation;

  • DeFi indexing;

  • dedicated or capacity-limited access.

Production checklist

Before launch, agree on:

  • exact networks and chain IDs;

  • endpoint URLs and authentication;

  • rate and concurrency limits;

  • data retention and archive depth;

  • latency and availability objectives;

  • regional deployment and failover;

  • logging, monitoring, and incident contacts;

  • change management and maintenance windows.

Important limitation

This documentation does not publish a universal endpoint, SLA, rate limit, or supported-method matrix because those depend on the contracted deployment. Request the specification for your environment from Altitude.

Last updated