Skip to content
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

[TECHDEBT] [P2P] Complete P2P Module #275

Closed
7 tasks
deblasis opened this issue Oct 3, 2022 · 8 comments
Closed
7 tasks

[TECHDEBT] [P2P] Complete P2P Module #275

deblasis opened this issue Oct 3, 2022 · 8 comments
Assignees
Labels
p2p P2P specific changes

Comments

@deblasis
Copy link
Contributor

deblasis commented Oct 3, 2022

Objective

Tend to this TODO:

// TODO(team): This is a a temporary parallel to the real `p2p` module.
// It should be removed once the real `p2p` module is ready but is meant
// to be a "real" replacement for now.

We need to identify the definition of "ready" within the current milestone and update below accordingly

Origin Document

[ Why? Issue justification and/or link to another document]

Goals

  • _REPLACE_ME: List of things that are high level ideas or goals driving the task
  • ...

Deliverable

  • _REPLACE_ME: List of things that are concrete deliverables
  • ...

Non-goals / Non-deliverables

  • _REPLACE_ME: List of things that are out of scope
  • ...

General issue deliverables

  • Update the appropriate CHANGELOG
  • Update any relevant READMEs (local and/or global)
  • Update any relevant global documentation & references
  • If applicable, update the source code tree explanation
  • If applicable, add or update a state, sequence or flowchart diagram using mermaid

[Optional] Testing Methodology

  • _REPLACE_ME: Make sure to update the testing methodology appropriately_
  • Task specific tests: make ...
  • All tests: make test_all
  • LocalNet: verify a LocalNet is still functioning correctly by following the instructions at docs/development/README.md

Creator: @deblasis
Co-Owners: @Olshansk

@deblasis deblasis added the p2p P2P specific changes label Oct 3, 2022
@deblasis deblasis self-assigned this Oct 3, 2022
@Olshansk
Copy link
Member

Olshansk commented Oct 4, 2022

This was an outdated comment and I believe I removed it in one of the inflight PRs.

We had a different p2p module in the past.

We're going to go with this one, but I think more importantly is creating a ticket to:

  1. Research https://libp2p.io/
  2. Summarize & present learnings to the team (plus what we should & shouldn't use from the library)
  3. If we decide to move forward with it, a ticket to integrate it.

Could you create a discussion on GH to "Investigate whether libp2p should be used as the foundational network layer" and look into that? I can mark this one as "in progress" and we can close it out once those issues & discussions are created and the TODO is removed.

@Olshansk Olshansk moved this to In Progress in V1 Dashboard Oct 4, 2022
@jessicadaugherty jessicadaugherty moved this from In Progress to Rescope / decompose in V1 Dashboard Oct 5, 2022
@deblasis
Copy link
Contributor Author

deblasis commented Oct 5, 2022

Could you create a discussion on GH to "Investigate whether libp2p should be used as the foundational network layer" and look into that? I can mark this one as "in progress" and we can close it out once those issues & discussions are created and the TODO is removed.

I have created the discussion here: #287

@jessicadaugherty
Copy link
Contributor

Thank you @deblasis! Let me know if this should turn into an issue (research spike) at any point so the work stays visible on the board.

@deblasis
Copy link
Contributor Author

deblasis commented Oct 5, 2022

@jessicadaugherty:

Thank you @deblasis! Let me know if this should turn into an issue (research spike) at any point so the work stays visible on the board.

Yeah I think it should be tracked on the board and also, I would sadistically ask for a deadline so that I can plan all my other activities (life included :)) accordingly.

"work expands so as to fill the time available for its completion."

https://en.wikipedia.org/wiki/Parkinson%27s_law

@Olshansk
Copy link
Member

Olshansk commented Oct 5, 2022

@jessicadaugherty Can you link to the libp2p research ticket here once it's ready, and we'll document the results of that work in #287.

Once the ticket is created, we can close this one out.

@Olshansk Olshansk removed the triage It requires some decision-making at team level (it can't be worked on as it stands) label Oct 5, 2022
@deblasis
Copy link
Contributor Author

deblasis commented Oct 24, 2022

@Olshansk:

@jessicadaugherty Can you link to the libp2p research ticket here once it's ready, and we'll document the results of that work in #287.

Once the ticket is created, we can close this one out.

I believe that the creation of pokt-network/pocket-network-protocol#16 and pokt-network/pocket-network-protocol#17 should close this one.

@Olshansk
Copy link
Member

Agreed. Closing per the comment above.

Repository owner moved this from Rescope to Done in V1 Dashboard Oct 24, 2022
@Olshansk
Copy link
Member

Note that this also involves some work related to the testing framework, redundancy layer, etc, but all of that work is captured in more well scoped tickets.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
p2p P2P specific changes
Projects
Status: Done
Development

No branches or pull requests

3 participants