Identity #20

New issue

Closed

opened 2026-01-10 02:38:44 +00:00 by scott · 2 comments

scott commented

2026-01-10 02:38:44 +00:00

Owner

We need an identity system, at least to link on chain public keys with Mycelium addresses, for Hero. Can do more later too.

Implementing on: https://forge.ourworld.tf/geomind_research/hero_ledger/src/branch/identity

We need an identity system, at least to link on chain public keys with Mycelium addresses, for Hero. Can do more later too. Implementing on: https://forge.ourworld.tf/geomind_research/hero_ledger/src/branch/identity

scott commented

2026-01-14 04:17:14 +00:00

Author

Owner

Identities have two parts:

Public addresses, or "hero" addresses, which link to a hero personal backend
Private addresses, or "device" addresses, which link to devices running a hero app connected with that backend

For the initial implementation, public addresses are public to everyone, and private addresses are visible only via an authenticated call.

However, we can go a step further link the logic for public addresses with circles, so that even the public address isn't visible unless there is a shared circle. This would make lookups much more expensive though, because we would need to check all circles for shared membership.

Identities have two parts: 1. Public addresses, or "hero" addresses, which link to a hero personal backend 2. Private addresses, or "device" addresses, which link to devices running a hero app connected with that backend For the initial implementation, public addresses are public to everyone, and private addresses are visible only via an authenticated call. However, we can go a step further link the logic for public addresses with circles, so that even the public address isn't visible unless there is a shared circle. This would make lookups much more expensive though, because we would need to check all circles for shared membership.