Provar a assinatura FROST 2 de 3 compatível com o manifesto do Hypercore
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- cryptography, javascript
- Domain
- cryptography, security
Research direction
Read docs/design.md lines 84–96 and docs/protocol.md lines 13–14, then review dependency #41 to understand the identity and migration assumptions. Build a 2-of-3 FROST proof of concept for Ed25519 using the project's real formats, and assess participant failures, share renewal, and pilot migration. Done means any two shares produce a block accepted by v1 seeders and apps, one share cannot sign, and an independent cryptographic review documents whether to adopt the design or use an alternative.
Written by the indexing model from the issue text.
Description
Contexto
A chave de cada pessoa deve ser dividida em três partes com assinatura por limiar FROST (RFC 9591). A compatibilidade com o manifesto de um assinante do Hypercore, a renovação de partes e as falhas de participantes não podem ser presumidas; precisam de prova e revisão criptográfica.
Escopo
- Prova de conceito 2 de 3 sobre Ed25519 com os formatos reais do projeto
- Avaliar identificador estável, renovação de partes, migração do piloto e falhas
- Revisão criptográfica independente do desenho
Critérios de aceite
- Qualquer dupla assina um bloco aceito por semeadores e apps v1; uma parte isolada não assina
- A revisão aprova ou bloqueia a adoção com alternativa documentada
Depende de
- #41 — Fazer backup da identidade cifrado por passkey e restaurar sem criar fork
Fontes
Fase: Fase 2 — Ondas do canal · Dificuldade: grande · sensível à segurança · depende de parecer ou serviço externo
- Dominant language
- JavaScript
- Stars
- 2
- Forks
- 1
- Avg merge
- 12m
- Merged PRs (30d)
- 4
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 ·
-
área:identidade área:produto sem-fase tipo:verificação
Difficulty 5/5 Over a week Newbie friendliness 25/100
Varanda-org/varanda#93 ·
-
área:identidade área:produto sem-fase tipo:decisão
Difficulty 5/5 Over a week Newbie friendliness 25/100
Varanda-org/varanda#92 ·
-
área:moderação área:produto sem-fase tipo:decisão
Difficulty 5/5 Over a week Newbie friendliness 35/100
Varanda-org/varanda#90 ·
-
área:produto sem-fase tipo:decisão
Difficulty 5/5 Over a week Newbie friendliness 35/100
Varanda-org/varanda#89 ·
All issues in Varanda-org/varanda
Similar issues
-
bug needs triage P3
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
pbakaus/impeccable#1143 ·
Maintainers usually reply within 1 day
-
status: waiting for maintainer
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
mui/material-ui#49547 ·
Maintainers usually reply within 1 day
-
next() is called twice when the request closes after busboy fails to startPossibly taken @NgoQuocViet2001 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
[2.x] extension-manager: translation keys that changed meaning keep their old namesPossibly taken A pull request linked to this issue is open or already merged. Opentype/bug
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day