| … | … | @@ -314,7 +314,12 @@ designed before either registry is in use would be designed against guesses. |
| 314 | 314 | |
| 315 | 315 | 1. **Where favela's registry autobase lives** — its own corestore, or a namespace in the peer's |
| 316 | 316 | existing one. Affects backup and the blast radius of a corrupt store. |
| 317 | | 2. **Who admits the first writer**, and how a second device joins. `DeviceLinker` blind-pairing is |
| 317 | 2. **Who admits the first writer**, and how a second device joins. ⛔ **There are TWO `DeviceLinker`s** |
| 318 | (measured 2026-09-05, `hyper-social/docs/FAVELA-PEER.md` §4.2): `hyper-identity`'s **v1** transfers |
| 319 | the **BIP39 mnemonic** — the package favela already depends on — and pear-git-v3's **v3** transfers |
| 320 | a device-scoped keypair plus an `attestDevice` chain. Use **v3**: a device holding the seed cannot |
| 321 | be revoked, which would make `interaction.md` §3.4.2's epoch floor meaningless. Superseded text: |
| 322 | `DeviceLinker` blind-pairing is |
| 318 | 323 | the candidate and is what #49 describes from scratch; it is not yet chosen here. |
| 319 | 324 | 3. **Scoping the ~120 call sites** — mechanical rename or genuine model change, per site. |
| 320 | 325 | 4. ~~**Whether the peer or favela-web owns the registry instance.**~~ **CLOSED (2026-09-02)** — |