Skip to content

The Raw Signal ​

An Endpoint is the atomic unit of chain connection.

It represents the physical interface to a blockchain node—the raw signal that Backpac perpetually vets before it is promoted to the Orchestration Engine.

Sovereign vs. Managed Performance ​

Backpac supports two fundamental models for signal acquisition:

Sovereign Infrastructure (BYO) ​

Integrate any compatible RPC gateway as a private, sovereign endpoint. This enables complete control over your provider architecture (Alchemy, Infura, or self-hosted).

  • Sovereignty: Absolute control over provider relationships and custom header mandates.
  • Isolation: Unified access for authenticated infrastructure.

Managed High-Fidelity (DIN) ​

Leverage the Decentralized Infrastructure Network (DIN) for pre-vetted, high-performance signal paths.

  • Dynamic Resolution: Automatic endpoint discovery and failover across the DIN cluster.
  • Latency Optimization: Optimized routing through Backpac's institutional backbone.

Direct Orchestration ​

While most traffic is governed by Reliability Pools, Backpac supports Direct Orchestration for specific technical overrides.

Direct Node Assignment ​

You can pin an Institutional Entry Point to a specific endpoint, bypassing the load balancer to route 100% of traffic to a single infrastructure provider. This is the requirement for debugging state-specific consistency or forensic isolation.

Active Verification ​

Backpac does not trust upstream providers. The Monitor Service executes sub-second verification loops on every active endpoint:

  1. Liveness Verification: Direct HTTP 200 state checks.
  2. Telemetry Profiling: Real-time and historical latency EMA tracking.
  3. Chain Freshness: Strict verification of slot/block drift from the network tip.

Endpoints that fail verification are immediately pruned from the orchestration logic to protect the Unified SLA.

Metadata Enrichment ​

Endpoints can be tagged with operational metadata to influence orchestration:

  • Regional Anchoring: Geographic tagging (GCP, AWS, Global) to enforce physical proximity.
  • Routing Attributes: Custom key-value pairs used by Orchestrator Laws to steer traffic based on provider-specific logic.

The endpoint is the wire. The logic is the current.

Settlement Certainty Layer