RSP is the invisible coordination layer beneath Love Key Link, Love Key Hub and the Love Key Help Network. It synchronises consent, permissions, identity context, roles, presence and support signals without making families feel like they are entering a protocol.
Translate behaviour. Synchronise the signal. Burn the identifiable source.
The Event Token is the cryptographic receipt of the Reciprocal Status Protocol. Every time two nodes genuinely coordinate, a token is minted — and the identifiable source data is burned before the token ever exists. It records that reciprocity happened, never who, where, or how.
Within the RSP ecosystem it is the unit of trust: an unbounded, auto-minted proof that turns private, consent-based coordination into verifiable status — without surveillance, scores, or stored identity.
RSP defines how an application observes, interprets, and forgets — without surveilling, profiling, or coercing anyone.
The public experience starts with a simple promise: are my people okay? RSP sits underneath to make each handoff safer, more contextual and more respectful.
Love Key Link stays warm and human. RSP remains behind the scenes as trust and synchronisation architecture.
One profile is created with privacy-first defaults, permission preparation and future hub bridging.
Membership, contextual roles and hub boundaries prevent context collapse across family, work, community and recovery spaces.
Gentle states such as available, busy, quiet, all good or needs support sync only to permitted people.
RSP decides which trusted contacts should be notified, applies escalation rules and records a respectful support event.
When private support is not enough, routing considers category, urgency, consent and trusted helper availability.
RSP modules map directly to the Love Key data model and Help Network routing rules, while keeping protocol concepts out of the family UI.
Minimal install and links to packages and repository.
npm install @rsp-protocol/core npm install @rsp-protocol/react
Packages: @rsp-protocol/core, @rsp-protocol/react. Source: https://github.com/rsp.
import { createConsent, hasConsent, translate, aggregate,
toNodeSignal, markBurned, generateBurnReceipt } from '@rsp-protocol/core'When user behaviour is translated, synchronised, aggregated, or converted into a protocol signal, any identifiable source information should be removed, destroyed, cryptographically erased, or irreversibly decoupled as soon as it is no longer necessary — unless retention is required by law, explicit consent, safety, or legitimate accountability.
RSP is designed for any system where group coordination intersects with privacy — human, AI, or hybrid.
RSP reduces raw behaviour to 13 low-resolution visual states. Signal weights control how strongly each event contributes.
RSP NFTs are utility tokens — provenance, access, participation, and certification. Not investment products.
The Reciprocal Status Protocol is the native credential of the Respectful Synchronisation Protocol (RSP) — a cryptographic record that a validated coordination event occurred, with source identity destroyed before the token exists.
Every validated coordination event across RSP nodes produces one Event Token. It carries the signal — event type, weight, node state, a blurred timestamp — but the source identity is cryptographically destroyed at or before mint. The burn receipt hash embedded in the token proves that destruction happened. You can verify the coordination. You cannot recover the person.
Minting is automatic. Once a validation delay clears and the event commits to node state, the token is issued. Supply is unbounded: one token per validated event, across every node, forever.
In Love Key Link, each validated hub moment also writes an auditablersp_validation_events record containing the source event reference, validation reason, timestamp, burn receipt hash, and Event Token payload. That backend record is the bridge from the live family hub to this Event Token contract.
RSP credits are described here as service accounting primitives for certification, review, partner onboarding and governance work. This page is technical documentation, not a consumer sales funnel.
Credits are not cash, not fiat-redeemable and not investment products. Any activation must follow legal, financial, privacy and security review.