filecoin-project / filecoin-project/specs

Pubsub data format per topic

Open
#899 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
SCSS
Stars
363
Forks
164
PR merge metrics
No merged PRs in 30d

Description

The block topic has a data format for sending block headers and message cids that is not simply a cbor serialized block header. Currently there is no spec for block topic data serialization.

It is the default encoding (ordered cbor tuple encoding) of
```golang
type Payload struct {
Header block.Block
BLSMsgCids []e.Cid
SECPMsgCids []e.Cid
}
```

The message topic data is simply a signed message but that also needs to be specced

Contributor guide

No contributing guide indexed for this repository

Research direction

Begin with the block topic and the Payload tuple shown in the issue, then review how the message topic carries a signed message. Done means the block-topic serialization and message-topic signed-message format are explicitly specified, including the fields and encoding identified here.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
distributed-systems, documentation
Issue type
Documentation
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.