Skip to content

Conversation

@unnawut
Copy link
Collaborator

@unnawut unnawut commented Aug 13, 2025

πŸ—’οΈ Description

Introducing the 1st draft of the networking specs for pqdevnet-0. Basically a trimmed down version of phase0 networking.

πŸ”— Related Issues or PRs

N/A

βœ… Checklist

  • Ran tox checks to avoid unnecessary CI fails:
    uvx --with=tox-uv tox
  • Considered adding appropriate tests for the changes.
  • Considered updating the online docs in the ./docs/ directory.

@unnawut unnawut requested a review from fselmo August 13, 2025 11:37
@unnawut unnawut self-assigned this Aug 13, 2025
@unnawut
Copy link
Collaborator Author

unnawut commented Aug 13, 2025

@fselmo Appreciate if you could guide where best to keep plaintext specs like this one

@unnawut unnawut marked this pull request as draft August 13, 2025 11:37
@fselmo
Copy link
Contributor

fselmo commented Aug 13, 2025

@fselmo Appreciate if you could guide where best to keep plaintext specs like this one

Perhaps something like (docs/client/networking.md, docs/client/validator.md) from the main repo directory for now - and docs/ can have a similar structure to the spec structure for easier reference.

cc: @tcoratger, did you have something in mind for docs organization?

## Setup

- Transport: QUIC on IPv4
- Encryption and identification: [Libp2p-noise](https://github.com/libp2p/specs/tree/master/noise) with `secp256k1` identities
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

QUIC already integrates TLS, so maybe we don't have to bother with Noise?

@tcoratger
Copy link
Collaborator

Perhaps something like (docs/client/networking.md, docs/client/validator.md) from the main repo directory for now - and docs/ can have a similar structure to the spec structure for easier reference.

@fselmo Yep this structure looks good to me :)

@unnawut unnawut mentioned this pull request Aug 13, 2025
3 tasks
@unnawut
Copy link
Collaborator Author

unnawut commented Aug 13, 2025

Closing in favor of #8. Will reopen this PR when there's more clarity around the specs format.

@unnawut unnawut closed this Aug 13, 2025
@unnawut unnawut deleted the networking branch October 7, 2025 08:06
@unnawut unnawut added the specs Scope: Changes to the specifications label Oct 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

specs Scope: Changes to the specifications

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants