Infrastructure Status

EVM JSON-RPC for the Integra testnet (chain ID 26218), served via Caddy path routing on the Helsinki gateway (46.225.231.81). Used by the development team for testing smart contract deployments, EVM transaction flows, and wallet integration. Downtime blocks the entire dev team from testing any EVM-related feature changes.

CometBFT RPC for the Integra testnet chain, served via Caddy path routing on the Helsinki gateway (46.225.231.81). Provides block data, transaction broadcasting, and consensus state for development and QA. Powers the testnet block explorer with live chain data.

Cosmos REST/LCD for the Integra testnet, served via Caddy path routing on the Helsinki gateway (46.225.231.81). Serves governance, staking, and account queries over HTTP for development.

Companion probe to testnet-signer1-evm-rpc. Targets the second upstream in the Caddy least_conn pool. Requires ufw on signer-2 to allow 45.77.139.208 (this host) before enabling.

Polls the testnet CometBFT RPC /status endpoint every minute, comparing sync_info.latest_block_time to wall-clock now. Goes DEGRADED at 5 minutes of staleness, DOWN (and pages on Telegram via the 2-consecutive-failure flow) at 30 minutes. This is the canonical signal that explorer.testnet is showing live-but-stale data.

Polls /num_unconfirmed_txs on the testnet RPC every minute. A healthy testnet drains the mempool in <1 block (~5s) so steady-state depth is single-digit. DEGRADED at ≥300 pending txs, DOWN at ≥1000. Common triggers: a service stuck retrying the same nonce with insufficient gas bump (replacement-underpriced storm), an external spammer, or block-level inclusion failures (gas, ABCI rejection).

Monitors the testnet block explorer's indexer sync status by comparing its latest indexed block height against the Ormos testnet chain head. Same check logic as mainnet — detects stuck sync jobs and worker failures. Critical for the dev team to notice when testnet explorer data goes stale during active development and QA testing. The most common cause of a DOWN result is the explorer auto-disabling itself (shouldSync=false) after 10+ consecutive RPC failures — the sync-status API returns an empty explorers array in this state. Recovery: UPDATE explorers SET "shouldSync"=true, "syncFailedAttempts"=0, "syncDisabledAt"=NULL WHERE id=1.

The primary backend powering the Integra Dashboard with 75+ REST API endpoints, built with NestJS, PostgreSQL, and JWT authentication. Handles portfolio management, staking position tracking, XP/points integration, asset management, bulk CSV imports, notification preferences, and direct AWS SNS dispatch for SMS/email notifications (consolidated from the retired notification-api). The production Dashboard frontend is 100% dependent on this — if it goes down, users see a blank dashboard. Depends on the Absinthe XP API for points and leaderboard data.

Development instance of the Dashboard API, running the same NestJS codebase as production but connected to testnet blockchain networks and a separate dev database. Used by Nawar and the backend team for feature development, API testing, and QA validation before promoting changes to production. Also depends on Absinthe for XP features. If down, the dev Dashboard frontend is completely unusable, blocking frontend development and integration testing.

The game backend for City of Integra, a gamified city builder experience hosted on AWS App Runner in ap-south-1 (Mumbai). Manages all game state including building placement, resource generation, city progression, upgrade paths, and player inventories. The City Builder frontend is 100% dependent on this service — without it, the game is completely unplayable. Deep health checks verify database connectivity and game state consistency. Contact Kalki for game logic issues or Nawar for infrastructure/deployment concerns.

A lightweight API endpoint serving the current circulating supply of IRL tokens, consumed by cryptocurrency exchanges (for market cap calculations), data aggregators like CoinGecko and CoinMarketCap, and portfolio trackers. Returns a single number but has outsized importance — incorrect or unavailable supply data causes wrong market cap figures across all listing platforms. Hosted on Polytrade infrastructure (legacy domain). Contact Parth for supply calculation logic updates.

Real-time token pricing API that aggregates IRL and related token prices from multiple sources, serving them to the Dashboard for portfolio valuations, staking reward estimates, and transaction value displays. If this endpoint goes down or returns stale data, users see incorrect portfolio totals and missing price charts in the production Dashboard. Hosted on Polytrade infrastructure. No external dependencies but impacts user confidence when prices appear stale or zero.

Stateless microservice that generates time-limited pre-signed AWS S3 URLs for secure file uploads, used by the Dashboard for document uploads (KYC, title deeds) and the City Builder for asset uploads. Each URL expires after 15 minutes and is scoped to a specific S3 path. If down, all file upload workflows across the platform fail silently — users see upload buttons but files never reach S3. Contact Parth for S3 bucket configuration or CORS issues.

Companion service to the Presigned URL API that tracks file upload progress, stores metadata (file size, type, upload timestamp), and confirms successful uploads to the requesting application. The Dashboard polls this service to show upload progress bars and confirm document receipt. If down, uploads still succeed (files reach S3) but the frontend shows perpetual "uploading" spinners and cannot confirm completion to the user.

