sentinel-primary-sources-2026-05-14

Sentinel primary sources

Reviewed: 2026-05-14 UTC

Official homepage

• https://sentinel.co/
  • Best concise source for Sentinel’s current positioning.
  • Used to confirm that Sentinel now markets itself as “The Layer 1 for P2P Bandwidth,” not only as a dVPN protocol.
  • Important because the homepage explicitly spans privacy access, bandwidth monetization, AI/data-scraping flows, multi-app distribution, and SDK-based app building.

Documentation hub

• https://docs.sentinel.co/
  • Best broad index of the project’s current documentation surface.
  • Used to confirm that Sentinel presents itself as decentralized bandwidth-market infrastructure with validators, nodes, frontends, and development teams rather than one app.

Whitepaper landing page

• https://docs.sentinel.co/get-started/whitepaper
  • Best source for the canonical whitepaper reference.
  • Used to confirm the official PDF location and the whitepaper’s own topic coverage: vision, VPN-industry decentralization, Cosmos-based blockchain architecture, P2P architecture, coin utility, hardware integration, and organizational structure.

Whitepaper PDF

• https://docs.sentinel.co/assets/files/whitepaper-513665f81a5d6c4b462e111926d26f57.pdf
  • Saved locally as sentinel-whitepaper.pdf.
  • Best canonical long-form primary document for Sentinel’s original protocol architecture and framing.

dVPN apps page

• https://docs.sentinel.co/get-started/apps
  • Best source for the project’s network of independent apps claim.
  • Used to confirm that Sentinel explicitly treats dVPN products like Shield, Norse Labs, Independent dVPN, Ryn VPN, Meile, VALT, encryptSIM, and Telegram-bot clients as separate applications built atop the same underlying protocol.

Node earnings / subscription-plan revenue

• https://docs.sentinel.co/dvpn-nodes/earnings
  • Best source for how node monetization currently works.
  • Used to confirm that white-label apps can share or create onchain subscription plans, that nodes are paid hourly from plan allocations, and that pricing is meant to balance demand against operator-set bandwidth costs.
  • Especially useful because it makes the revenue layer explicit rather than hiding it behind consumer-app branding.

Node health check overview

• https://docs.sentinel.co/dvpn-nodes/health-check/overview
  • Best source for admission and compliance logic around node revenue eligibility.
  • Used to confirm daily health checks, price ceilings, connectivity requirements, and subnet / ASN / city distribution rules that shape which nodes can enter subscription plans.
  • Important because it surfaces practical control over node inclusion and decentralization policy.

Plan Manager docs

• https://docs.sentinel.co/sdk/plan-manager
  • Best source for the commerce/operator layer built above the base protocol.
  • Used to confirm that Plan Manager is a community-built full-stack studio for creating plans, curating node pools, managing subscribers, issuing fee grants, and exposing HTTP/CLI control for plan operations.
  • Important because it shows how Sentinel becomes an actual bandwidth business stack rather than only a chain plus node network.

Main takeaways from this pass

• Sentinel is worth cataloging separately because it is not only a privacy network or a dVPN brand; it is a bandwidth-market stack with explicit app/operator/node/compliance layers.
• The most reusable analytical split is between node-supplied bandwidth, app-owned user relationships, chain-native subscription commerce, and node-admission/revenue policy.
• The node health-check and plan-manager materials are especially valuable because they show where practical control accumulates: who curates supply, who abstracts gas, who bundles nodes into plans, and who decides what node quality counts as monetizable.
• Sentinel is also increasingly useful as a comparison point between privacy transport and AI/data-access infrastructure, because the same underlying bandwidth layer is now being marketed to both dVPN and public-web retrieval workflows.