01 / Overview · What is the RPOW Gateway?
The RPOW Gateway demonstrates an admission protocol that provides scoped access to restricted resources using Bitcoin transactions over a Lightning node. A successful admission does not grant universal trust: it creates a narrow, time-bound lease for a specific person, network, client, and service.
The transaction acts as an accountable signal within a larger control system. Identity, policy, device state, segmentation, audit, and operator authority remain essential. The prototype asks whether access can carry an explicit cost, a defined scope, and an observable lifecycle—from admission through session end.
02 / Strategic imperative · Why build it?
A conceptual synthesis informed by research on physical constraint and power projection in digital systems, alongside technical assessments of contested operational environments. This prototype is independent research; the framing below is not an official Department of War position.
What current access models leave unresolved
What the gateway is designed to test
Criteria for an operationally useful result
03 / Questions answered · The test, in plain language
It places a policy-enforcing admission layer in front of protected resources. Access is constrained by identity, card possession, network policy, destination, and session duration. A Lightning-backed hold adds an accountable transaction to the decision, while segmentation and operator controls limit what an admitted user can reach.
The proof of concept demonstrates the full control loop: authenticate, evaluate policy, create a scoped admission, expose only the approved client and service, collect AU-6-relevant telemetry, and end or revoke the session. That proves technical feasibility in the lab—not production readiness, universal security, or formal authorization.
That is the central experiment. RPOW connects a measurable transaction to a narrow access lease and a complete operator-visible lifecycle. The result gives defenders one record that can link who entered, what they were allowed to use, what occurred, and how the session ended.
04 / Operator telemetry · Information available to cyber operators
Inside an RPOW-protected network, operators can review admission decisions, active sessions, AU-6 security events, network enforcement, and audit health—then suspend or revoke access from the same operational context.
Attempted access and RBAC network probes by origin country, with a live feed of blocked events.
Screen 02 Open ↗Authentication anomalies, privileged account activity, audit log integrity, and cross-source correlation.
Screen 03 Open ↗Operator and admission activity, network enforcement, service telemetry, and session state.
Live Kibana Canvas presentation using synthetic demonstration events only. Operational evidence remains inside the protected environment.