Research

Build with SOVP

The Sovereign Validation Protocol is an open, deterministic infrastructure validation standard for the agentic web.

Quick start: verify a SOVP identity

python3 -m venv .venv
. .venv/bin/activate
pip install sovp
python3
from sovp.resolver import validate_domain
result = validate_domain("litzki-systems.com")
print(result["psi_core"], result["outcome"])
1 verified

Resources

IETF

IETF Draft

draft-litzki-sovp-04 · Experimental

[VIEW ON IETF DATATRACKER]

GITHUB

GitHub Repository

Python reference implementation

[VIEW ON GITHUB]

PYPI

PyPI Package

pip install sovp

[VIEW ON PYPI]

INTEGRATION

AgenTrust TRACE Bridge

Sign a SOVP result as an AgenTrust TRACE v0.2 Trust Record

[VIEW ON GITHUB]

Quickstart

Shell

# Install into its own virtual environment, not system-wide
python3 -m venv .venv
. .venv/bin/activate
pip install sovp

Python

# Verify a host's signed SOVP identity document against its DNS key.
# Fetches https://<host>/.well-known/sovp-identity.json, key from the TXT record _sovp.<host>
from sovp.resolver import validate_domain
result = validate_domain("litzki-systems.com")
print(result["psi_core"], result["outcome"])  # 1 verified
# outcome (reachable from validate_domain; table 3 of the draft lists further values):
#   verified, document_invalid, host_mismatch, invalid_signature, stale
# Raises SOVPResolverError if the document or the DNS key cannot be retrieved.
# CERTIFIED / NOT_CONFORMANT / INCOMPLETE come from the full scan.

Core concepts

Layer 0

Infrastructure ingress: the validation layer before agent data ingestion.

Ψ_core

Signature verification function over the RFC 8785 (JCS) canonicalized payload. Deterministic binary output.

Ed25519 Signature

Identity anchor published in DNS. Signature-verifiable, reproducible.

CERTIFIED / NOT_CONFORMANT / INCOMPLETE

Three-state verdict. Same input always produces same output.

Protocol and code

Check and read

Protocol Notice: SOVP and draft-sovereign-svtp

SVTP and SOVP: the dates

  1. SVTP submittedMay 3draft-sovereign-svtp-00, Sovereign AG
  2. IPR disclosureMay 12No. 7291 under RFC 8179
  3. SOVP publicMay 14draft-litzki-sovp
  4. Deadline endsJune 12no reply in the Datatracker
The dates from the notice, all in 2026.

Litzki Systems LLC has no affiliation with the Internet-Draft draft-sovereign-svtp-00 (“Sovereign Verification & Trust Protocol (SVTP) v1.0”), submitted to the IETF on May 3, 2026 by an entity identifying itself as Sovereign AG.

IPR disclosure 7291

Regarding the naming overlap between SVTP and SOVP (Sovereign Validation Protocol), Litzki Systems LLC submitted IPR Disclosure ID 7291 on May 12, 2026 under RFC 8179, asserting that mechanisms described in draft-sovereign-svtp-00 (specifically the Protocol Seal, Immutable Audit Chain, and Transparent Proxy Architecture) overlap with pending claims in U.S. Patent Application No. 64/005,737 (“System and Method for Infrastructure Validation and Signal-to-Noise Separation via Sovereign Gateway”, filed March 14, 2026).

Publicly accessible

The disclosure is publicly accessible at https://datatracker.ietf.org/ipr/7291/. The IETF Secretariat has notified Sovereign AG; the response period ended on June 12, 2026. No response is recorded on the Datatracker (as of October 28, 2026).

The active draft

Litzki Systems LLC exclusively develops and maintains the Sovereign Validation Protocol (SOVP). The active IETF Draft is draft-litzki-sovp, live since May 14, 2026. Any references to SVTP, draft-sovereign-svtp, or svtp-sdk as equivalent or related to SOVP are factually incorrect.

Contact: ietf@litzki-systems.com