Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

feat(auth): Sign-in with Ethereum for Better Auth

Aberta
  • Algo errado?
#23 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
42/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
github, mongodb, next.js, typescript
Domínio
authentication, backend

Direção de pesquisa

Start with frontend/src/features/auth/server/auth.ts and the sign-in components under features/auth/components; first verify whether Better Auth provides a SIWE plugin and read its API. Trace how the existing email OTP flow and MongoDB adapter handle accounts and sessions, then check compatibility with the signed assertion bridge on feat/toju-agent-storage. Done means wallet linking and unlinking work, replayed or invalid SIWE messages are rejected, and proxy/session behavior remains unchanged.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

chain-integration enhancement help wanted identity tier-1

Summary

Add wallet-based sign-in (EIP-4361) alongside the existing email OTP flow, optionally pulling the user's ENS name and avatar into the profile.

Motivation

Crypto-native users expect to sign in with their wallet, and it ties account identity to the addresses used for payments and agents.

Current state in this repo

  • frontend/src/features/auth/server/auth.ts configures Better Auth with the MongoDB adapter, email-OTP and Next cookies; sign-in forms are under features/auth/components.

Proposal

  • Add a SIWE flow (nonce, message, signature verification) if Better Auth provides a plugin; otherwise implement a small custom plugin.
  • Link a wallet address to an existing account (verified by signature) rather than creating duplicate accounts.
  • Optional: show ENS name/avatar from the ENS issue's resolution helper.

Acceptance criteria

  • Nonces are single-use and expire; replayed signatures are rejected.
  • Domain, chain id and expiry in the SIWE message are validated.
  • A user can link and unlink a wallet; the proxy/session behaviour is unchanged.

Out of scope

  • Replacing email OTP.

Technical notes and risks

  • Backend identity for agent endpoints uses a different mechanism on feat/toju-agent-storage (signed assertion bridge); keep the two flows compatible.

Verify before implementing

  • Whether Better Auth currently ships a SIWE plugin and its API.

References

Part of ##1. Ground rules for all issues in this roadmap are listed there (testnet-first, no secrets in the repo, chain logic behind the registry, tests and docs with every PR).

Linguagem predominante
Python
Estrelas
2
Forks
4
Merge médio
5h 19min
PRs com merge (30d)
11

Preparar o ambiente

  • Inclui um Dockerfile ou arquivo Docker Compose
  • Sem modelo de pull request
  • Sem guia de contribuição

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de QMeshPy/distributed-quantum

Todas as issues de QMeshPy/distributed-quantum

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.