Node Operator Admission: HostDeFi as stVault Basic Operator

Node Operators stVaults Identification
1

1. Identification

HostDeFi is an independent, non-custodial validator and node-infrastructure collective. We request identification as a Basic Identified Node Operator under the individual node-operator path. Our role is purely as a node operator / infrastructure provider ā€” we run validators for stVault creators rather than sourcing ETH ourselves.

We operate dedicated bare-metal hardware (US, Ryzen 7950X / 128 GB / NVMe) plus distributed cloud instances, running a multi-network node fleet: an Obol DVT cluster on Ethereum Hoodi testnet (3/3 nodes live and attesting across three independent hosts), an EigenDA operator registration, an Espresso node registered on-chain, a Babylon testnet validator bonded on-chain, a Cosmos ICS testnet validator, Solana mainnet + testnet validator infrastructure (SFDP application in Foundation review), and a DePIN fleet (Theta edge, Storj, AIOZ, Pactus, Xandeum, Asentum). We also operate an 82-chain public RPC relay.

2. Business case

  • ETH sourcing potential: none claimed ā€” we do not plan to attract ETH ourselves. Our intended role is an infrastructure operator available to stVault creators who want an independent, dedicated-hardware operator in their operator set.
  • User segments / channels: independent node operators and sub-operators; we coordinate via our public site and direct ops contact.
  • Timelines: operational now ā€” existing clusters can accept stVault duties as soon as the Committee admits us.
  • Fee policy: we will follow the stVaults operator fee framework and stay competitive within Committee norms.

3. Operations & decentralization

  • Client mix: Lighthouse validator clients inside our Obol DVT cluster (charon middleware); Solana agave/jito client; Cosmos SDK (gaiad), Babylon, and other chains under their standard clients.
  • Infra footprint: dedicated bare-metal (US) + distributed cloud instances; the Obol cluster spans three physical hosts for fault tolerance.
  • Jurisdictional spread: currently US-centric; expanding.
  • MEV posture: no custom MEV strategies ā€” standard client defaults and Committee guidance.

4. Supporting links

New accounts on this forum cannot embed links, so contact details are written out: our site is hostdefi dot com, our public RPC relay is rpc dot hostdefi dot com, ops contact is ops at hostdefi dot com, Telegram handle is at HostDeFiOps.

The mandatory Basic stVaults Identification form was submitted via the private intake last Friday; we are proceeding with the KYB step in parallel and can share formation documentation when it lands.

1 Like