casper-network / casper-network/casper-node

moving the network message deserialization from raw into components

Open
#4,198 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
399
Forks
224
Avg merge
15h 44m
Merged PRs (30d)
2

Description

sending and receiving the raw data, is done by creating the juliet crate, it is built from the ground up to only support that behavior. Once it is in, we will still do the encoding/decoding inside the network component though before handing it to juliet, to preserve internal compatibility.

Changing it so that components do to the encoding/decoding is a *major* change. it has far reaching consequences for every component that does any sort of network communication. I assume that it will also require paying back up some technical debt.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reading the juliet crate and the network components responsible for sending and receiving messages. Trace where encoding and decoding currently occur and identify the affected communication paths. Done means components perform that work while preserving internal compatibility, but the issue does not name specific files or tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
distributed-systems, networking
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.