Acquaintance
A one-way recognition possibility I label locally.
No usernames · local trust · cosmic scale
Trust people, groups, devices, and agents without turning them into usernames.
Abracadoo lets you create local relationship labels — the “Bob” in your app is simply what you call that trust edge. The contact can persist, fade, be revoked, or be rebuilt one consentful loop at a time.
- Local-first
- No usernames
- Human-mediated
- Open protocols
The simple model
A contact is not a username. It is a local relationship label.
Abracadoo names the relationship edge instead of pretending one master identity can carry every context. Nobody else has to call Bob “Bob.”
Path
A route that can carry a short proof, message, or trust event.
Loop
Two connected Paths that have carried a reciprocal exchange.
Relationship
A remembered Loop with scoped trust, not a permanent account.
No usernames
The name is yours. The trust is earned.
Bob may be Chuck. Alice may be your D&D club. A trusted agent may participate in a loop. Abracadoo does not need a global handle to make the relationship legible to you.
Your labels live in your universe. A label does not prove identity, grant authority, or make someone discoverable. It only helps you remember a relationship edge.
Local labelWhat you call the edge.
Scoped trustWhat this edge may do.
Revocable loopWhat can expire, renew, or be rebuilt.
Not another identity stack
Human before technical. Magical but grounded.
Not this
- Usernames as identity
- Searchable by default
- Institutional permission
- Permanent public profiles
Instead
- Local relationship labels
- Consentful trust events
- Context-specific identity
- Revocable loops
What works today
A small, useful beginning.
The current Abracadoo MVP creates local HumanKey acquaintances using Authenticator-compatible TOTP tokens. It is intentionally simple: create, share, recognize, and keep your trust material local. Labels are for your device and your memory; they are not global usernames.
The app is a lantern to return us to contact-based trust — no cloud required, no public handle required.
Try the live app →Protocol-native
From a local label to a universe of witnessed trust.
1Create a Pathlocal recognition, no username
2Exchangehuman-mediated proof
3Complete a Loopreciprocal trust event
For builders
Open enough to inspect. Warm enough to invite.
Abracadoo should be easy to explain to a neighbor and serious enough for protocol people to inspect. The work starts with HumanKey, then grows toward reciprocal loops, relationship proofs, and consent-aware trust surfaces. EphemeralTrust can become the plain-language field guide for why local labels, revocable identity, and consent-shaped trust matter.