The backend API service for the testnet block explorer, same stack as mainnet (Node.js + BullMQ). Indexes Ormos testnet blocks and transactions, serving the testnet explorer frontend. Used by the dev team for testing explorer features and verifying testnet chain activity.

Polls /api/health/alerter on the testnet explorer and checks that its module-scoped Telegram delivery state shows a successful send within the last 30 minutes. If the alerter has been silent for longer, this probe trips DEGRADED (>30 min) or DOWN (>120 min), and integra-status sends its own Telegram alert — using a separate bot+token, on a separate host (Vultr) from the explorer (Hetzner). This is the meta-watchdog called out by GOAL_TESTNET_STABILITY.md §6.D4. The thresholds were relaxed from 15min/60min on 2026-05-13 to eliminate self-noise during healthy quiet periods; they will be tightened back once the explorer ships a periodic Telegram heartbeat that updates lastSuccessAt every ~5 min regardless of whether real alerts are being sent.

Testnet block explorer for the Ormos chain, hosted on the Helsinki gateway (46.225.231.81). Used daily by the dev team to verify test transactions, inspect testnet blocks, and validate governance features during QA. Depends on testnet Cosmos RPC and REST.

The Integra infrastructure status page co-hosted on the Vultr signer1 box (45.77.139.208) at status.integralayer.com via Caddy reverse proxy (port 3003). Monitors all enabled endpoints across blockchain nodes, validators, APIs, frontends, and external services. Self-monitoring ensures the status page itself is accessible when users need to check system health during incidents. Telegram bot @IntegraHealthBot sends alerts on status transitions.

Validator dashboard web app built with Next.js 15 + TypeScript + Tailwind + shadcn/ui, deployed on Vercel. Features chain status monitoring, health dashboard, and wallet connect (MetaMask/Keplr/OKX). Pinned to testnet after the mainnet retirement — the mainnet network toggle was disabled in the upstream integra-portal repo.

The testnet blockchain portal for the Ormos chain, same app as mainnet but connected to testnet endpoints. Provides network metrics, validator list, governance proposals, and chain parameters for the Ormos testnet (EVM chain ID 26218). Used by the dev team and external testers to interact with the testnet. If down, validators and testers lose the primary UI for testnet chain interaction.

Developer documentation site hosted via CloudFront (d1xxuq0cmqccbi.cloudfront.net). Contains API references, SDK integration guides, node operator runbooks, architecture overviews, and smart contract documentation. First stop for external developers integrating with Integra.

The primary public-facing website for Integra Layer, hosted on Webflow (www.integralayer.com → cdn.webflow.com). Serves as the main entry point for potential users, investors, partners, and developers discovering the Integra ecosystem. Contains the product overview, team page, ecosystem links, blog, and investor materials. Downtime is highly visible — it is the first URL shared in pitches, press releases, and social media.

The production Integra Dashboard — the flagship user-facing application built with React and deployed via CloudFront (d30tx0nyvfn5m7.cloudfront.net). Provides portfolio management, staking delegation, XP tracking, asset management, leaderboard rankings, and notification preferences. This is where Integra users spend most of their time and is the single most important frontend service. Fully depends on the Dashboard API for all data.

Development instance of the Dashboard frontend on CloudFront (d30tx0nyvfn5m7.cloudfront.net), connected to the dev Dashboard API and testnet blockchain endpoints. Used for building and testing new UI features before production deployment.

The production City of Integra web application — a gamified city builder deployed via CloudFront (d2qwqsckcs28yb.cloudfront.net). Users construct and manage virtual cities to earn XP and rewards. Fully depends on the City API for all game logic.

Development instance of the City of Integra frontend on CloudFront (d2qwqsckcs28yb.cloudfront.net). Used for testing new game UI features and playtesting mechanics before production.

The Integra Layer technical whitepaper, hosted on GitBook (10f87b7384-hosting.gitbook.io) via CNAME. Details the protocol design, CometBFT consensus mechanism, EVM module architecture, tokenomics (IRL supply, staking rewards, inflation), and network governance model. Referenced in investor due diligence, exchange listing applications, and developer onboarding.

The XP Portal built with React on Vercel, where users track their accumulated points, view real-time leaderboard rankings, complete quests, and claim rewards. This is a key community engagement tool — active users check it daily for leaderboard position changes and new quest availability. Depends entirely on the Absinthe XP API for all points data and leaderboard calculations. If Absinthe is down, the portal shows stale or empty data. Contact Tara for frontend issues or Parth for Absinthe integration.

The staking interface built with React on Vercel (Polytrade legacy domain), where users delegate IRL tokens to validators, manage their delegation positions, redelegate between validators, and claim accumulated staking rewards. This is critical for network security — it is the primary way token holders participate in consensus by staking. If down, users cannot delegate or claim rewards, potentially impacting validator economics and network security participation rates. Contact Tara for frontend issues.

