Projetar a migração explícita entre associações
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- javascript
- Domain
- distributed-systems, security
Research direction
Read docs/protocol.md at line 72, docs/app.md at line 32, and docs/verification.md at line 152 to understand the current association and trust model. Decide whether migration should exist and define its guarantees, consent, certificates, history, and followers. Done means an approved document addresses identifier continuity and a two-association proof rejects false authorization while preserving data after interruption.
Written by the indexing model from the issue text.
Description
Contexto
A associação é imutável depois que a identidade existe; trocar hoje exige apagar os dados. Oferecer migração depende de decisão de produto e de confiança: identificadores, certificados, histórico e seguidores, sem troca silenciosa da raiz de confiança.
Escopo
- Decidir se haverá migração, em qual fase e quais garantias de continuidade
- Especificar consentimento, certificados, histórico e seguidores na nova associação
- Prototipar transição e recuperação de falha sem troca silenciosa de raiz
Critérios de aceite
- Documento aprovado descreve preservação ou mudança de identificadores e seus limites
- Prova com duas associações recusa autorização falsa e preserva dados se interrompida
Fontes
Fase: sem fase definida · Dificuldade: grande · sensível à segurança
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 1
- Avg merge
- 32m
- Merged PRs (30d)
- 17
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Varanda-org/varanda
-
área:app área:produto sem-fase tipo:decisão
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
Varanda-org/varanda#91 ·
Maintainers usually reply within 1 day
-
área:jurídico área:operações portão:1 tipo:operação
Difficulty 5/5 Over a week Newbie friendliness 20/100
Varanda-org/varanda#96 ·
Maintainers usually reply within 1 day
-
área:identidade área:produto sem-fase tipo:verificação
Difficulty 5/5 Over a week Newbie friendliness 25/100
Varanda-org/varanda#93 ·
Maintainers usually reply within 1 day
-
área:moderação área:produto sem-fase tipo:decisão
Difficulty 5/5 Over a week Newbie friendliness 35/100
Varanda-org/varanda#90 ·
Maintainers usually reply within 1 day
-
área:produto sem-fase tipo:decisão
Difficulty 5/5 Over a week Newbie friendliness 35/100
Varanda-org/varanda#89 ·
Maintainers usually reply within 1 day
All issues in Varanda-org/varanda
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
awesome-dsh-plugin/awesome-dsh-plugin#9184 ·
Maintainers usually reply within 1 day
-
CloudredirectOpen
Difficulty 1/5 Under an hour Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
NanmiCoder/dsh-agent-teams#277 ·
Maintainers usually reply within 1 day
-
[ordering-review] workshop order graph: 1 confirmed ordering problem, 3 cycles are false positivesOpen
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
githubnext/gh-aw-workshop#4943 ·
Maintainers usually reply within 1 day