Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Problem: Anyone can sync with TSN nodes

Abierto
  • ¿Algo no está bien?
#470 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Error
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
go
Área
authorization, distributed-systems, networking

Línea de trabajo

The issue names no files, tests, or entry points. Start by tracing how TSN/Kwil nodes authorize peer access and synchronization, then confirm the chosen VPN or validator-only approach with maintainers. Done means unauthorized peers cannot populate a read-only node with chain data and the operational guidance reflects the decision.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

What is happening:
  • before node operators, our p2p port was closed.
  • with node operators, we need to give nodes p2p access
  • currently, anyone with p2p access can say, "I want to be a read-only node of TSN chain" even if they are not validators
  • this means, when they connect, their DB is filled with all current data, without needing an approval
Solutions:
  1. make VPN part of our infra, guide node operators to connect through it
  2. ask the kwil team to add an option that disallows syncing without being a validator (1 week work, Brennan said). This makes the read-only nodes not possible, correct?
  3. keep it insecure for now, relying on the obscurity that our tsn-node-operators can remain private for now, and people won't immediately know the servers, genesis file, software, etc

(@brennanjl all correct?)

I'd vote for 2, or incrementally 3, then 2. Reasons:

  • onboarding won't be blocked
  • 1 makes the infra + onboarding significantly more complex
  • 3 seems ok with Cameron's decision about priority
  • VPN would also be a temporary solution, requiring more trust in operators, etc

Originally posted by @outerlook in https://github.com/truflation/tsn/issues/457#issuecomment-2288518928

@markholdex

@outerlook let's go with 3 now until 2 is not ready. Isolate no 2 in a separate problem, please.

@brennanjl What are the limitations or negative consequences of option 2? When can you put it on your roadmap and when can we see it ready?

Lenguaje dominante
Go
Estrellas
7
Forks
3
Merge medio
11 h 53 min
PR fusionados (30 d)
13

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de trufnetwork/node

Todos los issues de trufnetwork/node

Issues similares

Más issues de Go

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.