lhumina_code/hero_ledger
24
0
Fork 1
Code Issues 8 Pull requests Projects Releases 3 Packages 1 Wiki Activity Actions 1

Identity #20

New issue
Open
opened 2026-01-10 02:38:44 +00:00 by scott · 1 comment
scott commented 2026-01-10 02:38:44 +00:00
Member
Copy link

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
Member
Copy link

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.

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.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
development
development-static-build
development-wasm-plan-execution
main
development_rename
identity
v1.3.0
v1.2.0
v1.1.1
v1.1.0
v1.0.0
Labels
Clear labels   
urgent
No labels
urgent
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lhumina_code/hero_ledger#20
No description provided.