YOU ARE VIEWING STEP 01Waiting for an execution
NO RUN DATA YETExecute a scenario to see the exact payload here.
NO DOMAIN VALUE IN THIS STEPDomain values normally appear in the signed presentation.
ROBOT IDENTITY / AUTHENTICATION OBSERVATORYSee every message.
See every message.
Know what it proves.
Verifier A observes three Presenter candidates, selects one, and asks it to prove identity. Inspect each payload and keep protocol data separate from domain attributes. Every run is generated in isolated memory and discarded; no account, registry, or saved history is used.
ACTIVE TESTValid authenticationTARGET / Presenter B1 · PROFILE / OFF · READY
PROTOCOL RUN / 05 STEPS
Open a step. See its result and data.
Each row is one protocol step. The selected row expands immediately below—no separate inspector to hunt for.
RUN RESULTNOT RUNExecute a scenario above
CORE AUTHENTICATION DATADOMAIN EXTENSION DATA
VERIFIER A asks for identity proof.PRESENTER B returns session-bound proof.DOMAIN LOGIC decides what to do afterward.
IMPLEMENT / QUICKSTART
OPEN SDK REPOSITORY ↗Install the protocol on both sides.
The presenter and verifier use different parts of the same SDK. You do not leave the verifier without a protocol implementation.
Robot, vehicle, device, or peer
SDK / PRESENTER ROLE- Create rotating advertisements
- Keep the identity key private
- Sign the session transcript
- Attach optional domain envelopes
Robot, application, station, or peer
SDK / VERIFIER ROLE- Track discovery candidates
- Create sessions and nonces
- Load trust and replay state
- Verify proof and create the report
Add a sensor method without changing RIP core.
RIP authenticates the endpoint. A companion profile binds that verified session to a local camera, UWB, direction, acoustic, or multi-modal observation.
- 01 / REQUESTChoose a method and place a fresh profile challenge in the RIP initiation extensions.
- 02 / COMMITHave the Presenter return the challenge hash inside a RIP-signed Attribute Envelope.
- 03 / OBSERVERecord the matching physical response under a verifier-local sensor track ID.
- 04 / REPORTCompare session, nonce, method, time, signed response, and observation; report it separately from core authentication.
- 01Choose roles
Decide which endpoint presents identity and which endpoint verifies it. Mutual authentication uses both roles on both endpoints.
- 02Add identity keys
Connect the Presenter role to a software key for a PoC or to a secure key adapter for a real deployment.
- 03Choose a bearer
Map discovery and message delivery to in-memory, local WebSocket, BLE, UWB-assisted, Wi-Fi, or another adapter.
- 04Discover and select
Collect short-lived advertisements as separate candidates. Select one before creating an isolated session.
- 05Challenge and present
Verifier creates a nonce; Presenter signs the advertisement, session, challenge, and presentation as one transcript.
- 06Verify locally
Verifier checks signature, local trust, freshness, replay state, attributes, and available physical-binding evidence.
- 07Add domain data
Define an Attribute Envelope schema such as nominalPayloadKg. The core carries it without defining its business meaning.
- 08Use the report
Pass evidence to separate domain logic. Authentication itself never permits a robot action.
CURRENT ALPHAImplemented now
One-way proof, local trusted keys, expiry, replay guard, arbitrary Attribute Envelopes, and an optional physical-binding profile with a simulated optical observation.
NOT YET IMPLEMENTEDDo not assume production support
Mutual flow, real bearer and sensor adapters, issuer-proof verification, relay-resistant physical binding, certification, and production security review.