Luganodes

• Name: Luganodes
• URL: https://www.luganodes.com/
• Category: institutional staking operator / validator operations company / staking API middleware
• Tags: ethereum-ecosystem solana-ecosystem
• Summary: Luganodes belongs as an entity note. The interesting surface is not just that it runs validators. It is that the company bundles non-custodial staking operations, provisioning APIs, reporting, account-level analytics, gatewayed billing, and chain-specific tooling into one operator-controlled workflow shell.
• What it does:
  • Operates non-custodial staking and validator infrastructure across a large set of proof-of-stake networks for institutions and individuals while keeping funds in users’ existing custody setups
  • Exposes Ethereum-facing APIs for validator provisioning, staking workflows, validator objects, deposit details, rewards, transaction history, and related data services
  • Offers an institutional Terminal that uses in-house indexers to consolidate wallet, delegation, and reward insights across supported networks
  • Publishes operational tooling such as chain indexers, monitoring software, and validator-operation utilities through both docs and public GitHub repositories
  • Documents Settlex Flow, a pay-per-request API onboarding and gateway layer that routes third-party provider calls through a funded-party model rather than simple subscription billing
• Key claims:
  • Luganodes’ docs describe it as a world-class non-custodial blockchain infrastructure provider with institutional-grade staking, 99.9% uptime, 24/7 SRE monitoring, and support across 30+ PoS networks; treat those scale claims as company-published figures rather than independent verification
  • The docs say staking is non-custodial and explicitly note that Luganodes does not keep custody of clients’ withdrawal-wallet credentials, which makes the company boundary about workflow, validator operations, and visibility rather than direct asset possession
  • Official materials emphasize early compliance and security posture through SOC 2 Type II, GDPR, and ISO 27001 references, showing that the company is packaging institutional assurances alongside validator operations
  • The llms/docs surface reveals a wider product map than the homepage alone suggests, including staking APIs, provisioning APIs, indexers, Hyperliquid monitoring, Terminal analytics, and Settlex pay-per-request gatewaying
  • The public GitHub organization reinforces that Luganodes ships real operational software, including chain indexers, monitoring tools, and validator-operation utilities, rather than acting as a thin reseller shell
• Whitepaper: No standalone company whitepaper is the point here. The strongest primary materials for this pass were the official site, core docs, API and FAQ pages, Terminal / Settlex / tooling docs, and the public GitHub organization; see ../whitepapers/luganodes-primary-sources-2026-04-25.md.
• Sources:
  • https://www.luganodes.com/
  • https://docs.luganodes.com/
  • https://docs.luganodes.com/apis/ethereum/faqs
  • https://docs.luganodes.com/apis/settlex-flow.md
  • https://docs.luganodes.com/terminal/overview.md
  • https://docs.luganodes.com/tools/solana/solana-indexer.md
  • https://github.com/luganodes

Internal linkages

• Project-layer alias: luganodes.
• Keep this note on the clearest adjacent reads: figment, kiln, and p2p-org.
• Useful workflow contrast: obol.
• The analytical point is operator workflow, validator leverage, API-mediated access, and institution-facing staking packaging — not a directory of every validator shop.

Protocol / company boundary

• There is not a very useful standalone Luganodes protocol boundary doing most of the analytical work.
• The useful questions are who operates the validators, who authors the provisioning and reporting APIs, who controls account routing and analytics visibility, and who packages the supported staking workflows institutions inherit.
• That is why this note belongs in companies/: the practical authority lives in the company-run operating shell rather than in a neutral protocol primitive.

Control surface

• The leverage sits in validator operations, provisioning API defaults, supported-network coverage, reporting visibility, account routing, and the gatewayed billing / access layer around Settlex Flow.

• Terminal and the tooling/docs surface matter because they turn Luganodes into more than a validator endpoint: the company becomes part of the operator truth layer for monitoring, staking lifecycle state, and which integrations become easiest to run.

• Read Luganodes as a validator-operations and staking-workflow company, not as a protocol in its own right.

• Last reviewed: 2026-08-06 UTC