NFT metadata and media storage service hosted on Vercel, serving asset images, metadata JSON files, and collection information for NFT display across the Dashboard and marketplace features. Follows the ERC-721/1155 metadata standard so wallets and aggregators can resolve token URIs. If down, NFT thumbnails and metadata fail to load across the platform — users see broken images and missing asset names. Contact Tara for deployment or Parth for metadata schema changes.

The primary GitHub organization for Integra Layer, hosting all active repositories including the explorer, dashboard, city builder, validator tooling, and infrastructure-as-code. Monitored via the GitHub API to detect outages that would block CI/CD pipelines, code deployments, PR reviews, and developer collaboration. A GitHub outage halts all development velocity across the team. Contact Adam for org-level access issues.

Legacy GitHub organization from the Polytrade Finance era, still hosting shared libraries, older smart contracts, and utility packages that some services depend on. Monitored to ensure CI/CD pipelines that pull from these repos continue to function. Being gradually migrated to the Integra-layer org. Contact Adam for access or migration questions.

Absinthe Network's GraphQL API (gql3.absinthe.network) powering the entire XP/points ecosystem — point accumulation, leaderboard rankings, quest tracking, and reward eligibility calculations. This is a critical third-party dependency with wide blast radius: both Dashboard API instances (prod and dev) and the XP Portal depend on it. When Absinthe is down, XP features show errors across the Dashboard, the Portal displays empty leaderboards, and quest progress stops updating. Contact Parth for integration issues or escalation to the Absinthe team.

Web3Auth third-party service enabling non-custodial wallet pregeneration and social login for Integra users. When a user signs up via Google or email, Web3Auth generates an Integra wallet using MPC (multi-party computation) without the user managing a seed phrase. The Passport API depends on this for all new user registrations. If Web3Auth is down, new user onboarding fails completely — existing users can still log in via cached sessions but no new wallets can be created. Contact Parth for Web3Auth configuration or API key issues.

OpenAI API integration (GPT-4 Vision) used in the Dashboard for AI-powered title deed extraction and document processing. When users upload property documents, the system uses GPT-4V to perform OCR, extract structured data (owner name, property details, valuation), and auto-populate form fields. If OpenAI is down, document uploads still succeed but automatic data extraction fails — users must manually enter all property information. Non-blocking but degrades UX significantly. Contact Parth for API key or model configuration.

Alchemy's enterprise blockchain infrastructure providing fallback RPC access for Ethereum mainnet and EVM-compatible chains, plus webhook-based event indexing for token transfers and contract events. Acts as a reliability layer — if Integra's primary EVM RPC nodes are slow or unresponsive, services can failover to Alchemy endpoints. Also powers webhook-driven notifications for on-chain events. If Alchemy is down, the fallback RPC path is lost and webhook-based event processing stops. Contact Adam for Alchemy dashboard access or API key rotation.

Twitter/X API v2 integration for displaying the Integra social media feed on the Dashboard, showing recent announcements, community highlights, and ecosystem updates. While non-critical to core functionality, the social feed is prominently placed on the Dashboard home screen and its absence is visually noticeable to users. Frequent Twitter API rate limits or outages cause the feed section to show an empty state. Contact Tara for frontend display issues or Parth for API credential management.

Google OAuth 2.0 / OpenID Connect endpoint used for social login authentication in the Passport API. When users click "Sign in with Google," the authentication flow hits this endpoint for token exchange and identity verification. If Google OAuth is down (extremely rare), all Google-based sign-ups and logins fail — users must wait or use alternative login methods. The Passport API checks the OIDC discovery document on startup to cache signing keys. Contact Parth for OAuth client configuration or redirect URI changes.

DiceBear API v7 for procedural avatar generation in the City of Integra, creating unique identicon-style SVG avatars based on user wallet addresses or usernames. Both the production and dev City Builder frontends request avatars on-demand from this API. If DiceBear is down, avatar images fail to load and users see broken image placeholders in their city profiles and leaderboard entries. Low severity but visually noticeable. Contact Kalki for City Builder integration or consider caching avatars locally.

WalletConnect v2 relay server enabling external wallet connections (MetaMask, Trust Wallet, Rainbow, Coinbase Wallet, etc.) to the Integra Dashboard via QR code scanning or deep links. This is the bridge between mobile/browser wallets and the Dashboard — if the relay is down, users cannot connect their wallets to perform transactions, stake tokens, or sign messages. High impact because many users rely on external wallets rather than the embedded Passport wallet. Contact Tara for WalletConnect SDK integration or Parth for project ID configuration.

Vercel platform-level availability monitoring — Vercel hosts all Integra frontend applications (Dashboard, Explorer, City Builder, Portal, Staking), documentation, whitepaper, and static sites. This is a platform-level dependency with the widest blast radius of any external service: if Vercel experiences an outage, the majority of user-facing Integra services go down simultaneously. Vercel provides edge CDN, serverless functions, and automatic deployments from GitHub. Contact Adam for Vercel team access or billing, or Tara for deployment configuration.