Skip to main content
The checked .env.example files describe names and local defaults. Actual values belong in private deployment configuration. A frontend variable is public once bundled.

​
API configuration

An empty contract address is a not-deployed state, not a reason to substitute fixture data into Live mode. A changed deployment identity requires deliberate index/replay planning.

​
Frontend configuration

Rebuild the frontend when changing build-time public configuration. Never place the private RPC provider URL, signing key, database URL, or provider application key in a NEXT_PUBLIC_* field.

​
Optional API services

The Aurora verification RPC is a separate mainnet connection. It does not change the settlement CHAIN_ID. A configured provider key is also not proof of a completed real transfer.

​
Envio configuration

Use the indexer environment example. The worker needs ENVIO_API_TOKEN, its realtime MONAD_RPC_URL, PostgreSQL connection settings, and ENVIO_PG_SCHEMA=envio. The API’s application tables remain separate from that schema. Hasura is disabled in this deployment. HyperIndex 3.14 still initializes configuration fields for it, so retain the documented unused loopback endpoint and disabled settings rather than exposing a query server. Bind health/metrics locally if publishing the container port. Use appropriate TLS verification for database connections across untrusted networks. Keep the worker’s system CA bundle installed for its native RPC client. A successful Node RPC check does not prove the native worker can establish TLS.

​
Configuration changes that need special care

Changing origins invalidates assumptions about cookies and CSRF. Changing chain, token, contract, or deployment block changes what the index means. Changing an insight budget can permit additional provider spend. Treat those as explicit operational changes, then verify their observable result through status and controlled reads.