-
Notifications
You must be signed in to change notification settings - Fork 33
Issues: pokt-network/pocket
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
[Persistence] Implement proper SQL migration strategy (i.e. move SQL table schemas to .sql files)
core
Core infrastructure - protocol related
persistence
Persistence specific changes
[P2P] RainTree Redundancy Layer Implementation
core
Core infrastructure - protocol related
p2p
P2P specific changes
[Consensus] Twins: BFT Systems Made Robust
consensus
Consensus specific changes
core
Core infrastructure - protocol related
[Consensus] BLS Signature Aggregation
consensus
Consensus specific changes
core
Core infrastructure - protocol related
[Consensus] Foundation for DKG and Threshold Signatures
consensus
Consensus specific changes
core
Core infrastructure - protocol related
[Telemetry] Distributed Tracing in a V1 Node
core starter task
Good for newcomers, but aimed at core team members though still open for everyone
infra
Core infrastructure - not protocol related
telemetry
everything related to collection telemetry
tooling
tooling to support development, testing et al
[Development] Documentation for local debugging using dlv
infra
Core infrastructure - not protocol related
tooling
tooling to support development, testing et al
[Utility] Research and make sure we are handling correctly deterministic serialization
client
work needed to interface with the node (rpc, cli, etc..)
core
Core infrastructure - protocol related
[Code Structure] Follow protobuf enum best practices
code health
Nice to have code improvement
core
Core infrastructure - protocol related
[TECHDEBT] [P2P] Raintree test suite improvements: Add configurations tests for dead and partially visible nodes
core starter task
Good for newcomers, but aimed at core team members though still open for everyone
p2p
P2P specific changes
[TECHDEBT] [P2P] Should we have entropy at Raintree level?
discussion
It has a related Discussion
p2p
P2P specific changes
triage
It requires some decision-making at team level (it can't be worked on as it stands)
[Utility] Design & implement a better approach to Nice to have code improvement
core
Core infrastructure - protocol related
utility
Utility specific changes
GenericParam
/ ActorSpecificParam
code health
[Consensus] Leader Election - Productionize the sortition algorithm
consensus
Consensus specific changes
[Core] Tx Fee Business Logic - Improve State Visibility
core
Core infrastructure - protocol related
testing
Defining, adding, automating or modifying tests
tooling
tooling to support development, testing et al
[Persistence][Core][Savepoints/Rollbacks] Implement KISS SavePoints - Serialize WorldState from Persistence
consensus
Consensus specific changes
core
Core infrastructure - protocol related
persistence
Persistence specific changes
testing
Defining, adding, automating or modifying tests
utility
Utility specific changes
[Core] Define Edge Cases for Save Points and Rollbacks
consensus
Consensus specific changes
core
Core infrastructure - protocol related
persistence
Persistence specific changes
triage
It requires some decision-making at team level (it can't be worked on as it stands)
utility
Utility specific changes
[P2P][LibP2P][SPIKE] Consolidate and Refactor Node Identity
consensus
Consensus specific changes
core
Core infrastructure - protocol related
p2p
P2P specific changes
triage
It requires some decision-making at team level (it can't be worked on as it stands)
[Consensus] State Sync - Request, download and apply blocks
consensus
Consensus specific changes
core
Core infrastructure - protocol related
[Persistence] First State Hash Implementation - Followup Investigations
persistence
Persistence specific changes
[Core] Follow industry standards for Golang project folder structure
code health
Nice to have code improvement
core
Core infrastructure - protocol related
documentation
Improvements or additions to documentation
[Persistence] Refactor ReadContext and RWContext interfaces
code health
Nice to have code improvement
persistence
Persistence specific changes
[Utility] Client Side Challenges - Handling Request Types
documentation
Improvements or additions to documentation
utility
Utility specific changes
[Consensus] Common bus may be a potential attack surface and performance bottleneck
consensus
Consensus specific changes
discussion
It has a related Discussion
Previous Next
ProTip!
Add no:assignee to see everything that’s not assigned.