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 — and, in an online world where people increasingly show up through avatars, likeness and AI stand-ins, it keeps that represented self tied to the person it belongs to, without making families feel like they are entering a protocol.
Translate behaviour. Synchronise the signal. Burn the identifiable source.
RSP is the consent and coordination layer that governs how personal data, identity and permissions move between people and products across the Love Key ecosystem. Being clear about what it refuses to do matters as much as what it does.
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.
Each part of RSP has its own page — principles, mechanics, dimensions, implementations and developer docs.
The core commitments RSP is built on.
Consent grants, identity context, presence, revocation.
The consent dimensions RSP tracks, including avatars.
Interactively secure your avatar: claim, grant, project, revoke.
Where RSP is deployed and what it governs.
Proof that coordination happened, source burned.
Install, core concepts and integration.
Tiers, credits and the burn clause.
@rsp/macro: capacity-aware search and ad auctions.
Global population pulse & resource allocation standard.
Plain-language answers for visitors.